Oops, I missed it in my last post...
I got the same problem. What I did (and it worked, even as it seems
that it shouldn't) was to store a session reference in the application
context in the last non-secure page, and then retrieve it in the first
secure page. Every object that was store in the session was retrieved.
It's been working fine for over a month. Only be sure that you use a
unique identifier to store it, and to remove the reference after you
use it.
It's not as clean as I wish it to be, but works...
Final Note: I have the shared=true tag set, it suppose that Sessions
are shared too, but they're not.
Tuesday, March 06, 2001, 1:30:18 PM, you wrote:
GM> First, a thank-you to Jay Armstrong for his SimplePortTester. Indeed,
GM> Apache had port 443 locked up even though I thought I had stopped Apache.
GM> Here's the problem of the day:
GM> I'm only using JSP and Beans. It seems when I switch between http and https,
GM> Orion crreates a 'second session'. I have inserted a System.err.println in
GM> EVERY method of my SessionBean which has a single boolean property:
GM> loggedOn. My comments (//)
GM> Is this a bug or a feature? If it's a bug or a feature, is there a
GM> work-around? It makes no sense to me why you would want to create a second
GM> 'session'.
--
Best regards,
Rafael mailto:[EMAIL PROTECTED]
