Re: JSESSIONID issues on WebFacing app

Other than in the very early versions WebFacing is very careful only to 
modify it's own session variables so I can't imagine that it would be 
doing something to kill the session itself.  Currently WF just ignores the 
JSESSIONID URL parm and relies entirely upon the browser handling cookies. 
 Keep in mind that you can only run one WF session in a browser instance 
unless you are running Portal.

Mike



Mike Hockings, P.Eng.
WebSphere Development Tools for AS/400  -  CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory 
hockings@xxxxxxxxxx 
voice 905 413 3199




Christian Lugo <kristpy@xxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
2005-06-27 21:37
Please respond to
Websphere Development Studio Client for iSeries 


To
wdsci-l@xxxxxxxxxxxx
cc

Subject
[WDSCI-L] JSESSIONID issues on Webfacing app






Hello,

What's the proper way to access WebFaced applications
from a menu.

I'm putting all webfaed applications on a menu that's
inside a websphere application, but when I logon to
webfacing it kills my session with the websphere
application and sometimes the user just hangs in the
login screen after I put the password for the webfaced
app.

I guess that the JSESSIONID cookie has the same name
and gets overwritten or something.

Thanks for any help.



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com