[seam-issues] [JBoss JIRA] Updated: (SEAMWICKET-10) numberguess example does not deploy on tomcat
Dan Allen (JIRA)
jira-events at lists.jboss.org
Thu Mar 24 16:14:47 EDT 2011
[ https://issues.jboss.org/browse/SEAMWICKET-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Allen updated SEAMWICKET-10:
--------------------------------
Summary: numberguess example does not deploy on tomcat (was: webbeans-numberguess-wicket does not deploy on tomcat)
> numberguess example 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
More information about the seam-issues
mailing list