Danilo Ghirardelli ha scritto:
We sometimes work on integrated
configuration where there is not only Magnolia and so this unique
constraint falls. Maybe I wasn't clear enough on this part.
In this case, I reinforce what I said, separate at servlet/filter config
.xml is the *better* solution; I can imagine that for some cases it can
not be affordable. In that case you can have issues like the one you are
describing.
it may not be so obvious to extend the required base Magnolia filter.
Yes, I can understood this point but filter extension can be consider a
"last chance" option. And it is a low-level option too, so if you can
consider to adopt it, it means you can consider also reading some packet
code (from source, of course..). But you are right, it is not so easy.
if there are other filters in chain, why Magnolia should be the only
one allowed to generate and serve resources?
I can suggest to avoid chaining Magnolia with other legacy apps. It is
better another approach, e.g.: mapping the other filter chain on another
extension (*.old) or to separate both context. Anyway, this is only my
point of view.
Having Magnolia as a
global handler also for the custom system is something that quicken
migration, but when the custom handler is a filter there is this
limitation.
But in this case, why not you integrate you legacy system with Magnolia
at filter level? Place a filter (tune the position in filter chain) and
forward the call for certain pages, stopping the chain before reach the
CMS. In this case Magnolia CMS is the last filter and you can serve
legacy pages / systems integrating them, for instance, with Magnolia
authentication.
Ok, let me rephrase the question: why can't I configure a filter after
the last rendering one? Try putting some logging filter after the
rendering one and see it is never called, because the renderdering
filter has the chain.doFilter commented out. And I was just wondering why.
I understood. I don't know the reason of that, what you say seems
reasonable.
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
