Michael McGrady wrote:
We had a round of discussions on this in the near past. Right Mark? Mark
has gone back to crack after that discussion. LOL
Well, actually, Mark took Neill's advice and became a cgi programmer.. (So
crack is now in his job description.)
Gopalakrishnan, Jayesh wrote:
Andy,
Just to understand your page flow
The first request goes to /home.do, which puts junkbean
into the request scope, forwards to index.jsp.
On submit of the form on index.jsp, /login.do is invoked
which then forwards to /home.do.
Is this
How about putting some log statements around the code which sets the request
attribute? That'll assure you that the code is getting executed, and that
the data you're putting there actually has values in them.
Have you tried re-requesting home.do after a successful login? Does the data
show
Hubert Rabago [EMAIL PROTECTED] wrote:
How about putting some log statements around the code which sets the
request attribute? That'll assure you that the code is getting
executed, and that the data you're putting there actually has values
in them.
No I haven't, but that's a good idea.
Hi all,
I'm working on a web app where I have my JSPs hidden beneath WEB-INF.
In doing so, I of course have actions which RequestDispatch those pages
to the user. In doing this I am running into a problem where beans in
those returned JSPs are not getting updated when they are returned from
I am having a hard time seeing what you want to do, but I know that your
issues with the junkbean are unrelated to the hiding of the JSPs
behind/beneath/be-whatever WEB-INF. If you want to access data, including
an object, then the data must be saved somewhere and then accessed where it
is
In addition to my previous nonsense, let me spout the following too:
At 02:44 PM 3/4/2004, you wrote:
Hi all,
I'm working on a web app where I have my JSPs hidden beneath WEB-INF.
In doing so, I of course have actions which RequestDispatch those pages
to the user. In doing this I am running
Michael McGrady wrote:
I am having a hard time seeing what you want to do, but I know that
your issues with the junkbean are unrelated to the hiding of the
JSPs behind/beneath/be-whatever WEB-INF. If you want to access data,
including an object, then the data must be saved somewhere and then
Michael McGrady wrote:
There are no beans in returned JSPs. In fact, there are no returned
JSPs. I assume you mean to talk about the response object. That
includes only HTML in your case, I am betting.
Yes -- that's what I meant.
The client requests /login.do. What it means to say
Your junkbean is lost once index.jsp is rendered on the browser. Thats
the end of the request scope. If you want the junkbean to last
for more than 1 page on the browser, I guess session scope is
appropriate. You can always remove it from the session after u
have used it in LoginAction.
hth
, 2004 5:13 PM
:- To: Struts Users Mailing List
:- Subject: Re: Returning fully-stocked Actions/JSPs from other Actions
:-
:-
:- Michael McGrady wrote:
:-
:- I am having a hard time seeing what you want to do, but I
:- know that
:- your issues with the junkbean are unrelated to the
:- hiding
Randy Dillon [EMAIL PROTECTED] wrote:
... Your first request scope ends once index.jsp loads; if you want
to use the junkbean again after that, you have to save it again,
either in the new request or in the session (or possibly other
places, but those are the 2 most obvious).
Right -- I am
Gopalakrishnan, Jayesh wrote:
Your junkbean is lost once index.jsp is rendered on the browser.
Thats the end of the request scope. If you want the junkbean to
last for more than 1 page on the browser, I guess session scope is
appropriate.
Sure, but I don't want the bean to be saved at the
-Original Message-
From: Andy Engle [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 04, 2004 3:47 PM
To: Struts Users Mailing List
Subject: RE: Returning fully-stocked Actions/JSPs from other Actions
Gopalakrishnan, Jayesh wrote:
Your junkbean is lost once index.jsp is rendered
: Returning fully-stocked Actions/JSPs from other Actions
:-
:-
:- Randy Dillon [EMAIL PROTECTED] wrote:
:-
:- ... Your first request scope ends once index.jsp loads;
:- if you want
:- to use the junkbean again after that, you have to save it again,
:- either in the new request or in the session
If you save it in request scope, then it will be gone afterward. That is
your problem.
At 03:22 PM 3/4/2004, you wrote:
Michael McGrady wrote:
There are no beans in returned JSPs. In fact, there are no returned
JSPs. I assume you mean to talk about the response object. That
includes only
We had a round of discussions on this in the near past. Right Mark? Mark
has gone back to crack after that discussion. LOL Anyway, I don't think
it is advisable to save the contents of an action form in session
scope. But, exactly what you are doing is not clear. Maybe in your case
it
The key here is NOT which ACTION but which SCOPE.
At 03:44 PM 3/4/2004, you wrote:
Randy Dillon [EMAIL PROTECTED] wrote:
... Your first request scope ends once index.jsp loads; if you want
to use the junkbean again after that, you have to save it again,
either in the new request or in the
I cannot say I am a fan of any of this, but the fact that you want to
update the bean is reason to save it not toss it.
At 03:47 PM 3/4/2004, you wrote:
Gopalakrishnan, Jayesh wrote:
Your junkbean is lost once index.jsp is rendered on the browser.
Thats the end of the request scope. If you
19 matches
Mail list logo
