Community
Participate
Working Groups
On the EclipseLink platform we need to add support for the NamedStoredProcedureQuery and NamedStoreProcedureQueries annotations and the corresponding eclipselink-orm.xml element named-stored-procedure-query. This is supported on Entity and entity-mappings. http://wiki.eclipse.org/Using_EclipseLink_JPA_Extensions_%28ELUG%29#Using_EclipseLink_JPA_Extensions_for_Stored_Procedure_Query
Validation: 1. The name and procedureName attributes are specified. Null and empty value, like @NamedStoredProcedureQuery(name = "", procedureName = " ") or <named-stored-procedure-query name=" " procedure-name=""/>, should be reported. 2. All the given query names should be unique cross the persistence unit. 3. The query names given in the nested @NamedStoreProcedureQueries annotation should also be verified.
Moving JPA specific bugs to new JPA component in bugzilla.
Now that we have added JPA 2.1 support for named stored procedure queries (bug 392701), I think we should add support for the EclipseLink ones as well. We now support converting JPA 2.1 NamedStoredProcedureQuery java annotations to xml and also include these queries in the query namespace, thus providing validation for duplicates. So we would want this same support for the EclipseLink ones. Do you agree with this assessment, Neil? I'll set it to 3.3M6 for now
In EclipseLink 2.5 (maybe 2.4?) several annotation elements on NamedStoredProcedureQuery were deprecated: -resultSetMapping (replaced with resultSetMappings, same as JPA 2.1) -resultClass (replaced with resultClasses, same as JPA 2.1) StoredProcedureParameter deprecated: -direction (replaced with mode, same as JPA 2.1) I don't know if we still want to support the deprecated elements. Doing the conversion from Java to XML we would lose those deprecated settings if we don't add the support in the model. EclipseLink NamedStoredProcedureQuery settings beyond the JPA 2.1 spec: -boolean multipleResultSets -boolean resturnsResultSet -boolean callByIndex EclipseLink StoredProcedureParameter settings beyond the JPA 2.1 spec: -String queryParameter -boolean optional -int jdbcType() -String jdbcTypeName()
It was decided that this was less important now that it was implemented in the 2.1 spec.
