June 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1115) UnserializableDependencyException with dependency on SLSB

by Marek Schmidt (JIRA)

Marek Schmidt created WELD-1115: ----------------------------------- Summary: UnserializableDependencyException with dependency on SLSB Key: WELD-1115 URL: https://issues.jboss.org/browse/WELD-1115 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 2.0.0.Alpha2 Environment: AS 7.1.1.Final with Weld 2.0.0.Alpha2 Reporter: Marek Schmidt Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha3 An application containing the following beans (among others) fails to deploy with org.jboss.weld.exceptions.UnserializableDependencyException. {code} @SessionScoped @Stateful public EjbGameBean implements Serializable { ... @Inject RandomStatelessEjb randomStatelessEjb; ... } {code} {code} @Stateless public class RandomStatelessEjb { @Inject @Random Instance<Integer> randomNumber; public int getRandom() { return randomNumber.get(); } } {code} It probably shouldn't require a @Stateless session bean to be Serializable. {noformat} JBAS014777: Services which failed to start: service jboss.deployment.unit."weld-clustering-tests.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."weld-clustering-tests.war".WeldService: org.jboss.weld.exceptions.UnserializableDependencyException: WELD-001413 The bean Session bean [class org.jboss.weld.tests.clustering.numberguess.decorator.EjbGameBean with qualifiers [@Default @Named @Any]; local interfaces are [GameLocal] declares passivating scope but has non-serializable dependency Session bean [class org.jboss.weld.tests.clustering.numberguess.decorator.RandomStatelessEjb with qualifiers [@Any @Default]; local interfaces are [RandomStatelessEjb] {noformat} -- 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

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] (WELD-1121) Passivating-scoped SFSB fails to deploy if not implementing java.io.Serializable

by Marek Schmidt (JIRA)

Marek Schmidt created WELD-1121: ----------------------------------- Summary: Passivating-scoped SFSB fails to deploy if not implementing java.io.Serializable Key: WELD-1121 URL: https://issues.jboss.org/browse/WELD-1121 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 2.0.0.Alpha2 Environment: AS7.1.1.Final + Weld 2.0.0.Alpha2 Reporter: Marek Schmidt Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha3 Deployment of the pastecode example fails with {noformat} 10:32:47,568 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."weld-pastecode.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."weld-pastecode.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-000072 Bean declaring a passivating scope must be passivation capable. Bean: Session bean [class org.jboss.weld.examples.pastecode.session.PostTracker with qualifiers [@Any @Default]; local interfaces are [PostTracker] 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$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-000072 Bean declaring a passivating scope must be passivation capable. Bean: Session bean [class org.jboss.weld.examples.pastecode.session.PostTracker with qualifiers [@Any @Default]; local interfaces are [PostTracker] at org.jboss.weld.bean.SessionBean.checkType(SessionBean.java:327) at org.jboss.weld.bean.AbstractBean.initializeAfterBeanDiscovery(AbstractBean.java:145) at org.jboss.weld.bean.AbstractClassBean.initializeAfterBeanDiscovery(AbstractClassBean.java:230) at org.jboss.weld.bean.SessionBean.initializeAfterBeanDiscovery(SessionBean.java:191) at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$5.doWork(ConcurrentBeanDeployer.java:126) at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$5.doWork(ConcurrentBeanDeployer.java:123) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_30] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_30] ... 3 more 10:32:47,786 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015870: Deploy of deployment "weld-pastecode.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"weld-pastecode.war\".WeldService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"weld-pastecode.war\".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-000072 Bean declaring a passivating scope must be passivation capable. Bean: Session bean [class org.jboss.weld.examples.pastecode.session.PostTracker with qualifiers [@Any @Default]; local interfaces are [PostTracker]"}} 10:32:47,816 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011403: Stopping Persistence Unit Service 'weld-pastecode.war#pastecodeDatabase' 10:32:47,817 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-3) HHH000227: Running hbm2ddl schema export 10:32:47,849 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-3) HHH000230: Schema export complete 10:32:47,876 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment weld-pastecode.war in 89ms 10:32:47,882 INFO [org.jboss.as.controller] (management-handler-thread - 4) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."weld-pastecode.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."weld-pastecode.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-000072 Bean declaring a passivating scope must be passivation capable. Bean: Session bean [class org.jboss.weld.examples.pastecode.session.PostTracker with qualifiers [@Any @Default]; local interfaces are [PostTracker] {noformat} The PostTracker bean is {code} @SessionScoped @Stateful // Adds passivation capabilities.... public class PostTracker { ... } {code} -- 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

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] (CDITCK-272) Revise tests for inheritance of member-level metadata for generic types

by Martin Kouba (JIRA)

Martin Kouba created CDITCK-272: ----------------------------------- Summary: Revise tests for inheritance of member-level metadata for generic types Key: CDITCK-272 URL: https://issues.jboss.org/browse/CDITCK-272 Project: CDI TCK Issue Type: Task Security Level: Public (Everyone can see) Reporter: Martin Kouba Assignee: Martin Kouba Fix For: 1.1.0.Alpha3 -- 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

12 years, 2 months

2
4
0 / 0

[JBoss JIRA] (WELD-892) Calling session-scoped components from session initialized observer goes into infinite loop

by Ales Justin (JIRA)

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WELD-892) Calling session-scoped components from session initialized observer goes into infinite loop

by Ales Justin (JIRA)

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDITCK-269) Tests for ProcessProducer*.getAnnotatedDisposedParameter()

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDITCK-269: -------------------------------------- Summary: Tests for ProcessProducer*.getAnnotatedDisposedParameter() Key: CDITCK-269 URL: https://issues.jboss.org/browse/CDITCK-269 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.1.0.Alpha1 Reporter: Jozef Hartinger Assignee: Martin Kouba Fix For: TBC Verify that there is already a test for ProcessProducerMethod.getAnnotatedDisposedParameter() and implement a test for ProcessProducerField.getAnnotatedDisposedParameter() -- 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

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] (WELD-892) Calling session-scoped components from session initialized observer goes into infinite loop

by Nicklas Karlsson (JIRA)

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WELD-1149) Fix specialization

by Jozef Hartinger (JIRA)

12 years, 2 months

1
1
0 / 0

[JBoss JIRA] (WELD-1154) Create scope like AccessScopedView of Apache CODI

by Glauber Matos (JIRA)

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WELD-1009) Bean in different wars should be allowed to have the same EL name

by Juergen Hoffmann (Created) (JIRA)

Bean in different wars should be allowed to have the same EL name ----------------------------------------------------------------- Key: WELD-1009 URL: https://issues.jboss.org/browse/WELD-1009 Project: Weld Issue Type: Feature Request Components: CDI API, Scopes & Contexts Affects Versions: 1.1.2.Final Reporter: Juergen Hoffmann Priority: Minor see https://issues.jboss.org/browse/CDI-188 naming of beans which are annotated with @Named and not being provided with a Name Value although packaged in different war files, hence utilizing on war class level isolation, the naming context is started within the ear file. I have attached a simple test application which demonstrates the issue. -- 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

12 years, 2 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues June 2012