tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Ignatyev (JIRA)" <...@tapestry.apache.org>
Subject [jira] Updated: (TAPESTRY-1698) On the windows component class change does not get loaded
Date Wed, 08 Aug 2007 21:56:59 GMT

     [ https://issues.apache.org/jira/browse/TAPESTRY-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Konstantin Ignatyev updated TAPESTRY-1698:
------------------------------------------

    Description: 
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.

  was:
T senses that 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.

        Summary: On the windows component class change does not get loaded  (was: On the windows
new class does not get loaded)

> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message