Contexts are really thin in Webware/WebKit right now. I mean really thin. The only time they've come into play for me is acting as a container for how WebKit instantiates servlets. Unless you do a lot of intra-context servlet inheriting, you've probably never had occasion to read that code.
It's kind of woeful that contexts don't "wrap" a mini-application better to
allow for more configurability. The stickler for me is having to use the
same Session class across all contexts.
do you mean having a single session across contexts? if so, thanks for reminding me of this, since it's a perfect example of the separation i'm referring to.
if contexts are "applications", as i understand them to be, shouldn't they maintain separate state in sessions?
or maybe there is a preferred way to achieve this that i'm not aware of?
------------------------------------------------------- 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
