> From: Robert Bourdeau [mailto:[EMAIL PROTECTED]] > > That's pretty unsatisfying. > I just disentangled my Tomcat 3.x JSP apps from each other when > upgrading to Tomcat 4, localizing their WEB-INF dirs to allow > them to be evolved independently. > Now, with Cocoon, I'm back to a single WEB-INF? Not a good solution. > > I found a message from Vadim in the archive (following the Nagoya link) > that suggested the one other idea I had, to add a classpath parameter > to web.xml.
With recent Cocoon versions, this will work only with ParanoidCocoonServlet (IIRC), and intended to be used with servlet engines which do not play nice. > That'll probably work for now, but it introduces name > collisions in classes across multiple applications. This all seems > kinda unsatisfying, but perhaps there's no "good" solution with > Cocoon XSP. I guess I want to think of Cocoon as the application server > with all the flexibility in configuration, but it's an application > IN the server and is restricted accordingly. Exaclty. There is nothing wrong with how Cocoon works. It just follows servlet specification. > It's not that these solutions won't work, but they feel awkward and > seem a little like hacks. I work in a shop where we have multiple > virtual hosts running on a single server configuration, and within > each virtual host, multiple applications. Further, there are dev, > alpha, beta, and prod configurations of everything, so I expect to > be able to configure my software to allow for the independent upgrade > of a Cocoon application from dev to prod without interferring > with any of my other applications (except for changes in the common > components, Cocoon, Tomcat, etc.) Every application has WEB-INF directory, thus, it has all the libraries it needs and it does not interfere with other applications. When you upgrade one of the applications, you just replace application directory with the version of the new one, replacing all the libraries old application has with new versions. This does not affect any other application deployed in the system. So, what's the issue? Vadim > There's no "best practices" guide out there that I found yet for such > configurations. > If not, and if I ever find a nice way to integrate Cocoon into this setup, > perhaps > I'd write it up (if anyone else finds themselves supporting such an > environment). > But I'm still unsatisfied. > > --- Bob > > > > > cocoon/WEB-INF/classes or cocoon/WEB-INF/libs (for jar files) > > > > -Andy > > > > Robert Bourdeau wrote: > > > > >I think there was a thread on this, BUT it appears that the > > >cocoon-users archive is not indexed, there is no web archive, and > > >I can't keep all the Cocoon-user messages. So, apologies in advance > > >if this question was recently asked. (I did check the FAQ, nothing > > >there). > > > > > >Ok, I want to utilize application specific java classes in my XSPs > > >that, using JSP, I would normally location within the <appdir>/WEB-INF > > >directory. I'm quite familiar with the Tomcat 4 class loaders, but > > >Cocoon is its own Tomcat servlet, so it would seem that I'm forced > > >to utilize a WEB-INF directory within the cocoon dir? > > > > > >Suggestions or pointers? > > >Using: > > > Cocoon 2.0.1-dev > > > Tomcat 4.0.1, Apache 1.3.24 with WARP > > > JDK 1.3.1 > > > Solaris 2.7 on a Sparc platform > > > > > > > > >Thanks > > > > > >--- Bob --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
