[
https://issues.apache.org/jira/browse/ARIES-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163273#comment-14163273
]
Andrei Shakirin commented on ARIES-1247:
----------------------------------------
Hi Charlie,
Can you explain what is the benefit to create EntityManagerFactory for such
bundles (have the entities, persistence.xml and daos exported services), if
bundle is only in RESOLVED and not in ACTIVE state?
My problem is that in RESOLVED state bundle context is still null and all
operations used the bundle context (for example OSGi services lookup) fail.
Regards,
Andrei.
> EntityManagerFactoryManager: remove the try of creation of
> EntityManagerFactories from Bundle.RESOLVED event
> ------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-1247
> URL: https://issues.apache.org/jira/browse/ARIES-1247
> Project: Aries
> Issue Type: Improvement
> Components: JPA
> Affects Versions: jpa-container-context-1.0.3
> Reporter: Andrei Shakirin
> Assignee: Christian Schneider
> Attachments: ARIES-jpa-EntityManagerFactoryManager.patch
>
>
> EntityManagerFactoryManager:
> As it was already mentioned in ARIES-1160, I do not see any benefit for
> trying to create EntityManagerFactories on Bundle.RESOLVED event.
> On time of Bundle.RESOLVED the bundle context is still not initialized and
> trying of creation EntityManagerFactory will likely failed (Hibernate and
> EclipseLink implementations are failed by lookup of DataSource service).
> It only confuses user with a stack trace.
> The EntityManagerFactories will be created a tick later on Bundle.ACTIVE
> event by calling registerEntityManagerFactories() method.
> Patch is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
