[
https://issues.apache.org/jira/browse/ARIES-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164858#comment-14164858
]
Christian Schneider commented on ARIES-1247:
--------------------------------------------
Not sure what you refer to. The aries jpa extender only creates the EMF as a
service.
So it is the job of the user injection system like blueprint or DS to react on
the EMF service and instantiate the beans.
> 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)
