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

[jaikiran pai (JIRA)]

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

jaikiran pai commented on JBAS-9355:
------------------------------------

IRC discussion for reference:

{quote}
(06:56:39  IST) dmlloyd: EE.8.3.2
(06:57:00  IST) 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.
dmison_a` dmlloyd 
(06:58:09  IST) Jaikiran: dmlloyd: indeed!
(06:58:16  IST) Jaikiran: i wasn't aware that wasn't portable
(06:58:24  IST) Jaikiran: but would be really useful to enable that in AS&
(06:58:26  IST) Jaikiran: AS7
(06:58:33  IST) Jaikiran: assuming there's no technical issue
(06:58:34  IST) dmlloyd: well if you weren't aware I imagine most of our users aren't either
(06:58:41  IST) dmlloyd: so perhaps it should be a configurable default
(06:59:23  IST) Jaikiran: from what i have seen, users (and even maven?) just creates the top level ejb jar and expects the classes in ejb deployment to be visible in web
(06:59:29  IST) fbricon: last time I checked, my sample project ran on glassfish 3.x
(06:59:50  IST) hardy [~hardy at 81-235-238-123-no92.tbcn.telia.com] entered the room.
(07:00:02  IST) dmlloyd: Jaikiran: you mean, in an EAR right?
dmison_a` dmlloyd 
(07:00:07  IST) Jaikiran: dmlloyd: yes
(07:00:18  IST) Jaikiran: both war in EJB jar in the .ear
(07:00:46  IST) fbricon: dmlloyd: Jaikiran: ^that's my setup
(07:00:58  IST) dmlloyd: sounds like a config param for the EE subsystem: <isolate-ear-contents value="true"/>
(07:01:12  IST) Jaikiran: that "sounds" different
(07:01:18  IST) dmlloyd: can one of you guys open a JIRA for that?  assign it to CR1 or something?
(07:01:27  IST) Jaikiran: given our usage of ear isolation in previous AS version
(07:01:39  IST) dmlloyd: I think the more strict behavior should be the default though.  That will encourage people to move towards better spec compliance in their deployments
(07:01:50  IST) fbricon: dmlloyd: ok I can create the issue and attach my sample project
(07:01:53  IST) Jaikiran: basically, isolate-ear in previous releases meant that each ear would have a separate cl and wouldn't see each other
(07:02:03  IST) Jaikiran: so it might be better to use a different term for this attribute
(07:02:06  IST) dmlloyd: true, we may want to choose better wording
(07:02:09  IST) Jaikiran: yeah
(07:02:14  IST) Jaikiran: but yes, a JIRA would be a starting point
(07:02:30  IST) Jaikiran: fbricon: yes, please do attach a app for easy testing
{quote}


> 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
>            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