And another problem:
[WARNING] You set reloadGoals and watcherBouncing > 1, behavior is undefined How can I disable reloadGoals? OPEN KNOWLEDGE GmbH Poststraße 1, 26122 Oldenburg Mobil: +49 151 - 108 22 942 Tel: +49 441 - 4082-154 Fax: +49 441 - 4082-111 [email protected] www.openknowledge.de <https://www.openknowledge.de/> Registergericht: Amtsgericht Oldenburg, HRB 4670 Geschäftsführer: Lars Röwekamp, Jens Schumann Treffen Sie uns auf kommenden Konferenzen und Workshops: Zu unseren Events<https://www.openknowledge.de/event/> ________________________________ Von: Arne Limburg Gesendet: Donnerstag, 23. April 2020 11:57:39 An: [email protected] Betreff: AW: Meecrowave auto reload Hi, I just found another hint to the problem: [11:41:48.621][INFO ][cher-redeployer][.catalina.core.StandardContext] Unable to set the web application class loader property [clearReferencesObjectStreamClassCaches] to [true] as the property does not exist. [11:41:48.621][INFO ][cher-redeployer][.catalina.core.StandardContext] Unable to set the web application class loader property [clearReferencesObjectStreamClassCaches] to [true] as the property does not exist. [11:41:48.622][INFO ][cher-redeployer][.catalina.core.StandardContext] Unable to set the web application class loader property [clearReferencesThreadLocals] to [true] as the property does not exist. This may be part of the problem also tomcat doc states that the properties are true by default. ________________________________ Von: Arne Limburg <[email protected]> Gesendet: Donnerstag, 23. April 2020 11:50:09 An: [email protected] Betreff: Meecrowave auto reload Hi, I am fiddling around with the auto-reload feature in meecrowave. I have configured the maven plugin to set watcherBouncing to 1 and start meecrowave with the plugin. The log correctly states that target classes is scanned OpenWebBeans scanning: [...] [11:41:48.738][INFO ][cher-redeployer][ans.OWBTomcatWebScannerService] [...]/target/classes When I change a class in the deployment, the server correctly does a redeploy, but after the redeploy the content of the changed class seems not to have changed in the server. The class behaves like before. Is there some hidden class caching somewhere (in cxf or tomcat or so), which I have to turn of? Any ideas? Cheers, Arne
