Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] JPA-RS Reorganization

The same changes are now in our 2.4 stream.

On 11/10/2012 8:58 AM, Tom Ware wrote:
The suggested changes have been checked in to trunk.  When running JPA-RS from
trunk, you now need the dbws functionality on the server.  For GlassFish that
means including the dbws bundle in GlassFish's modules directory.  On WebLogic,
since the full EclipseLink jar is used, there is no change.


On 04/10/2012 3:21 PM, Tom Ware wrote:
Hi All,

   I am considering reorganizing where our JPA-RS classes are found.

   Currently JPA-RS is shipped as a web-fragment that contains 3 classes that
enable the RS facade and a larger number of classes that provide the core
functionality.  Users deploy that web-fragment in their WAR/EAR to get the
JPA-RS functionality.

   I propose moving all the classes that provide core functionality into our
org.eclipse.persistence.dbws bundle and leaving only the 3 classes that enable
the RS facade in the web fragment.

   Moving the core JPA-RS classes into a component that is part of the server
will make it easier to extend the functionality for other Services that want to
use the functionality they provide without duplication of code.

   The DBWS bundle already provides some services that are similar to what
JPA-RS provides (a direct XML-Relational translation).  Additionally, it either
already has, or is planning to add the many of the dependencies JPA-RS requires.

Please reply to this thread if you have concerns,

Back to the top