[jboss-jira] [JBoss JIRA] Updated: (JBAS-9355) EJBs contained in an EAR are not accessible to WARs in the same EAR

[Fred Bricon (JIRA)]

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

Fred Bricon updated JBAS-9355:
------------------------------

    Attachment: demo-ear.ear


Test application 

> EJBs contained in an EAR are not accessible to WARs in the same EAR
> -------------------------------------------------------------------
>
>                 Key: JBAS-9355
>                 URL: https://issues.jboss.org/browse/JBAS-9355
>             Project: JBoss Application Server
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          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
>         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