On Saturday 28 February 2009 00:11:21 Dave Newton wrote:
> Andreas Joseph Krogh wrote:
> > On Friday 27 February 2009 15:04:52 Musachy Barroso wrote:
> >> Hi Andreas, attaching the patch to a jira ticket is the way to go to
> >> make sure we don't forget about it.
> > 
> > Updated patch here:
> > https://issues.apache.org/struts/browse/WW-3017
> > 
> > After eyeballing the code some more I finally figured out how to use a 
> > property configured in struts.xml or struts.properties. So no init-params 
> > in servlet-filter-config necessary anymore.
> 
> Personally I'd rather use filter init-params for this--just seems like 
> it'd be more local to where filter mapping normally takes place.
> 
> Plus I don't use struts.properties or struts.xml files too much anymore.

He he, that's the beauty of it is, you *can* still specify it in the filter's 
init-params like you want. You see, the filter's init-params and the properties 
defined in struts.properties and struts.xml are merged by Struts2. So setting 
this as a filter-param like you want works just fine alongside with specifying 
it in the struts' config-files.

This way we're both happy:-)

-- 
Andreas Joseph Krogh <[email protected]>
Senior Software Developer / CEO
------------------------+---------------------------------------------+
OfficeNet AS            | The most difficult thing in the world is to |
Rosenholmveien 25       | know how to do a thing and to watch         |
1414 TrollÄsen          | somebody else doing it wrong, without       |
NORWAY                  | comment.                                    |
                        |                                             |
Tlf:    +47 24 15 38 90 |                                             |
Fax:    +47 24 15 38 91 |                                             |
Mobile: +47 909  56 963 |                                             |
------------------------+---------------------------------------------+

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to