Skip to main content

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.

Jump to: navigation, search

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

Line 4: Line 4:
 
==== Future ====
 
==== Future ====
 
[http://tinyurl.com/27tvhfv These items are not currently targetted for a specific release]
 
[http://tinyurl.com/27tvhfv These items are not currently targetted for a specific release]
* AQ Web Services [https://bugs.eclipse.org/bugs/show_bug.cgi?id=322950 bug 322950])
+
* AQ Web Services ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=322950 bug 322950])
 
** Investigate how to support; add usecase to DBWS section of User Guide
 
** Investigate how to support; add usecase to DBWS section of User Guide
 
** Highlighted as lower priority
 
** Highlighted as lower priority

Revision as of 10:22, 13 June 2011

DBWS Road Map

Future

These items are not currently targetted for a specific release

  • 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'
  • DBRS
    • Look at role of DBWS in RESTful web applications
  • bug 300398 - Add "get(String, Class)" method to DynamicEntity
  • Align DBWS internal metadata with JPA/JAXB metadata (requires JPA/JAXB 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 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

2.4


2.3

  • 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
  • bug 303333 Handle overloaded Stored Procedure/Functions as WSDL operations

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:

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

Back to the top