[MAGNOLIA-3504] Filters: dispatching configuration is not taken into account Created: 11/Jan/11  Updated: 02/Feb/11  Resolved: 19/Jan/11

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.4
Fix Version/s: 4.4.2

Type: Bug Priority: Blocker
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
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
Date of First Response:

 Description   

According to the following log the dispatching configuration is wrongly transformed into a composition of filters:

INFO   info.magnolia.cms.filters.CompositeFilter 01.12.2010 15:24:54 -- Initializing filter [rendering]
INFO   info.magnolia.cms.filters.CompositeFilter 01.12.2010 15:24:54 -- Initializing filter [dispatching]
INFO   info.magnolia.cms.filters.CompositeFilter 01.12.2010 15:24:54 -- Initializing filter [request]
INFO   info.magnolia.cms.filters.CompositeFilter 01.12.2010 15:24:54 -- Initializing filter [error]
INFO   info.magnolia.cms.filters.CompositeFilter 01.12.2010 15:24:54 -- Initializing filter [forward]
INFO   info.magnolia.cms.filters.CompositeFilter 01.12.2010 15:24:54 -- Initializing filter [include]


 Comments   
Comment by Philipp Bärfuss [ 12/Jan/11 ]

the property in AbstractMgnlFilter was named wrongly

Comment by Jan Haderka [ 17/Jan/11 ]

Merge with trunk is missing or not having proper log comment.

Comment by Magnolia International [ 17/Jan/11 ]

Shouldn't the title of the issue be different, now that we've identified it ? It probably prevented the dispatching configuration to work at all ... ?

Comment by Federico Grilli [ 18/Jan/11 ]

Before closing the issue, shouldn't this be backported to the trunk too?

Comment by Philipp Bärfuss [ 19/Jan/11 ]

Ups! thanks I have backported it now.

Generated at Mon Feb 12 03:47:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.