I would be happy to make any modifications that would be required. I've spent a bit of time looking around at the source already, but I'm not sure what the best approach would be. It would be nice if it could be done in a "plugin" kind of way, but after looking around a bit, it seems that the concept of a single physical directory as a docbase is pretty ingrained (comments?).
So far, I've looked at the following: 1. Writing a new catalina Context implementation 2. Writing a new jndi DirContext implementation, that would be configurable to take multiple directories Of those two, I think #2 makes the most sense, but I have doubts as to whether it would solve the problem. What I'm afraid of is that the changes required are peppered throughout the Tomcat codebase. Any pointers that you could give me to get me started in the right direction initially would be hugely appreciated. The only reason that I'm spending so much energy on this is that for very large web applications that are not structured as a webapp, which I think is rather common, it would be a HUGE aid in debugging to be able to pull something like this off. The code/compile/debug cycle gets a bit cumbersome when one is constantly redeploying large apps. I think for deployment the spec works just fine. Thanks again for your help, and all of your excellent work. Dave Keyes -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 22, 2003 4:24 PM To: Tomcat Users List Subject: RE: Resources for a Context On Wed, 22 Jan 2003, David Keyes wrote: > Date: Wed, 22 Jan 2003 15:53:22 -0500 > From: David Keyes <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: Tomcat Users List <[EMAIL PROTECTED]> > Subject: RE: Resources for a Context > > So what mechanism would you suggest for making MORE than one Resources > directory available for a Context? * Modify Tomcat to support multiple resources directories (It's open source :-). Note that you're violating the letter and spirit of the servlet spec's requirements on webapp organization, so it would be problematic accepting such a change back into Tomcat's core. * Use symbolic links (which doesn't help Windows users much). * Build deployment scripts that copy everything you need in the webapp together. Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
