[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
Mark Struberg created WELD-1113: --- Summary: Specializing beans in different bean archives is still broken Key: WELD-1113 URL: https://issues.jboss.org/browse/WELD-1113 Project: Weld Issue Type: Bug Reporter: Mark Struberg This is a follow up on WELD-912. It appears that this is still broken! I tried it first on glassfish-3.1.1. with an upgraded weld-osgi-bundle.1.1.7.Final. I get the following error reported: remote failure: Error occurred during deployment: Exception while loading the app : WELD-47 Specializing bean must extend another bean: Managed Bean [class at.ac.tuwien.tiss.core.fe.codi.TissCodiWindowContextConfig] with qualifiers [@Any @Default]. Please see server.log for more details. But my class extends the parent class: public class TissCodiWindowContextConfig extends WindowContextConfig { .. The TissCodiWindowContextConfig is in my project jar, the parent class in codi-jsf.jar, both in my WEB-INF/lib folders of my webapp. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
[ https://issues.jboss.org/browse/WELD-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12686492#comment-12686492 ] Ales Justin commented on WELD-1113: --- @Mark: can you provide an Arquillian test for this? > Specializing beans in different bean archives is still broken > - > > Key: WELD-1113 > URL: https://issues.jboss.org/browse/WELD-1113 > Project: Weld > Issue Type: Bug >Reporter: Mark Struberg > > This is a follow up on WELD-912. > It appears that this is still broken! > I tried it first on glassfish-3.1.1. with an upgraded > weld-osgi-bundle.1.1.7.Final. > I get the following error reported: > remote failure: Error occurred during deployment: Exception while loading the > app : WELD-47 Specializing bean must extend another bean: Managed Bean > [class at.ac.tuwien.tiss.core.fe.codi.TissCodiWindowContextConfig] with > qualifiers [@Any @Default]. Please see server.log for more details. > But my class extends the parent class: > public class TissCodiWindowContextConfig extends WindowContextConfig { .. > The TissCodiWindowContextConfig is in my project jar, the parent class in > codi-jsf.jar, both in my WEB-INF/lib folders of my webapp. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
[ https://issues.jboss.org/browse/WELD-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin reassigned WELD-1113: - Assignee: Marko Lukša > Specializing beans in different bean archives is still broken > - > > Key: WELD-1113 > URL: https://issues.jboss.org/browse/WELD-1113 > Project: Weld > Issue Type: Bug >Reporter: Mark Struberg >Assignee: Marko Lukša > > This is a follow up on WELD-912. > It appears that this is still broken! > I tried it first on glassfish-3.1.1. with an upgraded > weld-osgi-bundle.1.1.7.Final. > I get the following error reported: > remote failure: Error occurred during deployment: Exception while loading the > app : WELD-47 Specializing bean must extend another bean: Managed Bean > [class at.ac.tuwien.tiss.core.fe.codi.TissCodiWindowContextConfig] with > qualifiers [@Any @Default]. Please see server.log for more details. > But my class extends the parent class: > public class TissCodiWindowContextConfig extends WindowContextConfig { .. > The TissCodiWindowContextConfig is in my project jar, the parent class in > codi-jsf.jar, both in my WEB-INF/lib folders of my webapp. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
[ https://issues.jboss.org/browse/WELD-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12687011#comment-12687011 ] Marko Lukša commented on WELD-1113: --- We really need the test (or at least the war or the stack trace at the very minimum). I played around with this yesterday, but couldn't reproduce it. The same error is thrown in 4 places I think, so even the stacktrace would really help. > Specializing beans in different bean archives is still broken > - > > Key: WELD-1113 > URL: https://issues.jboss.org/browse/WELD-1113 > Project: Weld > Issue Type: Bug >Reporter: Mark Struberg >Assignee: Marko Lukša > > This is a follow up on WELD-912. > It appears that this is still broken! > I tried it first on glassfish-3.1.1. with an upgraded > weld-osgi-bundle.1.1.7.Final. > I get the following error reported: > remote failure: Error occurred during deployment: Exception while loading the > app : WELD-47 Specializing bean must extend another bean: Managed Bean > [class at.ac.tuwien.tiss.core.fe.codi.TissCodiWindowContextConfig] with > qualifiers [@Any @Default]. Please see server.log for more details. > But my class extends the parent class: > public class TissCodiWindowContextConfig extends WindowContextConfig { .. > The TissCodiWindowContextConfig is in my project jar, the parent class in > codi-jsf.jar, both in my WEB-INF/lib folders of my webapp. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
[ https://issues.jboss.org/browse/WELD-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12687015#comment-12687015 ] Mark Struberg commented on WELD-1113: - will try to reproduce it later today, currently in another project. > Specializing beans in different bean archives is still broken > - > > Key: WELD-1113 > URL: https://issues.jboss.org/browse/WELD-1113 > Project: Weld > Issue Type: Bug >Reporter: Mark Struberg >Assignee: Marko Lukša > > This is a follow up on WELD-912. > It appears that this is still broken! > I tried it first on glassfish-3.1.1. with an upgraded > weld-osgi-bundle.1.1.7.Final. > I get the following error reported: > remote failure: Error occurred during deployment: Exception while loading the > app : WELD-47 Specializing bean must extend another bean: Managed Bean > [class at.ac.tuwien.tiss.core.fe.codi.TissCodiWindowContextConfig] with > qualifiers [@Any @Default]. Please see server.log for more details. > But my class extends the parent class: > public class TissCodiWindowContextConfig extends WindowContextConfig { .. > The TissCodiWindowContextConfig is in my project jar, the parent class in > codi-jsf.jar, both in my WEB-INF/lib folders of my webapp. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
Ales Justin commented on WELD-1113 Specializing beans in different bean archives is still broken Is this still an issue, with our latest BeansClosure fix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
Mark Struberg commented on WELD-1113 Specializing beans in different bean archives is still broken Hi! I hope to be able to give it a try in the next month. Needs just some tweaking to get our app running on jbossas as we use openjpa, quartz, etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
Armin Schaberl commented on WELD-1113 Specializing beans in different bean archives is still broken hi, we have the same problem in our applications on JBoss 7.1.3.Final (Weld 1.1.9.Final). the stack trace is: {25.03.2013 11:24:37,109 ERROR [ org.jboss.msc.service.fail] ([MSC service thread 1]) MSC1: Failed to start service jboss.deployment.unit."myapp1.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."myapp1.war".WeldService: org.jboss.weld.exceptions.DefinitionException: WELD-47 Specializing bean must extend another bean: Managed Bean [class a.b.c.myapp1.beans.Preferences] with qualifiers [@Any @Default] at org.jboss.as.weld.services.WeldService.start(WeldService.java:83) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-47 Specializing bean must extend another bean: Managed Bean [class a.b.c.myapp1.beans.Preferences] with qualifiers [@Any @Default] at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:459) at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:125) at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:174) at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:325) at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:116) at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:217) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:358) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) ... 5 more it mostly occurs on server (re-)starts. in many cases this goes hand in hand with an second exception of an other deployment: {25.03.2013 08:34:11,499 ERROR [ org.jboss.msc.service.fail] ([MSC service thread 1]) MSC1: Failed to start service jboss.deployment.unit."myapp2.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."myapp2.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name preferences resolves to beans [Managed Bean [class a.b.c.myapp2.bean.Myapp2Preferences] with qualifiers [@Any @Default @Named], Managed Bean [class a.b.c.mylib.DefaultPreferences] with qualifiers [@Any @Default @Named]] at org.jboss.as.weld.services.WeldService.start(WeldService.java:83) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name preferences resolves to beans [Managed Bean [class a.b.c.myapp2.bean.Myapp2Preferences] with qualifiers [@Any @Default @Named], Managed Bean [class a.b.c.mylib.DefaultPreferences] with qualifiers [@Any @Default @Named]] at org.jboss.weld.bootstrap.Validator.validateBeanNames(Validator.java:476) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:373) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:380) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83) at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) ... 5 more both applications are using the same library (=bean archive) in their /WEB-INF/lib ! the bean archive contains an @javax.inject.Named("preferences") @javax.enterprise.context.SessionScoped class DefaultPreferences and the applications which are using this library provide their own @Specializes Preferences c
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
Armin Schaberl updated WELD-1113 Specializing beans in different bean archives is still broken here are the three test projects. i found out, that the problem can reliably be reproduced by deploying/publishing the two webapps at the same time! if the applications were deployed separately everything works fine. Change By: Armin Schaberl (26/Mar/13 6:56 AM) Attachment: weld.1113.zip Attachment: publish.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
Jozef Hartinger commented on WELD-1113 Specializing beans in different bean archives is still broken Would you be able to verify this on Weld 2.0? The easiest way to use Weld is to use the weld 2 subsystem from here https://github.com/weld/as7-weld-subsystem/tree/2.0.0.Beta6 and run the installer against JBoss EAP 6.1 Alpha (available from jboss.org). Note that you cannot use JBoss AS 7.1.x for this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
Marko Lukša commented on WELD-1113 Specializing beans in different bean archives is still broken Armin, I was able to reproduce your "WELD-001414 Bean name is ambiguous" problem with Weld 1.1.9 immediately. I wasn't able to reproduce it with Weld 1.1.11, though. I tried it at least 10 times, so I guess this is fixed. I also wasn't able to reproduce the problem with Weld 2.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
Armin Schaberl commented on WELD-1113 Specializing beans in different bean archives is still broken i upgraded the weld-core module of my jboss as to 1.1.11 and wasn't able to reproduce the bug too. it really seems to be fixed by this version! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken
Jozef Hartinger resolved WELD-1113 as Out of Date Specializing beans in different bean archives is still broken This has been fixed. Feel free to reopen if you come up with a working reproducer. Change By: Jozef Hartinger (14/May/13 6:40 AM) Status: Open Resolved Resolution: Out of Date This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues