[MAGNOLIA-1247] No possibility to have a filter after CMSFilter Created: 04/Dec/06 Updated: 23/Jan/13 Resolved: 04/Dec/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.0 Final |
| Fix Version/s: | 3.0.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Sameer Charles | Assignee: | Sameer Charles |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
CMSFilter breaks the filter chain, its assumed that it will always be the last filter. we should change it so it behaves the same way as any other filter if there are other filters configured in a chain after CMSFilter |
| Comments |
| Comment by Sameer Charles [ 04/Dec/06 ] |
|
CMS filter only breaks the chain on error, else it acts as any other filter |