I asked a much more involved question before and no one responded, so...
Is there a way to share sessions across webapps running in the same
container? A previous message talked about putting a singleton in
/common/lib, but wasn't too specific about how to work it. Could
somebody be more
that and share that user info between multiple
webapps in the same container.
If this hasn't been fleshed out anywhere that's publicly accessible,
would someone like to flesh it out for me and posterity? Or talk me out
of it. I'm open at this point...
Thanks,
Todd O'Bryan
Thanks, Doug. I'll have a look at this today and make sure I understand
it.
Todd
On Dec 3, 2003, at 11:30 PM, Doug Parsons wrote:
The whole class I need, apparently.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
On Dec 3, 2003, at 6:59 PM, Kwok Peng Tuck wrote:
But this means I still have to get a connection, create a statement,
and execute a query or update on the statement in every servlet where
I want to use the connection. Yes, it locates the connection details
(i.e., the JDBC connection method,
I hadn't noticed that ResultSets need to be closed. But why couldn't I
close it after dealing with it in whichever servlet I call it from?
Also, if the Connection is a static variable in SQLUtils that all the
servlets use, it won't ever get closed.
I'm just realizing that there's probably a
On Dec 3, 2003, at 2:59 AM, Nikola Milutinovic wrote:
Peter Harrison wrote:
On Wed, 03 Dec 2003 16:18, Todd O'Bryan wrote:
How do people handle this elegantly? The requirements are: a single,
globally visible (within a webapp) database interface and the ability
to access multiple databases easily
On Dec 3, 2003, at 5:40 AM, Todd O'Bryan wrote:
On Dec 3, 2003, at 2:59 AM, Nikola Milutinovic wrote:
Peter Harrison wrote:
On Wed, 03 Dec 2003 16:18, Todd O'Bryan wrote:
How do people handle this elegantly? The requirements are: a single,
globally visible (within a webapp) database interface
This may not be the right place to ask this, but if you can direct me
to the right place, I'd appreciate it.
I'm looking for a design pattern that someone must have already thought
through so that my head can stop hurting. Here's the problem:
I'm designing a webapp that has several servlets
Is there any block against someone stealing someone else's session id
and using it for nefarious purposes? In other words, if I write a grade
book program, could a sharp student write down the session id from a
web address (if cookies are off) or look in the teacher's cookie file,
and then go
