You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Javier Molina <ja...@comunicamultimedia.com> on 2008/04/16 13:42:45 UTC
Automatic class reloading on Tomcat 6 not working for me
I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14 and 6.0.16). Automatic
class reloading doesn't work for pages (there are no components yet in this test
application, so I haven't checked that). Jetty 6 works fine and does autoreload pages.
Is this a known issue? Do I have to configure anything in Tomcat to get class reloading to
work?
Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by "Blower, Andy" <An...@proquest.co.uk>.
You're quite right, this is what's happening rather than the live class reloading. My mistake.
> -----Original Message-----
> From: Peter Stavrinides [mailto:p.stavrinides@albourne.com]
> Sent: 24 April 2008 07:14
> To: Tapestry users
> Subject: Re: AW: Automatic class reloading on Tomcat 6 not working for
> me
>
> Tomcat in eclipse has an Automatic publishing feature, which is not to
> be confused with live class reloading. Publishing requires a partial
> restart and republishes the war, you will notice the difference when
> your web application grows, running the same app under jetty reloading
> reloading is instant whereas under Tomcat it degrades significantly as
> it grows.
>
>
> Blower, Andy wrote:
> > Tomcat 5.5 live reloading works for me with Eclipse. I followed the
> setup process from the Tapestry 5 - Building Web Applications book and
> it works fine. I've not really got into figuring out how a real dev
> environment should be set up yet - I'm just evaluating/prototyping so
> far. I've not tried TC6.
> >
> >
> >> -----Original Message-----
> >> From: Peter Stavrinides [mailto:p.stavrinides@albourne.com]
> >> Sent: 23 April 2008 15:44
> >> To: Tapestry users
> >> Subject: Re: AW: Automatic class reloading on Tomcat 6 not working
> for
> >> me
> >>
> >> Hi Josh,
> >>
> >> I am pleasantly surprised to hear it works in IntelliJ, has anyone
> got
> >> it working in eclipse?
> >>
> >> Josh Canfield wrote:
> >>
> >>> Hmm... after reading the title again I guess the fact that it works
> >>>
> >> in
> >>
> >>> Tomcat 5.5 is irrelevant... sorry for the sidetrack.
> >>>
> >>> On Thu, Apr 17, 2008 at 10:01 AM, Josh Canfield
> >>>
> >> <jo...@thedailytube.com> wrote:
> >>
> >>>> I use Tomcat 5.5 and IntelliJ, I haven't tried tomcat in eclipse.
> >>>>
> >> I've
> >>
> >>>> found that if I don't allow IntelliJ to replace the classes while
> >>>> debugging then the Tapestry reloading will work. Otherwise, it
> might
> >>>> work once then goes back to the old class.
> >>>>
> >>>> Josh
> >>>>
> >>>>
> >>>> On Thu, Apr 17, 2008 at 2:44 AM, Martin Kersten
> >>>> <Ma...@mercateo.com> wrote:
> >>>>
> >>>>
> >>>>> Is it still true? I use hot replacement for components and
> somehow
> >>>>>
> >> the class
> >>
> >>>>> is reloaded. I thought this issue was solved. Do I miss
> something?
> >>>>> (Using also T6)
> >>>>>
> >>>>> -----Ursprüngliche Nachricht-----
> >>>>> Von: Peter Stavrinides [mailto:p.stavrinides@albourne.com]
> >>>>> Gesendet: Donnerstag, 17. April 2008 11:05
> >>>>> An: Tapestry users
> >>>>> Betreff: Re: AW: Automatic class reloading on Tomcat 6 not
> working
> >>>>>
> >> for me
> >>
> >>>>> You cannot use Tomcat for class reloading, this is not a bug,
> it's
> >>>>>
> >> a feature which apparently is a result of the limitations Java has
> for
> >> package traversal and exploration, Jetty somehow gets around this
> >> partially but its also not perfect...
> >>
> >>>>> http://tapestryjava.blogspot.com/2007/02/fighting-with-
> tomcat.html
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> Filip S. Adamsen wrote:
> >>>>>
> >>>>>
> >>>>>> There's an equivalent antiResource(s)Locking attribute as well
> >>>>>>
> >> that I
> >>
> >>>>>> think you might need.
> >>>>>>
> >>>>>> I use Jetty for all my development, though, and only test in
> >>>>>>
> >> Tomcat
> >>
> >>>>>> before deploying my applications.
> >>>>>>
> >>>>>> -Filip
> >>>>>>
> >>>>>> On 2008-04-16 18:45, Javier Molina wrote:
> >>>>>>
> >>>>>>
> >>>>>>> Do you work on Windows? I've changed my packaging to build a
> .jar
> >>>>>>> with my classes and put it in WEB-INF/lib instead of having the
> >>>>>>> exploded classes in WEB-INF/classes but once the webapp is
> >>>>>>>
> >> started, I
> >>
> >>>>>>> can't replace the .jar, the file is locked. I have tried to set
> >>>>>>> antiJARLocking="true" in the <Context> element but that doesn't
> >>>>>>>
> >> help.
> >>
> >>>>>>> Is anyone working with tapestry 5 and tomcat on windows with
> >>>>>>>
> >> working
> >>
> >>>>>>> auto-reload of classes?
> >>>>>>>
> >>>>>>> Filip S. Adamsen escribió:
> >>>>>>>
> >>>>>>>
> >>>>>>>> I believe the reloading is the only Tapestry-related thing
> >>>>>>>>
> >> affected
> >>
> >>>>>>>> by this. But I use Maven and archiveClasses in both
> development
> >>>>>>>>
> >> and
> >>
> >>>>>>>> production so I can't say for sure.
> >>>>>>>>
> >>>>>>>> -Filip
> >>>>>>>>
> >>>>>>>> On 2008-04-16 16:38, Stranzenbach, Ralf wrote:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> Hi.
> >>>>>>>>>
> >>>>>>>>> Does this "tomcat bug" affect only the class/page reloading
> >>>>>>>>>
> >> process
> >>
> >>>>>>>>> or is there any other significant problem that may arise
> during
> >>>>>>>>> development / production.
> >>>>>>>>>
> >>>>>>>>> I've tried to create a sample application using Tomcat +
> >>>>>>>>>
> >> Tapestry
> >>
> >>>>>>>>> 5.0.10 and everything seems to work fine beside that
> reloading
> >>>>>>>>>
> >> issues.
> >>
> >>>>>>>>> - Ralf
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> ________________________________
> >>>>>>>>>
> >>>>>>>>> Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
> >>>>>>>>> Gesendet: Mi 16.04.2008 16:36
> >>>>>>>>> An: Tapestry users
> >>>>>>>>> Betreff: Re: Automatic class reloading on Tomcat 6 not
> working
> >>>>>>>>>
> >> for
> >>
> >>>>>>>>> me
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Hi,
> >>>>>>>>>
> >>>>>>>>> Due to the way class loaders work in Tomcat you have to jar
> >>>>>>>>>
> >> your
> >>
> >>>>>>>>> classes etc. and put the jar into WEB-INF/lib.
> >>>>>>>>>
> >>>>>>>>> http://tapestry.apache.org/tapestry5/tomcat.html
> >>>>>>>>>
> >>>>>>>>> -Filip
> >>>>>>>>>
> >>>>>>>>> On 2008-04-16 13:42, Javier Molina wrote:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on
> >>>>>>>>>>
> >> 6.0.14
> >>
> >>>>>>>>>> and 6.0.16). Automatic class reloading doesn't work for
> pages
> >>>>>>>>>> (there are no components yet in this test application, so I
> >>>>>>>>>> haven't checked that).
> >>>>>>>>>> Jetty 6 works fine and does autoreload pages.
> >>>>>>>>>>
> >>>>>>>>>> Is this a known issue? Do I have to configure anything in
> >>>>>>>>>>
> >> Tomcat
> >>
> >>>>>>>>>> to get class reloading to work?
> >>>>>>>>>>
> >>>>>>>>>> Thank you.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>> -------------------------------------------------------------
> --
> >>>>>>>>>
> >> ----
> >>
> >>>>>>>>> -- To unsubscribe, e-mail: users-
> >>>>>>>>>
> >> unsubscribe@tapestry.apache.org
> >>
> >>>>>>>>> For additional commands, e-mail: users-
> help@tapestry.apache.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >> *******************************************************************
> >>
> >>>>>>>>> ********************************
> >>>>>>>>>
> >>>>>>>>> The information in this email is confidential and may be
> >>>>>>>>>
> >> legally
> >>
> >>>>>>>>> privileged. Access to this email by anyone other than the
> >>>>>>>>>
> >> intended
> >>
> >>>>>>>>> addressee is unauthorized. If you are not the intended
> >>>>>>>>>
> >> recipient of
> >>
> >>>>>>>>> this message, any review, disclosure, copying, distribution,
> >>>>>>>>> retention, or any action taken or omitted to be taken in
> >>>>>>>>>
> >> reliance
> >>
> >>>>>>>>> on it is prohibited and may be unlawful. If you are not the
> >>>>>>>>> intended recipient, please reply to or forward a copy of this
> >>>>>>>>> message to the sender and delete the message, any
> attachments,
> >>>>>>>>>
> >> and
> >>
> >>>>>>>>> any copies thereof from your system.
> >>>>>>>>>
> >>>>>>>>>
> >> *******************************************************************
> >>
> >>>>>>>>> ********************************
> >>>>>>>>>
> >>>>>>>>> BearingPoint GmbH
> >>>>>>>>> Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler
> >>>>>>>>> (stellv. Vorsitzender), Wilfried Erber, Werner Kreutzmann,
> >>>>>>>>> Hans-Werner Wurzel
> >>>>>>>>> Aufsichtsratsvorsitzender: Roderick McGeary
> >>>>>>>>> Sitz: Frankfurt am Main
> >>>>>>>>> Registergericht: Amtsgericht Frankfurt am Main HRB 55490
> >>>>>>>>>
> >>>>>>>>> -------------------------------------------------------------
> --
> >>>>>>>>>
> >> ----
> >>
> >>>>>>>>> -- To unsubscribe, e-mail: users-
> >>>>>>>>>
> >> unsubscribe@tapestry.apache.org
> >>
> >>>>>>>>> For additional commands, e-mail: users-
> help@tapestry.apache.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>> --------------------------------------------------------------
> --
> >>>>>>>>
> >> ----
> >>
> >>>>>>>> - To unsubscribe, e-mail: users-
> unsubscribe@tapestry.apache.org
> >>>>>>>> For additional commands, e-mail: users-
> help@tapestry.apache.org
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>> ---------------------------------------------------------------
> --
> >>>>>>>
> >> ----
> >>
> >>>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>> ----------------------------------------------------------------
> --
> >>>>>>
> >> ---
> >>
> >>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> -----------------------------------------------------------------
> --
> >>>>>
> >> --
> >>
> >>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>>
> >>>>>
> >>>>> -----------------------------------------------------------------
> --
> >>>>>
> >> --
> >>
> >>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>> --
> >>>> --
> >>>> TheDailyTube.com. Sign up and get the best new videos on the
> >>>>
> >> internet
> >>
> >>>> delivered fresh to your inbox.
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >> --------------------------------------------------------------------
> -
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by Don Ryan <do...@dit.ie>.
On 24 Apr 2008, at 07:14, Peter Stavrinides wrote:
> Tomcat in eclipse has an Automatic publishing feature, which is not
> to be confused with live class reloading.
I'm currently using Tomcat 6 with Eclipse/WTP. I'm not publishing
anything as I'm using the "Serve modules without publishing" option,
designed to get Tomcat to serve directly from the project folder.
Class reloading works flawlessly. (Well, as far as I can detect;
changes are instantly live, without a context reload or any other
kind of restart happening). My only difficulty at the moment is that
changes to templates in the context root (i.e. not under WEB-INF/
classes) are not picked up and require a restart.
It's clear from the variety of previous responses (ranging from
claims that you can't use Tomcat for class reloading to reported
success) that there is considerable confusion on this issue. As it's
something that so fundamentally affects developer productivity, it
would be great if someone could offer a definitive clarification on
where things stand. My understanding (from a quick preliminary trawl)
is as follows:
The current Tapestry 5 documentation indicates that Tomcat deployment
requires that you use the Maven war plugin archiveClasses option.
This workaround was first mentioned by Howard in the discussion on
Tapestry-1287. It seems that the source of the difficult, at the
time, was the following line in ComponentClassLocatorImpl:
Enumeration<URL> urls = _contextClassLoader.getResources(packagePath);
Howard felt that if you pass a folder to the above, you should get
back an enumeration of the folder's contents and he posted a Tomcat
bug to this extent:
https://issues.apache.org/bugzilla/show_bug.cgi?id=41664
The Tomcat people responded that their classloader implementation was
correct; that you should get back an object representing the folder
and you need to examine its contents yourself. Ben Sommerville then
submitted a patch that did this. His patch was eventually
incorporated into the Tapestry codebase via Tapestry-1333. This was
marked as Fixed back on 30th April, 2007. As such, it's not clear why
the archiveClasses workaround is still there in the documentation.
Unless, of course, it's required because of a totally separate issue
to the one that it was originally introduced to work around. Can
someone in the know clarify on this?
Regards,
Don.
P.S. If anyone has any pointers on the template reloading issue, that
would be great.
This message has been scanned for content and viruses by the DIT Information Services E-Mail Scanning Service, and is believed to be clean. http://www.dit.ie
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by Peter Stavrinides <p....@albourne.com>.
Tomcat in eclipse has an Automatic publishing feature, which is not to
be confused with live class reloading. Publishing requires a partial
restart and republishes the war, you will notice the difference when
your web application grows, running the same app under jetty reloading
reloading is instant whereas under Tomcat it degrades significantly as
it grows.
Blower, Andy wrote:
> Tomcat 5.5 live reloading works for me with Eclipse. I followed the setup process from the Tapestry 5 - Building Web Applications book and it works fine. I've not really got into figuring out how a real dev environment should be set up yet - I'm just evaluating/prototyping so far. I've not tried TC6.
>
>
>> -----Original Message-----
>> From: Peter Stavrinides [mailto:p.stavrinides@albourne.com]
>> Sent: 23 April 2008 15:44
>> To: Tapestry users
>> Subject: Re: AW: Automatic class reloading on Tomcat 6 not working for
>> me
>>
>> Hi Josh,
>>
>> I am pleasantly surprised to hear it works in IntelliJ, has anyone got
>> it working in eclipse?
>>
>> Josh Canfield wrote:
>>
>>> Hmm... after reading the title again I guess the fact that it works
>>>
>> in
>>
>>> Tomcat 5.5 is irrelevant... sorry for the sidetrack.
>>>
>>> On Thu, Apr 17, 2008 at 10:01 AM, Josh Canfield
>>>
>> <jo...@thedailytube.com> wrote:
>>
>>>> I use Tomcat 5.5 and IntelliJ, I haven't tried tomcat in eclipse.
>>>>
>> I've
>>
>>>> found that if I don't allow IntelliJ to replace the classes while
>>>> debugging then the Tapestry reloading will work. Otherwise, it might
>>>> work once then goes back to the old class.
>>>>
>>>> Josh
>>>>
>>>>
>>>> On Thu, Apr 17, 2008 at 2:44 AM, Martin Kersten
>>>> <Ma...@mercateo.com> wrote:
>>>>
>>>>
>>>>> Is it still true? I use hot replacement for components and somehow
>>>>>
>> the class
>>
>>>>> is reloaded. I thought this issue was solved. Do I miss something?
>>>>> (Using also T6)
>>>>>
>>>>> -----Ursprüngliche Nachricht-----
>>>>> Von: Peter Stavrinides [mailto:p.stavrinides@albourne.com]
>>>>> Gesendet: Donnerstag, 17. April 2008 11:05
>>>>> An: Tapestry users
>>>>> Betreff: Re: AW: Automatic class reloading on Tomcat 6 not working
>>>>>
>> for me
>>
>>>>> You cannot use Tomcat for class reloading, this is not a bug, it's
>>>>>
>> a feature which apparently is a result of the limitations Java has for
>> package traversal and exploration, Jetty somehow gets around this
>> partially but its also not perfect...
>>
>>>>> http://tapestryjava.blogspot.com/2007/02/fighting-with-tomcat.html
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Filip S. Adamsen wrote:
>>>>>
>>>>>
>>>>>> There's an equivalent antiResource(s)Locking attribute as well
>>>>>>
>> that I
>>
>>>>>> think you might need.
>>>>>>
>>>>>> I use Jetty for all my development, though, and only test in
>>>>>>
>> Tomcat
>>
>>>>>> before deploying my applications.
>>>>>>
>>>>>> -Filip
>>>>>>
>>>>>> On 2008-04-16 18:45, Javier Molina wrote:
>>>>>>
>>>>>>
>>>>>>> Do you work on Windows? I've changed my packaging to build a .jar
>>>>>>> with my classes and put it in WEB-INF/lib instead of having the
>>>>>>> exploded classes in WEB-INF/classes but once the webapp is
>>>>>>>
>> started, I
>>
>>>>>>> can't replace the .jar, the file is locked. I have tried to set
>>>>>>> antiJARLocking="true" in the <Context> element but that doesn't
>>>>>>>
>> help.
>>
>>>>>>> Is anyone working with tapestry 5 and tomcat on windows with
>>>>>>>
>> working
>>
>>>>>>> auto-reload of classes?
>>>>>>>
>>>>>>> Filip S. Adamsen escribió:
>>>>>>>
>>>>>>>
>>>>>>>> I believe the reloading is the only Tapestry-related thing
>>>>>>>>
>> affected
>>
>>>>>>>> by this. But I use Maven and archiveClasses in both development
>>>>>>>>
>> and
>>
>>>>>>>> production so I can't say for sure.
>>>>>>>>
>>>>>>>> -Filip
>>>>>>>>
>>>>>>>> On 2008-04-16 16:38, Stranzenbach, Ralf wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi.
>>>>>>>>>
>>>>>>>>> Does this "tomcat bug" affect only the class/page reloading
>>>>>>>>>
>> process
>>
>>>>>>>>> or is there any other significant problem that may arise during
>>>>>>>>> development / production.
>>>>>>>>>
>>>>>>>>> I've tried to create a sample application using Tomcat +
>>>>>>>>>
>> Tapestry
>>
>>>>>>>>> 5.0.10 and everything seems to work fine beside that reloading
>>>>>>>>>
>> issues.
>>
>>>>>>>>> - Ralf
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ________________________________
>>>>>>>>>
>>>>>>>>> Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
>>>>>>>>> Gesendet: Mi 16.04.2008 16:36
>>>>>>>>> An: Tapestry users
>>>>>>>>> Betreff: Re: Automatic class reloading on Tomcat 6 not working
>>>>>>>>>
>> for
>>
>>>>>>>>> me
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> Due to the way class loaders work in Tomcat you have to jar
>>>>>>>>>
>> your
>>
>>>>>>>>> classes etc. and put the jar into WEB-INF/lib.
>>>>>>>>>
>>>>>>>>> http://tapestry.apache.org/tapestry5/tomcat.html
>>>>>>>>>
>>>>>>>>> -Filip
>>>>>>>>>
>>>>>>>>> On 2008-04-16 13:42, Javier Molina wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on
>>>>>>>>>>
>> 6.0.14
>>
>>>>>>>>>> and 6.0.16). Automatic class reloading doesn't work for pages
>>>>>>>>>> (there are no components yet in this test application, so I
>>>>>>>>>> haven't checked that).
>>>>>>>>>> Jetty 6 works fine and does autoreload pages.
>>>>>>>>>>
>>>>>>>>>> Is this a known issue? Do I have to configure anything in
>>>>>>>>>>
>> Tomcat
>>
>>>>>>>>>> to get class reloading to work?
>>>>>>>>>>
>>>>>>>>>> Thank you.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------
>>>>>>>>>
>> ----
>>
>>>>>>>>> -- To unsubscribe, e-mail: users-
>>>>>>>>>
>> unsubscribe@tapestry.apache.org
>>
>>>>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>> *******************************************************************
>>
>>>>>>>>> ********************************
>>>>>>>>>
>>>>>>>>> The information in this email is confidential and may be
>>>>>>>>>
>> legally
>>
>>>>>>>>> privileged. Access to this email by anyone other than the
>>>>>>>>>
>> intended
>>
>>>>>>>>> addressee is unauthorized. If you are not the intended
>>>>>>>>>
>> recipient of
>>
>>>>>>>>> this message, any review, disclosure, copying, distribution,
>>>>>>>>> retention, or any action taken or omitted to be taken in
>>>>>>>>>
>> reliance
>>
>>>>>>>>> on it is prohibited and may be unlawful. If you are not the
>>>>>>>>> intended recipient, please reply to or forward a copy of this
>>>>>>>>> message to the sender and delete the message, any attachments,
>>>>>>>>>
>> and
>>
>>>>>>>>> any copies thereof from your system.
>>>>>>>>>
>>>>>>>>>
>> *******************************************************************
>>
>>>>>>>>> ********************************
>>>>>>>>>
>>>>>>>>> BearingPoint GmbH
>>>>>>>>> Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler
>>>>>>>>> (stellv. Vorsitzender), Wilfried Erber, Werner Kreutzmann,
>>>>>>>>> Hans-Werner Wurzel
>>>>>>>>> Aufsichtsratsvorsitzender: Roderick McGeary
>>>>>>>>> Sitz: Frankfurt am Main
>>>>>>>>> Registergericht: Amtsgericht Frankfurt am Main HRB 55490
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------
>>>>>>>>>
>> ----
>>
>>>>>>>>> -- To unsubscribe, e-mail: users-
>>>>>>>>>
>> unsubscribe@tapestry.apache.org
>>
>>>>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> ----------------------------------------------------------------
>>>>>>>>
>> ----
>>
>>>>>>>> - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> -----------------------------------------------------------------
>>>>>>>
>> ----
>>
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> ------------------------------------------------------------------
>>>>>>
>> ---
>>
>>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>> -------------------------------------------------------------------
>>>>>
>> --
>>
>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>>
>> --
>>
>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>> --
>>>> --
>>>> TheDailyTube.com. Sign up and get the best new videos on the
>>>>
>> internet
>>
>>>> delivered fresh to your inbox.
>>>>
>>>>
>>>>
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
RE: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by "Blower, Andy" <An...@proquest.co.uk>.
Tomcat 5.5 live reloading works for me with Eclipse. I followed the setup process from the Tapestry 5 - Building Web Applications book and it works fine. I've not really got into figuring out how a real dev environment should be set up yet - I'm just evaluating/prototyping so far. I've not tried TC6.
> -----Original Message-----
> From: Peter Stavrinides [mailto:p.stavrinides@albourne.com]
> Sent: 23 April 2008 15:44
> To: Tapestry users
> Subject: Re: AW: Automatic class reloading on Tomcat 6 not working for
> me
>
> Hi Josh,
>
> I am pleasantly surprised to hear it works in IntelliJ, has anyone got
> it working in eclipse?
>
> Josh Canfield wrote:
> > Hmm... after reading the title again I guess the fact that it works
> in
> > Tomcat 5.5 is irrelevant... sorry for the sidetrack.
> >
> > On Thu, Apr 17, 2008 at 10:01 AM, Josh Canfield
> <jo...@thedailytube.com> wrote:
> >
> >> I use Tomcat 5.5 and IntelliJ, I haven't tried tomcat in eclipse.
> I've
> >> found that if I don't allow IntelliJ to replace the classes while
> >> debugging then the Tapestry reloading will work. Otherwise, it might
> >> work once then goes back to the old class.
> >>
> >> Josh
> >>
> >>
> >> On Thu, Apr 17, 2008 at 2:44 AM, Martin Kersten
> >> <Ma...@mercateo.com> wrote:
> >>
> >>> Is it still true? I use hot replacement for components and somehow
> the class
> >>> is reloaded. I thought this issue was solved. Do I miss something?
> >>> (Using also T6)
> >>>
> >>> -----Ursprüngliche Nachricht-----
> >>> Von: Peter Stavrinides [mailto:p.stavrinides@albourne.com]
> >>> Gesendet: Donnerstag, 17. April 2008 11:05
> >>> An: Tapestry users
> >>> Betreff: Re: AW: Automatic class reloading on Tomcat 6 not working
> for me
> >>>
> >>>
> >>> You cannot use Tomcat for class reloading, this is not a bug, it's
> a feature which apparently is a result of the limitations Java has for
> package traversal and exploration, Jetty somehow gets around this
> partially but its also not perfect...
> >>> http://tapestryjava.blogspot.com/2007/02/fighting-with-tomcat.html
> >>>
> >>>
> >>>
> >>>
> >>> Filip S. Adamsen wrote:
> >>>
> >>>> There's an equivalent antiResource(s)Locking attribute as well
> that I
> >>>> think you might need.
> >>>>
> >>>> I use Jetty for all my development, though, and only test in
> Tomcat
> >>>> before deploying my applications.
> >>>>
> >>>> -Filip
> >>>>
> >>>> On 2008-04-16 18:45, Javier Molina wrote:
> >>>>
> >>>>> Do you work on Windows? I've changed my packaging to build a .jar
> >>>>> with my classes and put it in WEB-INF/lib instead of having the
> >>>>> exploded classes in WEB-INF/classes but once the webapp is
> started, I
> >>>>> can't replace the .jar, the file is locked. I have tried to set
> >>>>> antiJARLocking="true" in the <Context> element but that doesn't
> help.
> >>>>>
> >>>>> Is anyone working with tapestry 5 and tomcat on windows with
> working
> >>>>> auto-reload of classes?
> >>>>>
> >>>>> Filip S. Adamsen escribió:
> >>>>>
> >>>>>> I believe the reloading is the only Tapestry-related thing
> affected
> >>>>>> by this. But I use Maven and archiveClasses in both development
> and
> >>>>>> production so I can't say for sure.
> >>>>>>
> >>>>>> -Filip
> >>>>>>
> >>>>>> On 2008-04-16 16:38, Stranzenbach, Ralf wrote:
> >>>>>>
> >>>>>>> Hi.
> >>>>>>>
> >>>>>>> Does this "tomcat bug" affect only the class/page reloading
> process
> >>>>>>> or is there any other significant problem that may arise during
> >>>>>>> development / production.
> >>>>>>>
> >>>>>>> I've tried to create a sample application using Tomcat +
> Tapestry
> >>>>>>> 5.0.10 and everything seems to work fine beside that reloading
> issues.
> >>>>>>>
> >>>>>>> - Ralf
> >>>>>>>
> >>>>>>>
> >>>>>>> ________________________________
> >>>>>>>
> >>>>>>> Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
> >>>>>>> Gesendet: Mi 16.04.2008 16:36
> >>>>>>> An: Tapestry users
> >>>>>>> Betreff: Re: Automatic class reloading on Tomcat 6 not working
> for
> >>>>>>> me
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> Due to the way class loaders work in Tomcat you have to jar
> your
> >>>>>>> classes etc. and put the jar into WEB-INF/lib.
> >>>>>>>
> >>>>>>> http://tapestry.apache.org/tapestry5/tomcat.html
> >>>>>>>
> >>>>>>> -Filip
> >>>>>>>
> >>>>>>> On 2008-04-16 13:42, Javier Molina wrote:
> >>>>>>>
> >>>>>>>> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on
> 6.0.14
> >>>>>>>> and 6.0.16). Automatic class reloading doesn't work for pages
> >>>>>>>> (there are no components yet in this test application, so I
> >>>>>>>> haven't checked that).
> >>>>>>>> Jetty 6 works fine and does autoreload pages.
> >>>>>>>>
> >>>>>>>> Is this a known issue? Do I have to configure anything in
> Tomcat
> >>>>>>>> to get class reloading to work?
> >>>>>>>>
> >>>>>>>> Thank you.
> >>>>>>>>
> >>>>>>> ---------------------------------------------------------------
> ----
> >>>>>>> -- To unsubscribe, e-mail: users-
> unsubscribe@tapestry.apache.org
> >>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> *******************************************************************
> >>>>>>> ********************************
> >>>>>>>
> >>>>>>> The information in this email is confidential and may be
> legally
> >>>>>>> privileged. Access to this email by anyone other than the
> intended
> >>>>>>> addressee is unauthorized. If you are not the intended
> recipient of
> >>>>>>> this message, any review, disclosure, copying, distribution,
> >>>>>>> retention, or any action taken or omitted to be taken in
> reliance
> >>>>>>> on it is prohibited and may be unlawful. If you are not the
> >>>>>>> intended recipient, please reply to or forward a copy of this
> >>>>>>> message to the sender and delete the message, any attachments,
> and
> >>>>>>> any copies thereof from your system.
> >>>>>>>
> *******************************************************************
> >>>>>>> ********************************
> >>>>>>>
> >>>>>>> BearingPoint GmbH
> >>>>>>> Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler
> >>>>>>> (stellv. Vorsitzender), Wilfried Erber, Werner Kreutzmann,
> >>>>>>> Hans-Werner Wurzel
> >>>>>>> Aufsichtsratsvorsitzender: Roderick McGeary
> >>>>>>> Sitz: Frankfurt am Main
> >>>>>>> Registergericht: Amtsgericht Frankfurt am Main HRB 55490
> >>>>>>>
> >>>>>>> ---------------------------------------------------------------
> ----
> >>>>>>> -- To unsubscribe, e-mail: users-
> unsubscribe@tapestry.apache.org
> >>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>> ----------------------------------------------------------------
> ----
> >>>>>> - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> -----------------------------------------------------------------
> ----
> >>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>>
> >>>>>
> >>>> ------------------------------------------------------------------
> ---
> >>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>
> >>>>
> >>> -------------------------------------------------------------------
> --
> >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>
> >>>
> >>> -------------------------------------------------------------------
> --
> >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>
> >>>
> >>>
> >>
> >> --
> >> --
> >> TheDailyTube.com. Sign up and get the best new videos on the
> internet
> >> delivered fresh to your inbox.
> >>
> >>
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by Peter Stavrinides <p....@albourne.com>.
Hi Josh,
I am pleasantly surprised to hear it works in IntelliJ, has anyone got
it working in eclipse?
Josh Canfield wrote:
> Hmm... after reading the title again I guess the fact that it works in
> Tomcat 5.5 is irrelevant... sorry for the sidetrack.
>
> On Thu, Apr 17, 2008 at 10:01 AM, Josh Canfield <jo...@thedailytube.com> wrote:
>
>> I use Tomcat 5.5 and IntelliJ, I haven't tried tomcat in eclipse. I've
>> found that if I don't allow IntelliJ to replace the classes while
>> debugging then the Tapestry reloading will work. Otherwise, it might
>> work once then goes back to the old class.
>>
>> Josh
>>
>>
>> On Thu, Apr 17, 2008 at 2:44 AM, Martin Kersten
>> <Ma...@mercateo.com> wrote:
>>
>>> Is it still true? I use hot replacement for components and somehow the class
>>> is reloaded. I thought this issue was solved. Do I miss something?
>>> (Using also T6)
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Peter Stavrinides [mailto:p.stavrinides@albourne.com]
>>> Gesendet: Donnerstag, 17. April 2008 11:05
>>> An: Tapestry users
>>> Betreff: Re: AW: Automatic class reloading on Tomcat 6 not working for me
>>>
>>>
>>> You cannot use Tomcat for class reloading, this is not a bug, it's a feature which apparently is a result of the limitations Java has for package traversal and exploration, Jetty somehow gets around this partially but its also not perfect...
>>> http://tapestryjava.blogspot.com/2007/02/fighting-with-tomcat.html
>>>
>>>
>>>
>>>
>>> Filip S. Adamsen wrote:
>>>
>>>> There's an equivalent antiResource(s)Locking attribute as well that I
>>>> think you might need.
>>>>
>>>> I use Jetty for all my development, though, and only test in Tomcat
>>>> before deploying my applications.
>>>>
>>>> -Filip
>>>>
>>>> On 2008-04-16 18:45, Javier Molina wrote:
>>>>
>>>>> Do you work on Windows? I've changed my packaging to build a .jar
>>>>> with my classes and put it in WEB-INF/lib instead of having the
>>>>> exploded classes in WEB-INF/classes but once the webapp is started, I
>>>>> can't replace the .jar, the file is locked. I have tried to set
>>>>> antiJARLocking="true" in the <Context> element but that doesn't help.
>>>>>
>>>>> Is anyone working with tapestry 5 and tomcat on windows with working
>>>>> auto-reload of classes?
>>>>>
>>>>> Filip S. Adamsen escribió:
>>>>>
>>>>>> I believe the reloading is the only Tapestry-related thing affected
>>>>>> by this. But I use Maven and archiveClasses in both development and
>>>>>> production so I can't say for sure.
>>>>>>
>>>>>> -Filip
>>>>>>
>>>>>> On 2008-04-16 16:38, Stranzenbach, Ralf wrote:
>>>>>>
>>>>>>> Hi.
>>>>>>>
>>>>>>> Does this "tomcat bug" affect only the class/page reloading process
>>>>>>> or is there any other significant problem that may arise during
>>>>>>> development / production.
>>>>>>>
>>>>>>> I've tried to create a sample application using Tomcat + Tapestry
>>>>>>> 5.0.10 and everything seems to work fine beside that reloading issues.
>>>>>>>
>>>>>>> - Ralf
>>>>>>>
>>>>>>>
>>>>>>> ________________________________
>>>>>>>
>>>>>>> Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
>>>>>>> Gesendet: Mi 16.04.2008 16:36
>>>>>>> An: Tapestry users
>>>>>>> Betreff: Re: Automatic class reloading on Tomcat 6 not working for
>>>>>>> me
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Due to the way class loaders work in Tomcat you have to jar your
>>>>>>> classes etc. and put the jar into WEB-INF/lib.
>>>>>>>
>>>>>>> http://tapestry.apache.org/tapestry5/tomcat.html
>>>>>>>
>>>>>>> -Filip
>>>>>>>
>>>>>>> On 2008-04-16 13:42, Javier Molina wrote:
>>>>>>>
>>>>>>>> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14
>>>>>>>> and 6.0.16). Automatic class reloading doesn't work for pages
>>>>>>>> (there are no components yet in this test application, so I
>>>>>>>> haven't checked that).
>>>>>>>> Jetty 6 works fine and does autoreload pages.
>>>>>>>>
>>>>>>>> Is this a known issue? Do I have to configure anything in Tomcat
>>>>>>>> to get class reloading to work?
>>>>>>>>
>>>>>>>> Thank you.
>>>>>>>>
>>>>>>> -------------------------------------------------------------------
>>>>>>> -- To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *******************************************************************
>>>>>>> ********************************
>>>>>>>
>>>>>>> The information in this email is confidential and may be legally
>>>>>>> privileged. Access to this email by anyone other than the intended
>>>>>>> addressee is unauthorized. If you are not the intended recipient of
>>>>>>> this message, any review, disclosure, copying, distribution,
>>>>>>> retention, or any action taken or omitted to be taken in reliance
>>>>>>> on it is prohibited and may be unlawful. If you are not the
>>>>>>> intended recipient, please reply to or forward a copy of this
>>>>>>> message to the sender and delete the message, any attachments, and
>>>>>>> any copies thereof from your system.
>>>>>>> *******************************************************************
>>>>>>> ********************************
>>>>>>>
>>>>>>> BearingPoint GmbH
>>>>>>> Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler
>>>>>>> (stellv. Vorsitzender), Wilfried Erber, Werner Kreutzmann,
>>>>>>> Hans-Werner Wurzel
>>>>>>> Aufsichtsratsvorsitzender: Roderick McGeary
>>>>>>> Sitz: Frankfurt am Main
>>>>>>> Registergericht: Amtsgericht Frankfurt am Main HRB 55490
>>>>>>>
>>>>>>> -------------------------------------------------------------------
>>>>>>> -- To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>>>
>>>>>>>
>>>>>> --------------------------------------------------------------------
>>>>>> - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>>
>>
>> --
>> --
>> TheDailyTube.com. Sign up and get the best new videos on the internet
>> delivered fresh to your inbox.
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by Josh Canfield <jo...@thedailytube.com>.
Hmm... after reading the title again I guess the fact that it works in
Tomcat 5.5 is irrelevant... sorry for the sidetrack.
On Thu, Apr 17, 2008 at 10:01 AM, Josh Canfield <jo...@thedailytube.com> wrote:
> I use Tomcat 5.5 and IntelliJ, I haven't tried tomcat in eclipse. I've
> found that if I don't allow IntelliJ to replace the classes while
> debugging then the Tapestry reloading will work. Otherwise, it might
> work once then goes back to the old class.
>
> Josh
>
>
> On Thu, Apr 17, 2008 at 2:44 AM, Martin Kersten
> <Ma...@mercateo.com> wrote:
> > Is it still true? I use hot replacement for components and somehow the class
> > is reloaded. I thought this issue was solved. Do I miss something?
> > (Using also T6)
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Peter Stavrinides [mailto:p.stavrinides@albourne.com]
> > Gesendet: Donnerstag, 17. April 2008 11:05
> > An: Tapestry users
> > Betreff: Re: AW: Automatic class reloading on Tomcat 6 not working for me
> >
> >
> > You cannot use Tomcat for class reloading, this is not a bug, it's a feature which apparently is a result of the limitations Java has for package traversal and exploration, Jetty somehow gets around this partially but its also not perfect...
> > http://tapestryjava.blogspot.com/2007/02/fighting-with-tomcat.html
> >
> >
> >
> >
> > Filip S. Adamsen wrote:
> > > There's an equivalent antiResource(s)Locking attribute as well that I
> > > think you might need.
> > >
> > > I use Jetty for all my development, though, and only test in Tomcat
> > > before deploying my applications.
> > >
> > > -Filip
> > >
> > > On 2008-04-16 18:45, Javier Molina wrote:
> > >> Do you work on Windows? I've changed my packaging to build a .jar
> > >> with my classes and put it in WEB-INF/lib instead of having the
> > >> exploded classes in WEB-INF/classes but once the webapp is started, I
> > >> can't replace the .jar, the file is locked. I have tried to set
> > >> antiJARLocking="true" in the <Context> element but that doesn't help.
> > >>
> > >> Is anyone working with tapestry 5 and tomcat on windows with working
> > >> auto-reload of classes?
> > >>
> > >> Filip S. Adamsen escribió:
> > >>> I believe the reloading is the only Tapestry-related thing affected
> > >>> by this. But I use Maven and archiveClasses in both development and
> > >>> production so I can't say for sure.
> > >>>
> > >>> -Filip
> > >>>
> > >>> On 2008-04-16 16:38, Stranzenbach, Ralf wrote:
> > >>>> Hi.
> > >>>>
> > >>>> Does this "tomcat bug" affect only the class/page reloading process
> > >>>> or is there any other significant problem that may arise during
> > >>>> development / production.
> > >>>>
> > >>>> I've tried to create a sample application using Tomcat + Tapestry
> > >>>> 5.0.10 and everything seems to work fine beside that reloading issues.
> > >>>>
> > >>>> - Ralf
> > >>>>
> > >>>>
> > >>>> ________________________________
> > >>>>
> > >>>> Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
> > >>>> Gesendet: Mi 16.04.2008 16:36
> > >>>> An: Tapestry users
> > >>>> Betreff: Re: Automatic class reloading on Tomcat 6 not working for
> > >>>> me
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi,
> > >>>>
> > >>>> Due to the way class loaders work in Tomcat you have to jar your
> > >>>> classes etc. and put the jar into WEB-INF/lib.
> > >>>>
> > >>>> http://tapestry.apache.org/tapestry5/tomcat.html
> > >>>>
> > >>>> -Filip
> > >>>>
> > >>>> On 2008-04-16 13:42, Javier Molina wrote:
> > >>>>> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14
> > >>>>> and 6.0.16). Automatic class reloading doesn't work for pages
> > >>>>> (there are no components yet in this test application, so I
> > >>>>> haven't checked that).
> > >>>>> Jetty 6 works fine and does autoreload pages.
> > >>>>>
> > >>>>> Is this a known issue? Do I have to configure anything in Tomcat
> > >>>>> to get class reloading to work?
> > >>>>>
> > >>>>> Thank you.
> > >>>>
> > >>>> -------------------------------------------------------------------
> > >>>> -- To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > >>>> For additional commands, e-mail: users-help@tapestry.apache.org
> > >>>>
> > >>>>
> > >>>>
> > >>>> *******************************************************************
> > >>>> ********************************
> > >>>>
> > >>>> The information in this email is confidential and may be legally
> > >>>> privileged. Access to this email by anyone other than the intended
> > >>>> addressee is unauthorized. If you are not the intended recipient of
> > >>>> this message, any review, disclosure, copying, distribution,
> > >>>> retention, or any action taken or omitted to be taken in reliance
> > >>>> on it is prohibited and may be unlawful. If you are not the
> > >>>> intended recipient, please reply to or forward a copy of this
> > >>>> message to the sender and delete the message, any attachments, and
> > >>>> any copies thereof from your system.
> > >>>> *******************************************************************
> > >>>> ********************************
> > >>>>
> > >>>> BearingPoint GmbH
> > >>>> Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler
> > >>>> (stellv. Vorsitzender), Wilfried Erber, Werner Kreutzmann,
> > >>>> Hans-Werner Wurzel
> > >>>> Aufsichtsratsvorsitzender: Roderick McGeary
> > >>>> Sitz: Frankfurt am Main
> > >>>> Registergericht: Amtsgericht Frankfurt am Main HRB 55490
> > >>>>
> > >>>> -------------------------------------------------------------------
> > >>>> -- To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > >>>> For additional commands, e-mail: users-help@tapestry.apache.org
> > >>>>
> > >>>
> > >>> --------------------------------------------------------------------
> > >>> - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > >>> For additional commands, e-mail: users-help@tapestry.apache.org
> > >>>
> > >>>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > >> For additional commands, e-mail: users-help@tapestry.apache.org
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
>
> --
> --
> TheDailyTube.com. Sign up and get the best new videos on the internet
> delivered fresh to your inbox.
>
--
--
TheDailyTube.com. Sign up and get the best new videos on the internet
delivered fresh to your inbox.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by Josh Canfield <jo...@thedailytube.com>.
I use Tomcat 5.5 and IntelliJ, I haven't tried tomcat in eclipse. I've
found that if I don't allow IntelliJ to replace the classes while
debugging then the Tapestry reloading will work. Otherwise, it might
work once then goes back to the old class.
Josh
On Thu, Apr 17, 2008 at 2:44 AM, Martin Kersten
<Ma...@mercateo.com> wrote:
> Is it still true? I use hot replacement for components and somehow the class
> is reloaded. I thought this issue was solved. Do I miss something?
> (Using also T6)
>
> -----Ursprüngliche Nachricht-----
> Von: Peter Stavrinides [mailto:p.stavrinides@albourne.com]
> Gesendet: Donnerstag, 17. April 2008 11:05
> An: Tapestry users
> Betreff: Re: AW: Automatic class reloading on Tomcat 6 not working for me
>
>
> You cannot use Tomcat for class reloading, this is not a bug, it's a feature which apparently is a result of the limitations Java has for package traversal and exploration, Jetty somehow gets around this partially but its also not perfect...
> http://tapestryjava.blogspot.com/2007/02/fighting-with-tomcat.html
>
>
>
>
> Filip S. Adamsen wrote:
> > There's an equivalent antiResource(s)Locking attribute as well that I
> > think you might need.
> >
> > I use Jetty for all my development, though, and only test in Tomcat
> > before deploying my applications.
> >
> > -Filip
> >
> > On 2008-04-16 18:45, Javier Molina wrote:
> >> Do you work on Windows? I've changed my packaging to build a .jar
> >> with my classes and put it in WEB-INF/lib instead of having the
> >> exploded classes in WEB-INF/classes but once the webapp is started, I
> >> can't replace the .jar, the file is locked. I have tried to set
> >> antiJARLocking="true" in the <Context> element but that doesn't help.
> >>
> >> Is anyone working with tapestry 5 and tomcat on windows with working
> >> auto-reload of classes?
> >>
> >> Filip S. Adamsen escribió:
> >>> I believe the reloading is the only Tapestry-related thing affected
> >>> by this. But I use Maven and archiveClasses in both development and
> >>> production so I can't say for sure.
> >>>
> >>> -Filip
> >>>
> >>> On 2008-04-16 16:38, Stranzenbach, Ralf wrote:
> >>>> Hi.
> >>>>
> >>>> Does this "tomcat bug" affect only the class/page reloading process
> >>>> or is there any other significant problem that may arise during
> >>>> development / production.
> >>>>
> >>>> I've tried to create a sample application using Tomcat + Tapestry
> >>>> 5.0.10 and everything seems to work fine beside that reloading issues.
> >>>>
> >>>> - Ralf
> >>>>
> >>>>
> >>>> ________________________________
> >>>>
> >>>> Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
> >>>> Gesendet: Mi 16.04.2008 16:36
> >>>> An: Tapestry users
> >>>> Betreff: Re: Automatic class reloading on Tomcat 6 not working for
> >>>> me
> >>>>
> >>>>
> >>>>
> >>>> Hi,
> >>>>
> >>>> Due to the way class loaders work in Tomcat you have to jar your
> >>>> classes etc. and put the jar into WEB-INF/lib.
> >>>>
> >>>> http://tapestry.apache.org/tapestry5/tomcat.html
> >>>>
> >>>> -Filip
> >>>>
> >>>> On 2008-04-16 13:42, Javier Molina wrote:
> >>>>> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14
> >>>>> and 6.0.16). Automatic class reloading doesn't work for pages
> >>>>> (there are no components yet in this test application, so I
> >>>>> haven't checked that).
> >>>>> Jetty 6 works fine and does autoreload pages.
> >>>>>
> >>>>> Is this a known issue? Do I have to configure anything in Tomcat
> >>>>> to get class reloading to work?
> >>>>>
> >>>>> Thank you.
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> -- To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>
> >>>>
> >>>>
> >>>> *******************************************************************
> >>>> ********************************
> >>>>
> >>>> The information in this email is confidential and may be legally
> >>>> privileged. Access to this email by anyone other than the intended
> >>>> addressee is unauthorized. If you are not the intended recipient of
> >>>> this message, any review, disclosure, copying, distribution,
> >>>> retention, or any action taken or omitted to be taken in reliance
> >>>> on it is prohibited and may be unlawful. If you are not the
> >>>> intended recipient, please reply to or forward a copy of this
> >>>> message to the sender and delete the message, any attachments, and
> >>>> any copies thereof from your system.
> >>>> *******************************************************************
> >>>> ********************************
> >>>>
> >>>> BearingPoint GmbH
> >>>> Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler
> >>>> (stellv. Vorsitzender), Wilfried Erber, Werner Kreutzmann,
> >>>> Hans-Werner Wurzel
> >>>> Aufsichtsratsvorsitzender: Roderick McGeary
> >>>> Sitz: Frankfurt am Main
> >>>> Registergericht: Amtsgericht Frankfurt am Main HRB 55490
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> -- To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>
> >>>
> >>> --------------------------------------------------------------------
> >>> - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
--
TheDailyTube.com. Sign up and get the best new videos on the internet
delivered fresh to your inbox.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
AW: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by Martin Kersten <Ma...@mercateo.com>.
Is it still true? I use hot replacement for components and somehow the class
is reloaded. I thought this issue was solved. Do I miss something?
(Using also T6)
-----Ursprüngliche Nachricht-----
Von: Peter Stavrinides [mailto:p.stavrinides@albourne.com]
Gesendet: Donnerstag, 17. April 2008 11:05
An: Tapestry users
Betreff: Re: AW: Automatic class reloading on Tomcat 6 not working for me
You cannot use Tomcat for class reloading, this is not a bug, it's a feature which apparently is a result of the limitations Java has for package traversal and exploration, Jetty somehow gets around this partially but its also not perfect...
http://tapestryjava.blogspot.com/2007/02/fighting-with-tomcat.html
Filip S. Adamsen wrote:
> There's an equivalent antiResource(s)Locking attribute as well that I
> think you might need.
>
> I use Jetty for all my development, though, and only test in Tomcat
> before deploying my applications.
>
> -Filip
>
> On 2008-04-16 18:45, Javier Molina wrote:
>> Do you work on Windows? I've changed my packaging to build a .jar
>> with my classes and put it in WEB-INF/lib instead of having the
>> exploded classes in WEB-INF/classes but once the webapp is started, I
>> can't replace the .jar, the file is locked. I have tried to set
>> antiJARLocking="true" in the <Context> element but that doesn't help.
>>
>> Is anyone working with tapestry 5 and tomcat on windows with working
>> auto-reload of classes?
>>
>> Filip S. Adamsen escribió:
>>> I believe the reloading is the only Tapestry-related thing affected
>>> by this. But I use Maven and archiveClasses in both development and
>>> production so I can't say for sure.
>>>
>>> -Filip
>>>
>>> On 2008-04-16 16:38, Stranzenbach, Ralf wrote:
>>>> Hi.
>>>>
>>>> Does this "tomcat bug" affect only the class/page reloading process
>>>> or is there any other significant problem that may arise during
>>>> development / production.
>>>>
>>>> I've tried to create a sample application using Tomcat + Tapestry
>>>> 5.0.10 and everything seems to work fine beside that reloading issues.
>>>>
>>>> - Ralf
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
>>>> Gesendet: Mi 16.04.2008 16:36
>>>> An: Tapestry users
>>>> Betreff: Re: Automatic class reloading on Tomcat 6 not working for
>>>> me
>>>>
>>>>
>>>>
>>>> Hi,
>>>>
>>>> Due to the way class loaders work in Tomcat you have to jar your
>>>> classes etc. and put the jar into WEB-INF/lib.
>>>>
>>>> http://tapestry.apache.org/tapestry5/tomcat.html
>>>>
>>>> -Filip
>>>>
>>>> On 2008-04-16 13:42, Javier Molina wrote:
>>>>> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14
>>>>> and 6.0.16). Automatic class reloading doesn't work for pages
>>>>> (there are no components yet in this test application, so I
>>>>> haven't checked that).
>>>>> Jetty 6 works fine and does autoreload pages.
>>>>>
>>>>> Is this a known issue? Do I have to configure anything in Tomcat
>>>>> to get class reloading to work?
>>>>>
>>>>> Thank you.
>>>>
>>>> -------------------------------------------------------------------
>>>> -- To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>>> *******************************************************************
>>>> ********************************
>>>>
>>>> The information in this email is confidential and may be legally
>>>> privileged. Access to this email by anyone other than the intended
>>>> addressee is unauthorized. If you are not the intended recipient of
>>>> this message, any review, disclosure, copying, distribution,
>>>> retention, or any action taken or omitted to be taken in reliance
>>>> on it is prohibited and may be unlawful. If you are not the
>>>> intended recipient, please reply to or forward a copy of this
>>>> message to the sender and delete the message, any attachments, and
>>>> any copies thereof from your system.
>>>> *******************************************************************
>>>> ********************************
>>>>
>>>> BearingPoint GmbH
>>>> Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler
>>>> (stellv. Vorsitzender), Wilfried Erber, Werner Kreutzmann,
>>>> Hans-Werner Wurzel
>>>> Aufsichtsratsvorsitzender: Roderick McGeary
>>>> Sitz: Frankfurt am Main
>>>> Registergericht: Amtsgericht Frankfurt am Main HRB 55490
>>>>
>>>> -------------------------------------------------------------------
>>>> -- To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by Peter Stavrinides <p....@albourne.com>.
You cannot use Tomcat for class reloading, this is not a bug, it's a
feature which apparently is a result of the limitations Java has for
package traversal and exploration, Jetty somehow gets around this
partially but its also not perfect...
http://tapestryjava.blogspot.com/2007/02/fighting-with-tomcat.html
Filip S. Adamsen wrote:
> There's an equivalent antiResource(s)Locking attribute as well that I
> think you might need.
>
> I use Jetty for all my development, though, and only test in Tomcat
> before deploying my applications.
>
> -Filip
>
> On 2008-04-16 18:45, Javier Molina wrote:
>> Do you work on Windows? I've changed my packaging to build a .jar
>> with my classes and put it in WEB-INF/lib instead of having the
>> exploded classes in WEB-INF/classes but once the webapp is started, I
>> can't replace the .jar, the file is locked. I have tried to set
>> antiJARLocking="true" in the <Context> element but that doesn't help.
>>
>> Is anyone working with tapestry 5 and tomcat on windows with working
>> auto-reload of classes?
>>
>> Filip S. Adamsen escribió:
>>> I believe the reloading is the only Tapestry-related thing affected
>>> by this. But I use Maven and archiveClasses in both development and
>>> production so I can't say for sure.
>>>
>>> -Filip
>>>
>>> On 2008-04-16 16:38, Stranzenbach, Ralf wrote:
>>>> Hi.
>>>>
>>>> Does this "tomcat bug" affect only the class/page reloading process
>>>> or is there any other significant problem that may arise during
>>>> development / production.
>>>>
>>>> I've tried to create a sample application using Tomcat + Tapestry
>>>> 5.0.10 and everything seems to work fine beside that reloading issues.
>>>>
>>>> - Ralf
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
>>>> Gesendet: Mi 16.04.2008 16:36
>>>> An: Tapestry users
>>>> Betreff: Re: Automatic class reloading on Tomcat 6 not working for me
>>>>
>>>>
>>>>
>>>> Hi,
>>>>
>>>> Due to the way class loaders work in Tomcat you have to jar your
>>>> classes
>>>> etc. and put the jar into WEB-INF/lib.
>>>>
>>>> http://tapestry.apache.org/tapestry5/tomcat.html
>>>>
>>>> -Filip
>>>>
>>>> On 2008-04-16 13:42, Javier Molina wrote:
>>>>> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14 and
>>>>> 6.0.16). Automatic class reloading doesn't work for pages (there
>>>>> are no
>>>>> components yet in this test application, so I haven't checked that).
>>>>> Jetty 6 works fine and does autoreload pages.
>>>>>
>>>>> Is this a known issue? Do I have to configure anything in Tomcat
>>>>> to get
>>>>> class reloading to work?
>>>>>
>>>>> Thank you.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>>> ***************************************************************************************************
>>>>
>>>> The information in this email is confidential and may be legally
>>>> privileged. Access to this email by anyone other than the intended
>>>> addressee is unauthorized. If you are not the intended recipient of
>>>> this message, any review, disclosure, copying, distribution,
>>>> retention, or any action taken or omitted to be taken in reliance
>>>> on it is prohibited and may be unlawful. If you are not the
>>>> intended recipient, please reply to or forward a copy of this
>>>> message to the sender and delete the message, any attachments, and
>>>> any copies thereof from your system.
>>>> ***************************************************************************************************
>>>>
>>>> BearingPoint GmbH
>>>> Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler
>>>> (stellv. Vorsitzender), Wilfried Erber, Werner Kreutzmann,
>>>> Hans-Werner Wurzel
>>>> Aufsichtsratsvorsitzender: Roderick McGeary
>>>> Sitz: Frankfurt am Main
>>>> Registergericht: Amtsgericht Frankfurt am Main HRB 55490
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by "Filip S. Adamsen" <fs...@fsadev.com>.
There's an equivalent antiResource(s)Locking attribute as well that I
think you might need.
I use Jetty for all my development, though, and only test in Tomcat
before deploying my applications.
-Filip
On 2008-04-16 18:45, Javier Molina wrote:
> Do you work on Windows? I've changed my packaging to build a .jar with
> my classes and put it in WEB-INF/lib instead of having the exploded
> classes in WEB-INF/classes but once the webapp is started, I can't
> replace the .jar, the file is locked. I have tried to set
> antiJARLocking="true" in the <Context> element but that doesn't help.
>
> Is anyone working with tapestry 5 and tomcat on windows with working
> auto-reload of classes?
>
> Filip S. Adamsen escribió:
>> I believe the reloading is the only Tapestry-related thing affected by
>> this. But I use Maven and archiveClasses in both development and
>> production so I can't say for sure.
>>
>> -Filip
>>
>> On 2008-04-16 16:38, Stranzenbach, Ralf wrote:
>>> Hi.
>>>
>>> Does this "tomcat bug" affect only the class/page reloading process
>>> or is there any other significant problem that may arise during
>>> development / production.
>>>
>>> I've tried to create a sample application using Tomcat + Tapestry
>>> 5.0.10 and everything seems to work fine beside that reloading issues.
>>>
>>> - Ralf
>>>
>>>
>>> ________________________________
>>>
>>> Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
>>> Gesendet: Mi 16.04.2008 16:36
>>> An: Tapestry users
>>> Betreff: Re: Automatic class reloading on Tomcat 6 not working for me
>>>
>>>
>>>
>>> Hi,
>>>
>>> Due to the way class loaders work in Tomcat you have to jar your classes
>>> etc. and put the jar into WEB-INF/lib.
>>>
>>> http://tapestry.apache.org/tapestry5/tomcat.html
>>>
>>> -Filip
>>>
>>> On 2008-04-16 13:42, Javier Molina wrote:
>>>> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14 and
>>>> 6.0.16). Automatic class reloading doesn't work for pages (there are no
>>>> components yet in this test application, so I haven't checked that).
>>>> Jetty 6 works fine and does autoreload pages.
>>>>
>>>> Is this a known issue? Do I have to configure anything in Tomcat to get
>>>> class reloading to work?
>>>>
>>>> Thank you.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>>
>>> ***************************************************************************************************
>>>
>>> The information in this email is confidential and may be legally
>>> privileged. Access to this email by anyone other than the intended
>>> addressee is unauthorized. If you are not the intended recipient of
>>> this message, any review, disclosure, copying, distribution,
>>> retention, or any action taken or omitted to be taken in reliance on
>>> it is prohibited and may be unlawful. If you are not the intended
>>> recipient, please reply to or forward a copy of this message to the
>>> sender and delete the message, any attachments, and any copies
>>> thereof from your system.
>>> ***************************************************************************************************
>>>
>>> BearingPoint GmbH
>>> Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler
>>> (stellv. Vorsitzender), Wilfried Erber, Werner Kreutzmann,
>>> Hans-Werner Wurzel
>>> Aufsichtsratsvorsitzender: Roderick McGeary
>>> Sitz: Frankfurt am Main
>>> Registergericht: Amtsgericht Frankfurt am Main HRB 55490
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by Javier Molina <nu...@myrealbox.com>.
Do you work on Windows? I've changed my packaging to build a .jar with my classes and put
it in WEB-INF/lib instead of having the exploded classes in WEB-INF/classes but once the
webapp is started, I can't replace the .jar, the file is locked. I have tried to set
antiJARLocking="true" in the <Context> element but that doesn't help.
Is anyone working with tapestry 5 and tomcat on windows with working auto-reload of classes?
Filip S. Adamsen escribió:
> I believe the reloading is the only Tapestry-related thing affected by
> this. But I use Maven and archiveClasses in both development and
> production so I can't say for sure.
>
> -Filip
>
> On 2008-04-16 16:38, Stranzenbach, Ralf wrote:
>> Hi.
>>
>> Does this "tomcat bug" affect only the class/page reloading process or
>> is there any other significant problem that may arise during
>> development / production.
>>
>> I've tried to create a sample application using Tomcat + Tapestry
>> 5.0.10 and everything seems to work fine beside that reloading issues.
>>
>> - Ralf
>>
>>
>> ________________________________
>>
>> Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
>> Gesendet: Mi 16.04.2008 16:36
>> An: Tapestry users
>> Betreff: Re: Automatic class reloading on Tomcat 6 not working for me
>>
>>
>>
>> Hi,
>>
>> Due to the way class loaders work in Tomcat you have to jar your classes
>> etc. and put the jar into WEB-INF/lib.
>>
>> http://tapestry.apache.org/tapestry5/tomcat.html
>>
>> -Filip
>>
>> On 2008-04-16 13:42, Javier Molina wrote:
>>> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14 and
>>> 6.0.16). Automatic class reloading doesn't work for pages (there are no
>>> components yet in this test application, so I haven't checked that).
>>> Jetty 6 works fine and does autoreload pages.
>>>
>>> Is this a known issue? Do I have to configure anything in Tomcat to get
>>> class reloading to work?
>>>
>>> Thank you.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>>
>> ***************************************************************************************************
>>
>> The information in this email is confidential and may be legally
>> privileged. Access to this email by anyone other than the intended
>> addressee is unauthorized. If you are not the intended recipient of
>> this message, any review, disclosure, copying, distribution,
>> retention, or any action taken or omitted to be taken in reliance on
>> it is prohibited and may be unlawful. If you are not the intended
>> recipient, please reply to or forward a copy of this message to the
>> sender and delete the message, any attachments, and any copies thereof
>> from your system.
>> ***************************************************************************************************
>>
>> BearingPoint GmbH
>> Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler (stellv.
>> Vorsitzender), Wilfried Erber, Werner Kreutzmann, Hans-Werner Wurzel
>> Aufsichtsratsvorsitzender: Roderick McGeary
>> Sitz: Frankfurt am Main
>> Registergericht: Amtsgericht Frankfurt am Main HRB 55490
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: AW: Automatic class reloading on Tomcat 6 not working for me
Posted by "Filip S. Adamsen" <fs...@fsadev.com>.
I believe the reloading is the only Tapestry-related thing affected by
this. But I use Maven and archiveClasses in both development and
production so I can't say for sure.
-Filip
On 2008-04-16 16:38, Stranzenbach, Ralf wrote:
> Hi.
>
> Does this "tomcat bug" affect only the class/page reloading process or is there any other significant problem that may arise during development / production.
>
> I've tried to create a sample application using Tomcat + Tapestry 5.0.10 and everything seems to work fine beside that reloading issues.
>
> - Ralf
>
>
> ________________________________
>
> Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
> Gesendet: Mi 16.04.2008 16:36
> An: Tapestry users
> Betreff: Re: Automatic class reloading on Tomcat 6 not working for me
>
>
>
> Hi,
>
> Due to the way class loaders work in Tomcat you have to jar your classes
> etc. and put the jar into WEB-INF/lib.
>
> http://tapestry.apache.org/tapestry5/tomcat.html
>
> -Filip
>
> On 2008-04-16 13:42, Javier Molina wrote:
>> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14 and
>> 6.0.16). Automatic class reloading doesn't work for pages (there are no
>> components yet in this test application, so I haven't checked that).
>> Jetty 6 works fine and does autoreload pages.
>>
>> Is this a known issue? Do I have to configure anything in Tomcat to get
>> class reloading to work?
>>
>> Thank you.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
> ***************************************************************************************************
> The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
> ***************************************************************************************************
>
> BearingPoint GmbH
> Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler (stellv. Vorsitzender), Wilfried Erber, Werner Kreutzmann, Hans-Werner Wurzel
> Aufsichtsratsvorsitzender: Roderick McGeary
> Sitz: Frankfurt am Main
> Registergericht: Amtsgericht Frankfurt am Main HRB 55490
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
AW: Automatic class reloading on Tomcat 6 not working for me
Posted by "Stranzenbach, Ralf" <ra...@bearingpoint.com>.
Hi.
Does this "tomcat bug" affect only the class/page reloading process or is there any other significant problem that may arise during development / production.
I've tried to create a sample application using Tomcat + Tapestry 5.0.10 and everything seems to work fine beside that reloading issues.
- Ralf
________________________________
Von: Filip S. Adamsen [mailto:fsa@fsadev.com]
Gesendet: Mi 16.04.2008 16:36
An: Tapestry users
Betreff: Re: Automatic class reloading on Tomcat 6 not working for me
Hi,
Due to the way class loaders work in Tomcat you have to jar your classes
etc. and put the jar into WEB-INF/lib.
http://tapestry.apache.org/tapestry5/tomcat.html
-Filip
On 2008-04-16 13:42, Javier Molina wrote:
> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14 and
> 6.0.16). Automatic class reloading doesn't work for pages (there are no
> components yet in this test application, so I haven't checked that).
> Jetty 6 works fine and does autoreload pages.
>
> Is this a known issue? Do I have to configure anything in Tomcat to get
> class reloading to work?
>
> Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
***************************************************************************************************
The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
***************************************************************************************************
BearingPoint GmbH
Geschäftsführer: Peter Mockler (Vorsitzender), Marcel Nickler (stellv. Vorsitzender), Wilfried Erber, Werner Kreutzmann, Hans-Werner Wurzel
Aufsichtsratsvorsitzender: Roderick McGeary
Sitz: Frankfurt am Main
Registergericht: Amtsgericht Frankfurt am Main HRB 55490
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Automatic class reloading on Tomcat 6 not working for me
Posted by "Filip S. Adamsen" <fs...@fsadev.com>.
Hi,
Due to the way class loaders work in Tomcat you have to jar your classes
etc. and put the jar into WEB-INF/lib.
http://tapestry.apache.org/tapestry5/tomcat.html
-Filip
On 2008-04-16 13:42, Javier Molina wrote:
> I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14 and
> 6.0.16). Automatic class reloading doesn't work for pages (there are no
> components yet in this test application, so I haven't checked that).
> Jetty 6 works fine and does autoreload pages.
>
> Is this a known issue? Do I have to configure anything in Tomcat to get
> class reloading to work?
>
> Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org