On 9/4/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>
> make sure your wicket-1.3.0-beta3 jar is good, looks like tomcat has a
> problem opening it and finding the webapp calss.


The JAR file is good.  I was able to compile against it and look at it and
unzip it to look at the files and confirm the paths for the correct package.

also on a related note hellowicket.html should be in the same dir as
> hellowicket.java


Thank you for this note.  I thought that it had to be in the same location
as the base of the package.

if you cant get it to work i strongly recommend creating an app using our
> maven2 quickstart archetype. you can then launch it in one of two ways

either using mvn jetty:jetty or by simply launching the Start class that
> comes with it


-igor
>

I had no problem getting the wicket-quickstart-1.2.6 to work.  However, that
works with a very specific configuration that doesn't meet my needs.  When I
did try to add an application to that set-up, I got some Jetty errors in
Eclipse's console that I didn't bother to troubleshoot because learning
Jetty would be counter-productive right now.  While I can get the quickstart
to work using Eclipse, I need to create and deploy a portable application
that works with the latest versions of Tomcat and Wicket and I need to
understand the structure and deployment of that application.

I know I'm a novice here and I have a lot to learn, but learning the details
is really my goal.  It won't be enough to just get it working.

Thank you,
    Vince

Reply via email to