![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Affects Versions:
|
amdatu-platform-1.0.0 |
|
Assignee:
|
Unassigned |
|
Created:
|
11/May/12 11:13 AM
|
|
Description:
|
The dispatcher strategy for building filter/servlet chains in the dispatcher is to consider all filters/servlets that are a) registered by the resolved tenant or b) for no tenant at all. The latter is used to support the "global" filters/servlets.
With the introduction of the mt model this does not fit 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 suggest we support that the dispatcher considers PLATFORM scope filters/servlets as well. Maybe always or based on configuration?
|
|
Fix Versions:
|
Backlog |
|
Project:
|
Amdatu
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Bram de Kruijff
|
|
|
|
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
