Well I figured it out. When I accessed the index.jsp, I accesses it
with a different context root (In tomcat, it was the project name).
Tomvat is somehow allowing me to do that.
Since the history page had no context root, it woked, but after that
when I use the correctcontext root, a new session
--- Dilip Ladhani <[EMAIL PROTECTED]> wrote:
> Index Page
> Home Page
>
> header,jsp
> Schedule
> Page
>
> Is the context root (present in header, missing in
> index) making a difference??
Do both ways of making links work?! If you're creating
absolute URLs then aren't the above two links pointi
Sure. Actually, the code to access the session is in the action
classes and not the jsps. It's the same code in both actions (for jsp1
and jsp2)
String cdsID =
((UserTO)request.getSession().getAttribute("userInfo")).getCdsID();
I tried another thing, instead of going to jsp1 from index page (wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dilip,
Dilip Ladhani wrote:
> I have this wierd problem, I have spent a few hours debugging.
[index.jsp:]
> session.invalidate();
> session = request.getSession(true);
>session.setAttribute("userInfo", user);
>
> Now I go to
Hello,
I have this wierd problem, I have spent a few hours debugging. I am
on tomcat 5.5 struts 1.29.
I was using tomcat 5.0.x and struts 1.3.5 earlier and all seemed well.
I switch and encounter this strange problem.
My home jsp is a simple page, where I invalidate the session, create
new and
5 matches
Mail list logo