[jboss-jira] [JBoss JIRA] Commented: (AS7-306) EJBs contained in an EAR are not accessible to WARs in the same EAR

[jaikiran pai (JIRA)]

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

jaikiran pai commented on AS7-306:
----------------------------------

This is resolved in latest AS7 upstream https://github.com/jbossas/jboss-as/tree/89c9a215ccf8935e83c5629debcc97ede834f218

The subdeployments (by default) can see each other's classes now (just like previous versions of JBoss AS). 

If required, this behaviour can be either overridden at the EE subsystem level (i.e. applies to all deployments) or at each individual deployment unit level (via .ear/META-INF/jboss-deployment-structure.xml). The element that controls this behaviour is named "ear-subdeployments-isolated" and takes either true or false as values. By default, it's false.

See the jboss-ee.xsd and jboss-deployment-structure.xsd for more details:

jboss-ee.xsd: https://github.com/jbossas/jboss-as/blob/89c9a215ccf8935e83c5629debcc97ede834f218/ee/src/main/resources/schema/jboss-ee.xsd#L36

jboss-deployment-structure.xsd: https://github.com/jbossas/jboss-as/blob/89c9a215ccf8935e83c5629debcc97ede834f218/server/src/main/resources/schema/jboss-deployment-structure-1_0.xsd#L48




> EJBs contained in an EAR are not accessible to WARs in the same EAR
> -------------------------------------------------------------------
>
>                 Key: AS7-306
>                 URL: https://issues.jboss.org/browse/AS7-306
>             Project: Application Server 7
>          Issue Type: Enhancement
>          Components: EE, EJB
>    Affects Versions: 7.0.0.Beta2
>         Environment: Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Default locale: fr_FR, platform encoding: UTF-8
> OS name: "linux", version: "2.6.35.12-88.fc14.x86_64", arch: "amd64", family: "unix"
>            Reporter: Fred Bricon
>            Assignee: jaikiran pai
>             Fix For: 7.0.0.CR1
>
>         Attachments: demo-ear.ear
>
>
> In order to test m2eclipse-wtp, I usually use the multi-javaee5-archetype (mvn archetype:generate -DarchetypeCatalog=http://open-archetypes.googlecode.com/svn/snapshots-repository/archetype-catalog.xml) to create an EAR containing an EJB jar and a WAR referencing said EJB.
> The generated EAR deploys and runs on JBoss AS 5, 6, Glassfish 3.x but fails on deploying in JBoss AS 7 :
> {noformat} Caused by: java.lang.ClassNotFoundException: foo.bar.demo.ejb.HelloService from [Module "deployment.demo-ear.ear.demo-web-0.0.1-SNAPSHOT.war:main" from Service Module Loader]{noformat}
> It seems AS 7 strictly enforces the EE spec :
> {quote}
> (15:26:40) dmlloyd: EE.8.3.2
> (15:27:01) dmlloyd: portable applications must not depend on having or not having access to these classes or resources: The content of any EJB jar files included in the same ear file.
> {quote}
> I guess it would be practical if EJBs inside an EAR were still available to WARs from the same EAR, from a migration point of view first, and it would also allow projects to be deployed using m2eclipse-wtp/jboss tools out of the box :-D

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira