You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by akochnev <ak...@gmail.com> on 2008/11/20 05:27:18 UTC
Live class reloading problems
I'm running into some trouble w/ the live class reloading feature (the
template reloading works fine), tested both on Tomcat 6 , Glassfish 3
Prelude, and Glassfish V2 (all three servers support exploded war
deployment). If I re-deploy the application in these servers, then I get the
new version of the class. Everything works if I'm running it in Jetty (mvn
jetty:run).
Here's what I do ( I use NetBeans to go through these steps):
* Create a new project based on a quickstart archetype
* Changed the <archiveClasses> option in the war goal to false so that
re-deploying to the app server doesn't fail with the "manifest not found
problem"
* I run the app. I can successfully reload the Index page and it works OK.
Now, for testing the live reloading. Using the war:exploded target, I can
have the app running on the server, and without re-deploying the app in the
server, I can update the .tml files and the class files inside of the
target/app-name directory. However, T5 doesn't seem to pick up the class
changes neither in Tomcat nor in Glassfish. Interestingly enough, after I
run "mvn compile war:exploded", the next time I refresh the page, I see some
T5 output on the console indicating that the class is being transformed.
However, the output of the Index.class is the same as with the old version
of the class.
Any ideas about why this might be so ? Is anyone else developing on
something other than Jetty to confirm that the live class reloading works
for them ?
--
View this message in context: http://www.nabble.com/Live-class-reloading-problems-tp20594857p20594857.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Live class reloading problems
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Em Thu, 20 Nov 2008 01:27:18 -0300, akochnev <ak...@gmail.com> escreveu:
> I'm running into some trouble w/ the live class reloading feature (the
> template reloading works fine), tested both on Tomcat 6 , Glassfish 3
> Prelude, and Glassfish V2 (all three servers support exploded war
> deployment).
As far as I know, Tapestry's live class reloading never really worked in
Tomcat (because of it, not because of Tapestry), but I haven't tested it
for a while. I don't know about Glassfish.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Live class reloading problems
Posted by Geoff Callender <ge...@gmail.com>.
I use the Tomcat that's in JBoss, so it might be a little different,
but all it needs is reloadable="true" in the Context element of
context.xml. eg.
<Context cookies="true" crossContext="true" reloadable="true">
and the .tml files together with the .classes in the war's WEB-INF//
classes/. eg.
WEB-INF/classes/com/acme/myapp/pages/Index.tml
WEB-INF/classes/com/acme/myapp/pages/Index.class
Might be worth a try in vanilla Tomcat.
On 20/11/2008, at 9:59 PM, Hugo Palma wrote:
> I'm using Tomcat for development and both template and class live
> reloading
> work just fine.
>
> Although, i'm using the maven tomcat plugin to run the app in my
> laptop with
> the "mvn tomcat:run" command. I haven't tried it with my local
> instalation
> of tomcat. Can you try using the maven tomcat plugin and see if it
> works for
> you ?
>
> On Thu, Nov 20, 2008 at 4:27 AM, akochnev <ak...@gmail.com> wrote:
>
>>
>> I'm running into some trouble w/ the live class reloading feature
>> (the
>> template reloading works fine), tested both on Tomcat 6 ,
>> Glassfish 3
>> Prelude, and Glassfish V2 (all three servers support exploded war
>> deployment). If I re-deploy the application in these servers, then
>> I get
>> the
>> new version of the class. Everything works if I'm running it in
>> Jetty (mvn
>> jetty:run).
>>
>> Here's what I do ( I use NetBeans to go through these steps):
>> * Create a new project based on a quickstart archetype
>> * Changed the <archiveClasses> option in the war goal to false so
>> that
>> re-deploying to the app server doesn't fail with the "manifest not
>> found
>> problem"
>> * I run the app. I can successfully reload the Index page and it
>> works OK.
>>
>> Now, for testing the live reloading. Using the war:exploded target,
>> I can
>> have the app running on the server, and without re-deploying the
>> app in the
>> server, I can update the .tml files and the class files inside of the
>> target/app-name directory. However, T5 doesn't seem to pick up the
>> class
>> changes neither in Tomcat nor in Glassfish. Interestingly enough,
>> after I
>> run "mvn compile war:exploded", the next time I refresh the page, I
>> see
>> some
>> T5 output on the console indicating that the class is being
>> transformed.
>> However, the output of the Index.class is the same as with the old
>> version
>> of the class.
>>
>> Any ideas about why this might be so ? Is anyone else developing on
>> something other than Jetty to confirm that the live class reloading
>> works
>> for them ?
>> --
>> View this message in context:
>> http://www.nabble.com/Live-class-reloading-problems-tp20594857p20594857.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
Re: Live class reloading problems
Posted by Hugo Palma <hu...@gmail.com>.
I'm using Tomcat for development and both template and class live reloading
work just fine.
Although, i'm using the maven tomcat plugin to run the app in my laptop with
the "mvn tomcat:run" command. I haven't tried it with my local instalation
of tomcat. Can you try using the maven tomcat plugin and see if it works for
you ?
On Thu, Nov 20, 2008 at 4:27 AM, akochnev <ak...@gmail.com> wrote:
>
> I'm running into some trouble w/ the live class reloading feature (the
> template reloading works fine), tested both on Tomcat 6 , Glassfish 3
> Prelude, and Glassfish V2 (all three servers support exploded war
> deployment). If I re-deploy the application in these servers, then I get
> the
> new version of the class. Everything works if I'm running it in Jetty (mvn
> jetty:run).
>
> Here's what I do ( I use NetBeans to go through these steps):
> * Create a new project based on a quickstart archetype
> * Changed the <archiveClasses> option in the war goal to false so that
> re-deploying to the app server doesn't fail with the "manifest not found
> problem"
> * I run the app. I can successfully reload the Index page and it works OK.
>
> Now, for testing the live reloading. Using the war:exploded target, I can
> have the app running on the server, and without re-deploying the app in the
> server, I can update the .tml files and the class files inside of the
> target/app-name directory. However, T5 doesn't seem to pick up the class
> changes neither in Tomcat nor in Glassfish. Interestingly enough, after I
> run "mvn compile war:exploded", the next time I refresh the page, I see
> some
> T5 output on the console indicating that the class is being transformed.
> However, the output of the Index.class is the same as with the old version
> of the class.
>
> Any ideas about why this might be so ? Is anyone else developing on
> something other than Jetty to confirm that the live class reloading works
> for them ?
> --
> View this message in context:
> http://www.nabble.com/Live-class-reloading-problems-tp20594857p20594857.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>