EclipseLink/Development/DBWS

Welcome to the Development Home page for the EclipseLink Database Web Services (DBWS) component

This page displays information about the current state of DBWS development.

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'
bug 300398 - Add "get(String, Class)" method to DynamicEntity
Align DBWS metadata with JPA/JAXB metadata
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 305522 Dynamic Entities do not work with JPA 2.0 Criteria Queries
- required work for DBWS Restful Component above
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

DBWS should support batch SQL operations bug 326953 (done)
- Request to put transaction-handling SQL into the DBWSBuilder file (encompassing more than one SQL statement)
DBWS Refactor - Parsing DDL
The following use cases cannot be handled by the existing DBWSBuilder design - the key part of the proposed refactor is the use of DDL text for database artifacts (tables, procedures, types, etc.) instead of the use of the Oracle Data Dictionary views (via the modified JPub code)
- Use Cases
  1. DBWSProvider does not handle weakly-typed REF CURSORs (bug 325124)
  2. DBWSProvider does not handle strongly-typed REF CURSORs (bug 339721)
  3. DBWSProvider does not handle optional arguments for Stored Procedures (bug 234385)
  4. DBWS does not handle %ROWTYPE mix of PL/SQL types and JDBC Advanced types bug 329435
- Design Documentation
- Source Code Incubation
  - The code for the standard-alone Oracle DDL parser will be stored in a Git repository at the Eclipse Foundation

Build environment
- Plan to include DBWS feature in SDK bundle made available in p2 repository

Completed in EclipseLink2.3

EclipseLink should support complex PL/SQL arguments for Stored Functions
bug 332221 Support Stored Procs returning multiple rowsets.
- Brand new core capability. Only for those platforms (Sybase, MySQL) that support it
DBWS Server tests
- expand existing WLS server tests to run on WAS, JBoss and Glassfish
- TBD: expand test coverage - what additional tests are useful?
bug 344341 Support complex PL/SQL arguments for Stored Functions
- core EclipseLink bug 275156
bug 303333 Handle overloaded Stored Procedure/Functions as WSDL operations

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

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

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

The focus is on providing capabilities based upon the 3 types of database artifacts: