[JBoss JIRA] Created: (SEAMWICKET-27) Unable to build the module
by Jozef Hartinger (JIRA)
Unable to build the module
--------------------------
Key: SEAMWICKET-27
URL: https://issues.jboss.org/browse/SEAMWICKET-27
Project: Seam for Apache Wicket
Issue Type: Bug
Reporter: Jozef Hartinger
Assignee: Shane Bryzak
Priority: Critical
Fix For: 3.0.0.CR1
Between version b09 and CR1, the Seam BOM has changed. One of the changes is that the jboss spec dependency has been removed (it is still imported, but is not itself a possible dependency)
- <!-- make Java EE 6 API available as stack -->
- <dependency>
- <groupId>org.jboss.spec</groupId>
- <artifactId>jboss-javaee-6.0</artifactId>
- <version>${jboss.javaee.version}</version>
- <scope>provided</scope>
- <type>pom</type>
- </dependency>
-
As a result, it is not possible to compile the Wicket module anymore:
[jharting@jharting wicket]$ mci
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.jboss.seam.wicket:seam-wicket:3.0.0-SNAPSHOT (/home/jharting/jboss/Seam_3/modules/wicket/impl/pom.xml) has 1 error
[ERROR] 'dependencies.dependency.version' for org.jboss.spec:jboss-javaee-6.0:pom is missing. @ line 42, column 19
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Updated: (SEAMWICKET-10) webbeans-numberguess-wicket does not deploy on tomcat
by Shane Bryzak (JIRA)
[ https://issues.jboss.org/browse/SEAMWICKET-10?page=com.atlassian.jira.plu... ]
Shane Bryzak updated SEAMWICKET-10:
-----------------------------------
Fix Version/s: 3.0.0.Final
(was: 3.0.0.CR1)
> webbeans-numberguess-wicket does not deploy on tomcat
> -----------------------------------------------------
>
> Key: SEAMWICKET-10
> URL: https://issues.jboss.org/browse/SEAMWICKET-10
> Project: Seam for Apache Wicket
> Issue Type: Bug
> Affects Versions: 1.0.0.Beta1
> Environment: Tomcat 6.0.18
> JDK 5 update 16
> Reporter: Jozef Hartinger
> Assignee: Clint Popetz
> Fix For: 3.0.0.Final
>
>
> Application throws the following exception during deployment:
> Apr 24, 2009 10:45:39 AM org.apache.catalina.core.StandardContext filterStart
> SEVERE: Exception starting filter wicket.numberguess-example
> java.lang.NoClassDefFoundError: org/jboss/webbeans/manager/api/WebBeansManager
> at org.jboss.webbeans.wicket.WebBeansApplication.<init>(WebBeansApplication.java:37)
> at org.jboss.webbeans.examples.wicket.SampleApplication.<init>(SampleApplication.java:5)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at java.lang.Class.newInstance0(Class.java:355)
> at java.lang.Class.newInstance(Class.java:308)
> at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72)
> at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:49)
> at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:552)
> at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
> at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
> at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108)
> at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3709)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4363)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830)
> at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719)
> at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
> at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1217)
> at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.ClassNotFoundException: org.jboss.webbeans.manager.api.WebBeansManager
> at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387)
> at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
> ... 30 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Closed: (SEAMJMS-16) Event to JMS to Event mapping behavior
by John Ament (JIRA)
[ https://issues.jboss.org/browse/SEAMJMS-16?page=com.atlassian.jira.plugin... ]
John Ament closed SEAMJMS-16.
-----------------------------
> Event to JMS to Event mapping behavior
> --------------------------------------
>
> Key: SEAMJMS-16
> URL: https://issues.jboss.org/browse/SEAMJMS-16
> Project: Seam JMS
> Issue Type: Bug
> Reporter: John Ament
>
> While working on seam jms, I've noted the following behavior.
> java.lang.IllegalStateException: Singleton not set for BaseClassLoader@3479404a{vfs:///apps/jboss/jboss-6.0.0.Final/server/all/conf/jboss-service.xml}
> at org.jboss.weld.integration.provider.JBossSingletonProvider$EarSingleton.get(JBossSingletonProvider.java:59) [:6.0.0.Final]
> at org.jboss.weld.Container.instance(Container.java:58) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.checkQualifier(ResolvableBuilder.java:209) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.addQualifier(ResolvableBuilder.java:174) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.addQualifierIfAbsent(ResolvableBuilder.java:184) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.resolveObserverMethods(BeanManagerImpl.java:464) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:604) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:598) [:6.0.0.Final]
> at org.jboss.seam.jms.bridge.IngressMessageListener.onMessage(IngressMessageListener.java:45)
> at org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:822) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:940) [:6.0.0.Final]
> at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.0.0.Final]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
> This exception occurs when trying to fire an event with the contents of a JMS message. The message listener in this case is instantiated from the portable extension and receives the bean manager as an argument in the constructor. I am able to get as far as reading the data from JMS, but when firing the second event the above exception occurs. I'm not certain that this is a Weld problem, but it seem slike a good place to start based on the packages shown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Resolved: (SEAMJMS-16) Event to JMS to Event mapping behavior
by John Ament (JIRA)
[ https://issues.jboss.org/browse/SEAMJMS-16?page=com.atlassian.jira.plugin... ]
John Ament resolved SEAMJMS-16.
-------------------------------
Resolution: Rejected
Rejecting, as this was a development issue that was believed by the dev to be a weld problem but is really a CL issue.
> Event to JMS to Event mapping behavior
> --------------------------------------
>
> Key: SEAMJMS-16
> URL: https://issues.jboss.org/browse/SEAMJMS-16
> Project: Seam JMS
> Issue Type: Bug
> Reporter: John Ament
>
> While working on seam jms, I've noted the following behavior.
> java.lang.IllegalStateException: Singleton not set for BaseClassLoader@3479404a{vfs:///apps/jboss/jboss-6.0.0.Final/server/all/conf/jboss-service.xml}
> at org.jboss.weld.integration.provider.JBossSingletonProvider$EarSingleton.get(JBossSingletonProvider.java:59) [:6.0.0.Final]
> at org.jboss.weld.Container.instance(Container.java:58) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.checkQualifier(ResolvableBuilder.java:209) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.addQualifier(ResolvableBuilder.java:174) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.addQualifierIfAbsent(ResolvableBuilder.java:184) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.resolveObserverMethods(BeanManagerImpl.java:464) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:604) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:598) [:6.0.0.Final]
> at org.jboss.seam.jms.bridge.IngressMessageListener.onMessage(IngressMessageListener.java:45)
> at org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:822) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:940) [:6.0.0.Final]
> at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.0.0.Final]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
> This exception occurs when trying to fire an event with the contents of a JMS message. The message listener in this case is instantiated from the portable extension and receives the bean manager as an argument in the constructor. I am able to get as far as reading the data from JMS, but when firing the second event the above exception occurs. I'm not certain that this is a Weld problem, but it seem slike a good place to start based on the packages shown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Commented: (SEAMJMS-16) Event to JMS to Event mapping behavior
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/SEAMJMS-16?page=com.atlassian.jira.plugin... ]
Pete Muir commented on SEAMJMS-16:
----------------------------------
John, I obviously failed to explain this well to you, as this is what I was getting at when we were chatting ;- Sorry about that!
> Event to JMS to Event mapping behavior
> --------------------------------------
>
> Key: SEAMJMS-16
> URL: https://issues.jboss.org/browse/SEAMJMS-16
> Project: Seam JMS
> Issue Type: Bug
> Reporter: John Ament
>
> While working on seam jms, I've noted the following behavior.
> java.lang.IllegalStateException: Singleton not set for BaseClassLoader@3479404a{vfs:///apps/jboss/jboss-6.0.0.Final/server/all/conf/jboss-service.xml}
> at org.jboss.weld.integration.provider.JBossSingletonProvider$EarSingleton.get(JBossSingletonProvider.java:59) [:6.0.0.Final]
> at org.jboss.weld.Container.instance(Container.java:58) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.checkQualifier(ResolvableBuilder.java:209) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.addQualifier(ResolvableBuilder.java:174) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.addQualifierIfAbsent(ResolvableBuilder.java:184) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.resolveObserverMethods(BeanManagerImpl.java:464) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:604) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:598) [:6.0.0.Final]
> at org.jboss.seam.jms.bridge.IngressMessageListener.onMessage(IngressMessageListener.java:45)
> at org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:822) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:940) [:6.0.0.Final]
> at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.0.0.Final]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
> This exception occurs when trying to fire an event with the contents of a JMS message. The message listener in this case is instantiated from the portable extension and receives the bean manager as an argument in the constructor. I am able to get as far as reading the data from JMS, but when firing the second event the above exception occurs. I'm not certain that this is a Weld problem, but it seem slike a good place to start based on the packages shown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Commented: (SEAMJMS-16) Event to JMS to Event mapping behavior
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/SEAMJMS-16?page=com.atlassian.jira.plugin... ]
Pete Muir commented on SEAMJMS-16:
----------------------------------
John, I obviously failed to explain this well to you, as this is what I was getting at when we were chatting ;- Sorry about that!
> Event to JMS to Event mapping behavior
> --------------------------------------
>
> Key: SEAMJMS-16
> URL: https://issues.jboss.org/browse/SEAMJMS-16
> Project: Seam JMS
> Issue Type: Bug
> Reporter: John Ament
>
> While working on seam jms, I've noted the following behavior.
> java.lang.IllegalStateException: Singleton not set for BaseClassLoader@3479404a{vfs:///apps/jboss/jboss-6.0.0.Final/server/all/conf/jboss-service.xml}
> at org.jboss.weld.integration.provider.JBossSingletonProvider$EarSingleton.get(JBossSingletonProvider.java:59) [:6.0.0.Final]
> at org.jboss.weld.Container.instance(Container.java:58) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.checkQualifier(ResolvableBuilder.java:209) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.addQualifier(ResolvableBuilder.java:174) [:6.0.0.Final]
> at org.jboss.weld.resolution.ResolvableBuilder.addQualifierIfAbsent(ResolvableBuilder.java:184) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.resolveObserverMethods(BeanManagerImpl.java:464) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:604) [:6.0.0.Final]
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:598) [:6.0.0.Final]
> at org.jboss.seam.jms.bridge.IngressMessageListener.onMessage(IngressMessageListener.java:45)
> at org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:822) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.Final]
> at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:940) [:6.0.0.Final]
> at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.0.0.Final]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
> This exception occurs when trying to fire an event with the contents of a JMS message. The message listener in this case is instantiated from the portable extension and receives the bean manager as an argument in the constructor. I am able to get as far as reading the data from JMS, but when firing the second event the above exception occurs. I'm not certain that this is a Weld problem, but it seem slike a good place to start based on the packages shown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month