thanks for the help.

this thread started as me asking if anyone could shed some light on why it isn't working for me.

yet while no one including yourself could explain what I'm experiencing a few people confirmed that they experience the same behaviour.

and i'm not sure if you read the thread from the beginning, but howard's response was basically "use resin" which kind of confirms his disinterest in supporting this feature for tomcat.

anyway, back to the point, if anyone has any tips on how to get this to work in tomcat i'm all ears.

regards, paul.

Kalle Korhonen wrote:
Suit yourself but you shouldn't claim it doesn't work at all if you
can not get it working.

Kalle


On Mon, Jul 12, 2010 at 9:34 PM, Paul Stanton <p...@mapshed.com.au> wrote:
no kalle, i am not.

we cannot get tapestry's class reloading working with tomcat.

regards, paul.

Kalle Korhonen wrote:
On Mon, Jul 12, 2010 at 7:34 PM, Paul Stanton <p...@mapshed.com.au> wrote:

There's misinformation in this thread in that Tomcat does support
reloading
in a regular classloader, but does not support tapestry 5's class
reloading.
For example, under Tomcat, the implementation of a service will reload
fine,
however the implementation of a tapestry page or component class will
not.

You are confusing JVM hot code swapping with Tapestry's live class
reloading feature. Both work fine with Tomcat.

Kalle



Inge Solvoll wrote:

Strange, I've been explicitly told earlier on the mailing list that the
classloader of tomcat works in a way that doesn't allow the reloading
technique used by T5.

Happy to hear that this is wrong :)

On Wed, Jun 16, 2010 at 7:28 PM, Kalle Korhonen
<kalle.o.korho...@gmail.com>wrote:



Live class reloading works fine in Tomcat.

Kalle (just combating the misinformation)


On Wed, Jun 16, 2010 at 3:31 AM, Inge Solvoll <inge.tapes...@gmail.com>
wrote:


Unfortunately, live class reloading does not work in tomcat, only
jetty.

On Wed, Jun 16, 2010 at 12:25 PM, Paul Stanton <p...@mapshed.com.au>


wrote:


thanks sven,

does anyone know if there is an equivalent for tomcat?

also, note that this does not happen all the time, probably 10% of
the
time. the class re-loading problem is 100% of the time however.

regards, paul.


Sven Homburg wrote:



http://wiki.github.com/dpp/liftweb/how-to-fix-file-locking-problem-with-jettyrun-in-windows


with regards
Sven Homburg
Founder of the Chenille Kit Project
http://chenillekit.codehaus.org




2010/6/16 Paul Stanton <p...@mapshed.com.au>





howard,

my application classes are not packed up into jars. they are in
.class
files on the classpath (web-inf/classes). should they be reloaded?

i'm assuming it's due to tapestry extending the classes at runtime,


and


your classloader (via maven/jetty) somehow  handles this.. is there
no
way
to get this type of reloading support when your application classes


are


loose?

regards, paul.


Howard Lewis Ship wrote:





If classes are packaged up into JARs they will not be live
reloaded.
Use Jetty for development even if you use Tomcat for deployment.

On Tue, Jun 15, 2010 at 3:51 PM, Thiago H. de Paula Figueiredo
<thiag...@gmail.com> wrote:






On Tue, 15 Jun 2010 19:45:35 -0300, Paul Stanton <


p...@mapshed.com.au>


wrote:







http://tapestry.apache.org/tapestry5.1/guide/reload.html*

*Hi all,






Hi!







I've our project is set up so that tomcat runs from the
src/main/webapp
dir which contains jars and compiled code. Maven is set up to
maintains
the
jars within src/main/webapp/WEB-INF/lib and src/main/java and
src/main/resources compile to /src/main/webapp/WEB-INF/classes.

I'm aware that this is not quite the typical setup.






Why not Jetty, at least when developing?







Quite often a change to a resource such as a TML or a JS
referenced


by


an
@IncludeJavascript will cause a compile error if the web app is
running:
...The project was not built due to "Could not delete
'.../src/main/webapp/WEB-INF/classes/com'...
and any change to a tapestry page or component fails to


hot-replace.


I've seen this problem happening with Jetty too, but only on


Windows.


This
is a problem of file locking, not Tapestry itself or your setup.
I


use


Linux
and I've never met this problem. :)

--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant,
developer,
and
instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br




---------------------------------------------------------------------


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









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




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




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


Reply via email to