i always loved the productivity i got from tomcat using exploded wars. using eclipse and directly compiling into the exploded WEB-INF/classes got Tomcat pick up my changes in seconds. Using wso2 with its embedded tomcat i noticed, that you turned off this great feature. any chance, that you could repair this?
i tinkered around with your code base and got the context reloading working by a small change in TomcatGenericWebappsDeployer https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk05/components/webapp-mgt/org.wso2.carbon.webapp.mgt/4.2.2/src/main/java/org/wso2/carbon/webapp/mgt/TomcatGenericWebappsDeployer.java. I just commented out the statement "context.setReloadable(false)". I also had to turn off the checkAccess method in CarbonTomcatSessionManager <https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk05/components/webapp-mgt/org.wso2.carbon.webapp.mgt/4.2.2/src/main/java/org/wso2/carbon/webapp/mgt/CarbonTomcatSessionManager.java> https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk05/components/webapp-mgt/org.wso2.carbon.webapp.mgt/4.2.2/src/main/java/org/wso2/carbon/webapp/mgt/CarbonTomcatSessionManager.java I assume, the latter is quite a little bit brute force and there should be a better way. Anyway, with these two changes i got back the Tomcat productivity with WSO2 AS 5.2.1. Would like to get your feedback on a) my approach b) any possibly better alternatives, you could suggest, which i might have missed c) what chance to get back the tomcat development speed with exploded wars in a future release of wso2 as best regards, thomas wieger
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
