[jboss-jira] [JBoss JIRA] (AS7-6773) org.jboss.as.cmp dependency added only to EJB subdeployments

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/AS7-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762508#comment-12762508 ] 

RH Bugzilla Integration commented on AS7-6773:
----------------------------------------------

James Livingston <jlivings at redhat.com> made a comment on [bug 924548|https://bugzilla.redhat.com/show_bug.cgi?id=924548]

When an ejb-jar.xml defines a CMP entity bean, whose <ejb-class> refers to a class that is not located in the EJB jar, it does not work correctly.

It will fail when used because the CmpProxy class is only make available in the EJB jar's classloader, but the proxy stub is created in the same classloader as the original bean class.
                
> org.jboss.as.cmp dependency added only to EJB subdeployments
> ------------------------------------------------------------
>
>                 Key: AS7-6773
>                 URL: https://issues.jboss.org/browse/AS7-6773
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
>            Reporter: James Livingston
>            Assignee: jaikiran pai
>
> The CMP code adds a module dependency on org.jboss.as.cmp if there are any CMP beans in it (via the CMP marker).
> If the <ejb-class> refers to a class not in the EJB jar itself, such as in a library jar, this will result in the proxy being created in the EAR classloader and not being able to find JBoss' CmpProxy class.
> The solution is to add the dependency to the top-level deployment so it is available in all sub-deployments, rather than the such the ejb subdeployment.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira