Am 12.11.2014 um 13:40 schrieb Lukasz Lenart:
2014-11-12 13:25 GMT+01:00 Volker Krebs <volker.kr...@abas.de>:
Am 12.11.2014 um 10:07 schrieb Lukasz Lenart:
2014-11-10 16:30 GMT+01:00 Volker Krebs <volker.kr...@abas.de>:
https://github.com/VolkerK/struts-examples/
branch develop
Thanks a lot for the example, it was very helpful! Btw. you can
prepare a PR to push it to the struts-example project :-)
One remark, you cannot use such configuration:
<interceptor-ref name="params">
<param name="params">someParameter</param>
</interceptor-ref>
<interceptor-ref name="basicStack"/>
as in such case params interceptor will run two times - first as a
part of defaultStack and second time as a part of basicStack, you must
use it that way
Actually this is what I wanted to do. A couple of years ago I read somewhere
about the params - prepare - params approach.
First set some paras that are required in the prepare method, and then after
prepare is finished set the some more params (and don't overwrite the ones
from the first params call).
Ok that's probably too much of the domain (back-end) logic pressed into the
struts framework (workflow), but thats how I did it years ago when
I was naive and unexperienced :)
Good to know, at least you know what you doing :-)
Can I prepare new release, what do you think?
For exclude pattern I would use addExcludedPatterns and for accept
patterns I would use setAcceptedPatterns.
IMO, just by setting (adding) an exclude pattern it shouldn't be
possible to overwrite security relevant excludes.
But I don't know exactly what the purpose of
DefaultAcceptedPatternsChecker.ACCEPTED_PATTERNS is. So I'm skating a
bit on thin ice here.
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
