Re: Upgrade to 6.5.0

2013-01-28 Thread Paul Bors
Looks like your application server is not finding your com.myApp.myAppApp
as per:
Caused by: java.lang.ClassNotFoundException: com.myApp.myAppApp from
[Module deployment.myApp-1.0-SNAPSHOT.war:main from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)

Most likely your deployment is corupt.

~ Thank you,
   Paul Bors

On Sat, Jan 26, 2013 at 5:37 PM, Stephen Walsh 
step...@connectwithawalsh.com wrote:

 I've been out of development on my side project for awhile and recently
 just got back in.  I upgraded to the latest version and got this this
 morning and could not figure it out.

 Any help?

 16:29:30,433 ERROR
 [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/myApp-1.0-SNAPSHOT]]
 (MSC service thread 1-3) Exception starting filter wicket.myApp:
 org.apache.wicket.WicketRuntimeException: Unable to create application of
 class com.myApp.myAppApp
 at
 org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:86)
 [wicket-core-6.5.0.jar:6.5.0]
 at
 org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:50)
 [wicket-core-6.5.0.jar:6.5.0]
 at
 org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:370)
 [wicket-core-6.5.0.jar:6.5.0]
 at
 org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:336)
 [wicket-core-6.5.0.jar:6.5.0]
 at
 org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447)
 [jbossweb-7.0.13.Final.jar:]
 at
 org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3269)
 [jbossweb-7.0.13.Final.jar:]
 at
 org.apache.catalina.core.StandardContext.start(StandardContext.java:3865)
 [jbossweb-7.0.13.Final.jar:]
 at
 org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90)
 [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
 at
 org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
 at
 org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 [classes.jar:1.6.0_37]
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 [classes.jar:1.6.0_37]
 at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
 Caused by: java.lang.ClassNotFoundException: com.myApp.myAppApp from
 [Module deployment.myApp-1.0-SNAPSHOT.war:main from Service Module Loader]
 at
 org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
 at
 org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
 at
 org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
 at
 org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
 at
 org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
 at
 org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
 at java.lang.Class.forName0(Native Method) [classes.jar:1.6.0_37]
 at java.lang.Class.forName(Class.java:247) [classes.jar:1.6.0_37]
 at
 org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72)
 [wicket-core-6.5.0.jar:6.5.0]
 ... 12 more

 16:29:30,469 ERROR [org.apache.catalina.core.StandardContext] (MSC service
 thread 1-3) Error filterStart
 16:29:30,470 ERROR [org.apache.catalina.core.StandardContext] (MSC service
 thread 1-3) Context [/myApp-1.0-SNAPSHOT] startup failed due to previous
 errors
 16:29:30,471 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3)
 MSC1: Failed to start service
 jboss.web.deployment.default-host./myApp-1.0-SNAPSHOT:
 org.jboss.msc.service.StartException in service
 jboss.web.deployment.default-host./myApp-1.0-SNAPSHOT: JBAS018040: Failed
 to start context
 at
 org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
 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)
 [classes.jar:1.6.0_37]
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 [classes.jar:1.6.0_37]
 at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]

 16:29:30,765 INFO  [org.jboss.as.server] (management-handler-thread - 8)
 

Re: Upgrade to 6.5.0

2013-01-28 Thread Stephen Walsh
That ended up being the issue. Had to clear out my JBOSS and change a
line in my web.xml.

Thanks!

__
Stephen Walsh | http://connectwithawalsh.com

On Jan 28, 2013, at 9:48, Paul Bors p...@bors.ws wrote:

 Looks like your application server is not finding your com.myApp.myAppApp
 as per:
 Caused by: java.lang.ClassNotFoundException: com.myApp.myAppApp from
 [Module deployment.myApp-1.0-SNAPSHOT.war:main from Service Module Loader]
 at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)

 Most likely your deployment is corupt.

 ~ Thank you,
   Paul Bors

 On Sat, Jan 26, 2013 at 5:37 PM, Stephen Walsh 
 step...@connectwithawalsh.com wrote:

 I've been out of development on my side project for awhile and recently
 just got back in.  I upgraded to the latest version and got this this
 morning and could not figure it out.

 Any help?

 16:29:30,433 ERROR
 [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/myApp-1.0-SNAPSHOT]]
 (MSC service thread 1-3) Exception starting filter wicket.myApp:
 org.apache.wicket.WicketRuntimeException: Unable to create application of
 class com.myApp.myAppApp
at
 org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:86)
 [wicket-core-6.5.0.jar:6.5.0]
at
 org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:50)
 [wicket-core-6.5.0.jar:6.5.0]
at
 org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:370)
 [wicket-core-6.5.0.jar:6.5.0]
at
 org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:336)
 [wicket-core-6.5.0.jar:6.5.0]
at
 org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447)
 [jbossweb-7.0.13.Final.jar:]
at
 org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3269)
 [jbossweb-7.0.13.Final.jar:]
at
 org.apache.catalina.core.StandardContext.start(StandardContext.java:3865)
 [jbossweb-7.0.13.Final.jar:]
at
 org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90)
 [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at
 org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at
 org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 [classes.jar:1.6.0_37]
at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 [classes.jar:1.6.0_37]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
 Caused by: java.lang.ClassNotFoundException: com.myApp.myAppApp from
 [Module deployment.myApp-1.0-SNAPSHOT.war:main from Service Module Loader]
at
 org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at
 org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
 org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
 org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
 org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at
 org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [classes.jar:1.6.0_37]
at java.lang.Class.forName(Class.java:247) [classes.jar:1.6.0_37]
at
 org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72)
 [wicket-core-6.5.0.jar:6.5.0]
... 12 more

 16:29:30,469 ERROR [org.apache.catalina.core.StandardContext] (MSC service
 thread 1-3) Error filterStart
 16:29:30,470 ERROR [org.apache.catalina.core.StandardContext] (MSC service
 thread 1-3) Context [/myApp-1.0-SNAPSHOT] startup failed due to previous
 errors
 16:29:30,471 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3)
 MSC1: Failed to start service
 jboss.web.deployment.default-host./myApp-1.0-SNAPSHOT:
 org.jboss.msc.service.StartException in service
 jboss.web.deployment.default-host./myApp-1.0-SNAPSHOT: JBAS018040: Failed
 to start context
at
 org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
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)
 [classes.jar:1.6.0_37]
at
 

Re: Upgrade to 6.5.0

2013-01-27 Thread Sven Meier
You're sure the application class is com.myApp.myAppApp? Looks like an 
accidental duplication of myApp.


Sven


On 01/26/2013 11:36 PM, Stephen Walsh wrote:

Caused by: java.lang.ClassNotFoundException: com.myApp.myAppApp from [Module 
deployment.myApp-



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Upgrade to 6.5.0

2013-01-27 Thread Stephen Walsh
I did a find and replace to remove the app name. That was an oversight.

__
Stephen Walsh | http://connectwithawalsh.com

On Jan 27, 2013, at 5:07, Sven Meier s...@meiers.net wrote:

 You're sure the application class is com.myApp.myAppApp? Looks like an 
 accidental duplication of myApp.

 Sven


 On 01/26/2013 11:36 PM, Stephen Walsh wrote:
 Caused by: java.lang.ClassNotFoundException: com.myApp.myAppApp from [Module 
 deployment.myApp-


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Upgrade to 6.5.0

2013-01-27 Thread Stephen Walsh
Here was the original error:

16:29:29,557 INFO  [org.jboss.as.repository] (management-handler-thread - 8) 
JBAS014900: Content added at location 
/usr/share/jboss-as-7.1.1.Final/standalone/data/content/2c/fd9a0ad0a567de3c4bfde63b541413297ba7f5/content
16:29:29,617 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) 
JBAS015876: Starting deployment of campingawaits-1.0-SNAPSHOT.war
16:29:30,433 ERROR 
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/campingawaits-1.0-SNAPSHOT]]
 (MSC service thread 1-3) Exception starting filter wicket.campingawaits: 
org.apache.wicket.WicketRuntimeException: Unable to create application of class 
com.campingawaits.CampingAwaitsApp
at 
org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:86)
 [wicket-core-6.5.0.jar:6.5.0]
at 
org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:50)
 [wicket-core-6.5.0.jar:6.5.0]
at 
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:370) 
[wicket-core-6.5.0.jar:6.5.0]
at 
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:336) 
[wicket-core-6.5.0.jar:6.5.0]
at 
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447)
 [jbossweb-7.0.13.Final.jar:]
at 
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3269) 
[jbossweb-7.0.13.Final.jar:]
at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:3865) 
[jbossweb-7.0.13.Final.jar:]
at 
org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90)
 [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at 
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at 
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 [classes.jar:1.6.0_37]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
[classes.jar:1.6.0_37]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
Caused by: java.lang.ClassNotFoundException: com.campingawaits.CampingAwaitsApp 
from [Module deployment.campingawaits-1.0-SNAPSHOT.war:main from Service 
Module Loader]
at 
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at 
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at 
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at 
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at 
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at 
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [classes.jar:1.6.0_37]
at java.lang.Class.forName(Class.java:247) [classes.jar:1.6.0_37]
at 
org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72)
 [wicket-core-6.5.0.jar:6.5.0]
... 12 more

16:29:30,469 ERROR [org.apache.catalina.core.StandardContext] (MSC service 
thread 1-3) Error filterStart
16:29:30,470 ERROR [org.apache.catalina.core.StandardContext] (MSC service 
thread 1-3) Context [/campingawaits-1.0-SNAPSHOT] startup failed due to 
previous errors
16:29:30,471 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) 
MSC1: Failed to start service 
jboss.web.deployment.default-host./campingawaits-1.0-SNAPSHOT: 
org.jboss.msc.service.StartException in service 
jboss.web.deployment.default-host./campingawaits-1.0-SNAPSHOT: JBAS018040: 
Failed to start context
at 
org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
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)
 [classes.jar:1.6.0_37]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
[classes.jar:1.6.0_37]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]

16:29:30,765 INFO  [org.jboss.as.server] (management-handler-thread - 8) 
JBAS018562: Redeployed campingawaits-1.0-SNAPSHOT.war
16:29:30,766 INFO  [org.jboss.as.controller] (management-handler-thread - 8) 
JBAS014774: Service status report
JBAS014777:   Services which failed to 

Re: Upgrade to 6.5.0

2013-01-27 Thread Stephen Walsh
Also, it seems like this might be a deployment issue, but I'm not sure.  

I'm using mvn package jboss-as:deploy to get my package into jboss, and after 
rolling back to 6.0.0, I'm still having the same issue

09:45:27,020 INFO  [org.jboss.as.repository] (management-handler-thread - 1) 
JBAS014900: Content added at location 
/usr/share/jboss-as-7.1.1.Final/standalone/data/content/a2/dffcda3610a8edc34edcd11ac16fc22eed4591/content
09:45:27,057 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) 
JBAS015876: Starting deployment of campingawaits-1.0-SNAPSHOT.war
09:45:27,948 ERROR 
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/campingawaits-1.0-SNAPSHOT]]
 (MSC service thread 1-3) Exception starting filter wicket.campingawaits: 
org.apache.wicket.WicketRuntimeException: Unable to create application of class 
com.campingawaits.CampingAwaitsApp
at 
org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:86)
 [wicket-core-6.0.0.jar:6.0.0]
at 
org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:50)
 [wicket-core-6.0.0.jar:6.0.0]
at 
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:339) 
[wicket-core-6.0.0.jar:6.0.0]
at 
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:314) 
[wicket-core-6.0.0.jar:6.0.0]
at 
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447)
 [jbossweb-7.0.13.Final.jar:]
at 
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3269) 
[jbossweb-7.0.13.Final.jar:]
at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:3865) 
[jbossweb-7.0.13.Final.jar:]
at 
org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90)
 [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at 
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at 
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 [classes.jar:1.6.0_37]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
[classes.jar:1.6.0_37]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
Caused by: java.lang.ClassNotFoundException: com.campingawaits.CampingAwaitsApp 
from [Module deployment.campingawaits-1.0-SNAPSHOT.war:main from Service 
Module Loader]
at 
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at 
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at 
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at 
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at 
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at 
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [classes.jar:1.6.0_37]
at java.lang.Class.forName(Class.java:247) [classes.jar:1.6.0_37]
at 
org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72)
 [wicket-core-6.0.0.jar:6.0.0]
... 12 more

09:45:27,959 ERROR [org.apache.catalina.core.StandardContext] (MSC service 
thread 1-3) Error filterStart
09:45:27,960 ERROR [org.apache.catalina.core.StandardContext] (MSC service 
thread 1-3) Context [/campingawaits-1.0-SNAPSHOT] startup failed due to 
previous errors
09:45:28,111 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) 
MSC1: Failed to start service 
jboss.web.deployment.default-host./campingawaits-1.0-SNAPSHOT: 
org.jboss.msc.service.StartException in service 
jboss.web.deployment.default-host./campingawaits-1.0-SNAPSHOT: JBAS018040: 
Failed to start context
at 
org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
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)
 [classes.jar:1.6.0_37]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
[classes.jar:1.6.0_37]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]

09:45:28,146 INFO  [org.jboss.as.server] (management-handler-thread - 1) 
JBAS018562: Redeployed 

Re: Upgrade to 6.5.0

2013-01-27 Thread Stephen Walsh
I'm using the default web.xml.  I've never touched it since I've started,
but here it is:

?xml version=1.0 encoding=ISO-8859-1?

web-app xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;

xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd;

version=2.5


 display-namecampingawaits/display-name


 !--

There are three means to configure Wickets configuration mode and they

are tested in the order given.

 1) A system property: -Dwicket.configuration

2) servlet specific init-param

3) context specific context-param


 The value might be either development (reloading when templates change)
or

deployment. If no configuration is found, development is the default.
--


 filter

filter-namewicket.campingawaits/filter-name

filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class

init-param

param-nameapplicationClassName/param-name

param-valuecom.campingawaits.CampingAwaitsApp/param-value

/init-param

/filter


 filter-mapping

filter-namewicket.campingawaits/filter-name

url-pattern/*/url-pattern

/filter-mapping

/web-app


I ran mvn clean and it was successful.


WEB-INF, does have the classes folders and my classes that have been built.


I'm not sure what you mean by your last question.  I'm on a Mac and using
Terminal, Maven, and the j-boss maven plugin to deploy to my jboss install.


Update to the above.


I ran into the same issue, but now jboss won't even start.  I've got a few
away from desk items, so I'll have to check this when I get back and after
a clean jboss install.


Thanks for the help thus far.

___
Stephen Walsh | http://connectwithawalsh.com


On Sun, Jan 27, 2013 at 9:52 AM, Stephen Walsh 
step...@connectwithawalsh.com wrote:

 Also, it seems like this might be a deployment issue, but I'm not sure.

 I'm using mvn package jboss-as:deploy to get my package into jboss, and
 after rolling back to 6.0.0, I'm still having the same issue

 09:45:27,020 INFO  [org.jboss.as.repository] (management-handler-thread -
 1) JBAS014900: Content added at location
 /usr/share/jboss-as-7.1.1.Final/standalone/data/content/a2/dffcda3610a8edc34edcd11ac16fc22eed4591/content
 09:45:27,057 INFO  [org.jboss.as.server.deployment] (MSC service thread
 1-1) JBAS015876: Starting deployment of campingawaits-1.0-SNAPSHOT.war
 09:45:27,948 ERROR
 [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/campingawaits-1.0-SNAPSHOT]]
 (MSC service thread 1-3) Exception starting filter wicket.campingawaits:
 org.apache.wicket.WicketRuntimeException: Unable to create application of
 class com.campingawaits.CampingAwaitsApp
  at
 org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(
 ContextParamWebApplicationFactory.java:86) [wicket-core-6.0.0.jar:6.0.0]
  at
 org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(
 ContextParamWebApplicationFactory.java:50) [wicket-core-6.0.0.jar:6.0.0]
  at org.apache.wicket.protocol.http.WicketFilter.init(
 WicketFilter.java:339) [wicket-core-6.0.0.jar:6.0.0]
  at org.apache.wicket.protocol.http.WicketFilter.init(
 WicketFilter.java:314) [wicket-core-6.0.0.jar:6.0.0]
  at org.apache.catalina.core.ApplicationFilterConfig.getFilter(
 ApplicationFilterConfig.java:447) [jbossweb-7.0.13.Final.jar:]
  at org.apache.catalina.core.StandardContext.filterStart(
 StandardContext.java:3269) [jbossweb-7.0.13.Final.jar:]
  at org.apache.catalina.core.StandardContext.start(
 StandardContext.java:3865) [jbossweb-7.0.13.Final.jar:]
  at org.jboss.as.web.deployment.WebDeploymentService.start(
 WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
  at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(
 ServiceControllerImpl.java:1811)
  at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(
 ServiceControllerImpl.java:1746)
  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
 ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37]
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(
 ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37]
  at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
 Caused by: java.lang.ClassNotFoundException:
 com.campingawaits.CampingAwaitsApp from [Module
 deployment.campingawaits-1.0-SNAPSHOT.war:main from Service Module Loader]
  at org.jboss.modules.ModuleClassLoader.findClass(
 ModuleClassLoader.java:190)
  at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(
 ConcurrentClassLoader.java:468)
  at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(
 ConcurrentClassLoader.java:456)
  at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(
 ConcurrentClassLoader.java:423)
  at org.jboss.modules.ConcurrentClassLoader.performLoadClass(
 ConcurrentClassLoader.java:398)
  at org.jboss.modules.ConcurrentClassLoader.loadClass(
 ConcurrentClassLoader.java:120)
  

Re: Upgrade to 6.5.0

2013-01-27 Thread Stephen Walsh
Well, I got a clean install of jboss and used the web interface to add my war 
to the deployment area.  When I tried to enable it, I got the same errors as 
below.  

So I'm still not up and running with either 6.0.0 or 6.5.0. :(


On Jan 27, 2013, at 10:03 AM, Stephen Walsh step...@connectwithawalsh.com 
wrote:

 I'm using the default web.xml.  I've never touched it since I've started, but 
 here it is:
 
 ?xml version=1.0 encoding=ISO-8859-1?
 web-app xmlns=http://java.sun.com/xml/ns/javaee; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation=http://java.sun.com/xml/ns/javaee 
 http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd;
   version=2.5
 
   display-namecampingawaits/display-name
 
   !--
   There are three means to configure Wickets configuration mode 
 and they 
   are tested in the order given.
   
   1) A system property: -Dwicket.configuration 
   2) servlet specific init-param 
   3) context specific context-param
 
   The value might be either development (reloading when 
 templates change) or 
   deployment. If no configuration is found, development is 
 the default. --
 
   filter
   filter-namewicket.campingawaits/filter-name
   
 filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class
   init-param
   param-nameapplicationClassName/param-name
   
 param-valuecom.campingawaits.CampingAwaitsApp/param-value
   /init-param
   /filter
 
   filter-mapping
   filter-namewicket.campingawaits/filter-name
   url-pattern/*/url-pattern
   /filter-mapping
 /web-app
 
 I ran mvn clean and it was successful.
 
 WEB-INF, does have the classes folders and my classes that have been built.
 
 I'm not sure what you mean by your last question.  I'm on a Mac and using 
 Terminal, Maven, and the j-boss maven plugin to deploy to my jboss install.
 
 Update to the above.
 
 I ran into the same issue, but now jboss won't even start.  I've got a few 
 away from desk items, so I'll have to check this when I get back and after a 
 clean jboss install.
 
 Thanks for the help thus far.
 
 ___
 Stephen Walsh | http://connectwithawalsh.com
 
 
 On Sun, Jan 27, 2013 at 9:52 AM, Stephen Walsh 
 step...@connectwithawalsh.com wrote:
 Also, it seems like this might be a deployment issue, but I'm not sure.  
 
 I'm using mvn package jboss-as:deploy to get my package into jboss, and 
 after rolling back to 6.0.0, I'm still having the same issue
 
 09:45:27,020 INFO  [org.jboss.as.repository] (management-handler-thread - 1) 
 JBAS014900: Content added at location 
 /usr/share/jboss-as-7.1.1.Final/standalone/data/content/a2/dffcda3610a8edc34edcd11ac16fc22eed4591/content
 09:45:27,057 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) 
 JBAS015876: Starting deployment of campingawaits-1.0-SNAPSHOT.war
 09:45:27,948 ERROR 
 [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/campingawaits-1.0-SNAPSHOT]]
  (MSC service thread 1-3) Exception starting filter wicket.campingawaits: 
 org.apache.wicket.WicketRuntimeException: Unable to create application of 
 class com.campingawaits.CampingAwaitsApp
   at 
 org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:86)
  [wicket-core-6.0.0.jar:6.0.0]
   at 
 org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:50)
  [wicket-core-6.0.0.jar:6.0.0]
   at 
 org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:339) 
 [wicket-core-6.0.0.jar:6.0.0]
   at 
 org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:314) 
 [wicket-core-6.0.0.jar:6.0.0]
   at 
 org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447)
  [jbossweb-7.0.13.Final.jar:]
   at 
 org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3269)
  [jbossweb-7.0.13.Final.jar:]
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:3865) 
 [jbossweb-7.0.13.Final.jar:]
   at 
 org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90)
  [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
   at 
 org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
   at 
 org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  [classes.jar:1.6.0_37]
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  [classes.jar:1.6.0_37]
   at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
 Caused by: 

Re: Upgrade to 6.5.0

2013-01-27 Thread procrastinative.developer
I think that Sven has right about war duplication. Jboss maven plugin has 3
goals to manage deployments: deploy, redeploy, undeploy. If you use only
deploy goal, jboss could leave some trashes in deployment location. 

So if you reinstall JBoss, the old configuration files could still be on
your disc. You should remove this folders (temp, works etc) - I don't know
where this files are located on mac. 

Fast check: Download fresh zipped installation from JBoss site
(http://www.jboss.org/jbossas/downloads) and unzip it, copy war into
%JBOSS%/standalone/deployments and run it %JBOSS%/run/stanalone


Can you publish also the com.campingawaits.CampingAwaitsApp class? 



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Upgrade-to-6-5-0-tp4655782p4655802.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Upgrade to 6.5.0

2013-01-27 Thread Stephen Walsh
I'll have to double check on this for sure when I get home, but a simple
JBOSS question.  I can't just run mvn package jboss-as:deploy over and over
again?  This has seemed to work for months up until this point.  Obviously
I need to discontinue if it's not good practice; I just didn't know any
better.  I'll try again when I get home.  I'm on a different computer
that's out of sync with my code at home.

Here's the class:

package com.campingawaits;

import org.apache.wicket.Page;
import org.apache.wicket.Session;
import org.apache.wicket.authorization.IAuthorizationStrategy;
import
org.apache.wicket.authorization.strategies.page.SimplePageAuthorizationStrategy;
import org.apache.wicket.protocol.http.WebApplication;
import org.apache.wicket.request.Request;
import org.apache.wicket.request.Response;
import org.apache.wicket.settings.IRequestCycleSettings.RenderStrategy;

import com.campingawaits.auth.AuthenticatedWebPage;
import com.campingawaits.auth.CampingAwaitsSession;
import com.campingawaits.auth.SignIn;
import com.campingawaits.base.About;
import com.campingawaits.base.Blog;
import com.campingawaits.base.ContactUs;
import com.campingawaits.base.Index;
import com.campingawaits.blog.BlogDetails;

/**
 * Application object for your web application. If you want to run this
application without deploying, run the Start class.
 *
 * @see com.campingawaits.Start#main(String[])
 */
public class CampingAwaitsApplication extends WebApplication
{
/**
 * Contstruct
 */
public CampingAwaitsApplication()
 {
}
 /**
 * @see org.apache.wicket.Application#getHomePage()
 */
@Override
public Class? extends Page getHomePage() {
 return Index.class;
}

/**
 * @see
org.apache.wicket.protocol.http.WebApplication#newSession(org.apache.wicket.request.Request,
 *  org.apache.wicket.request.Response)
 */
 @Override
public Session newSession(Request request, Response response)
 {
return new CampingAwaitsSession(request);
 }

/**
 * @see org.apache.wicket.Application#init()
 */
 @Override
public void init() {
 super.init();
 getResourceSettings().setThrowExceptionOnMissingResource(false);

getRequestCycleSettings().setRenderStrategy(RenderStrategy.REDIRECT_TO_RENDER);
 IAuthorizationStrategy authorizationStrategy = new
SimplePageAuthorizationStrategy(
AuthenticatedWebPage.class, SignIn.class) {
 @Override
protected boolean isAuthorized() {
 return (((CampingAwaitsSession)Session.get()).isSignedIn());
}
 };
getSecuritySettings().setAuthorizationStrategy(authorizationStrategy);
 /*mountPage(/, Index.class);*/
 mountPage(/news, Blog.class);
mountPage(/news/${id}, BlogDetails.class);
 mountPage(/contact, ContactUs.class);
mountPage(/about, About.class);
 }
}


___
Stephen Walsh | http://connectwithawalsh.com


On Sun, Jan 27, 2013 at 10:38 AM, procrastinative.developer 
procrastinative.develo...@gmail.com wrote:

 I think that Sven has right about war duplication. Jboss maven plugin has 3
 goals to manage deployments: deploy, redeploy, undeploy. If you use only
 deploy goal, jboss could leave some trashes in deployment location.

 So if you reinstall JBoss, the old configuration files could still be on
 your disc. You should remove this folders (temp, works etc) - I don't know
 where this files are located on mac.

 Fast check: Download fresh zipped installation from JBoss site
 (http://www.jboss.org/jbossas/downloads) and unzip it, copy war into
 %JBOSS%/standalone/deployments and run it %JBOSS%/run/stanalone


 Can you publish also the com.campingawaits.CampingAwaitsApp class?



 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Upgrade-to-6-5-0-tp4655782p4655802.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




Re: Upgrade to 6.5.0

2013-01-27 Thread Stephen Walsh
Just to clarify, the class is not out of sync, the applications (Eclipse,
JBOSS, etc.)

___
Stephen Walsh | http://connectwithawalsh.com


On Sun, Jan 27, 2013 at 11:46 AM, Stephen Walsh 
step...@connectwithawalsh.com wrote:

 I'll have to double check on this for sure when I get home, but a simple
 JBOSS question.  I can't just run mvn package jboss-as:deploy over and
 over again?  This has seemed to work for months up until this point.
  Obviously I need to discontinue if it's not good practice; I just didn't
 know any better.  I'll try again when I get home.  I'm on a different
 computer that's out of sync with my code at home.

 Here's the class:

 package com.campingawaits;

 import org.apache.wicket.Page;
 import org.apache.wicket.Session;
 import org.apache.wicket.authorization.IAuthorizationStrategy;
 import
 org.apache.wicket.authorization.strategies.page.SimplePageAuthorizationStrategy;
 import org.apache.wicket.protocol.http.WebApplication;
 import org.apache.wicket.request.Request;
 import org.apache.wicket.request.Response;
 import org.apache.wicket.settings.IRequestCycleSettings.RenderStrategy;

 import com.campingawaits.auth.AuthenticatedWebPage;
 import com.campingawaits.auth.CampingAwaitsSession;
 import com.campingawaits.auth.SignIn;
 import com.campingawaits.base.About;
 import com.campingawaits.base.Blog;
 import com.campingawaits.base.ContactUs;
 import com.campingawaits.base.Index;
 import com.campingawaits.blog.BlogDetails;

 /**
  * Application object for your web application. If you want to run this
 application without deploying, run the Start class.
  *
  * @see com.campingawaits.Start#main(String[])
  */
 public class CampingAwaitsApplication extends WebApplication
 {
 /**
  * Contstruct
  */
 public CampingAwaitsApplication()
  {
 }
  /**
  * @see org.apache.wicket.Application#getHomePage()
  */
 @Override
 public Class? extends Page getHomePage() {
  return Index.class;
 }

 /**
  * @see
 org.apache.wicket.protocol.http.WebApplication#newSession(org.apache.wicket.request.Request,
  *  org.apache.wicket.request.Response)
  */
  @Override
 public Session newSession(Request request, Response response)
  {
 return new CampingAwaitsSession(request);
  }

 /**
  * @see org.apache.wicket.Application#init()
  */
  @Override
 public void init() {
  super.init();
  getResourceSettings().setThrowExceptionOnMissingResource(false);

 getRequestCycleSettings().setRenderStrategy(RenderStrategy.REDIRECT_TO_RENDER);
  IAuthorizationStrategy authorizationStrategy = new
 SimplePageAuthorizationStrategy(
 AuthenticatedWebPage.class, SignIn.class) {
  @Override
 protected boolean isAuthorized() {
  return (((CampingAwaitsSession)Session.get()).isSignedIn());
 }
  };
 getSecuritySettings().setAuthorizationStrategy(authorizationStrategy);
  /*mountPage(/, Index.class);*/
  mountPage(/news, Blog.class);
 mountPage(/news/${id}, BlogDetails.class);
  mountPage(/contact, ContactUs.class);
 mountPage(/about, About.class);
  }
 }


 ___
 Stephen Walsh | http://connectwithawalsh.com


 On Sun, Jan 27, 2013 at 10:38 AM, procrastinative.developer 
 procrastinative.develo...@gmail.com wrote:

 I think that Sven has right about war duplication. Jboss maven plugin has
 3
 goals to manage deployments: deploy, redeploy, undeploy. If you use only
 deploy goal, jboss could leave some trashes in deployment location.

 So if you reinstall JBoss, the old configuration files could still be on
 your disc. You should remove this folders (temp, works etc) - I don't know
 where this files are located on mac.

 Fast check: Download fresh zipped installation from JBoss site
 (http://www.jboss.org/jbossas/downloads) and unzip it, copy war into
 %JBOSS%/standalone/deployments and run it %JBOSS%/run/stanalone


 Can you publish also the com.campingawaits.CampingAwaitsApp class?



 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Upgrade-to-6-5-0-tp4655782p4655802.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org





Re: Upgrade to 6.5.0

2013-01-27 Thread Stephen Walsh
Got it working now.  I think I had some stuff that was keeping the new
install of JBOSS from actually being uninstalled.  Thanks for the help.
 Now to figure out why Maven keeps building with Java 1.5 instead of 1.6.

___
Stephen Walsh | http://connectwithawalsh.com


On Sun, Jan 27, 2013 at 12:08 PM, procrastinative.developer 
procrastinative.develo...@gmail.com wrote:

 if this fix help you can use JBoss maven plugin in old way.



 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Upgrade-to-6-5-0-tp4655782p4655809.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org