Ah, yes, of course. Sometimes the solution is so simple. Thanks, Martin! :-) B.
Am 07.04.2016 um 10:57 schrieb Martin Holz (for Usenet): > Am 04/06/2016 um 10:15 PM schrieb Burkhard Graves: >> ServletContext#getFilterRegistrations() returns an unordered map only - >> how to programmatically find out the order in which the filters are >> applied/registered? >> >> I know the specs ... >> >>> The order the container uses in building the chain of filters to be >>> applied for a particular request URI is as follows: >>> >>> First, the <url-pattern> matching filter mappings in the same order >>> that these elements appear in the deployment descriptor. >>> Next, the <servlet-name> matching filter mappings in the same order >>> that these elements appear in the deployment descriptor. >> ... but I would like to find out the order in retrospect (e.g. because >> the filters are set up by a given framework). >> >> > Look into the stacktrace of a service method. It will show the classes > of all applied filters in the applied order. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
