May 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1128) Deploy failed when jar-path contains a plus-sign or an exclamation point

by Dirk Ziegenbalg (JIRA)

Dirk Ziegenbalg created WELD-1128: ------------------------------------- Summary: Deploy failed when jar-path contains a plus-sign or an exclamation point Key: WELD-1128 URL: https://issues.jboss.org/browse/WELD-1128 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.1.8.Final Environment: Windows 7 64 bit, JAVA 7u2, Weld-SE Reporter: Dirk Ziegenbalg When the jar-path contains a plus or an exclamation point then the deploy of the jar failed with a FileNotFound-Exception: D:\tmp\lauf\client N!P\bin>"C:\Program files (x86)\Java\jdk1.7.0_02\bin\java" -Xmx500M -jar startclient.jar 07.05.12 12:14 INFO WELD-000900 1.1.8 (Final) [org.jboss.weld.Version] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:14 TRACE scanning: file:/D:/tmp/lauf/client N [org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler] 07.05.12 12:14 TRACE archive: D:\tmp\lauf\client N [org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler] 07.05.12 12:14 WARN could not read entries [org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler] java.io.FileNotFoundException: D:\tmp\lauf\client N (Das System kann die angegebene Datei nicht finden) at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:214) at java.util.zip.ZipFile.<init>(ZipFile.java:144) at java.util.zip.ZipFile.<init>(ZipFile.java:158) at org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler.handleArchiveByFile(FileSystemURLHandler.java:71) at org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler.handle(FileSystemURLHandler.java:58) at org.jboss.weld.environment.se.discovery.url.URLScanner.scan(URLScanner.java:102) at org.jboss.weld.environment.se.discovery.url.WeldSEUrlDeployment.<init>(WeldSEUrlDeployment.java:39) at org.jboss.weld.environment.se.Weld.createDeployment(Weld.java:177) at org.jboss.weld.environment.se.Weld.initialize(Weld.java:127) at de.nupis.kernel.plugins.Pluginzentrale.ladePlugins(Pluginzentrale.java:216) at de.nupis.kernel.Kernel.startePluginzentrale(Kernel.java:137) at de.nupis.kernel.Start.starteClient(Start.java:205) at de.nupis.kernel.Start.starteKernel(Start.java:126) at de.nupis.kernel.Start.main(Start.java:1518) As you can see, the path is trimmed at the exclamation point. If the path contains a plus-sign it's converted to a space (an so the resulting path is invalid): D:\tmp\lauf\client N+P\bin>"C:\Program files (x86)\Java\jdk1.7.0_02\bin\java" -Xmx500M -jar startclient.jar 07.05.12 12:19 INFO WELD-000900 1.1.8 (Final) [org.jboss.weld.Version] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 DEBUG URL Type: jar [org.jboss.weld.environment.se.discovery.url.URLScanner] 07.05.12 12:19 TRACE scanning: file:/D:/tmp/lauf/client N P/bin/de_nupis_einstellungen_client.jar [org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler] 07.05.12 12:19 TRACE archive: D:\tmp\lauf\client N P\bin\de_nupis_einstellungen_client.jar [org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler] 07.05.12 12:19 WARN could not read entries [org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler] java.io.FileNotFoundException: D:\tmp\lauf\client N P\bin\de_nupis_einstellungen_client.jar (Das System kann den angegebenen Pfad nicht finden) at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:214) at java.util.zip.ZipFile.<init>(ZipFile.java:144) at java.util.zip.ZipFile.<init>(ZipFile.java:158) at org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler.handleArchiveByFile(FileSystemURLHandler.java:71) at org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler.handle(FileSystemURLHandler.java:58) at org.jboss.weld.environment.se.discovery.url.URLScanner.scan(URLScanner.java:102) at org.jboss.weld.environment.se.discovery.url.WeldSEUrlDeployment.<init>(WeldSEUrlDeployment.java:39) at org.jboss.weld.environment.se.Weld.createDeployment(Weld.java:177) at org.jboss.weld.environment.se.Weld.initialize(Weld.java:127) at de.nupis.kernel.plugins.Pluginzentrale.ladePlugins(Pluginzentrale.java:216) at de.nupis.kernel.Kernel.startePluginzentrale(Kernel.java:137) at de.nupis.kernel.Start.starteClient(Start.java:205) at de.nupis.kernel.Start.starteKernel(Start.java:126) at de.nupis.kernel.Start.main(Start.java:1518) -- 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

11 years, 9 months

4
6
0 / 0

[JBoss JIRA] (CDITCK-263) UnproxyableManagedBeanTest should test runtime exception

by Martin Kouba (JIRA)

Martin Kouba created CDITCK-263: ----------------------------------- Summary: UnproxyableManagedBeanTest should test runtime exception Key: CDITCK-263 URL: https://issues.jboss.org/browse/CDITCK-263 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Martin Kouba Assignee: Martin Kouba Fix For: 1.1.0.CR1 Fix *org.jboss.jsr299.tck.tests.implementation.simple.lifecycle.unproxyable.UnproxyableManagedBeanTest* to test runtime exception (UnproxyableResolutionException) instead of deployment time exception (DefinitionException). -- 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

11 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (WELD-964) Unsatisfied dependency exception should differentiate between "class is not in classpath", "class is in classpath but not managed bean" and "class is in classpath and managed but not like that"

by Geoffrey De Smet (JIRA)

Unsatisfied dependency exception should differentiate between "class is not in classpath", "class is in classpath but not managed bean" and "class is in classpath and managed but not like that" ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: WELD-964 URL: https://issues.jboss.org/browse/WELD-964 Project: Weld Issue Type: Enhancement Reporter: Geoffrey De Smet Having an "unsatisfied dependency" can have several causes: - The jar is not in the classpath - The jar is in the classpath, but the beans.xml is not being picked up (for whatever reason, such as problems with WEB-INF/beans.xml on some containers) - The jar is in the classpath, the beans.xml is picked up but the qualifiers etc don't match. So, instead of just saying "unsatisfied dependency ...": it should say something like this: - Unsatisfied dependency ... and there is no concrete implementing class in the classpath. - Unsatisfied dependency ... and the concrete implementing class(es) are not loaded as managed beans through a beans.xml. - Unsatisfied dependency ... and none of the managed beans of the same type match. Note: spring's exceptions differentiate between these cases (they explicitly define their appContext.xml set, so case 2 is impossible and case 1 throws a "app context file not found" exception. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

3
2
0 / 0

[JBoss JIRA] (WELD-1045) ProcessBeanAttributes not fired for interceptors and decorators

by Martin Kouba (Created) (JIRA)

ProcessBeanAttributes not fired for interceptors and decorators --------------------------------------------------------------- Key: WELD-1045 URL: https://issues.jboss.org/browse/WELD-1045 Project: Weld Issue Type: Bug Reporter: Martin Kouba Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha1 The spec (CDI 1.1) states: "The container must fire an event for each enabled bean, interceptor or decorator deployed in a bean archive, before registering the Bean object." However ProcessBeanAttributes is not fired for interceptors and decorators. Probably because of *BeanDeployerEnvironment.addInterceptor(InterceptorImpl<?>)* and *BeanDeployerEnvironment.addDecorator(DecoratorImpl<?>)* do not add intercetors and decorators bean to classBeanMap - the source of beans used in *org.jboss.weld.bootstrap.BeanDeployer.processBeans()*. -- 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

11 years, 9 months

3
3
0 / 0

[JBoss JIRA] (WELD-998) Alternative custom bean not available for injection in other custom bean

by Martin Kouba (Created) (JIRA)

Alternative custom bean not available for injection in other custom bean ------------------------------------------------------------------------ Key: WELD-998 URL: https://issues.jboss.org/browse/WELD-998 Project: Weld Issue Type: Bug Affects Versions: 1.1.2.Final Reporter: Martin Kouba Suppose we have extension that registers two custom beans (while observing AfterBeanDiscovery event). Custom bean A is alternative. Custom bean B is not alternative and has injection point with type A. This scenario causes deployment error: "WELD-001408 Unsatisfied dependencies...". It seems that *ProcessBean* event is not fired after calling *javax.enterprise.inject.spi.AfterBeanDiscovery.addBean(Bean<?>)* because *org.jboss.weld.manager.BeanManagerImpl.isBeanEnabled(Bean<?>)* resolves to false at the given moment. Nevertheless it is available for injection in "regular" beans after deployment validation (suppose custom bean B is not included). Note that if custom bean A#isAlternative() returns false, test passes. See TCK test: https://github.com/jboss/cdi-tck/tree/master/impl/src/main/java/org/jboss... -- 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

11 years, 9 months

4
10
0 / 0

[JBoss JIRA] (WELD-1120) Create better bootstrap configuration

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1120: ------------------------------------- Summary: Create better bootstrap configuration Key: WELD-1120 URL: https://issues.jboss.org/browse/WELD-1120 Project: Weld Issue Type: Task Affects Versions: 2.0.0.Alpha2 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha3 So that we can configure: * number of threads used for deployer * enable / disable ContainerLifecycleEventPreloader * enable / disable ConcurrentBeanDeployer / Validator * suppress ExecutorServices entirely (for GAE) -- 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

11 years, 10 months

1
1
0 / 0

[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

11 years, 10 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

11 years, 10 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

11 years, 10 months

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

11 years, 10 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues May 2012