The tutorial starts with Jetty run from Maven, but then switches over to
JettyLauncher midway through chapter 2.

The fact that you were not able to back out the changes suggests that you
may have something either missing, or duplicated in your classpath.  Watch
out for remnants of the earlier Tapestry jars. (As an aside, I occasionally
find Maven really mixes things up with versions as third-party libraries
come into the mix.  Always check your classpath.)

I strongly recommend JettyLauncher.  I use it for development, and then do a
final test and deploy on tomcat or JBoss. It's a dream. The only change I
made was to use JettyPlus to get datasources into the mix.  JettyLauncher
recognizes JettyPlus as well.

I hope something there helps.

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 08, 2008 1:18 PM
> To: users@tapestry.apache.org
> Subject: Re: new user help required
> 
> 
> Thank you Christian and Jonathan for your quick replies.
> 
> I'm not using Jetty Runner - I did install JettyLoader. I'm running
> Jetty from Maven command line because, as I recall, that is what is in
> the Tutorial. Anyway, the observed reloading behaviour is fine - I did
> suspect that perhaps only template changes show up automagically but
> thanks for the confirmation.
> 
> 
> > Exactly what step in the tutorial did you carry out between "working"
> and
> "broken"?
> 
> Chapter 3 in creating the GameOver page towards the end of the
> chapter. While the other @Property worked fine earlier in the
> tutorial, as soon as I added this page the other bits of code it no
> longer liked @Property. I tried reverting everything back but it still
> doesn't like it. I got the error from the link on the first page of
> HiLo, so I didn't even get as far as executing the new GameOver code.
> I had thought of just using the g/s instead, but that would be giving
> up; especially as @Property was working fine!
> 
> thanks,
> p.
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to