You have a point about manually registering the entityManagerFactory in a
separate bundle. However, the entire point of Blueprint or Spring is to avoid
having to use OSGI APIs directly and registering/unregistering services
through Trackers. What if I want to have the persistance unit in the same
WAB, configured in the same applcationContext or blueprint.xml? It also goes
somewhat against the Enterprise OSGI JPA spec. The Aries JPA extender for
example will look for the Meta-Persistance manifest header and automatically
export the emf or EntityManager proxy as an OSGI service. The name of the
Glassfish one as Extender may be confusing for these reasons.
--
[Message sent by forum member 'chejavara']
View Post: http://forums.java.net/node/892749