I've just created enhancement request https://bugs.eclipse.org/bugs/show_bug.cgi?id=124914
From the description Over last few months I've developed alternative Tomcat 5.5 plugin which has two main advantages compared to standard Tomcat support provided by WTP * All resources and classes are deployed by reference to their workspace location, in other words, this plugin does not create/maintain exploded webapp under .metadata/.../tmpX directory. As a result, publish time is very small and does not depend on webapp size. Also, tomcat picks changes to JSPs without publish. * It is possible to publish set of related webapps with common dependent utility jars. You can, for example, develop and test related portlets as separate webapps with Tomcat/Pluto. There are also a number of smaller changes that solve minor annoyances I've come across while using standard Tomcat plugin v0.7. I did not check if any/all of these were fixed in WTP 1.0. * Source lookup works for dependent utility JARs. * Launch configuration does not explicitly reference Tomcat installation directory and can be shared among team members. * Server Classpath Container includes JAR/ZIP files from CATALINA_HOME/shared/lib. * Cleaner (at least in my opinion) management of Tomcat configuration files. Webapps are deployed using individual context xml files under CATALINA_BASE/conf/<Engine>/<Host>. Required config files (server.xml, catalina.properites, etc) will be copied from CATALINA_HOME/conf if not present in server configuration. As a result, server configuration is much easier to share among team members. * Most of <webapp>/WebContent/META-INF/context.xml is preserved during publish – only @docBase and /Loader are changed, everything else is copied as is without any modifications. * Better handling of webapp/server restart. Will not trigger restart after successfull Hot Code Replace. Restarts individual webapps when possible. * Handles external jar file dependent modules. Installation/configuration instructions This plugin is completely independent from regular Tomcat support and the two can coexist without problems. * This plugin was developed and somewhat ;-) tested using WTP 1.0. Make sure to use latest 1.0.1 M-build to avoid performance problems of 1.0. It works with 1.5 M4 too. * Drop org.eclipse.jst.server.experimental.tomcat_<version>.jar to WTP plugins directory and restart WTP * Define "Apache Tomcat v5.5 (Experimental)" runtime * Create "Tomcat v5.5 Server (Experimental)" server configuration. As described above, server config directory does not need to have files. Create configuration files (like tomcat-users.xml or server.xml) under <server-config>/conf directory if needed. * Use "Add and Remove Projects..." dialog (right click in Servers view) to add and remove projects deployed to this server. If you are interested in features provided by this plugin I encourage adding yourself to CC list of this bug so WTP developers and I ;-) can see if there is enough interest to continue deevelopment of this code. Also, feel free to add comments to this bug or ask questions on the newsgroup. -- Regards, Igor Fedorenko _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
