2) in a java servlet container like tomcat, each context is analagous to a separate application. in webware, this separation doesn't seem to exist. each context appears to be, basically, just a mapping of a URL segment to a directory. should i run a separate application server instance for each application that needs "separation" from other applications?
I think the answer is No. But I'm curious what kind of separation would you like? I haven't used Tomcat and I am thinking about if contexts should be removed from Webware since it doesn't do anything useful at the moment. Is there something good about contexts in Tomcat that we should build up?
it might just be a difference in architecture. i still don't quite get how the server and applications/contexts relate to each other in webware.
let's say i have two unrelated applications, "inventory" and "human-resources", to be hosted on the same physical machine. would i run MakeAppWorkDir for each:
MakeAppWorkDir -c inventory /usr/local/webapps/inventory MakeAppWorkDir -c human-resources /usr/local/webapps/human-resources
...and then create two init scripts, run two ThreadedAppServer instances on different ports, add entries for each in the apache config files, etc...? if so, it seems it would become unwieldy once you start getting into dozens of applications on the same box.
or, use MakeAppWorkDir once, and just create additional context directories manually:
MakeAppWorkDir -c inventory /usr/local/webapps mkdir /usr/local/webapps/human-resources
...and just put the human resources servlets etc in that directory?
while i have the opportunity, an unrelated question (which may stem from my conception of contexts as isolated applications): in servlets, is it possible (or even desirable) to have paths interpreted relative to the context root?
eg, using the example above, when i reference a cheetah template i have to do something like this:
template = Template(file="inventory/stock-levels.tmpl")
this feels awkward to me - again, perhaps because i think that the context is the application root, and therefore the application shouldn't have to know the name of the directory that its files are in.
thanks
------------------------------------------------------- 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
