On 19/4/2010 4:59 AM, Glyn Normington wrote:
This may be a reasonable requirement although part of me wonders if it would encourage people not to embrace OSGi properly. Also, keeping the JPA and web stuff in separate bundles would seem to be a better design, easier to test, and available essentially for free.
I agree. In a "native" OSGi web app using JPA there should be a
separate
Persistence bundle containing all the JPA classes and artifacts. The
support I'm proposing would be to enable the use of non-OSGi WARs that
contained JPA persistence units.
We're currently in a transition period for both OSGi EE runtime and
tooling. There was a session at EclipseCon by Tim DeBoer on how to
configure a WTP Dynamic Web project as a PDE project. The principal
issue being the location of the Manifest. Turns out PDE is being
enhanced in Helios to more easily support the use of WTP to build Web
Apps for OSGi which is great. Tim has also spoken to me about
configuring the location of the JPA persistence.xml file to support the
inclusion of a JPA persistence unit in a Dynamic Web Project (and he's
filed bug 309030[1] against Dali to pursue this). I assume he's
looking for this functionality to build apps for Aries/WebSphere. :-)
Plus if we produce integrated support for JPA in WAB, we would need to be careful not to bake in restrictions that would make it seem pretty limited as JPA outside WABs evolves.
Absolutely.
It's certainly not in plan.
That's why I brought it up. :-)
Shaun
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=309030
Regards,
Glyn
--
Shaun Smith | Principal
Product Manager
Phone: +19055023094
Oracle Server Technologies, Oracle TopLink
ORACLE Canada | 110 Matheson Boulevard West, Suite 100, Mississauga,
Ontario | L5R 3P4
Oracle is committed to
developing practices and products that help protect the environment
|