You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Romain Manni-Bucau (Jira)" <ji...@apache.org> on 2021/05/12 10:33:00 UTC
[jira] [Commented] (MEECROWAVE-290) Enable class-reloading for
watcher-bouncing
[ https://issues.apache.org/jira/browse/MEECROWAVE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343165#comment-17343165 ]
Romain Manni-Bucau commented on MEECROWAVE-290:
-----------------------------------------------
Hi [~arne] +1 to make reloadGoals - or just r/reload command - compatible with watcherBound (no need of any new config IMO) - https://github.com/apache/openwebbeans-meecrowave/blob/master/meecrowave-maven-plugin/src/main/java/org/apache/meecrowave/maven/MeecrowaveRunMojo.java#L424.
> 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
>
> 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)