Re: [T5.0.18] Class re-loading and eclipse debugger
On Thu, Mar 19, 2009 at 11:26 AM, Hugues Narjoux wrote: > I commented out the line :// > webapp.setDefaultsDescriptor(webapp.getResourceBase() + > "/WEB-INF/webdefault.xml"); > > and it works just G-R-E-A-T !!! Since I've worked with Jetty for the first time I just cannot think of using any other servlet container. Simple, fast, easily embeddable in your code. :) > Just one thing for those who would follow the same path: don't forget this : > http://tapestry.apache.org/tapestry5/jetty.html > Make sure the log4j version is at least 1.2.12 Maybe we should add this warning to that page . . . -- Thiago - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [T5.0.18] Class re-loading and eclipse debugger
I commented out the line :// webapp.setDefaultsDescriptor(webapp.getResourceBase() + "/WEB-INF/webdefault.xml"); and it works just G-R-E-A-T !!! Just one thing for those who would follow the same path: don't forget this : http://tapestry.apache.org/tapestry5/jetty.html Make sure the log4j version is at least 1.2.12 Thanks a lot ! On Thu, Mar 19, 2009 at 3:16 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Thu, Mar 19, 2009 at 11:11 AM, Hugues Narjoux > wrote: > > Thanks, looks like I am getting closer and closer ! But I alway get a > 404... > > Make sure TapestryFilter is being loaded by putting a breakpoint > inside it. If not, your Jetty configuration may be wrong. > > > What does your webdefault.xml look like please ? > > Exactly like this: > > http://ars-machina.svn.sourceforge.net/viewvc/ars-machina/example/trunk/src/main/webapp/WEB-INF/webdefault.xml?revision=424&content-type=text%2Fplain > > You just need it if you're working on a Windows machine. > > -- > Thiago > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
Re: [T5.0.18] Class re-loading and eclipse debugger
On Thu, Mar 19, 2009 at 11:11 AM, Hugues Narjoux wrote: > Thanks, looks like I am getting closer and closer ! But I alway get a 404... Make sure TapestryFilter is being loaded by putting a breakpoint inside it. If not, your Jetty configuration may be wrong. > What does your webdefault.xml look like please ? Exactly like this: http://ars-machina.svn.sourceforge.net/viewvc/ars-machina/example/trunk/src/main/webapp/WEB-INF/webdefault.xml?revision=424&content-type=text%2Fplain You just need it if you're working on a Windows machine. -- Thiago - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [T5.0.18] Class re-loading and eclipse debugger
Thanks, looks like I am getting closer and closer ! But I alway get a 404...
What does your webdefault.xml look like please ?
Cheers
Hugues
On Thu, Mar 19, 2009 at 1:15 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Thu, Mar 19, 2009 at 5:17 AM, Hugues Narjoux
> wrote:
> > I will try launching jetty using a java class. If I can do this, it will
> > solve all my pbs,,,
>
> This is exactly the code I use:
>
> Server server = new Server();
>
> Connector connector = new SelectChannelConnector();
> connector.setPort(80);
> server.setConnectors(new Connector[] { connector });
>
> WebAppContext webapp = new WebAppContext();
> webapp.setParentLoaderPriority(true);
> webapp.setContextPath("/");
> webapp.setResourceBase("src/main/webapp");
> webapp.setDefaultsDescriptor(webapp.getResourceBase() +
> "/WEB-INF/webdefault.xml");
> server.setHandler(webapp);
>
> server.start();
> server.join();
>
> --
> Thiago
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
Re: [T5.0.18] Class re-loading and eclipse debugger
On Thu, Mar 19, 2009 at 5:17 AM, Hugues Narjoux wrote:
> I will try launching jetty using a java class. If I can do this, it will
> solve all my pbs,,,
This is exactly the code I use:
Server server = new Server();
Connector connector = new SelectChannelConnector();
connector.setPort(80);
server.setConnectors(new Connector[] { connector });
WebAppContext webapp = new WebAppContext();
webapp.setParentLoaderPriority(true);
webapp.setContextPath("/");
webapp.setResourceBase("src/main/webapp");
webapp.setDefaultsDescriptor(webapp.getResourceBase() +
"/WEB-INF/webdefault.xml");
server.setHandler(webapp);
server.start();
server.join();
--
Thiago
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [T5.0.18] Class re-loading and eclipse debugger
Thanks for the suggestion but most of the work is done in the process-resources phase. Skipping the tests will not help. But I think this is not related to Tapestry anymore :) I will try launching jetty using a java class. If I can do this, it will solve all my pbs,,, For reference here is what I intend to do: http://docs.codehaus.org/display/JETTY/Embedding+Jetty http://www.codecommit.com/blog/java/so-long-wtp-embedded-jetty-for-me <http://www.codecommit.com/blog/java/so-long-wtp-embedded-jetty-for-me> Cheers Hugues On Wed, Mar 18, 2009 at 9:44 PM, Robert Zeigler wrote: > 5 minute test compilation?!? Wow... > Ok, so, how about: > > mvn -DskipTests jetty:run > > This will disable the test phase of the app, and, consequently, skip > test-source compilation. > > Cheers, > > Robert > > > On Mar 18, 2009, at 3/1811:32 AM , Hugues Narjoux wrote: > > But if you disable the automatic publishing, how would your modifications >> be >> updated ? I tried it, even with manual publising and I still do not see >> my >> the results of my update ... >> I tried the maven jetty plugin like Borut suggested.It works just fine as >> for class reloading. Except that every time you restart your server (mvn >> jettty:run) it runs the whole test-compile phase which in my case takes >> more >> than 5 minutes (don't ask why ;) ). Therefore I cannot use it for >> development. >> >> >> >> >> >> On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < >> p.stavrini...@albourne.com> wrote: >> >> This is a pain, and has been an issue for years already... and >>> unfortunately there is no end in site. There is a minor tweak though, WTP >>> has an option (in Tomcat server properties dialog) select 'never publish >>> automatically' >>> >>> regards, >>> Peter >>> >>> - Original Message - >>> From: "Thiago H. de Paula Figueiredo" >>> To: "Tapestry users" >>> Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, >>> Bucharest, Istanbul >>> Subject: Re: [T5.0.18] Class re-loading and eclipse debugger >>> >>> On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux >>> wrote: >>> >>>> WTP was great here because it >>>> would let you configure a deployment descriptor and automaticaly deploy >>>> >>> and >>> >>>> re-assemble your webapp. >>>> >>> >>> I guess the problem is exactly the reassemble process. Many times, >>> when using WTP in a Struts (aargh!) project, it >>> wouldn't update the application correctly when I changed one class. >>> Then I gave up. I never really deploy an application in development, >>> just when really deploying to the production server, not wasting a lot >>> of time with it. >>> >>> -- >>> Thiago >>> >>> - >>> 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 > >
Re: [T5.0.18] Class re-loading and eclipse debugger
5 minute test compilation?!? Wow... Ok, so, how about: mvn -DskipTests jetty:run This will disable the test phase of the app, and, consequently, skip test-source compilation. Cheers, Robert On Mar 18, 2009, at 3/1811:32 AM , Hugues Narjoux wrote: But if you disable the automatic publishing, how would your modifications be updated ? I tried it, even with manual publising and I still do not see my the results of my update ... I tried the maven jetty plugin like Borut suggested.It works just fine as for class reloading. Except that every time you restart your server (mvn jettty:run) it runs the whole test-compile phase which in my case takes more than 5 minutes (don't ask why ;) ). Therefore I cannot use it for development. On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: This is a pain, and has been an issue for years already... and unfortunately there is no end in site. There is a minor tweak though, WTP has an option (in Tomcat server properties dialog) select 'never publish automatically' regards, Peter - Original Message - From: "Thiago H. de Paula Figueiredo" To: "Tapestry users" Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: [T5.0.18] Class re-loading and eclipse debugger On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux wrote: WTP was great here because it would let you configure a deployment descriptor and automaticaly deploy and re-assemble your webapp. I guess the problem is exactly the reassemble process. Many times, when using WTP in a Struts (aargh!) project, it wouldn't update the application correctly when I changed one class. Then I gave up. I never really deploy an application in development, just when really deploying to the production server, not wasting a lot of time with it. -- Thiago - 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
Re: [T5.0.18] Class re-loading and eclipse debugger
+1 @Robert to mvn jetty:run. Portable to other IDEs as well as from command line. -Luther On Wed, Mar 18, 2009 at 12:57 PM, Hugues Narjoux wrote: > "Are you on windows? what Maven plug-in version are you running? on Ubuntu > it doesn't do this (there are some configuration options on the plug-in, > try > uncheck the ones you don't need)." > No, the reason is we are running fancy home-brewed maven plugins processing > zip files all around ... and this just takes hours > > On Wed, Mar 18, 2009 at 6:07 PM, Peter Stavrinides < > p.stavrini...@albourne.com> wrote: > > > Tomcat in the eclipse WTP can be very sensitive, I spent hours fiddling > > with it, so if you can use Jetty then forget Tomcat. I just happen to use > > both... Jetty mostly but sometimes Tomcat when I need to attach library > > modules to debug and edit. Live reloading can almost work right in Tomcat > > but not like Jetty, instead it does a partial reload (with some > complaints > > about resources being out of sync), nevertheless it can sort of work. > > > > >it runs the whole test-compile phase which in my case takes more > > >than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > > >development. > > Are you on windows? what Maven plug-in version are you running? on Ubuntu > > it doesn't do this (there are some configuration options on the plug-in, > try > > uncheck the ones you don't need). > > > > regards, > > Peter > > > > > > - Original Message ----- > > From: "Hugues Narjoux" > > To: "Tapestry users" > > Sent: Wednesday, 18 March, 2009 18:32:20 GMT +02:00 Athens, Beirut, > > Bucharest, Istanbul > > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > > > But if you disable the automatic publishing, how would your modifications > > be > > updated ? I tried it, even with manual publising and I still do not see > my > > the results of my update ... > > I tried the maven jetty plugin like Borut suggested.It works just fine as > > for class reloading. Except that every time you restart your server (mvn > > jettty:run) it runs the whole test-compile phase which in my case takes > > more > > than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > > development. > > > > > > > > > > > > On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < > > p.stavrini...@albourne.com> wrote: > > > > > This is a pain, and has been an issue for years already... and > > > unfortunately there is no end in site. There is a minor tweak though, > WTP > > > has an option (in Tomcat server properties dialog) select 'never > publish > > > automatically' > > > > > > regards, > > > Peter > > > > > > - Original Message - > > > From: "Thiago H. de Paula Figueiredo" > > > To: "Tapestry users" > > > Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, > > > Bucharest, Istanbul > > > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > > > > > On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux > > > wrote: > > > > WTP was great here because it > > > > would let you configure a deployment descriptor and automaticaly > deploy > > > and > > > > re-assemble your webapp. > > > > > > I guess the problem is exactly the reassemble process. Many times, > > > when using WTP in a Struts (aargh!) project, it > > > wouldn't update the application correctly when I changed one class. > > > Then I gave up. I never really deploy an application in development, > > > just when really deploying to the production server, not wasting a lot > > > of time with it. > > > > > > -- > > > Thiago > > > > > > - > > > 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 > > > > >
Re: [T5.0.18] Class re-loading and eclipse debugger
"Are you on windows? what Maven plug-in version are you running? on Ubuntu it doesn't do this (there are some configuration options on the plug-in, try uncheck the ones you don't need)." No, the reason is we are running fancy home-brewed maven plugins processing zip files all around ... and this just takes hours On Wed, Mar 18, 2009 at 6:07 PM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: > Tomcat in the eclipse WTP can be very sensitive, I spent hours fiddling > with it, so if you can use Jetty then forget Tomcat. I just happen to use > both... Jetty mostly but sometimes Tomcat when I need to attach library > modules to debug and edit. Live reloading can almost work right in Tomcat > but not like Jetty, instead it does a partial reload (with some complaints > about resources being out of sync), nevertheless it can sort of work. > > >it runs the whole test-compile phase which in my case takes more > >than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > >development. > Are you on windows? what Maven plug-in version are you running? on Ubuntu > it doesn't do this (there are some configuration options on the plug-in, try > uncheck the ones you don't need). > > regards, > Peter > > > - Original Message - > From: "Hugues Narjoux" > To: "Tapestry users" > Sent: Wednesday, 18 March, 2009 18:32:20 GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > But if you disable the automatic publishing, how would your modifications > be > updated ? I tried it, even with manual publising and I still do not see my > the results of my update ... > I tried the maven jetty plugin like Borut suggested.It works just fine as > for class reloading. Except that every time you restart your server (mvn > jettty:run) it runs the whole test-compile phase which in my case takes > more > than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > development. > > > > > > On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < > p.stavrini...@albourne.com> wrote: > > > This is a pain, and has been an issue for years already... and > > unfortunately there is no end in site. There is a minor tweak though, WTP > > has an option (in Tomcat server properties dialog) select 'never publish > > automatically' > > > > regards, > > Peter > > > > - Original Message - > > From: "Thiago H. de Paula Figueiredo" > > To: "Tapestry users" > > Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, > > Bucharest, Istanbul > > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > > > On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux > > wrote: > > > WTP was great here because it > > > would let you configure a deployment descriptor and automaticaly deploy > > and > > > re-assemble your webapp. > > > > I guess the problem is exactly the reassemble process. Many times, > > when using WTP in a Struts (aargh!) project, it > > wouldn't update the application correctly when I changed one class. > > Then I gave up. I never really deploy an application in development, > > just when really deploying to the production server, not wasting a lot > > of time with it. > > > > -- > > Thiago > > > > - > > 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 > >
Re: [T5.0.18] Class re-loading and eclipse debugger
Yes. Kalle On Wed, Mar 18, 2009 at 10:22 AM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: > I particularly liked Sysdeo and used it for a while, but with a newer > version of eclipse it stopped working so I tanked it. Do you use it with > eclipse 3.4 and Java 6 ? > > Peter > > - Original Message - > From: "Peter Stavrinides" > To: "Tapestry users" > Sent: Wednesday, 18 March, 2009 19:19:53 GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > Yes, but the problem with these is exactly what you mentioned, they are not > being maintained, once you move to newer versions of Tomcat and Java 6 then > you are going to have some fun! > > -- > If you are not an intended recipient of this e-mail, please notify the > sender, delete it and do not read, act upon, print, disclose, copy, retain > or redistribute it. Please visit http://www.albourne.com/email.html for > important additional terms relating to this e-mail. > > - Original Message - > From: "Kalle Korhonen" > To: "Tapestry users" > Sent: Wednesday, 18 March, 2009 19:16:13 GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > There are perfectly good Tomcat launchers for Eclipse as well that don't > use > the cumbersome WTP infrastructure that copies files around (causing these > issues and bad performance). http://merve.sourceforge.net/ works exactly > like Jetty launcher (but hasn't been updated for a while) and Sysdeo's > Tomcat plugin http://www.eclipsetotale.com/tomcatPlugin.html that offers > more features. > > Kalle > > > On Wed, Mar 18, 2009 at 10:07 AM, Peter Stavrinides < > p.stavrini...@albourne.com> wrote: > > > Tomcat in the eclipse WTP can be very sensitive, I spent hours fiddling > > with it, so if you can use Jetty then forget Tomcat. I just happen to use > > both... Jetty mostly but sometimes Tomcat when I need to attach library > > modules to debug and edit. Live reloading can almost work right in Tomcat > > but not like Jetty, instead it does a partial reload (with some > complaints > > about resources being out of sync), nevertheless it can sort of work. > > > > >it runs the whole test-compile phase which in my case takes more > > >than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > > >development. > > Are you on windows? what Maven plug-in version are you running? on Ubuntu > > it doesn't do this (there are some configuration options on the plug-in, > try > > uncheck the ones you don't need). > > > > regards, > > Peter > > > > > > - Original Message - > > From: "Hugues Narjoux" > > To: "Tapestry users" > > Sent: Wednesday, 18 March, 2009 18:32:20 GMT +02:00 Athens, Beirut, > > Bucharest, Istanbul > > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > > > But if you disable the automatic publishing, how would your modifications > > be > > updated ? I tried it, even with manual publising and I still do not see > my > > the results of my update ... > > I tried the maven jetty plugin like Borut suggested.It works just fine as > > for class reloading. Except that every time you restart your server (mvn > > jettty:run) it runs the whole test-compile phase which in my case takes > > more > > than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > > development. > > > > > > > > > > > > On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < > > p.stavrini...@albourne.com> wrote: > > > > > This is a pain, and has been an issue for years already... and > > > unfortunately there is no end in site. There is a minor tweak though, > WTP > > > has an option (in Tomcat server properties dialog) select 'never > publish > > > automatically' > > > > > > regards, > > > Peter > > > > > > - Original Message - > > > From: "Thiago H. de Paula Figueiredo" > > > To: "Tapestry users" > > > Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, > > > Bucharest, Istanbul > > > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > > > > > On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux > > > wrote: > > > > WTP was great here because it > > > > would let you configure a de
Re: [T5.0.18] Class re-loading and eclipse debugger
Thats what I use Robert, we also use a local nexus repo as we have about 50 megs of jars. - Original Message - From: "Robert Zeigler" To: "Tapestry users" Sent: Wednesday, 18 March, 2009 19:20:21 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: [T5.0.18] Class re-loading and eclipse debugger Personally, I use the m2eclipse plugin, and just define a new maven run configuration to jetty:run. But that's if you're using maven to control your build. :) Robert On Mar 18, 2009, at 3/1812:16 PM , Kalle Korhonen wrote: > There are perfectly good Tomcat launchers for Eclipse as well that > don't use > the cumbersome WTP infrastructure that copies files around (causing > these > issues and bad performance). http://merve.sourceforge.net/ works > exactly > like Jetty launcher (but hasn't been updated for a while) and Sysdeo's > Tomcat plugin http://www.eclipsetotale.com/tomcatPlugin.html that > offers > more features. > > Kalle > > > On Wed, Mar 18, 2009 at 10:07 AM, Peter Stavrinides < > p.stavrini...@albourne.com> wrote: > >> Tomcat in the eclipse WTP can be very sensitive, I spent hours >> fiddling >> with it, so if you can use Jetty then forget Tomcat. I just happen >> to use >> both... Jetty mostly but sometimes Tomcat when I need to attach >> library >> modules to debug and edit. Live reloading can almost work right in >> Tomcat >> but not like Jetty, instead it does a partial reload (with some >> complaints >> about resources being out of sync), nevertheless it can sort of work. >> >>> it runs the whole test-compile phase which in my case takes more >>> than 5 minutes (don't ask why ;) ). Therefore I cannot use it for >>> development. >> Are you on windows? what Maven plug-in version are you running? on >> Ubuntu >> it doesn't do this (there are some configuration options on the >> plug-in, try >> uncheck the ones you don't need). >> >> regards, >> Peter >> >> >> - Original Message - >> From: "Hugues Narjoux" >> To: "Tapestry users" >> Sent: Wednesday, 18 March, 2009 18:32:20 GMT +02:00 Athens, Beirut, >> Bucharest, Istanbul >> Subject: Re: [T5.0.18] Class re-loading and eclipse debugger >> >> But if you disable the automatic publishing, how would your >> modifications >> be >> updated ? I tried it, even with manual publising and I still do >> not see my >> the results of my update ... >> I tried the maven jetty plugin like Borut suggested.It works just >> fine as >> for class reloading. Except that every time you restart your server >> (mvn >> jettty:run) it runs the whole test-compile phase which in my case >> takes >> more >> than 5 minutes (don't ask why ;) ). Therefore I cannot use it for >> development. >> >> >> >> >> >> On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < >> p.stavrini...@albourne.com> wrote: >> >>> This is a pain, and has been an issue for years already... and >>> unfortunately there is no end in site. There is a minor tweak >>> though, WTP >>> has an option (in Tomcat server properties dialog) select 'never >>> publish >>> automatically' >>> >>> regards, >>> Peter >>> >>> - Original Message - >>> From: "Thiago H. de Paula Figueiredo" >>> To: "Tapestry users" >>> Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, >>> Bucharest, Istanbul >>> Subject: Re: [T5.0.18] Class re-loading and eclipse debugger >>> >>> On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux >>> wrote: >>>> WTP was great here because it >>>> would let you configure a deployment descriptor and automaticaly >>>> deploy >>> and >>>> re-assemble your webapp. >>> >>> I guess the problem is exactly the reassemble process. Many times, >>> when using WTP in a Struts (aargh!) project, it >>> wouldn't update the application correctly when I changed one class. >>> Then I gave up. I never really deploy an application in development, >>> just when really deploying to the production server, not wasting a >>> lot >>> of time with it. >>> >>> -- >>> Thiago >>> >>> - >>>
Re: [T5.0.18] Class re-loading and eclipse debugger
I particularly liked Sysdeo and used it for a while, but with a newer version of eclipse it stopped working so I tanked it. Do you use it with eclipse 3.4 and Java 6 ? Peter - Original Message - From: "Peter Stavrinides" To: "Tapestry users" Sent: Wednesday, 18 March, 2009 19:19:53 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: [T5.0.18] Class re-loading and eclipse debugger Yes, but the problem with these is exactly what you mentioned, they are not being maintained, once you move to newer versions of Tomcat and Java 6 then you are going to have some fun! -- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Please visit http://www.albourne.com/email.html for important additional terms relating to this e-mail. - Original Message - From: "Kalle Korhonen" To: "Tapestry users" Sent: Wednesday, 18 March, 2009 19:16:13 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: [T5.0.18] Class re-loading and eclipse debugger There are perfectly good Tomcat launchers for Eclipse as well that don't use the cumbersome WTP infrastructure that copies files around (causing these issues and bad performance). http://merve.sourceforge.net/ works exactly like Jetty launcher (but hasn't been updated for a while) and Sysdeo's Tomcat plugin http://www.eclipsetotale.com/tomcatPlugin.html that offers more features. Kalle On Wed, Mar 18, 2009 at 10:07 AM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: > Tomcat in the eclipse WTP can be very sensitive, I spent hours fiddling > with it, so if you can use Jetty then forget Tomcat. I just happen to use > both... Jetty mostly but sometimes Tomcat when I need to attach library > modules to debug and edit. Live reloading can almost work right in Tomcat > but not like Jetty, instead it does a partial reload (with some complaints > about resources being out of sync), nevertheless it can sort of work. > > >it runs the whole test-compile phase which in my case takes more > >than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > >development. > Are you on windows? what Maven plug-in version are you running? on Ubuntu > it doesn't do this (there are some configuration options on the plug-in, try > uncheck the ones you don't need). > > regards, > Peter > > > - Original Message - > From: "Hugues Narjoux" > To: "Tapestry users" > Sent: Wednesday, 18 March, 2009 18:32:20 GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > But if you disable the automatic publishing, how would your modifications > be > updated ? I tried it, even with manual publising and I still do not see my > the results of my update ... > I tried the maven jetty plugin like Borut suggested.It works just fine as > for class reloading. Except that every time you restart your server (mvn > jettty:run) it runs the whole test-compile phase which in my case takes > more > than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > development. > > > > > > On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < > p.stavrini...@albourne.com> wrote: > > > This is a pain, and has been an issue for years already... and > > unfortunately there is no end in site. There is a minor tweak though, WTP > > has an option (in Tomcat server properties dialog) select 'never publish > > automatically' > > > > regards, > > Peter > > > > - Original Message - > > From: "Thiago H. de Paula Figueiredo" > > To: "Tapestry users" > > Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, > > Bucharest, Istanbul > > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > > > On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux > > wrote: > > > WTP was great here because it > > > would let you configure a deployment descriptor and automaticaly deploy > > and > > > re-assemble your webapp. > > > > I guess the problem is exactly the reassemble process. Many times, > > when using WTP in a Struts (aargh!) project, it > > wouldn't update the application correctly when I changed one class. > > Then I gave up. I never really deploy an application in development, > > just when really deploying to the production server, not wasting a lot > > of time with it. > > > > -- > > Thiago > > > > - > > To u
Re: [T5.0.18] Class re-loading and eclipse debugger
I use Tomcat 6 and Java 6 with Sysdeo's plugin without any problems whatsoever. I also use use Jetty launcher. Kalle On Wed, Mar 18, 2009 at 10:19 AM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: > Yes, but the problem with these is exactly what you mentioned, they are not > being maintained, once you move to newer versions of Tomcat and Java 6 then > you are going to have some fun! > > -- > If you are not an intended recipient of this e-mail, please notify the > sender, delete it and do not read, act upon, print, disclose, copy, retain > or redistribute it. Please visit http://www.albourne.com/email.html for > important additional terms relating to this e-mail. > > - Original Message - > From: "Kalle Korhonen" > To: "Tapestry users" > Sent: Wednesday, 18 March, 2009 19:16:13 GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > There are perfectly good Tomcat launchers for Eclipse as well that don't > use > the cumbersome WTP infrastructure that copies files around (causing these > issues and bad performance). http://merve.sourceforge.net/ works exactly > like Jetty launcher (but hasn't been updated for a while) and Sysdeo's > Tomcat plugin http://www.eclipsetotale.com/tomcatPlugin.html that offers > more features. > > Kalle > > > On Wed, Mar 18, 2009 at 10:07 AM, Peter Stavrinides < > p.stavrini...@albourne.com> wrote: > > > Tomcat in the eclipse WTP can be very sensitive, I spent hours fiddling > > with it, so if you can use Jetty then forget Tomcat. I just happen to use > > both... Jetty mostly but sometimes Tomcat when I need to attach library > > modules to debug and edit. Live reloading can almost work right in Tomcat > > but not like Jetty, instead it does a partial reload (with some > complaints > > about resources being out of sync), nevertheless it can sort of work. > > > > >it runs the whole test-compile phase which in my case takes more > > >than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > > >development. > > Are you on windows? what Maven plug-in version are you running? on Ubuntu > > it doesn't do this (there are some configuration options on the plug-in, > try > > uncheck the ones you don't need). > > > > regards, > > Peter > > > > > > - Original Message - > > From: "Hugues Narjoux" > > To: "Tapestry users" > > Sent: Wednesday, 18 March, 2009 18:32:20 GMT +02:00 Athens, Beirut, > > Bucharest, Istanbul > > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > > > But if you disable the automatic publishing, how would your modifications > > be > > updated ? I tried it, even with manual publising and I still do not see > my > > the results of my update ... > > I tried the maven jetty plugin like Borut suggested.It works just fine as > > for class reloading. Except that every time you restart your server (mvn > > jettty:run) it runs the whole test-compile phase which in my case takes > > more > > than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > > development. > > > > > > > > > > > > On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < > > p.stavrini...@albourne.com> wrote: > > > > > This is a pain, and has been an issue for years already... and > > > unfortunately there is no end in site. There is a minor tweak though, > WTP > > > has an option (in Tomcat server properties dialog) select 'never > publish > > > automatically' > > > > > > regards, > > > Peter > > > > > > - Original Message - > > > From: "Thiago H. de Paula Figueiredo" > > > To: "Tapestry users" > > > Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, > > > Bucharest, Istanbul > > > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > > > > > On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux > > > wrote: > > > > WTP was great here because it > > > > would let you configure a deployment descriptor and automaticaly > deploy > > > and > > > > re-assemble your webapp. > > > > > > I guess the problem is exactly the reassemble process. Many times, > > > when using WTP in a Struts (aargh!) project, it > > > wouldn't update the application correctly when I changed one class. > > > Then I gave
Re: [T5.0.18] Class re-loading and eclipse debugger
Personally, I use the m2eclipse plugin, and just define a new maven run configuration to jetty:run. But that's if you're using maven to control your build. :) Robert On Mar 18, 2009, at 3/1812:16 PM , Kalle Korhonen wrote: There are perfectly good Tomcat launchers for Eclipse as well that don't use the cumbersome WTP infrastructure that copies files around (causing these issues and bad performance). http://merve.sourceforge.net/ works exactly like Jetty launcher (but hasn't been updated for a while) and Sysdeo's Tomcat plugin http://www.eclipsetotale.com/tomcatPlugin.html that offers more features. Kalle On Wed, Mar 18, 2009 at 10:07 AM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: Tomcat in the eclipse WTP can be very sensitive, I spent hours fiddling with it, so if you can use Jetty then forget Tomcat. I just happen to use both... Jetty mostly but sometimes Tomcat when I need to attach library modules to debug and edit. Live reloading can almost work right in Tomcat but not like Jetty, instead it does a partial reload (with some complaints about resources being out of sync), nevertheless it can sort of work. it runs the whole test-compile phase which in my case takes more than 5 minutes (don't ask why ;) ). Therefore I cannot use it for development. Are you on windows? what Maven plug-in version are you running? on Ubuntu it doesn't do this (there are some configuration options on the plug-in, try uncheck the ones you don't need). regards, Peter - Original Message - From: "Hugues Narjoux" To: "Tapestry users" Sent: Wednesday, 18 March, 2009 18:32:20 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: [T5.0.18] Class re-loading and eclipse debugger But if you disable the automatic publishing, how would your modifications be updated ? I tried it, even with manual publising and I still do not see my the results of my update ... I tried the maven jetty plugin like Borut suggested.It works just fine as for class reloading. Except that every time you restart your server (mvn jettty:run) it runs the whole test-compile phase which in my case takes more than 5 minutes (don't ask why ;) ). Therefore I cannot use it for development. On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: This is a pain, and has been an issue for years already... and unfortunately there is no end in site. There is a minor tweak though, WTP has an option (in Tomcat server properties dialog) select 'never publish automatically' regards, Peter - Original Message - From: "Thiago H. de Paula Figueiredo" To: "Tapestry users" Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: [T5.0.18] Class re-loading and eclipse debugger On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux wrote: WTP was great here because it would let you configure a deployment descriptor and automaticaly deploy and re-assemble your webapp. I guess the problem is exactly the reassemble process. Many times, when using WTP in a Struts (aargh!) project, it wouldn't update the application correctly when I changed one class. Then I gave up. I never really deploy an application in development, just when really deploying to the production server, not wasting a lot of time with it. -- Thiago - 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
Re: [T5.0.18] Class re-loading and eclipse debugger
Yes, but the problem with these is exactly what you mentioned, they are not being maintained, once you move to newer versions of Tomcat and Java 6 then you are going to have some fun! -- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Please visit http://www.albourne.com/email.html for important additional terms relating to this e-mail. - Original Message - From: "Kalle Korhonen" To: "Tapestry users" Sent: Wednesday, 18 March, 2009 19:16:13 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: [T5.0.18] Class re-loading and eclipse debugger There are perfectly good Tomcat launchers for Eclipse as well that don't use the cumbersome WTP infrastructure that copies files around (causing these issues and bad performance). http://merve.sourceforge.net/ works exactly like Jetty launcher (but hasn't been updated for a while) and Sysdeo's Tomcat plugin http://www.eclipsetotale.com/tomcatPlugin.html that offers more features. Kalle On Wed, Mar 18, 2009 at 10:07 AM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: > Tomcat in the eclipse WTP can be very sensitive, I spent hours fiddling > with it, so if you can use Jetty then forget Tomcat. I just happen to use > both... Jetty mostly but sometimes Tomcat when I need to attach library > modules to debug and edit. Live reloading can almost work right in Tomcat > but not like Jetty, instead it does a partial reload (with some complaints > about resources being out of sync), nevertheless it can sort of work. > > >it runs the whole test-compile phase which in my case takes more > >than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > >development. > Are you on windows? what Maven plug-in version are you running? on Ubuntu > it doesn't do this (there are some configuration options on the plug-in, try > uncheck the ones you don't need). > > regards, > Peter > > > - Original Message - > From: "Hugues Narjoux" > To: "Tapestry users" > Sent: Wednesday, 18 March, 2009 18:32:20 GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > But if you disable the automatic publishing, how would your modifications > be > updated ? I tried it, even with manual publising and I still do not see my > the results of my update ... > I tried the maven jetty plugin like Borut suggested.It works just fine as > for class reloading. Except that every time you restart your server (mvn > jettty:run) it runs the whole test-compile phase which in my case takes > more > than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > development. > > > > > > On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < > p.stavrini...@albourne.com> wrote: > > > This is a pain, and has been an issue for years already... and > > unfortunately there is no end in site. There is a minor tweak though, WTP > > has an option (in Tomcat server properties dialog) select 'never publish > > automatically' > > > > regards, > > Peter > > > > - Original Message - > > From: "Thiago H. de Paula Figueiredo" > > To: "Tapestry users" > > Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, > > Bucharest, Istanbul > > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > > > On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux > > wrote: > > > WTP was great here because it > > > would let you configure a deployment descriptor and automaticaly deploy > > and > > > re-assemble your webapp. > > > > I guess the problem is exactly the reassemble process. Many times, > > when using WTP in a Struts (aargh!) project, it > > wouldn't update the application correctly when I changed one class. > > Then I gave up. I never really deploy an application in development, > > just when really deploying to the production server, not wasting a lot > > of time with it. > > > > -- > > Thiago > > > > - > > 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
Re: [T5.0.18] Class re-loading and eclipse debugger
There are perfectly good Tomcat launchers for Eclipse as well that don't use the cumbersome WTP infrastructure that copies files around (causing these issues and bad performance). http://merve.sourceforge.net/ works exactly like Jetty launcher (but hasn't been updated for a while) and Sysdeo's Tomcat plugin http://www.eclipsetotale.com/tomcatPlugin.html that offers more features. Kalle On Wed, Mar 18, 2009 at 10:07 AM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: > Tomcat in the eclipse WTP can be very sensitive, I spent hours fiddling > with it, so if you can use Jetty then forget Tomcat. I just happen to use > both... Jetty mostly but sometimes Tomcat when I need to attach library > modules to debug and edit. Live reloading can almost work right in Tomcat > but not like Jetty, instead it does a partial reload (with some complaints > about resources being out of sync), nevertheless it can sort of work. > > >it runs the whole test-compile phase which in my case takes more > >than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > >development. > Are you on windows? what Maven plug-in version are you running? on Ubuntu > it doesn't do this (there are some configuration options on the plug-in, try > uncheck the ones you don't need). > > regards, > Peter > > > - Original Message - > From: "Hugues Narjoux" > To: "Tapestry users" > Sent: Wednesday, 18 March, 2009 18:32:20 GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > But if you disable the automatic publishing, how would your modifications > be > updated ? I tried it, even with manual publising and I still do not see my > the results of my update ... > I tried the maven jetty plugin like Borut suggested.It works just fine as > for class reloading. Except that every time you restart your server (mvn > jettty:run) it runs the whole test-compile phase which in my case takes > more > than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > development. > > > > > > On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < > p.stavrini...@albourne.com> wrote: > > > This is a pain, and has been an issue for years already... and > > unfortunately there is no end in site. There is a minor tweak though, WTP > > has an option (in Tomcat server properties dialog) select 'never publish > > automatically' > > > > regards, > > Peter > > > > - Original Message - > > From: "Thiago H. de Paula Figueiredo" > > To: "Tapestry users" > > Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, > > Bucharest, Istanbul > > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > > > On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux > > wrote: > > > WTP was great here because it > > > would let you configure a deployment descriptor and automaticaly deploy > > and > > > re-assemble your webapp. > > > > I guess the problem is exactly the reassemble process. Many times, > > when using WTP in a Struts (aargh!) project, it > > wouldn't update the application correctly when I changed one class. > > Then I gave up. I never really deploy an application in development, > > just when really deploying to the production server, not wasting a lot > > of time with it. > > > > -- > > Thiago > > > > - > > 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 > >
Re: [T5.0.18] Class re-loading and eclipse debugger
Tomcat in the eclipse WTP can be very sensitive, I spent hours fiddling with it, so if you can use Jetty then forget Tomcat. I just happen to use both... Jetty mostly but sometimes Tomcat when I need to attach library modules to debug and edit. Live reloading can almost work right in Tomcat but not like Jetty, instead it does a partial reload (with some complaints about resources being out of sync), nevertheless it can sort of work. >it runs the whole test-compile phase which in my case takes more >than 5 minutes (don't ask why ;) ). Therefore I cannot use it for >development. Are you on windows? what Maven plug-in version are you running? on Ubuntu it doesn't do this (there are some configuration options on the plug-in, try uncheck the ones you don't need). regards, Peter - Original Message - From: "Hugues Narjoux" To: "Tapestry users" Sent: Wednesday, 18 March, 2009 18:32:20 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: [T5.0.18] Class re-loading and eclipse debugger But if you disable the automatic publishing, how would your modifications be updated ? I tried it, even with manual publising and I still do not see my the results of my update ... I tried the maven jetty plugin like Borut suggested.It works just fine as for class reloading. Except that every time you restart your server (mvn jettty:run) it runs the whole test-compile phase which in my case takes more than 5 minutes (don't ask why ;) ). Therefore I cannot use it for development. On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: > This is a pain, and has been an issue for years already... and > unfortunately there is no end in site. There is a minor tweak though, WTP > has an option (in Tomcat server properties dialog) select 'never publish > automatically' > > regards, > Peter > > - Original Message - > From: "Thiago H. de Paula Figueiredo" > To: "Tapestry users" > Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux > wrote: > > WTP was great here because it > > would let you configure a deployment descriptor and automaticaly deploy > and > > re-assemble your webapp. > > I guess the problem is exactly the reassemble process. Many times, > when using WTP in a Struts (aargh!) project, it > wouldn't update the application correctly when I changed one class. > Then I gave up. I never really deploy an application in development, > just when really deploying to the production server, not wasting a lot > of time with it. > > -- > Thiago > > - > 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
Re: [T5.0.18] Class re-loading and eclipse debugger
But if you disable the automatic publishing, how would your modifications be updated ? I tried it, even with manual publising and I still do not see my the results of my update ... I tried the maven jetty plugin like Borut suggested.It works just fine as for class reloading. Except that every time you restart your server (mvn jettty:run) it runs the whole test-compile phase which in my case takes more than 5 minutes (don't ask why ;) ). Therefore I cannot use it for development. On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: > This is a pain, and has been an issue for years already... and > unfortunately there is no end in site. There is a minor tweak though, WTP > has an option (in Tomcat server properties dialog) select 'never publish > automatically' > > regards, > Peter > > - Original Message - > From: "Thiago H. de Paula Figueiredo" > To: "Tapestry users" > Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux > wrote: > > WTP was great here because it > > would let you configure a deployment descriptor and automaticaly deploy > and > > re-assemble your webapp. > > I guess the problem is exactly the reassemble process. Many times, > when using WTP in a Struts (aargh!) project, it > wouldn't update the application correctly when I changed one class. > Then I gave up. I never really deploy an application in development, > just when really deploying to the production server, not wasting a lot > of time with it. > > -- > Thiago > > - > 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 > >
Re: [T5.0.18] Class re-loading and eclipse debugger
This is a pain, and has been an issue for years already... and unfortunately there is no end in site. There is a minor tweak though, WTP has an option (in Tomcat server properties dialog) select 'never publish automatically' regards, Peter - Original Message - From: "Thiago H. de Paula Figueiredo" To: "Tapestry users" Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: [T5.0.18] Class re-loading and eclipse debugger On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux wrote: > WTP was great here because it > would let you configure a deployment descriptor and automaticaly deploy and > re-assemble your webapp. I guess the problem is exactly the reassemble process. Many times, when using WTP in a Struts (aargh!) project, it wouldn't update the application correctly when I changed one class. Then I gave up. I never really deploy an application in development, just when really deploying to the production server, not wasting a lot of time with it. -- Thiago - 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
Re: [T5.0.18] Class re-loading and eclipse debugger
On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux wrote: > WTP was great here because it > would let you configure a deployment descriptor and automaticaly deploy and > re-assemble your webapp. I guess the problem is exactly the reassemble process. Many times, when using WTP in a Struts (aargh!) project, it wouldn't update the application correctly when I changed one class. Then I gave up. I never really deploy an application in development, just when really deploying to the production server, not wasting a lot of time with it. -- Thiago - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [T5.0.18] Class re-loading and eclipse debugger
I just ran a test: when a java file is modified, WTP recompiles, publishes it to the server location automatically (so the .class file is updated) but tapestry won't see the change ... This is odd ... You're right, jetty or tomcat launchers are much easier to use. But I have an overly complex project structure where resources are scattered all over the place and arn't in a single directory. WTP was great here because it would let you configure a deployment descriptor and automaticaly deploy and re-assemble your webapp. I could not find the equivalent in jetty plugins or tomcats ... On Wed, Mar 18, 2009 at 2:36 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Wed, Mar 18, 2009 at 10:29 AM, Hugues Narjoux > wrote: > > Wow ! Thanks for the quick reply ! > > You're welcome! > > > However even if i ignore the message, the modification won't appear ... > > I don't use WTP for a very long time (it was much worse and error > prone than Tomcat Launcher), so I don't know what can be the problem. > I run Jetty directly, no plugins, just a small class with a main that > instantiates a server, a webapp context and runs them. :) > > > How does this class relaoding thing works ? Is tapestry detecting a > change > > in the .class file ? Or a change in the class loader ? > > Changes in .class files. Maybe your problem is exactly that: you > recompile a class, but the .class file that is in the classpath is not > updated. > > -- > Thiago > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
Re: [T5.0.18] Class re-loading and eclipse debugger
On Wed, Mar 18, 2009 at 10:29 AM, Hugues Narjoux wrote: > Wow ! Thanks for the quick reply ! You're welcome! > However even if i ignore the message, the modification won't appear ... I don't use WTP for a very long time (it was much worse and error prone than Tomcat Launcher), so I don't know what can be the problem. I run Jetty directly, no plugins, just a small class with a main that instantiates a server, a webapp context and runs them. :) > How does this class relaoding thing works ? Is tapestry detecting a change > in the .class file ? Or a change in the class loader ? Changes in .class files. Maybe your problem is exactly that: you recompile a class, but the .class file that is in the classpath is not updated. -- Thiago - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [T5.0.18] Class re-loading and eclipse debugger
Wow ! Thanks for the quick reply ! However even if i ignore the message, the modification won't appear ... How does this class relaoding thing works ? Is tapestry detecting a change in the .class file ? Or a change in the class loader ? Thanks Hugues On Wed, Mar 18, 2009 at 2:03 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Wed, Mar 18, 2009 at 10:00 AM, Hugues Narjoux > wrote: > > Hi, > > I am using Tapestry 5.0.18 and I read a lot about tapestry being able to > > reload classes without a restart. See: > > http://tapestry.apache.org/tapestry5/guide/reload.html > > > > But when I run my webapp in eclipse with WTP tools, and whenever I make a > > change to one of my page class, eclipse is always complaining that he > didn't > > succedd in reloading the class and the modification is not taken into > > account. > > > > Am I doing something wrong ? Is this an eclipse problem ? > > Just ignore the message. Eclipse doesn't know about Tapestry's live > class reloading, while the regular Java debugger one just handles > changes inside method bodies, not changes in class structure. > > -- > Thiago > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
Re: [T5.0.18] Class re-loading and eclipse debugger
Check this out http://bbwebcraft.blogspot.com/2009/01/task-3-rapid-turnaround-in-tapestry-5.html Cheers, borut 2009/3/18 Hugues Narjoux > Hi, > I am using Tapestry 5.0.18 and I read a lot about tapestry being able to > reload classes without a restart. See: > http://tapestry.apache.org/tapestry5/guide/reload.html > > But when I run my webapp in eclipse with WTP tools, and whenever I make a > change to one of my page class, eclipse is always complaining that he > didn't > succedd in reloading the class and the modification is not taken into > account. > > Am I doing something wrong ? Is this an eclipse problem ? > > Thanks, > Hugues >
Re: [T5.0.18] Class re-loading and eclipse debugger
On Wed, Mar 18, 2009 at 10:00 AM, Hugues Narjoux wrote: > Hi, > I am using Tapestry 5.0.18 and I read a lot about tapestry being able to > reload classes without a restart. See: > http://tapestry.apache.org/tapestry5/guide/reload.html > > But when I run my webapp in eclipse with WTP tools, and whenever I make a > change to one of my page class, eclipse is always complaining that he didn't > succedd in reloading the class and the modification is not taken into > account. > > Am I doing something wrong ? Is this an eclipse problem ? Just ignore the message. Eclipse doesn't know about Tapestry's live class reloading, while the regular Java debugger one just handles changes inside method bodies, not changes in class structure. -- Thiago - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
