You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by "Chenini, Mohamed " <MC...@geico.com> on 2009/04/09 23:56:14 UTC
debugging a Wicket application running under Jetty-6.1 in Eclipse
Hi,
This is about debugging a Wicket application running under Jetty-6.1 in
Eclipse.
I followed the steps shown at:
http://docs.codehaus.org/display/JETTY/Debugging+with+the+Maven+Jetty+Pl
ugin+inside+Eclipse
But I am getting this exception:
java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher
Exception in thread "main"
Any help?
The steps I followed are:
Step 1
Go to the Run/External Tools/External Tools ..." menu item on the "Run"
menu bar. Select "Program" and click the "New" button. On the "Main"
tab, fill in the "Location:" as the full path to your "mvn" executable.
C:\java\DEVTOOLS\MAIN\maven2\bin
For the "Working Directory:" select the workspace that matches your
webapp. For "Arguments:" add jetty:run.
Move to the "Environment" tab and click the "New" button to add a new
variable named MAVEN_OPTS with the value:
-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y
If you supply suspend=n instead of suspend=y you can start immediately
without running the debugger and launch the debugger at anytime you
really wish to debug.
Step 2
Then, pull up the "Run/Debug/Debug ..." menu item and select "Remote
Java Application" and click the "New" button. Fill in the dialog by
selecting your webapp project for the "Project:" field, and ensure you
are using the same port number as you specified in the address= property
above.
Now all you need to do is to Run/External Tools and select the name of
the maven tool setup you created in step 1 to start the plugin and then
Run/Debug and select the name of the debug setup you setup in step2.
Thanks,
Mohamed
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
RE: debugging a Wicket application running under Jetty-6.1 in Eclipse
Posted by "Chenini, Mohamed " <MC...@geico.com>.
It is working now. I am debugging in Eclipse.
Thanks a lot
-----Original Message-----
From: jcgarciam [mailto:jcgarciam@gmail.com]
Sent: Thursday, April 09, 2009 6:06 PM
To: users@wicket.apache.org
Subject: Re: debugging a Wicket application running under Jetty-6.1 in
Eclipse
I'll suggest to do it in the Wicket Way, you will have much more
benefits.
If you made your project from the QuickStart, you will notice a 'Start'
class under your 'test' source.
that what it does is just start an embedded jetty pointing to your
webapp
directory and mounting your application under "/" context.
so just right click on it and click "Debug as" -> Java Application and
you're done.
Even if you are working on a multi-module maven project this will work,
just make sure your module are installed on your local repository,
issuing
'mvn install' on the root project.
If you have question regarding the 'Start.java' class just let us know.
mchenini wrote:
>
> Hi,
>
>
>
> This is about debugging a Wicket application running under Jetty-6.1
in
> Eclipse.
>
>
>
> I followed the steps shown at:
>
http://docs.codehaus.org/display/JETTY/Debugging+with+the+Maven+Jetty+Pl
> ugin+inside+Eclipse
>
> But I am getting this exception:
>
>
>
> java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher
>
>
> Exception in thread "main"
>
>
> Any help?
>
>
> The steps I followed are:
>
>
> Step 1
> Go to the Run/External Tools/External Tools ..." menu item on the
"Run"
> menu bar. Select "Program" and click the "New" button. On the "Main"
> tab, fill in the "Location:" as the full path to your "mvn"
executable.
> C:\java\DEVTOOLS\MAIN\maven2\bin
>
> For the "Working Directory:" select the workspace that matches your
> webapp. For "Arguments:" add jetty:run.
>
> Move to the "Environment" tab and click the "New" button to add a new
> variable named MAVEN_OPTS with the value:
>
> -Xdebug -Xnoagent -Djava.compiler=NONE
> -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y
>
> If you supply suspend=n instead of suspend=y you can start immediately
> without running the debugger and launch the debugger at anytime you
> really wish to debug.
>
>
>
> Step 2
>
> Then, pull up the "Run/Debug/Debug ..." menu item and select "Remote
> Java Application" and click the "New" button. Fill in the dialog by
> selecting your webapp project for the "Project:" field, and ensure you
> are using the same port number as you specified in the address=
property
> above.
>
> Now all you need to do is to Run/External Tools and select the name of
> the maven tool setup you created in step 1 to start the plugin and
then
> Run/Debug and select the name of the debug setup you setup in step2.
>
>
>
>
>
>
>
> Thanks,
>
> Mohamed
>
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>
>
--
View this message in context:
http://www.nabble.com/debugging-a-Wicket-application-running-under-Jetty
-6.1-in-Eclipse-tp22979929p22980041.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: debugging a Wicket application running under Jetty-6.1 in
Eclipse
Posted by jcgarciam <jc...@gmail.com>.
I'll suggest to do it in the Wicket Way, you will have much more benefits.
If you made your project from the QuickStart, you will notice a 'Start'
class under your 'test' source.
that what it does is just start an embedded jetty pointing to your webapp
directory and mounting your application under "/" context.
so just right click on it and click "Debug as" -> Java Application and
you're done.
Even if you are working on a multi-module maven project this will work,
just make sure your module are installed on your local repository, issuing
'mvn install' on the root project.
If you have question regarding the 'Start.java' class just let us know.
mchenini wrote:
>
> Hi,
>
>
>
> This is about debugging a Wicket application running under Jetty-6.1 in
> Eclipse.
>
>
>
> I followed the steps shown at:
> http://docs.codehaus.org/display/JETTY/Debugging+with+the+Maven+Jetty+Pl
> ugin+inside+Eclipse
>
> But I am getting this exception:
>
>
>
> java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher
>
>
> Exception in thread "main"
>
>
> Any help?
>
>
> The steps I followed are:
>
>
> Step 1
> Go to the Run/External Tools/External Tools ..." menu item on the "Run"
> menu bar. Select "Program" and click the "New" button. On the "Main"
> tab, fill in the "Location:" as the full path to your "mvn" executable.
> C:\java\DEVTOOLS\MAIN\maven2\bin
>
> For the "Working Directory:" select the workspace that matches your
> webapp. For "Arguments:" add jetty:run.
>
> Move to the "Environment" tab and click the "New" button to add a new
> variable named MAVEN_OPTS with the value:
>
> -Xdebug -Xnoagent -Djava.compiler=NONE
> -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y
>
> If you supply suspend=n instead of suspend=y you can start immediately
> without running the debugger and launch the debugger at anytime you
> really wish to debug.
>
>
>
> Step 2
>
> Then, pull up the "Run/Debug/Debug ..." menu item and select "Remote
> Java Application" and click the "New" button. Fill in the dialog by
> selecting your webapp project for the "Project:" field, and ensure you
> are using the same port number as you specified in the address= property
> above.
>
> Now all you need to do is to Run/External Tools and select the name of
> the maven tool setup you created in step 1 to start the plugin and then
> Run/Debug and select the name of the debug setup you setup in step2.
>
>
>
>
>
>
>
> Thanks,
>
> Mohamed
>
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>
>
--
View this message in context: http://www.nabble.com/debugging-a-Wicket-application-running-under-Jetty-6.1-in-Eclipse-tp22979929p22980041.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org