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

Arne Limburg resolved MEECROWAVE-290.
-------------------------------------
    Fix Version/s: 1.2.12
       Resolution: Fixed

> Enable class-reloading for watcher-bouncing
> -------------------------------------------
>
>                 Key: MEECROWAVE-290
>                 URL: https://issues.apache.org/jira/browse/MEECROWAVE-290
>             Project: Meecrowave
>          Issue Type: Bug
>    Affects Versions: 1.2.11
>            Reporter: Arne Limburg
>            Assignee: Arne Limburg
>            Priority: Major
>             Fix For: 1.2.12
>
>
> Automatic reloading of the tomcat context currently can be enabled by setting 
> watcher-bouncing to a value greater than 0. Unfortunately the used class 
> loader is not replaced in that case, so that changes to classes are not 
> reflected in the newly loaded context.
> I suggest to add a configuration parameter "reloadClasses" to configure, if 
> classes should be reloaded in that case. Class-reloading is no problem with 
> the maven plugin, but causes problems, when reloading is done in the code 
> (i.e. WatcherTest)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to