m to
have more traction than anything else so that's probably where I'll
land.
-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2008 9:54 PM
To: Struts Users Mailing List; [EMAIL PROTECTED]
Subject: RE: [S2] Interceptor question
dave-
.
> Subject: [S2] Interceptor question
> Date: Tue, 16 Sep 2008 16:37:26 -0400
> From: [EMAIL PROTECTED]
> To: user@struts.apache.org; [EMAIL PROTECTED]
>
> I have a mature, home-grown database-backed authentication &
> authorization framework.
> It does not conform
I have a mature, home-grown database-backed authentication &
authorization framework.
It does not conform to JAAS or anything remotely similar.
I'd like to harness in a new struts2 site, because the core
functionality exists, it pre-populated, etc
At a very high level, would I be able to get some
No they won't. Only the login interceptor will be called.
hezjing wrote:
Hi
With the following struts.xml,
index.jsp
Will the interceptors configured in struts-default package be
executed, followed by the login interceptor?
Can we describe this
Hi
With the following struts.xml,
index.jsp
Will the interceptors configured in struts-default package be
executed, followed by the login interceptor?
Can we describe this behaviour in
http://struts.apache.org/2.0.9/docs/interceptors.html as well?
[...]
[this] means that there are no thread safety issues
*of the discussed kind* with interceptor instance variables.
[...]
should have been clear from the discussion context, but thanks for
further clarification :)
Dave Newton schrieb:
> --- Rene Gielen <[EMAIL PROTECTED]> wrote:
>> [this] mea
--- Rene Gielen <[EMAIL PROTECTED]> wrote:
> [this] means that there are no thread safety issues
> with interceptor instance variables.
Well, not in terms of a property of the same name set
in different interceptor references in a config file
(er... it made sense in my head) but interceptors
stil
te the documentation with Rene's finding, as I am sure
> others will also find this unclear and concerning.
>
> Thank you again!
>
> -Original Message-
> From: Rene Gielen [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 10, 2007 2:38 AM
> To: Struts Users Mail
k you again!
-Original Message-
From: Rene Gielen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 10, 2007 2:38 AM
To: Struts Users Mailing List
Subject: Re: [S2] Interceptor Question (Thread Safety)
Ken, others,
now for the definitive answer:
There is one instance per interceptor ref,
MAIL PROTECTED]
Sent: Sunday, July 08, 2007 7:00 AM
To: Struts Users Mailing List
Subject: Re: [S2] Interceptor Question (Thread Safety)
Ken,
there is no problem at all since s2 interceptor instances, as well as
action instances, are created per ActionInvokation, which means they are
always operate
>
> -Original Message-
> From: Rene Gielen [mailto:[EMAIL PROTECTED]
> Sent: Sunday, July 08, 2007 7:00 AM
> To: Struts Users Mailing List
> Subject: Re: [S2] Interceptor Question (Thread Safety)
>
> Ken,
>
> there is no problem at all since s2 interceptor insta
een requests
> and must be thread-safe.
>
> -Original Message-
> From: Rene Gielen [mailto:[EMAIL PROTECTED]
> Sent: Sunday, July 08, 2007 7:00 AM
> To: Struts Users Mailing List
> Subject: Re: [S2] Interceptor Question (Thread Safety)
>
> Ken,
>
> there is n
2007 7:00 AM
To: Struts Users Mailing List
Subject: Re: [S2] Interceptor Question (Thread Safety)
Ken,
there is no problem at all since s2 interceptor instances, as well as
action instances, are created per ActionInvokation, which means they are
always operated in a single thread.
Regards,
R
every request and do not need
to be thread-safe. Conversely, Interceptors are shared between requests
and must be thread-safe.
-Original Message-
From: Rene Gielen [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 08, 2007 7:00 AM
To: Struts Users Mailing List
Subject: Re: [S2] Interceptor
Ken,
there is no problem at all since s2 interceptor instances, as well as
action instances, are created per ActionInvokation, which means they are
always operated in a single thread.
Regards,
Rene
Hoying, Ken schrieb:
From what I understand from reading the documentation, interceptors are
Ken,
there is no problem at all since s2 interceptor instances, as well as
action instances, are created per ActionInvokation, which means they are
always operated in a single thread.
Regards,
Rene
Hoying, Ken schrieb:
From what I understand from reading the documentation, interceptors are
>From what I understand from reading the documentation, interceptors are
suppose to be thread safe. However, I have noticed that some of the
interceptors do contain instance variables and I have seen some
examples where these variables are set or modified from with in the
action configurations.
--- Shahak Nagiel <[EMAIL PROTECTED]> wrote:
> I'm not sure exactly what you're asking, but yes.
> For example, the Before and After annotations, as
> well as all of the validator annotations.
I would have thought he was talking about actual
interceptor refs, to define an interceptor stack for
an
.html
Validator annotations:
http://struts.apache.org/2.x/struts2-core/apidocs/com/opensymphony/xwork2/validator/annotations/package-frame.html
- Original Message
From: Shahak Nagiel <[EMAIL PROTECTED]>
To: Struts Users Mailing List
Sent: Monday, May 14, 2007 4:14:40 PM
Subject: Re: [S2]
g the following logic
in the interceptor class:
if (invocation.getAction().getClass().isAnnotationPresent(SSLProtected.class)){
//... redirect to HTTPS
}
- Original Message
From: Guilherme <[EMAIL PROTECTED]>
To: Struts Users Mailing List
Sent: Monday, May 14, 2007 3:
Hi,
There is a way to configure interceptor via annotations ? or this feature is
not available yet ?
Thanks!
--
Att
Guilherme Mello do Nascimento
PortalJava.com - A maior comunidade Java do Brasil
On 10/29/06 4:21 PM, "Don Brown" <[EMAIL PROTECTED]> wrote:
> Ok, I should have fixed the configuration files reloading too many
> times. Unfortunately, if you use the action tag, they will still
> reload, as that tag doesn't fully use the ActionContext instance from
> the request (where the flag
Ok, I should have fixed the configuration files reloading too many
times. Unfortunately, if you use the action tag, they will still
reload, as that tag doesn't fully use the ActionContext instance from
the request (where the flag to not reload is stored).
If you can, check out trunk and ensure t
On 10/29/06 11:45 AM, "Mark Menard" <[EMAIL PROTECTED]> wrote:
> Here's the log output:
>
> 11:35:40,557 INFO [STDOUT] 11:35:40,557 INFO [XmlConfigurationProvider]
> Parsing configuration file [struts-default.xml]
> 11:35:40,664 INFO [STDOUT] 11:35:40,664 INFO [XmlConfigurationProvider]
> Pars
On 10/29/06 1:59 PM, "Don Brown" <[EMAIL PROTECTED]> wrote:
> Well, first, what version of Struts 2 are you using? My guess is you are
> using Struts 2.0.0, which contained a bug where the configuration would be
> reloaded multiple times in a request.
I'm using struts2-all-2.0.1.jar, which I dow
Well, first, what version of Struts 2 are you using? My guess is you
are using Struts 2.0.0, which contained a bug where the configuration
would be reloaded multiple times in a request. As for your question
why various struts files are loaded, that is how the new plugin system
works. First, str
I was working on a custom interceptor that would use the init() method to
configure itself. After some analysis I realized that the init() method was
being called multiple times per action invocation. So, I made a very simple
interceptor to test to make sure I wasn¹t crazy about this.
package net.
27 matches
Mail list logo
