From: lloyd <sub...@tw...> - 2005-02-02 10:02:38
|
Ben Parker wrote: > Webware developers tend to think of separate contexts as separate > applications, but they are definitely not. Once you understand the > relationship, you can hand-wave it and go about building your app, most > likely ignoring contexts entirely aside from the one you set up to contain > the servlets. currently the few webware applications i've created each reside in a context, and each context contains its servlets, templates, etc. again, aknowledging my java servlet hang-over: in tomcat, each context is a separate web application, with its own class hierarchy, its own /lib, its own configuration like security settings, ip restrictions, etc. the same user visiting two contexts will receive a separate session for each context. so, to achieve this in webware, i must run separate instances of AppServer and change the apache config each time i add one, right? thanks a lot for your patience laying this out for me. maybe a "webware for java servlet developers" page might be nice to have in the wiki. fwiw, i just finished my first pair of webware applications, and i'm definitely liking it. if nothing blows up once they go into production i'll be a convert :-) |