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

Revision as of 14:22, 4 January 2011

DBWS Road Map

2.3 (committed)

Items 'above the line' are under development or potential development items for this release. Items below the line have been completed for this release

• Database web service call-out utility
  • New feature to allow code running on a database (eg. in PL/SQL module) to invoke a JAX-WS service. The input to the process is the WSDL for the Web service, along with any additional information necessary to locate and invoke the service (hostname, port, etc.)
• DBWS should support batch SQL operations bug 326953
  • Request to put transaction-handling SQL into the DBWSBuilder file (encompassing more than one SQL statement)
• DBWS Server tests
  • expand existing WLS server tests to run on WAS, JBoss and Glassfish
  • TBD: expand test coverage - what additional tests are useful?
• 329435 - DBWS does not handle %ROWTYPE mix of PL/SQL types and JDBC Advanced types
• Eclipse IDE based integration for the DBWS tooling
  • Need to provide an API that gives us the capability to specify where to find the driver class files
• Build environment
  • Plan to include DBWS feature in SDK bundle made available in p2 repository

Completed in EclipseLink2.3

• .

Backlog of work items

These items are not currently targetted for a specific release. Future Bugs

• AQ Web Services bug 322950)
  • Investigate how to support; add usecase to DBWS section of User Guide
  • Highlighted as lower priority
• Distributed transactional support via WS-AT
  • Q1: Is WS-AT policy even supported for Dynamic JAX-WS Endpoints?
  • Q2: If Q1 == true, what role does DBWS play? Adding the policy annotation is done completely through JDev 'Policy Inspector'
• DBWSProvider does not handle package REF CURSOR bug 325124
  • DBWS for PL/SQL procedure with out ref cursor parameter fails at runtime
• DBRS
  • Look at role of DBWS in RESTful web applications
• bug 300398 - Add "get(String, Class)" method to DynamicEntity
• bug 275156 Support complex PL/SQL arguments for Stored Functions
  • 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
  • requires core Foundation work
• Align DBWS internal metadata with JPA/JAXB metadata (requires JPA/JAXB work)
  • Use 'orm.xml' and 'oxm.xml' for metadata
• bug 234385 Support optional arguments for Stored Procedures (requires core Foundation work)
• bug 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"
• bug 303333 Handle overloaded Stored Procedure/Functions as WSDL operations
• bug 305522 Dynamic Entities do not work with JPA 2.0 Criteria Queries
• 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
• Development tooling support through IDEs
• Manageability features for DBWS
  • Provide exposure through MBeans to show underlying SQL query, etc
• DBWS running under OSGi: test on other platforms
  • Felix
  • Glassfish's HK2

2.2

• For DBWS Custom SQL usecases, get resultSet metadata at design-time to build eclipselink-dbws-schema.xsd (Custom SQL Design-time Schema, bug 322949)
  • use ResultSetMetaData to build DbColumn's and from that, a schema
  • Feature available in EclipseLink 2.1.2
• DBWS Sparse Merge (bug 322948)
  • Sparse merge requirements
  • build on top of newly-added support for Sparse Merge for Dynamic Persistence
  • add usecase to DBWS section of User Guide
  • nightly JUnit testing
• DBWS running under OSGi (done)
  • DBWS as OSGi bundle
  • Environment: Equinox + Jetty server
  • Documented here
• DBWS cannot execute certain Stored Procedure on MySql/J 5.1.13 bug 326804
• EclipseLink2.2 bugs: OPEN
• EclipseLink2.2 bugs: RESOLVED

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:

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