For the sake of a clean design, restrict your transaction management to
your model layer (in MVC). That means, like Navjot says, keep it clear
of your struts action classes.
On 02/24/2004 10:19 AM Navjot Singh wrote:
struts has nothing to do with managing sessions. we should better
talk about s
struts has nothing to do with managing sessions. we should better
talk about servlet containers that handles sessions.
btw, 100 sessions are nothing to worry about :-)
leave the txn mgmt to db layer. use any of the persistence frameworks
that can handles this for you.
>-Original Message
Jason Meredith wrote:
Chaps
I am sure this question has been asked before, if it has please point me in
the right direction (URL - example)
A user log's into a web site, once the user has been authenticated, a
session is created , there are many different actions that a user can
perform, and it
Jason,
Authentication and session creation are mostly independent -- you can have a
user with a session that has not been authenticated. I think a user will
always have a session once they have been authenticated, however.
I am not sure I understand quite what you are asking, but you can certainl
|What do I do for those pages that do not have actions, pages that have
|global forwards for example (org.apache.struts.actions.ForwardAction),
|things like legal pages, site maps, and so on? I don't want to create an
|action just to display a simple JSP/HTML page, that's why I used a forward.
|
t
TECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, January 13, 2003 7:07 AM
Subject: Re: Session Management
Re: Session ManagementAgree that hidden variables can be used to store some
values, but this may lead to higher network trafic.
Yeah for large applicatio
, January 11, 2003 4:45 AM
Subject: Re: Session Management
Puneet Agarwal wrote:
> Session Management is required to achieve persistence. there are two manner
> in which persistence can be achieved.
>
> 1. storing the information in HTTP session (possibly in session scope)
Puneet Agarwal wrote:
Session Management is required to achieve persistence. there are two manner
in which persistence can be achieved.
1. storing the information in HTTP session (possibly in session scope)
2. Storing the information using stateful session beans.
You can also use hidden fields
Session Management is required to achieve persistence. there are two manner
in which persistence can be achieved.
1. storing the information in HTTP session (possibly in session scope)
2. Storing the information using stateful session beans.
You have to take the decision based on your application
Session Management is required to achieve persistence. there are two manner
in which persistence can be achieved.
1. storing the information in HTTP session (possibly in session scope)
2. Storing the information using stateful session beans.
You have to take the decision based on your application
Either way is fine. It's highly unlikely that choice 2 would have any
noticable performance problems.
David
From: "JONATHAN PHILIP HOLLOWAY" <[EMAIL PROTECTED]>
Reply-To: "JONATHAN PHILIP HOLLOWAY" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Subject: Session Man
> -Original Message-
> From: JONATHAN PHILIP HOLLOWAY [mailto:[EMAIL PROTECTED]]
> 1. Storing things within the standard servlet session
>
> 2. Using a UserWrapper object and storing that within the session.
>
> Is the second way more preformance intensive or not and which is best
> pract
-
From: Thomas Eichberger [mailto:[EMAIL PROTECTED]]
Sent: Saturday, October 12, 2002 6:44 PM
To: Struts Users Mailing List
Cc: [EMAIL PROTECTED]
Subject: Re: session management problem
Maybe stupid question, but what session-timeout do you have? May be the
user just didn't do anything on the
Maybe stupid question, but what session-timeout do you have? May be the
user just didn't do anything on the page for a period longer than the
session timeout?
Thomas
At 17:25 12.10.2002 +0530, srinivas wrote:
>
>
>we are developing a intranet enterprise application, we are facing a
>typical
Users Mailing List
Subject: RE: Session management for cached resources
On Wed, 2002-10-02 at 19:14, Andrew Hill wrote:
> Im doing something rather like this, only I called it an
"OperationContext"
> which comprises a hashtable of attributes and an id to store it under in
the
>
On Wed, 2002-10-02 at 19:14, Andrew Hill wrote:
> Im doing something rather like this, only I called it an "OperationContext"
> which comprises a hashtable of attributes and an id to store it under in the
> session (passed in the request). I simply overrode the RequestProcessor so
> it knew to loo
Im doing something rather like this, only I called it an "OperationContext"
which comprises a hashtable of attributes and an id to store it under in the
session (passed in the request). I simply overrode the RequestProcessor so
it knew to look for an actionform in the OperationContext first if the
I created a filter as advised by Greg. It works wonderfully.
You could protect requests for any resource with Filters.
See suns j2ee web tutorial for a filter example.
On Wed, 2002-06-12 at 13:19, Dennis Muhlestein wrote:
> Using Struts 1.0.2
>
> Some of my pages have ActionForms.
> Some only
, but since silter is not support in any other servlet api that come
before Servlet2.3.
> -Original Message-
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, June 12, 2002 12:38 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Session Management Methodology
The standard wisdom is that you only do type-validation in the form and
you do business validation later, i.e. make sure a date's a date and a
number's a number. There's not exactly much overhead or drawback to
doing that for everybody, whether they're logged in or not.
If you're worried about
I think filters are the best way to handle redirection to a logon
screen, but that requires Servlet 2.3. Otherwise you have to either
modify the ActionServlet to redirect before calling the Action or
ActionForm, or put code in the Action that checks for a valid login
before continuing. I would m
Thanks for the input.
I thought of that. But what if My ActionForm needs to know who is
logged in before it can validate the data. That's pushing it I know, I
probably shouldn't validate that much data in a form. I don't think I
am... but what if?
Is there a standard way to intercept that o
I extended the Action class to do that. I have one Action class that
does that and so on, and all my other Action classes extend it.
Adam
Dennis Muhlestein wrote:
>Using Struts 1.0.2
>
>Some of my pages have ActionForms.
>Some only have Action Classes that do something.
>
>Some have nothing bu
On Mon, 11 Mar 2002, Mark Glass wrote:
> I'm developing a web application in Struts that requires a user to
> have a session before they can use the application. Currently anyone
> can bypass the logon and use the application. I would like the user to
> be required to login first. I am saving the
"Joseph Barefoot" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, March 11, 2002 8:27 PM
Subject: RE: Session management in Struts
> That sounds like a good idea to meso, this Authentication Filter is
sort
ther frameworks when using
Filters?
--joe
-Original Message-
From: Sean Willson [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 11, 2002 5:53 PM
To: Struts Users Mailing List
Subject: Re: Session management in Struts
We accomplished this by writing an Authentication Filter that sits in fron
We accomplished this by writing an Authentication Filter that sits in front
of all requests to the servlet container. The problem with putting it in a
Struts Action and then subclassing that (which we did do at one time) is
that you can only then protect things going through Struts. Which in itsel
Dear Mark:
Did you actually check if the session variables about username and pwd info were null
or correct at the beginning of those pages? Plus, you need to clear up these session
variables after the user log out.
Ye
Mark Glass wrote:
> I'm developing a web application in Struts that requi
The example application that comes with Struts has a taglib that
provides this very functionality. There's a tag that checks to make
sure that the user is properly stored in the session, and if they
aren't, it forwards them to the login page.
On Mon, Mar 11, 2002 at 04:07:39PM -0500, Mark Glass
I'm not sure about a paper or tutorial Mark, but we accomplish this by
sub-classing the struts Action class and peforming authentication there.
All Action classes in the system except the login Action use this class
(call it CustomAction) as their superclass. All user information (id,
password, e
"Nanduri, Amarnath" wrote:
> i have seen a posting on this list a month back where
> somebody has explained that using javascript we can generate a unique id for
> every new web browser that was opened by the user
search the archives for: "The Joy of File"
Pete
begin:vcard
n:;
x-mozilla
ECTED]]
Sent: Wednesday, May 09, 2001 5:44 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Session management with Struts
But that's exactly my problem. I have forms that may span multiple pages and
the ActionForm needs to be available across multiple requests. Any ideas
-Origin
TECTED]
cc:(bcc: Andrew Steady/Swindon01/Domino01/Kinesis)
Subject: RE: Session management with Struts
But that's exactly my problem. I have forms that may span multiple pages
and
the ActionForm needs to be available across multiple requests. Any
ideas
-Original Message-
From: Na
PROTECTED]'
Subject: RE: Session management with Struts
Keep the ActionForms in 'request' scope. Then each page will have its own
ActionForm. The problme occurs when you want to store these forms in session
scope.
cheers,
Amar..
-Original Message-
From: TJM Todd McGregor
Keep the ActionForms in 'request' scope. Then each page will have its own
ActionForm. The problme occurs when you want to store these forms in session
scope.
cheers,
Amar..
-Original Message-
From: TJM Todd McGregor [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 09, 2001 4:49 PM
To: [E
35 matches
Mail list logo
