Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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 (→Backlog of work items) |
m (→Backlog of work items) |
||
| Line 7: | Line 7: | ||
** 300398 - Add "get(String, Class)" method to DynamicEntity | ** 300398 - Add "get(String, Class)" method to DynamicEntity | ||
* 275156 Support complex PL/SQL arguments for Stored Functions (requires core Foundation work) | * 275156 Support complex PL/SQL arguments for Stored Functions (requires core Foundation work) | ||
| + | ** 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 | ||
* Align DBWS internal metadata with JPA/JAXB metadata (requires JPA/JAXB work) | * Align DBWS internal metadata with JPA/JAXB metadata (requires JPA/JAXB work) | ||
** [[EclipseLink/Development/DBWS/oNmMetadata|Use 'orm.xml' and 'oxm.xml' for metadata]] | ** [[EclipseLink/Development/DBWS/oNmMetadata|Use 'orm.xml' and 'oxm.xml' for metadata]] | ||
* Support optional arguments for Stored Procedures (requires core Foundation work) | * Support optional arguments for Stored Procedures (requires core Foundation work) | ||
* 290156 Validate SOAP message arguments (must be very efficient!) | * 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" | ||
| + | * 303333 Handle overloaded Stored Procedure/Functions as WSDL operations | ||
| + | * 305522 Dynamic Entities do not work with JPA 2.0 Criteria Queries | ||
==== 2.2 ==== | ==== 2.2 ==== | ||
Revision as of 10:37, 30 July 2010
DBWS Road Map
Backlog of work items
- Support 'sparse' merge (bug280667)
- Sparse merge requirements/Phase I Refactoring for
DynamicEntity - 300398 - Add "get(String, Class)" method to DynamicEntity
- Sparse merge requirements/Phase I Refactoring for
- 275156 Support complex PL/SQL arguments for Stored Functions (requires core Foundation work)
- 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
- Align DBWS internal metadata with JPA/JAXB metadata (requires JPA/JAXB work)
- Support optional arguments for Stored Procedures (requires core Foundation work)
- 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"
- 303333 Handle overloaded Stored Procedure/Functions as WSDL operations
- 305522 Dynamic Entities do not work with JPA 2.0 Criteria Queries
2.2
- Jetty/Equinox support
- DBWS deployed as OSGi bundle in Equinox environment, on Jetty server
- Usecase fully documented on EclipseLink wiki
- Scenario incorporated into DBWS server tests
- Glassfish support
- Complete testing of including OSGi bundle in Glassfish environment
- Sparse Merge support complete
- Documented in user guide
- Supported in nightly JUnit test environment
- DBWS Server tests
- DBWS Server tests need to be automated and run against WLS, WAS, Glassfish and JBoss containers on regular basis.
- Return query result as rowset
- JPub acquires the result set metadata using OracleResultSetMetaData.
- Expectation is that DBWS provides similar level of support.
- AQ Web Services
- Investigation/test to confirm current level of support
- Usecase and set-up criteria documented in user guide
- Distributed transactional support via WS-AT
- Investigation/test to confirm current level of support
- Usecase and set-up criteria documented in user guide
- DB-RS
- Proposal for how DB-RS could provide a RESTful WS solution
- 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
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