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:[EMAIL PROTECTED] 
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:[EMAIL PROTECTED]
>>>> 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: [EMAIL PROTECTED]
>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>>
>>>>
>>>>
>>>> *******************************************************************
>>>> ********************************
>>>>
>>>> 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: [EMAIL PROTECTED]
>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

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


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

Reply via email to