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
(→2.2) |
(→2.2) |
||
Line 17: | Line 17: | ||
==== 2.2 ==== | ==== 2.2 ==== | ||
− | <i>{divide items into 'above the line' and 'below the line' - items above the line require new DBWS development; items below the line are i) done or ii) being worked on in parallel}</i> | + | <i>{divide items into 'above the line' and 'below the line' - items above the line require new DBWS development; items below the line are either i) done or ii) being worked on in parallel}</i> |
* DBWS Sparse Merge | * DBWS Sparse Merge | ||
** build on-top-of newly-added support for Sparse Merge for Dynamic Persistence | ** build on-top-of newly-added support for Sparse Merge for Dynamic Persistence | ||
− | ** add to DBWS section of User Guide | + | ** add usecase to DBWS section of User Guide |
** nightly JUnit testing | ** nightly JUnit testing | ||
* Return query result as rowset | * Return query result as rowset | ||
** JPub acquires the result set metadata using OracleResultSetMetaData. | ** JPub acquires the result set metadata using OracleResultSetMetaData. | ||
** Expectation is that DBWS provides similar level of support. | ** Expectation is that DBWS provides similar level of support. | ||
− | + | * AQ Web Services | |
+ | ** Investigate how to support | ||
+ | ** add used to DBWS section of User Guide | ||
---- | ---- | ||
− | * Jetty/Equinox support | + | * Jetty/Equinox support (mostly done) |
** DBWS deployed as OSGi bundle | ** DBWS deployed as OSGi bundle | ||
** Environment: Equinox + Jetty server | ** Environment: Equinox + Jetty server | ||
** Documented [[EclipseLink/Examples/DBWS/AdvancedOSGi here]] | ** Documented [[EclipseLink/Examples/DBWS/AdvancedOSGi here]] | ||
− | ** TBD: Glassfish's Felix/HK2 | + | ** TBD: Glassfish's [http://felix.apache.org Felix]/[http://hk2.dev.java.net HK2] |
* DBWS Server tests | * DBWS Server tests | ||
− | ** DBWS | + | ** expand existing DBWS-running-on-WLS-server tests to run against WAS, JBoss and Glassfish |
− | + | ** TBD: expand test coverage | |
− | * | + | |
− | * | + | |
− | + | ||
* Distributed transactional support via WS-AT | * Distributed transactional support via WS-AT | ||
** Investigation/test to confirm current level of support | ** Investigation/test to confirm current level of support | ||
** Usecase and set-up criteria documented in user guide | ** Usecase and set-up criteria documented in user guide | ||
− | * | + | * DBRS |
** Proposal for how DB-RS could provide a RESTful WS solution | ** Proposal for how DB-RS could provide a RESTful WS solution | ||
* JPub -> EclipseLink DBWS migration strategy | * JPub -> EclipseLink DBWS migration strategy |
Revision as of 11:15, 17 August 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
{divide items into 'above the line' and 'below the line' - items above the line require new DBWS development; items below the line are either i) done or ii) being worked on in parallel}
- DBWS Sparse Merge
- build on-top-of newly-added support for Sparse Merge for Dynamic Persistence
- add usecase to DBWS section of User Guide
- nightly JUnit testing
- 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
- Investigate how to support
- add used to DBWS section of User Guide
- Jetty/Equinox support (mostly done)
- DBWS deployed as OSGi bundle
- Environment: Equinox + Jetty server
- Documented EclipseLink/Examples/DBWS/AdvancedOSGi here
- TBD: Glassfish's Felix/HK2
- DBWS Server tests
- expand existing DBWS-running-on-WLS-server tests to run against WAS, JBoss and Glassfish
- TBD: expand test coverage
- Distributed transactional support via WS-AT
- Investigation/test to confirm current level of support
- Usecase and set-up criteria documented in user guide
- DBRS
- 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