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.
EclipseLink/Development/DBWS/RoadMap
DBWS Road Map
Future
- Support 9https://bugs.eclipse.org/bugs/show_bug.cgi?id=280667 'sparse' merge (bug280667)] (requires core Foundation work)
- Sparse merge requirements
- currently, an Update operation (part of CRUD lifecycle) requires 'theInstance' to be fully specified in the SOAPMessage; it would be useful to support an update where - excluding PK fields - only the changed elements are specified
- Support complex PL/SQL arguments for Stored Functions (requires core Foundation work)
- Support additional JAX-WS implementations (GlassfishV3/Metro, JBoss, Websphere 7, etc.)
- align DBWS internal metadata with JPA/JAXB metadata (requires JPA/JAXB work)
- Support optional arguments for Stored Procedures (requires core Foundation work)
2.1
- Validate SOAP message elements passed to DBWS Web service
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