Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Development/DBWS/RoadMap"
< EclipseLink | Development | DBWS
m (→DBWS Road Map) |
m (→DBWS Road Map) |
||
Line 4: | Line 4: | ||
==== 2.2 ==== | ==== 2.2 ==== | ||
<i>{items 'above the line' are under development; items below the line have been completed for this release</i> | <i>{items 'above the line' are under development; items below the line have been completed for this release</i> | ||
− | |||
− | |||
− | |||
− | |||
* DBWS should support batch SQL operations [https://bugs.eclipse.org/bugs/show_bug.cgi?id=326953 bug 326953] | * DBWS should support batch SQL operations [https://bugs.eclipse.org/bugs/show_bug.cgi?id=326953 bug 326953] | ||
** New enhancement request, needs scoping out | ** New enhancement request, needs scoping out | ||
** Request to put transaction-handling SQL into the DBWSBuilder file (encompassing more than one SQL statement) | ** Request to put transaction-handling SQL into the DBWSBuilder file (encompassing more than one SQL statement) | ||
+ | * Distributed transactional support via WS-AT | ||
+ | ** Q1: Is WS-AT policy even supported for Dynamic JAX-WS Endpoints? | ||
+ | ** Q2: If Q1 == true, what role does DBWS play? Adding the policy annotation is done completely through JDev 'Policy Inspector' | ||
+ | * DBWS Server tests | ||
+ | ** expand existing WLS server tests to run on WAS, JBoss and Glassfish | ||
+ | ** TBD: expand test coverage - what additional tests are useful? | ||
+ | * AQ Web Services [https://bugs.eclipse.org/bugs/show_bug.cgi?id=322950 bug 322950]) | ||
+ | ** Investigate how to support; add usecase to DBWS section of User Guide | ||
+ | ** Highlighted as lower priority | ||
* DBRS | * DBRS | ||
** Look at role of DBWS in RESTful web applications | ** Look at role of DBWS in RESTful web applications | ||
---- | ---- | ||
+ | * For [[EclipseLink/Examples/DBWS/DBWSBasicSQL|DBWS Custom SQL usecases]], get resultSet metadata at design-time to build <tt>eclipselink-dbws-schema.xsd</tt> ([[EclipseLink/Development/DBWS/CustomSQLDesignTimeSchema|Custom SQL Design-time Schema]], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=322949 bug 322949]) | ||
+ | ** use ResultSetMetaData to build DbColumn's and from that, a schema | ||
* DBWS Sparse Merge ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=322948 bug 322948]) | * DBWS Sparse Merge ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=322948 bug 322948]) | ||
** [[EclipseLink/Development/Dynamic/RefactorPhaseIForSparseMerge#Custom FetchGroups|Sparse merge requirements]] | ** [[EclipseLink/Development/Dynamic/RefactorPhaseIForSparseMerge#Custom FetchGroups|Sparse merge requirements]] | ||
Line 23: | Line 30: | ||
** Environment: Equinox + Jetty server | ** Environment: Equinox + Jetty server | ||
** Documented [[EclipseLink/Examples/DBWS/AdvancedOSGi|here]] | ** Documented [[EclipseLink/Examples/DBWS/AdvancedOSGi|here]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
* [http://tinyurl.com/2e5j3eb EclipseLink2.2 bugs: OPEN] | * [http://tinyurl.com/2e5j3eb EclipseLink2.2 bugs: OPEN] | ||
* [http://tinyurl.com/259fhqq EclipseLink2.2 bugs: RESOLVED] | * [http://tinyurl.com/259fhqq EclipseLink2.2 bugs: RESOLVED] | ||
Line 50: | Line 46: | ||
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=303333 bug 303333] Handle overloaded Stored Procedure/Functions as WSDL operations | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=303333 bug 303333] Handle overloaded Stored Procedure/Functions as WSDL operations | ||
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=305522 bug 305522] Dynamic Entities do not work with JPA 2.0 Criteria Queries | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=305522 bug 305522] Dynamic Entities do not work with JPA 2.0 Criteria Queries | ||
+ | * JPub -> EclipseLink DBWS migration strategy | ||
+ | ** Need to document a path explaining steps a user needs to take to switch from JAX-RPC based technologies to DBWS (JAX-WS) solution | ||
+ | * Jetty/Equinox support | ||
+ | ** TBD: Glassfish's [http://felix.apache.org Felix] and [http://hk2.dev.java.net HK2] | ||
---- | ---- | ||
Revision as of 10:36, 5 October 2010
DBWS Road Map
2.2
{items 'above the line' are under development; items below the line have been completed for this release
- DBWS should support batch SQL operations bug 326953
- New enhancement request, needs scoping out
- Request to put transaction-handling SQL into the DBWSBuilder file (encompassing more than one SQL statement)
- Distributed transactional support via WS-AT
- Q1: Is WS-AT policy even supported for Dynamic JAX-WS Endpoints?
- Q2: If Q1 == true, what role does DBWS play? Adding the policy annotation is done completely through JDev 'Policy Inspector'
- DBWS Server tests
- expand existing WLS server tests to run on WAS, JBoss and Glassfish
- TBD: expand test coverage - what additional tests are useful?
- AQ Web Services bug 322950)
- Investigate how to support; add usecase to DBWS section of User Guide
- Highlighted as lower priority
- DBRS
- Look at role of DBWS in RESTful web applications
- For DBWS Custom SQL usecases, get resultSet metadata at design-time to build eclipselink-dbws-schema.xsd (Custom SQL Design-time Schema, bug 322949)
- use ResultSetMetaData to build DbColumn's and from that, a schema
- DBWS Sparse Merge (bug 322948)
- Sparse merge requirements
- build on top of newly-added support for Sparse Merge for Dynamic Persistence
- add usecase to DBWS section of User Guide
- nightly JUnit testing
- Jetty/Equinox support (done)
- DBWS deployed as OSGi bundle
- Environment: Equinox + Jetty server
- Documented here
- EclipseLink2.2 bugs: OPEN
- EclipseLink2.2 bugs: RESOLVED
Backlog of work items
- bug 300398 - Add "get(String, Class)" method to DynamicEntity
- bug 275156 Support complex PL/SQL arguments for Stored Functions
- Currently, complex schemas are generated for the arguments to named Stored Procedures that are PL/SQL collection/records or JDBC Object/Varrays; Need to extend this capability to Stored Functions
- requires core Foundation work
- Align DBWS internal metadata with JPA/JAXB metadata (requires JPA/JAXB work)
- Support optional arguments for Stored Procedures (requires core Foundation work)
- bug 290156 Validate SOAP message arguments (must be very efficient!)
- Currently perform no validation on objects passed via SOAPMessage. While complete validation is likely to be prohibitively expensive, some validation could result in errors better than "java.lang.reflect.InvocationTargetException"
- bug 303333 Handle overloaded Stored Procedure/Functions as WSDL operations
- bug 305522 Dynamic Entities do not work with JPA 2.0 Criteria Queries
- JPub -> EclipseLink DBWS migration strategy
- Need to document a path explaining steps a user needs to take to switch from JAX-RPC based technologies to DBWS (JAX-WS) solution
- Jetty/Equinox support
2.1
- accommodate internal changes for AttributeChangeTracking
- support DBWSBuilder-generated JAX-WS Provider on JRockit
- stop DBWSBuilder from truncating GROUP BY/ORDER BY clauses
- DBWSBuilder supports Eclipse WTP Dynamic Web Project structure
2.0.1
- align DBWS internal implementation with new Dynamic Persistence features
- DBWSBuilder utility auto-detect Optimistic Lock field
- fix issue with JDBC metadata and overloaded Stored Functions
- Support MTOM attachments
- fix Web service faults: contain better server-side root cause information
1.2
- For OraclePlatform, support advanced PL/SQL datatypes (records, collections, mixture of the two) as arguments to Stored Procedures
- need compatible JDBC 'shadow' types to align with PL/SQL types
- For OraclePlatform, support complex JDBC datatypes (objects, varrays, mixture of the two) as arguments to Stored Procedures
- Fix WSDL inline-schema to support above complex args
- Add support for SOAP 1.2
- Fix Delete operation (part of table-based CRUD): use only PK fields, not whole instance
- Use nillable="true" to represent database null
- DBWSBuilder utility to produce DDL for the compatible JDBC shadow types
1.1
- Deploy to JAX-WS 2.n complaint server (WebLogic 10)
- For OraclePlatform, support simple PL/SQL datatypes (PLSINTEGER, BOOLEAN, etc) as arguments to Stored Procedures
- Improve server-side exception handling
1.0
The focus is on providing capabilities based upon the 3 types of database artifacts:
- table: CRUD lifecycle
- Stored Procedure: specialized queries
- Result set: returned from SQL SELECT queries