If I right understood your question, the reason is that Magnolia is *by
default* the unique configured filter handling all requests coming (see
web.xml of every Magnolia context).
This is true, but it's true only for a "standard" Magnolia
configuration, the simplest. 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.
Filters are configured under <config>/server/filters and if a request
can not be matched with a page or with a virtualUriMapping the 404
standard Tomcat error page.
I know that but the filters configured there should extend an abstract
Magnolia filter, and if the filter is a pre-existing, jar-packed class
it may not be so obvious to extend the required base Magnolia filter.
The reason of filter stop is that there are no configured resources to
serve, so why go on among next filters?
Why not? I mean, if Magnolia is the only filter configured that's true,
but if there are other filters in chain, why Magnolia should be the only
one allowed to generate and serve resources?
Since you are using a CMS, it is strong enough to have your legacy apps
on a different context or map different requests with different
extensions / target path. In this way you can split all requests between
CMS and other systems.
I think this is not always true. Often the client has already developed
some sort of home-made CMS-like system, and asks to have something
better (which is Magnolia). In such cases we have to let Magnolia live
side-by-side with the custom system (also because a full migration is
often impossible in a reasonably short time). 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.
If you want to use another apps in chain with Magnolia, you can consider
to extend some of CMS filters here: <config>server/filters/CMS/* and try
to extends the standard behaviour, maybe with some forward requests...
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.
Regards, Danilo.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
