Hi John-
I'm curious about what the context does for you that you like? I'm wondering if you just had different directories inside one context, wouldn't that be about the same as different contexts?
idea (and if it really is a bad idea, I'd love to know why), but it seems to
I don't see it as a really bad idea, only that it's not that useful and there is a lot of special-case code to handle it.
-winston
On Jan 31, 2005, at 10:06 AM, John Dickinson wrote:
I have not used tomcat, but we do use webware contexts to separate "applications" from one another. Others on the list may think this is a bad idea (and if it really is a bad idea, I'd love to know why), but it seems to work for us. We have four instances of webware running: develop, model, demo, and prod. Develop is where we do all of our developing. Model and demo are for relatively stable versions for additional testing and demonsration purposes, and prod is where our production versions live. All four have the same (or similar) directory/context structure. So there may be a dozen different contexts in each of develop, model, etc., and each context is its own separate application. As each project (application) is developed, it moves through our four webware instances from develop to prod. I don't know if this system meets your needs for "separation," but it works for us.
--John
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
