The un-war-ing of our web application archives is not always happening reliably and our production deployment routine for our portlet applications is becoming just too cumbersome.
At the moment, we have to: 1. Deploy the war to jetspeed's deploy directory. 2. Once the context reloads, we then have to manually unwar it to get the latest changes into the exploded war directory. 3. Once the context reloads for the second time, we have to stop tomcat and wait for it to shut down completely and then start it again. This last step is required because we are getting PermGen out of memory exceptions all the time. We'd like to try by-passing jetspeed's deployment mechanism and try using tomcat's deployment tools directly to see if we can improve the situation. If we go this route, besides adding the JetspeedContainer servlet and servlet mapping and the portlet.tld, is there anything else i need to do? Do I need to notify jetspeed when I add a new portlet app or change a portlet.xml so that it reloads the portlet app and portlet specific db entries? thanks, aaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
