[ https://issues.jboss.org/browse/JBAS-9355?page=com.atlassian.jira.plugin.... ] jaikiran pai reassigned JBAS-9355: ---------------------------------- Assignee: jaikiran pai -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9355?page=com.atlassian.jira.plugin.... ] 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(a)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} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-306?page=com.atlassian.jira.plugin.sy... ] jaikiran pai commented on AS7-306: ---------------------------------- This is resolved in latest AS7 upstream https://github.com/jbossas/jboss-as/tree/89c9a215ccf8935e83c5629debcc97ed... 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/89c9a215ccf8935e83c5629debcc97ed... jboss-deployment-structure.xsd: https://github.com/jbossas/jboss-as/blob/89c9a215ccf8935e83c5629debcc97ed... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira