[ https://jira.jboss.org/browse/JBAS-8683?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici reopened JBAS-8683: ------------------------------------ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8683?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici updated JBAS-8683: ----------------------------------- Issue Type: Feature Request (was: Bug) Affects Version/s: (was: 6.0.0.CR1) Priority: Optional (was: Major) Setting as a feature, since this is not a bug -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8683?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on JBAS-8683: ------------------------------------- Marius, I think the spec is at least ambiguous here, and contradicts your current implementation in a few points. I think the terminus technicus 'container' is not well defined by the spec. At one point it is referring to the 'runtime container' at another point it says clearly: 11.3 "The container provides a built-in bean with bean type BeanManager" Which means (if I use the same 'only word based' interpretation strategy as you) that there is _exactly_one_ BeanManager per container. And here lies the problem! Because in another paragraph the spec says that we BeanManagers are _per_webapp_. Going back to the original problem now, we could also interpret that the terminus technicus 'container' in the spec here means the BeanManager, so _one_per_webapp_ ! Btw, having extensions detected by the BeanManager (so: per webapp) is the only scenario which makes sense, because if the extensions are only available in (and for) the EAR libs then no classes in any webapps WEB-INF/classes could be accessed and the whole extension mechanism would be simply useless for EAR projects! -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8683?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on JBAS-8683: ------------------------------------- imo your assumption is correct. Although never been released officially, Gavin clarified this in his last version of the post-1.0 spec (MR1 candidate pdf) also. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8683?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on JBAS-8683: ------------------------------------- exactly and @ApplicationScoped -> per webAPPLICATION :) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8683?page=com.atlassian.jira.plugin.sy... ] Heiko Braun updated JBAS-8683: ------------------------------ Priority: Minor (was: Optional) -- 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-8683?page=com.atlassian.jira.plugin.... ] Jozef Hartinger reopened JBAS-8683: ----------------------------------- This issue has a critical impact on Seam as any Seam project fails to deploy when bundled in an EAR. Therefore, we should consider fixing this issue for the 6.1.0 release. -- 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-8683?page=com.atlassian.jira.plugin.... ] Mark Struberg commented on JBAS-8683: ------------------------------------- oops, almost forgot about this already. I'm seriously unhappy about the @ApplicationScoped bean definition as being @EarScoped. Reason is that a bean which got created as @Alternative in a WebApp classloader will not be available to the MDB as of in your example. Mixing up those classloader hierarchy junks will give you the same bloody result as the current EE ClassLoader specification: THERE IS NO SUCH THING! There is no ClassLoader spec for EE, so we should go with the only safe bet: application == web application! E.g. webapp1 -> 1 instance; webapp2 -> 1 instance; MDBs, Quartzed tasks (all which gets loaded via the Ears standard classloader) -> 1 instance. If we don't clearly define this in the CDI spec, then the portability would be gone because this would work different in EVERY EE server. -- 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-8683?page=com.atlassian.jira.plugin.... ] Jan Groth edited comment on JBAS-8683 at 4/19/11 1:21 AM: ---------------------------------------------------------- See here for people with related issues all over Weld / Seam 3: SEAMFACES-76 SEAMFACES-114 WELD-888 WELD-889 This is a pretty serious issue. It affects more or less each non-trivial EAR-deployment, and certainly almost everyone using Seam 3 (e.g. how should one use Seam Solder / I18N / Config ... in WAR _and_ EJB-Modules?). In my opinion it's not an option to wait for JBoss 7. was (Author: asiandub): See here for people with related issues all over Weld / Seam 3: SEAMFACES-76 SEAMFACES-114 WELD-888 WELD-889 This is a pretty serious issue. It affects more or less every non-trivial EAR-deployment, and certainly almost everyone using Seam 3 (e.g. how should one use Seam Solder / I18N / Config ... in WAR _and_ EJB-Modules?). In my opinion it's not an option to wait for JBoss 7. -- 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-8683?page=com.atlassian.jira.plugin.... ] Juergen Zimmermann commented on JBAS-8683: ------------------------------------------ Marius, please take care of this issue. It's really a blocker. Do you see a realistic chance to get a 6.1 release containing this bug fix in the near future? -- 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-8683?page=com.atlassian.jira.plugin.... ] Marius Bogoevici commented on JBAS-8683: ---------------------------------------- For details on why this issue is delayed, please follow: WELD-778 -- 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-623?page=com.atlassian.jira.plugin.sy... ] Stuart Douglas resolved AS7-623. -------------------------------- Resolution: Done test case that shows this is not an issue on AS7 https://github.com/stuartwdouglas/jboss-as/commit/925eeb9c9bec0d3e97083b9... -- 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-623?page=com.atlassian.jira.plugin.sy... ] SBS JIRA Integration updated AS7-623: ------------------------------------- JBoss Forum Reference: http://community.jboss.org/message/570912#570912 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira