I did something like this too. I can't remember how I did it, but you can also put your app in a separate .war file and use the sitemap rules in the cocoon config file to forward requests to the correct context path.
The advantage of this is that, you don't have to repackage the cocoon.war everytime you redeploy, and you can keep your application in separate war. The disadvantage is that I think that this creates extra (internal) http requests. However in my tests, it didn't slow things down significantly. On Wed, 2003-06-25 at 15:54, Ryan Hoegg wrote: > Hi, > > I got Cocoon 2.1 pre-M1 working on JBoss 3.0.7 with nothing like this > kind of complication. You have to get accustomed to the new Cocoon > build process (since we don't have a binary distribution anymore) but > once its built I simply put my cocoon app into the cocoon WAR and drop > it in $JBOSS_HOME/server/$MY_SERVER/deploy . Works like a charm. > > The build process questions are best addressed to > [EMAIL PROTECTED] > > -- > Ryan Hoegg > ISIS Networks > http://www.isisnetworks.net > > Mitchell, Lincoln L. wrote: -- Peter Beck BEng (hons) MIEE - Managing Director, Electrostrata Ltd. http://www.electrostrata.com --+-+-- Experts in e-business and e-commerce ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
