You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Raghu Kanchustambham <kr...@gmail.com> on 2005/11/19 18:45:42 UTC
jaas authorization with struts
Hi,
I could successfully place my authentication scheme in place using the
article at
http://www.jroller.com/comments/tomdz?anchor=using_jaas_with_struts_a
I also could place "resource" level authorization in place. However the
definition of resource is the "traditional" action mapping. However I have a
requirement which goes beyond that. I have a centre based roles. Let us say
my application could be used by administrators at three centres. The trick
is that all of them can view the set of "resources"... but in a particular
JSP they are authorized to use only certain values for some of the fields.
For example, a Hyderabad administrator can view reports pertaining to
Hyderabad only and should not be allowed to see reports of Bangalore centre.
Which let us say in UI terms would translate to a dropdown of cities .. for
the Bangalore administrator... he probably can see the dropdown populate
with Bangalore... the Hyderabad admin sees it populated only with Hyderabad
and a HeadOffice admin sees all the cities in the cities dropdown.
What is the best way to achieve this?
One approach is to create a separate role for each centre user. For
example... have a role called Bangalore_Admin and Hyderabad_Admin etc. But
obvious drawback is that this approach won't scale well with the increase in
the number of centres.
The other approach I was thinking is writing code myself. Introduce a
column for centre in the user table. From the
request.getUserPrincipal().getName()
funcion I determine the user... hit the database to determine the centre and
then filter the cities based on the city and the role.
I don't like this approach because I have lost the advantages of a
declarative style of defining security permissions. Also, now my
authorization code would be mixed allover and would be difficult to change
the authorization policies on a later date.
The third approach is similar to the second one. Instead of defining a
centre at the user level, I could do it at the user_role mapping level.
User1 is the administrator of Hyderabad centre. He could be a regular user
for another centre (say Bangalore). Slightly better than second approach but
suffers from similar problems.
Is there a way that my getUserPrincipal() can be made to give me this extra
piece of information about the centre? That would make my code look lot
cleaner. I dont have to hit back the database just to find the centre.
Please comment.
Thanks much.
Regards,
Raghu
Re: jaas authorization with struts
Posted by Laurie Harper <la...@holoweb.net>.
It does rely on Spring, yes, but getting Spring to co-exist with Struts
is trivial; you don't need to change any existing code to do that,
though once you have Spring available you may well find yourself wanting
to take advantage of it ;-)
L.
Raghu Kanchustambham wrote:
> On the first cut this looks like authentication/authorization for Spring
> framework. Do I need to get struts co-exist with spring for this to work ?
> And how much of an effort would that be?
> But yes.. this looks quite a powerful and neat concept.
> Thanks for refering it.
> Regards,
> Raghu
>
>
> On 11/20/05, Laurie Harper <la...@holoweb.net> wrote:
>
>>Take a look at the Acegi Security project. It provides *extremely*
>>powerful declarative security capabilities, upto and including filtering
>>database query results to exclude things the current user shouldn't be
>>able to see. It might be exactly what you're looking for.
>>
>>L.
>>
>>Raghu Kanchustambham wrote:
>>
>>>Hi,
>>>I could successfully place my authentication scheme in place using the
>>>article at
>>>http://www.jroller.com/comments/tomdz?anchor=using_jaas_with_struts_a
>>>I also could place "resource" level authorization in place. However the
>>>definition of resource is the "traditional" action mapping. However I
>>
>>have a
>>
>>>requirement which goes beyond that. I have a centre based roles. Let us
>>
>>say
>>
>>>my application could be used by administrators at three centres. The
>>
>>trick
>>
>>>is that all of them can view the set of "resources"... but in a
>>
>>particular
>>
>>>JSP they are authorized to use only certain values for some of the
>>
>>fields.
>>
>>>For example, a Hyderabad administrator can view reports pertaining to
>>>Hyderabad only and should not be allowed to see reports of Bangalore
>>
>>centre.
>>
>>>Which let us say in UI terms would translate to a dropdown of cities ..
>>
>>for
>>
>>>the Bangalore administrator... he probably can see the dropdown populate
>>>with Bangalore... the Hyderabad admin sees it populated only with
>>
>>Hyderabad
>>
>>>and a HeadOffice admin sees all the cities in the cities dropdown.
>>>What is the best way to achieve this?
>>>One approach is to create a separate role for each centre user. For
>>>example... have a role called Bangalore_Admin and Hyderabad_Admin etc.
>>
>>But
>>
>>>obvious drawback is that this approach won't scale well with the
>>
>>increase in
>>
>>>the number of centres.
>>>The other approach I was thinking is writing code myself. Introduce a
>>>column for centre in the user table. From the
>>>request.getUserPrincipal().getName()
>>>funcion I determine the user... hit the database to determine the centre
>>
>>and
>>
>>>then filter the cities based on the city and the role.
>>>I don't like this approach because I have lost the advantages of a
>>>declarative style of defining security permissions. Also, now my
>>>authorization code would be mixed allover and would be difficult to
>>
>>change
>>
>>>the authorization policies on a later date.
>>>The third approach is similar to the second one. Instead of defining a
>>>centre at the user level, I could do it at the user_role mapping level.
>>>User1 is the administrator of Hyderabad centre. He could be a regular
>>
>>user
>>
>>>for another centre (say Bangalore). Slightly better than second approach
>>
>>but
>>
>>>suffers from similar problems.
>>>Is there a way that my getUserPrincipal() can be made to give me this
>>
>>extra
>>
>>>piece of information about the centre? That would make my code look lot
>>>cleaner. I dont have to hit back the database just to find the centre.
>>>Please comment.
>>>Thanks much.
>>>Regards,
>>>Raghu
>>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>>For additional commands, e-mail: user-help@struts.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: jaas authorization with struts
Posted by Laurie Harper <la...@holoweb.net>.
I'm not sure of the specifics, this isn't a capability I've used; I just
know it's there ;-)
L.
Adam Hardy wrote:
> Something that removes items from collections according to data
> visibility constraints declaratively must be quite complex.
>
> Presumably the collections are declared in a Spring-style context factory?
>
> And then you would have to declare which property of the item provides
> the IDs, and you also declare a set of IDs which each role has
> visibility of? Can you provide an object reference in Acegi config with
> a callable method that will return the IDs required?
>
> Or am I wide of the mark here?
>
> rgds
>
> Adam
>
> Laurie Harper on 20/11/05 23:38, wrote:
>
>> Actually, Acegi does offer what Raghu was looking for (or at least one
>> possible route to achieving it). One of the things it can do is
>> automatically filter collections to remove items the current user
>> shouldn't be allowed to see, so you don't have to bury that kind of
>> business logic in your database. Since it lets you do this
>> declaratively, it's easy to change with changing business requirements.
>>
>> L.
>>
>> Adam Hardy wrote:
>>
>>> Hi Raghu, Laurie,
>>>
>>> I did a project recently which used the Acegi security project which
>>> comes bundled with Spring, and although I was never involved in the
>>> implementation of it myself, I heard that it was effective.
>>>
>>> Am I correct in assuming though that it does not offer the
>>> alternative that Raghu was looking for, despite the fact that he(you)
>>> seems very positive about it?
>>>
>>> I can't see how such a security requirement can be implemented in any
>>> other way than via the database. It is simply a question of data
>>> visibility, in other words, who the data is visible to and to whom it
>>> is not visible. The best you can do as far as I can see is to
>>> optimise the caching, especially if the relationships are relatively
>>> stable.
>>>
>>> Or is this perhaps a pattern that I am not aware of?
>>>
>>>
>>> Adam
>>>
>>>
>>>
>>> Raghu Kanchustambham on 20/11/05 16:50, wrote:
>>>
>>>> On the first cut this looks like authentication/authorization for
>>>> Spring
>>>> framework. Do I need to get struts co-exist with spring for this to
>>>> work ?
>>>> And how much of an effort would that be?
>>>> But yes.. this looks quite a powerful and neat concept.
>>>> Thanks for refering it.
>>>> Regards,
>>>> Raghu
>>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: jaas authorization with struts
Posted by Adam Hardy <ah...@cyberspaceroad.com>.
Something that removes items from collections according to data
visibility constraints declaratively must be quite complex.
Presumably the collections are declared in a Spring-style context factory?
And then you would have to declare which property of the item provides
the IDs, and you also declare a set of IDs which each role has
visibility of? Can you provide an object reference in Acegi config with
a callable method that will return the IDs required?
Or am I wide of the mark here?
rgds
Adam
Laurie Harper on 20/11/05 23:38, wrote:
> Actually, Acegi does offer what Raghu was looking for (or at least one
> possible route to achieving it). One of the things it can do is
> automatically filter collections to remove items the current user
> shouldn't be allowed to see, so you don't have to bury that kind of
> business logic in your database. Since it lets you do this
> declaratively, it's easy to change with changing business requirements.
>
> L.
>
> Adam Hardy wrote:
>
>> Hi Raghu, Laurie,
>>
>> I did a project recently which used the Acegi security project which
>> comes bundled with Spring, and although I was never involved in the
>> implementation of it myself, I heard that it was effective.
>>
>> Am I correct in assuming though that it does not offer the alternative
>> that Raghu was looking for, despite the fact that he(you) seems very
>> positive about it?
>>
>> I can't see how such a security requirement can be implemented in any
>> other way than via the database. It is simply a question of data
>> visibility, in other words, who the data is visible to and to whom it
>> is not visible. The best you can do as far as I can see is to optimise
>> the caching, especially if the relationships are relatively stable.
>>
>> Or is this perhaps a pattern that I am not aware of?
>>
>>
>> Adam
>>
>>
>>
>> Raghu Kanchustambham on 20/11/05 16:50, wrote:
>>
>>> On the first cut this looks like authentication/authorization for Spring
>>> framework. Do I need to get struts co-exist with spring for this to
>>> work ?
>>> And how much of an effort would that be?
>>> But yes.. this looks quite a powerful and neat concept.
>>> Thanks for refering it.
>>> Regards,
>>> Raghu
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: jaas authorization with struts
Posted by Laurie Harper <la...@holoweb.net>.
Actually, Acegi does offer what Raghu was looking for (or at least one
possible route to achieving it). One of the things it can do is
automatically filter collections to remove items the current user
shouldn't be allowed to see, so you don't have to bury that kind of
business logic in your database. Since it lets you do this
declaratively, it's easy to change with changing business requirements.
L.
Adam Hardy wrote:
> Hi Raghu, Laurie,
>
> I did a project recently which used the Acegi security project which
> comes bundled with Spring, and although I was never involved in the
> implementation of it myself, I heard that it was effective.
>
> Am I correct in assuming though that it does not offer the alternative
> that Raghu was looking for, despite the fact that he(you) seems very
> positive about it?
>
> I can't see how such a security requirement can be implemented in any
> other way than via the database. It is simply a question of data
> visibility, in other words, who the data is visible to and to whom it is
> not visible. The best you can do as far as I can see is to optimise the
> caching, especially if the relationships are relatively stable.
>
> Or is this perhaps a pattern that I am not aware of?
>
>
> Adam
>
>
>
> Raghu Kanchustambham on 20/11/05 16:50, wrote:
>
>> On the first cut this looks like authentication/authorization for Spring
>> framework. Do I need to get struts co-exist with spring for this to
>> work ?
>> And how much of an effort would that be?
>> But yes.. this looks quite a powerful and neat concept.
>> Thanks for refering it.
>> Regards,
>> Raghu
>>
>>
>> On 11/20/05, Laurie Harper <la...@holoweb.net> wrote:
>>
>>> Take a look at the Acegi Security project. It provides *extremely*
>>> powerful declarative security capabilities, upto and including filtering
>>> database query results to exclude things the current user shouldn't be
>>> able to see. It might be exactly what you're looking for.
>>>
>>> L.
>>>
>>> Raghu Kanchustambham wrote:
>>>
>>>> Hi,
>>>> I could successfully place my authentication scheme in place using the
>>>> article at
>>>> http://www.jroller.com/comments/tomdz?anchor=using_jaas_with_struts_a
>>>> I also could place "resource" level authorization in place. However the
>>>> definition of resource is the "traditional" action mapping. However I
>>>
>>>
>>> have a
>>>
>>>> requirement which goes beyond that. I have a centre based roles. Let us
>>>
>>>
>>> say
>>>
>>>> my application could be used by administrators at three centres. The
>>>
>>>
>>> trick
>>>
>>>> is that all of them can view the set of "resources"... but in a
>>>
>>>
>>> particular
>>>
>>>> JSP they are authorized to use only certain values for some of the
>>>
>>>
>>> fields.
>>>
>>>> For example, a Hyderabad administrator can view reports pertaining to
>>>> Hyderabad only and should not be allowed to see reports of Bangalore
>>>
>>>
>>> centre.
>>>
>>>> Which let us say in UI terms would translate to a dropdown of cities ..
>>>
>>>
>>> for
>>>
>>>> the Bangalore administrator... he probably can see the dropdown
>>>> populate
>>>> with Bangalore... the Hyderabad admin sees it populated only with
>>>
>>>
>>> Hyderabad
>>>
>>>> and a HeadOffice admin sees all the cities in the cities dropdown.
>>>> What is the best way to achieve this?
>>>> One approach is to create a separate role for each centre user. For
>>>> example... have a role called Bangalore_Admin and Hyderabad_Admin etc.
>>>
>>>
>>> But
>>>
>>>> obvious drawback is that this approach won't scale well with the
>>>
>>>
>>> increase in
>>>
>>>> the number of centres.
>>>> The other approach I was thinking is writing code myself. Introduce a
>>>> column for centre in the user table. From the
>>>> request.getUserPrincipal().getName()
>>>> funcion I determine the user... hit the database to determine the
>>>> centre
>>>
>>>
>>> and
>>>
>>>> then filter the cities based on the city and the role.
>>>> I don't like this approach because I have lost the advantages of a
>>>> declarative style of defining security permissions. Also, now my
>>>> authorization code would be mixed allover and would be difficult to
>>>
>>>
>>> change
>>>
>>>> the authorization policies on a later date.
>>>> The third approach is similar to the second one. Instead of defining a
>>>> centre at the user level, I could do it at the user_role mapping level.
>>>> User1 is the administrator of Hyderabad centre. He could be a regular
>>>
>>>
>>> user
>>>
>>>> for another centre (say Bangalore). Slightly better than second
>>>> approach
>>>
>>>
>>> but
>>>
>>>> suffers from similar problems.
>>>> Is there a way that my getUserPrincipal() can be made to give me this
>>>
>>>
>>> extra
>>>
>>>> piece of information about the centre? That would make my code look lot
>>>> cleaner. I dont have to hit back the database just to find the centre.
>>>> Please comment.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: jaas authorization with struts
Posted by Adam Hardy <ah...@cyberspaceroad.com>.
Hi Raghu, Laurie,
I did a project recently which used the Acegi security project which
comes bundled with Spring, and although I was never involved in the
implementation of it myself, I heard that it was effective.
Am I correct in assuming though that it does not offer the alternative
that Raghu was looking for, despite the fact that he(you) seems very
positive about it?
I can't see how such a security requirement can be implemented in any
other way than via the database. It is simply a question of data
visibility, in other words, who the data is visible to and to whom it is
not visible. The best you can do as far as I can see is to optimise the
caching, especially if the relationships are relatively stable.
Or is this perhaps a pattern that I am not aware of?
Adam
Raghu Kanchustambham on 20/11/05 16:50, wrote:
> On the first cut this looks like authentication/authorization for Spring
> framework. Do I need to get struts co-exist with spring for this to work ?
> And how much of an effort would that be?
> But yes.. this looks quite a powerful and neat concept.
> Thanks for refering it.
> Regards,
> Raghu
>
>
> On 11/20/05, Laurie Harper <la...@holoweb.net> wrote:
>
>>Take a look at the Acegi Security project. It provides *extremely*
>>powerful declarative security capabilities, upto and including filtering
>>database query results to exclude things the current user shouldn't be
>>able to see. It might be exactly what you're looking for.
>>
>>L.
>>
>>Raghu Kanchustambham wrote:
>>
>>>Hi,
>>>I could successfully place my authentication scheme in place using the
>>>article at
>>>http://www.jroller.com/comments/tomdz?anchor=using_jaas_with_struts_a
>>>I also could place "resource" level authorization in place. However the
>>>definition of resource is the "traditional" action mapping. However I
>>
>>have a
>>
>>>requirement which goes beyond that. I have a centre based roles. Let us
>>
>>say
>>
>>>my application could be used by administrators at three centres. The
>>
>>trick
>>
>>>is that all of them can view the set of "resources"... but in a
>>
>>particular
>>
>>>JSP they are authorized to use only certain values for some of the
>>
>>fields.
>>
>>>For example, a Hyderabad administrator can view reports pertaining to
>>>Hyderabad only and should not be allowed to see reports of Bangalore
>>
>>centre.
>>
>>>Which let us say in UI terms would translate to a dropdown of cities ..
>>
>>for
>>
>>>the Bangalore administrator... he probably can see the dropdown populate
>>>with Bangalore... the Hyderabad admin sees it populated only with
>>
>>Hyderabad
>>
>>>and a HeadOffice admin sees all the cities in the cities dropdown.
>>>What is the best way to achieve this?
>>>One approach is to create a separate role for each centre user. For
>>>example... have a role called Bangalore_Admin and Hyderabad_Admin etc.
>>
>>But
>>
>>>obvious drawback is that this approach won't scale well with the
>>
>>increase in
>>
>>>the number of centres.
>>>The other approach I was thinking is writing code myself. Introduce a
>>>column for centre in the user table. From the
>>>request.getUserPrincipal().getName()
>>>funcion I determine the user... hit the database to determine the centre
>>
>>and
>>
>>>then filter the cities based on the city and the role.
>>>I don't like this approach because I have lost the advantages of a
>>>declarative style of defining security permissions. Also, now my
>>>authorization code would be mixed allover and would be difficult to
>>
>>change
>>
>>>the authorization policies on a later date.
>>>The third approach is similar to the second one. Instead of defining a
>>>centre at the user level, I could do it at the user_role mapping level.
>>>User1 is the administrator of Hyderabad centre. He could be a regular
>>
>>user
>>
>>>for another centre (say Bangalore). Slightly better than second approach
>>
>>but
>>
>>>suffers from similar problems.
>>>Is there a way that my getUserPrincipal() can be made to give me this
>>
>>extra
>>
>>>piece of information about the centre? That would make my code look lot
>>>cleaner. I dont have to hit back the database just to find the centre.
>>>Please comment.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: jaas authorization with struts
Posted by Raghu Kanchustambham <kr...@gmail.com>.
On the first cut this looks like authentication/authorization for Spring
framework. Do I need to get struts co-exist with spring for this to work ?
And how much of an effort would that be?
But yes.. this looks quite a powerful and neat concept.
Thanks for refering it.
Regards,
Raghu
On 11/20/05, Laurie Harper <la...@holoweb.net> wrote:
>
> Take a look at the Acegi Security project. It provides *extremely*
> powerful declarative security capabilities, upto and including filtering
> database query results to exclude things the current user shouldn't be
> able to see. It might be exactly what you're looking for.
>
> L.
>
> Raghu Kanchustambham wrote:
> > Hi,
> > I could successfully place my authentication scheme in place using the
> > article at
> > http://www.jroller.com/comments/tomdz?anchor=using_jaas_with_struts_a
> > I also could place "resource" level authorization in place. However the
> > definition of resource is the "traditional" action mapping. However I
> have a
> > requirement which goes beyond that. I have a centre based roles. Let us
> say
> > my application could be used by administrators at three centres. The
> trick
> > is that all of them can view the set of "resources"... but in a
> particular
> > JSP they are authorized to use only certain values for some of the
> fields.
> > For example, a Hyderabad administrator can view reports pertaining to
> > Hyderabad only and should not be allowed to see reports of Bangalore
> centre.
> > Which let us say in UI terms would translate to a dropdown of cities ..
> for
> > the Bangalore administrator... he probably can see the dropdown populate
> > with Bangalore... the Hyderabad admin sees it populated only with
> Hyderabad
> > and a HeadOffice admin sees all the cities in the cities dropdown.
> > What is the best way to achieve this?
> > One approach is to create a separate role for each centre user. For
> > example... have a role called Bangalore_Admin and Hyderabad_Admin etc.
> But
> > obvious drawback is that this approach won't scale well with the
> increase in
> > the number of centres.
> > The other approach I was thinking is writing code myself. Introduce a
> > column for centre in the user table. From the
> > request.getUserPrincipal().getName()
> > funcion I determine the user... hit the database to determine the centre
> and
> > then filter the cities based on the city and the role.
> > I don't like this approach because I have lost the advantages of a
> > declarative style of defining security permissions. Also, now my
> > authorization code would be mixed allover and would be difficult to
> change
> > the authorization policies on a later date.
> > The third approach is similar to the second one. Instead of defining a
> > centre at the user level, I could do it at the user_role mapping level.
> > User1 is the administrator of Hyderabad centre. He could be a regular
> user
> > for another centre (say Bangalore). Slightly better than second approach
> but
> > suffers from similar problems.
> > Is there a way that my getUserPrincipal() can be made to give me this
> extra
> > piece of information about the centre? That would make my code look lot
> > cleaner. I dont have to hit back the database just to find the centre.
> > Please comment.
> > Thanks much.
> > Regards,
> > Raghu
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
Re: jaas authorization with struts
Posted by Laurie Harper <la...@holoweb.net>.
Take a look at the Acegi Security project. It provides *extremely*
powerful declarative security capabilities, upto and including filtering
database query results to exclude things the current user shouldn't be
able to see. It might be exactly what you're looking for.
L.
Raghu Kanchustambham wrote:
> Hi,
> I could successfully place my authentication scheme in place using the
> article at
> http://www.jroller.com/comments/tomdz?anchor=using_jaas_with_struts_a
> I also could place "resource" level authorization in place. However the
> definition of resource is the "traditional" action mapping. However I have a
> requirement which goes beyond that. I have a centre based roles. Let us say
> my application could be used by administrators at three centres. The trick
> is that all of them can view the set of "resources"... but in a particular
> JSP they are authorized to use only certain values for some of the fields.
> For example, a Hyderabad administrator can view reports pertaining to
> Hyderabad only and should not be allowed to see reports of Bangalore centre.
> Which let us say in UI terms would translate to a dropdown of cities .. for
> the Bangalore administrator... he probably can see the dropdown populate
> with Bangalore... the Hyderabad admin sees it populated only with Hyderabad
> and a HeadOffice admin sees all the cities in the cities dropdown.
> What is the best way to achieve this?
> One approach is to create a separate role for each centre user. For
> example... have a role called Bangalore_Admin and Hyderabad_Admin etc. But
> obvious drawback is that this approach won't scale well with the increase in
> the number of centres.
> The other approach I was thinking is writing code myself. Introduce a
> column for centre in the user table. From the
> request.getUserPrincipal().getName()
> funcion I determine the user... hit the database to determine the centre and
> then filter the cities based on the city and the role.
> I don't like this approach because I have lost the advantages of a
> declarative style of defining security permissions. Also, now my
> authorization code would be mixed allover and would be difficult to change
> the authorization policies on a later date.
> The third approach is similar to the second one. Instead of defining a
> centre at the user level, I could do it at the user_role mapping level.
> User1 is the administrator of Hyderabad centre. He could be a regular user
> for another centre (say Bangalore). Slightly better than second approach but
> suffers from similar problems.
> Is there a way that my getUserPrincipal() can be made to give me this extra
> piece of information about the centre? That would make my code look lot
> cleaner. I dont have to hit back the database just to find the centre.
> Please comment.
> Thanks much.
> Regards,
> Raghu
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org