You can deploy with Tomcat but you can't use the standard Tomcat deployment
tree; that is, something like this won't work:
.../webapps
- mywebapp
- WEB-INF
- classes
- html
- images
- styles
- scripts
You have to put the html for a given class in the same directory as the
class file. The CSS, images and scripts can go in directories below that,
but they can't be above. So when your warfile expands, the directory
structure should be something like this:
...
- classes
- com/mycompany/myproject/
- myapp.class
myclass.class
myclass.html
- styles
style.css
- images
myimage.jpg
Again, your classes could be in directories below your application class,
but any resources they need must be parallel or below.
It is possible to create an Eclipse project to work with this but I didn't
have good luck with WicketPanda. I found it got in my way, put things in
places where I couldn't use them anyway, and burned up a lot of time, so I
just create the files I need by hand. Our deployment creates its own tomcat
tree so the Eclipse Tomcat plugin is of no help to me (it would be a
different instance of Tomcat) so I debug by attaching to the running Tomcat
process.
To debug, you have to set JPDA_SUSPEND to "y" in catalina.sh and use the
command "catalina.sh jpda start" to start up Tomcat. Then you fire up the
Eclipse debugger, then you open up a browser and point to your website.
Good luck!
Vernon-13 wrote:
>
> I just dip into Wicket. I notice that Wicket setup exclusively with Jetty,
> for example, the quick start page
> http://wicket.apache.org/quickstart.html. Can I create an Eclipse project
> for TC instead of Jetty?
>
>
>
>
>
--
View this message in context:
http://www.nabble.com/Wicket-on-Tomcat--tp19848408p19857232.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
