Each application does get it's own session. It's a security issue, so
one application can't spy on another. 

I believe you're going to have to resort to cookies, unless there is a
way that the business logic in the non-Struts application can be called
from within the Struts application. You could also send it on the query
string, perhaps encrypted and with a confirmation token, but that could
be some work ;-(

The Tomcat 4 Single Login source code might be a starting point for your
own implementation, if cookies can be required and don't raise security
issues. I don't have the package reference handy, but it's now hard to
find if you look.

-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel +1 716 737-3463
-- http://www.husted.com/about/struts/

[EMAIL PROTECTED] wrote:
> 
> Hi,
> 
> Not sure if this is a Struts/general servlet issue.
> 
> I have a non-struts servlet application that allows the user to logon , adding
> logon info to the httpSession, and then after choosing a menu item is redirected
> (response.sendRedirect(response.encodeRedirectURL(path)) to a struts
> application.
> 
> The issue is that the non-struts application and struts application each get
> their own session. So the struts application can not get any logon values from
> the session object.
> 
> I
> 
>   ------------------------------------------------------------------------
> 
> ?ve subclassed ActionServlet, and am calling HttpSession session =
> request.getSession(); from within the process method.
> 
> I?m running Weblogic sp8, and all the apps are running on the same box.
> 
> thanks
> neil
> 
> NOTICE
> The information contained in this electronic mail message is privileged and
> confidential, and is intended only for use of the addressee.  If you are not the
> intended recipient, you are hereby notified that any disclosure, reproduction,
> distribution or other use of this communication is strictly prohibited.  If you
> have received this communication in error, please notify the sender by reply
> transmission and delete the message without copying or disclosing it.

Reply via email to