Filters in 3.1 don't use priority anymore, but are simply executed in
the order in which they're stored. Each filter can have custom bypass
settings, which is prbly what you're looking for.
On Aug 23, 2007, at 12:50 , Ian Johannesen wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I've been trying to archive a servlet mapping without having to
mutilate
the web.xml by simply patching magnolia.
For the sake of common ground I'll mention this is 3.1-SNAPSHOT I'm
working with (/trunk).
So far I've created a custom module, which loads just fine, with a
customer filter. I've tried to set the priority both to very low and
high numbers. Neither does it help as MagnoliaMainFilter
(info.magnolia.cms.filters) still intercepts it and hence my custom
filter doesn't receive the request and due to this my custom servlet
doesn't get called.
Someone out there who could point me in the right direction perhaps?
- --
Digitally Yours,
Ian Johannesen
web: http://perlpimp.dk/
msn: [EMAIL PROTECTED]
cel: (+34) 663 739 237
cel: (+45) 21 19 35 34
tel: (+34) 952 206 905
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGzWZw0/HOnDavf4YRAglfAJsH/v7VC1DtO5rhMEDtAPvlvKQu5wCfT0xo
W3VavZFtz8Y+AlA5j8ZYCCM=
=AW11
-----END PGP SIGNATURE-----
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
