[
https://issues.apache.org/jira/browse/TAPESTRY-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529722
]
Nick Westgate commented on TAPESTRY-1698:
-----------------------------------------
Konstantin wrote Tomcat 5.5.23 in the Environment area above.
Someone on the list investigated and thinks this is because of Tomcat caching.
Here it is:
http://www.nabble.com/RE%3A-T5-developing-with-WTP-and-TOMCAT-p12505301.html
Cheers,
Nick.
> On the windows component class change does not get loaded
> ---------------------------------------------------------
>
> Key: TAPESTRY-1698
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1698
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.5
> Environment: Win XP, tomcat 5.5.23
> Reporter: Konstantin Ignatyev
> Fix For: 5.0.6
>
>
> T senses that component class was changed but still gets initial class
> definition from javassist pool and therefore enhances the old class
> definition that does not help at all.
> org.apache.tapestry.internal.services.ComponentInstantiatorSourceImpl#onLoad
> method gets called after changing the class, but actual changes do not get
> picked up.
> Surely if I restart whole application the change taking effect and everything
> is fine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
