[
https://issues.jboss.org/browse/JBAS-8563?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on JBAS-8563:
------------------------------------
JBCTS-1076 mentions a CTS issue. It appears that we are being too lazy about creating the
underlying (Hibernate persistence provider) Entity Manager that represents the XPC. The
CTS tests for this and I think they are right in doing so (to avoid EE behaviour
differences between vendors).
I took a look at it over the weekend and it looks like I might need a switchboard change
or a "behind the scenes" change perhaps (looks like I need to hack into the
StatefulContainer.invokePostActivate activity which in AS 6.0, eagerly helps to insert the
underlying EntityManager into the SFSB instance.
In PcEncInjector.inject(), we are updating the SFSB container on the fly to have an extra
injector ExtendedPersistenceContextInjector that eagerly helps to do the insertion (or the
EntityManager into SFSB).
At this point, I know that its too early at switchboard bind time, to attempt accessing
the SFSB context (not available yet via StatefulBeanContext.currentBean). Perhaps I need
to also use StatefulContainer.invokePostActivate activity (perhaps via backdoor access to
the current container that a SFSB is being created from).
Implement persistence-context-ref resource provider
---------------------------------------------------
Key: JBAS-8563
URL:
https://issues.jboss.org/browse/JBAS-8563
Project: Legacy JBoss Application Server 6
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Integration
Reporter: Shelly McGowan
Assignee: Scott Marlow
Fix For: 6.1.0
Attachments: pcrp_as6_patch, pcrp_ejb3-core.patch2.patch,
pcrp_ejb3-core.patch3.patch
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira