Difference between revisions of "EclipseLink/Development/DBWS/RoadMap"

Revision as of 14:18, 16 December 2009

DBWS Road Map

2.1

• Support optional arguments for Stored Procedures
• Support 'sparse' merge
• Validate arguments passed to Stored Procedures
• align DBWS internal metadata with JPA/JAXB metadata
  • Use 'orm.xml' and 'oxm.xml' for metadata

2.0.1

• align DBWS internal implementation with new Dynamic Persistence features
• DBWSBuilder utility auto-detect Optimistic Lock field
• Support complex PL/SQL arguments for Stored Functions
  • fix issue with JDBC metadata and overloaded Stored Functions
• Support MTOM attachments
  • generate xmime:expectedContentTypes for binary 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:

1. table: CRUD lifecycle
2. Stored Procedure: specialized queries
3. Result set: returned from SQL SELECT queries