|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
_______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
Alright, I now understand where you are coming from. The known and still current strategy for build filter/servlet chains in the dispatcher is to consider all filters/servlets that are a) for the tenant or b) for no tenant at all. The latter where the "global" filters/servlets. With the introduction of the mt model this does not work so well anymore. If you define binding PLATFORM, the new "global" method your servlet/filters will no longer match the heuristic used by the dispatcher. In fact, the only way to get in a tenant specific chain now is to not use the mt adapter at all, which has all kinds of different drawbacks.
I can imagine the dispatcher considering PLATFORM scope filters/servlets as well. Maybe always or based on configuration. I will create a change request for this where we can discuss the finer details of a possible solution.