[MAGNOLIA-1656] FilterDecorator could be configured more simply Created: 03/Aug/07  Updated: 23/Jan/13  Resolved: 06/Nov/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.1 M1
Fix Version/s: 3.5 RC1

Type: Improvement Priority: Major
Reporter: Magnolia International 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)
Date of First Response:

 Description   

At the moment, if one wants to use a Filter which is not a MagnoliaFilter needs to configure two properties : class: info.magnolia...FilterDecorator and decoratedFilterClass with the actual filter class. content2bean could hide that complexity and automagically wrap the filters in a FilterDecorator as needed.



 Comments   
Comment by Philipp Bracher [ 06/Nov/07 ]

we keep it as it is because it is more transparent

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