[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1685) EMF / EM JNDI bindings no longer create subcontexts

[Matt C (JIRA)]

     [ https://jira.jboss.org/jira/browse/EJBTHREE-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt C updated EJBTHREE-1685:
-----------------------------

    Attachment: EJBTHREE-1685_fix_v2_trunk.patch


Replacement patch. (Code only. Previous patch made pom changes and it shouldn't have.)

Affects jboss-jpa-deployers and jboss-common-core.

> EMF / EM JNDI bindings no longer create subcontexts
> ---------------------------------------------------
>
>                 Key: EJBTHREE-1685
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1685
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: jpa-deployers
>    Affects Versions: AS 5.0.0.CR1
>         Environment: NOTE: Issue present in AS 5.0.0.GA (which is not in "Affects Version/s" list yet)
>            Reporter: Matt C
>            Assignee: Andrew Lee Rubinger
>         Attachments: EJBTHREE-1685_fix_v1_trunk.patch, EJBTHREE-1685_fix_v2_trunk.patch
>
>
> In JBoss AS 4.2.0.GA / 4.2.1.GA it was possible to bind EM, EMF and hibernate SessionFactory objects to a sub-context in JNDI, e.g. "persistence-units/PU1". The target path was created if it didn't exist. Binding is done here using the following persistence unit properties in persistence.xml:
>   - jboss.entity.manager.jndi.name
>   - jboss.entity.manager.factory.jndi.name
>   - hibernate.session_factory_name
> In JBoss AS 5.0.0.GA binding to a JNDI sub-context no longer works if the sub-context needs to be auto-created. Binding to a context does work in general (EJBTHREE-1526) but only when the target context exists, e.g. when binding to the root.
> Applications that require a JNDI sub-context containing it's SFs and EMFs in this manner fail to deploy in 5.0.0.GA. This issue appeared while trying to upgrade an enterprise app from 4.2.1.GA to 5.0.0.GA.
> PersistenceUnitDeployment.java seems to be the culprit.
> Method calls to NonSerializableFactory.rebind() are made but to the variant of rebind() that won't auto-create the target context if necessary. This is a change of behavior from 4.2.1.GA. Another rebind() method is available with the argument createSubcontexts = true. If this method was used instead, backwards compatibility would be restored.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira