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 2: | Line 2: | ||
=== DBWS Road Map === | === DBWS Road Map === | ||
==== Backlog of work items ==== | ==== Backlog of work items ==== | ||
| − | [http://tinyurl.com/29kjwg2 DBWS Future Bugs] | + | * [http://tinyurl.com/29kjwg2 DBWS Future Bugs] |
| + | * [http://tinyurl.com/22wgve3 Foundation Future/2.2 bugs] | ||
# Support [https://bugs.eclipse.org/bugs/show_bug.cgi?id=280667 'sparse' merge (bug280667)] (requires core Foundation work) | # Support [https://bugs.eclipse.org/bugs/show_bug.cgi?id=280667 'sparse' merge (bug280667)] (requires core Foundation work) | ||
#* [[EclipseLink/Development/Dynamic/RefactorPhaseIForSparseMerge|Sparse merge requirements/Phase I Refactoring for <code>DynamicEntity</code>]] | #* [[EclipseLink/Development/Dynamic/RefactorPhaseIForSparseMerge|Sparse merge requirements/Phase I Refactoring for <code>DynamicEntity</code>]] | ||
#* 300398 - Add "get(String, Class)" method to DynamicEntity | #* 300398 - Add "get(String, Class)" method to DynamicEntity | ||
| − | # 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) |
# Support additional JAX-WS implementations (GlassfishV3/Metro, JBoss, Websphere 7, etc.) | # Support additional JAX-WS implementations (GlassfishV3/Metro, JBoss, Websphere 7, etc.) | ||
# align DBWS internal metadata with JPA/JAXB metadata (requires JPA/JAXB work) | # align DBWS internal metadata with JPA/JAXB metadata (requires JPA/JAXB work) | ||
Revision as of 13:48, 11 June 2010
DBWS Road Map
Backlog of work items
- Support 'sparse' merge (bug280667) (requires core Foundation work)
- 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)
- 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)
- Validate SOAP message arguments (must be very efficient!)
2.2
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