[MAGNOLIA-1615] filterChain contains null entries if filter manager fails to create filter from filter definition loaded from jcr. (leads to nullpointer exception) Created: 02/Jul/07  Updated: 23/Jan/13  Resolved: 02/Jul/07

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.0.2
Fix Version/s: 3.0.5

Type: Bug Priority: Major
Reporter: Chris Miner Assignee: Chris Miner
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   

Steps to reproduce
1. install enterprise edition modules
2. start up magnolia
3. enter license info
4. remove enterprise edition modules
5. start up magnolia

found: null pointer exception while trying to access application
expected: to be able to access the repository and otherwise use magnolia without the ee features.



 Comments   
Comment by Chris Miner [ 02/Jul/07 ]

The problem relates to filtering. The filterchain contains a null entry at the end. This is caused by init in info.magnolia.cms.beans.config.FilterManager. In this method, if a filter definition can't be used to create a filter, the filter definition is removed from the array of filterdefinitions. However, the filters array remains its original length. resulting in NPE when other code iterates over this array. for example in magnolia managed filter.

Comment by Chris Miner [ 02/Jul/07 ]

fixed in Committed revision 9886. filter chain is same length as filterdefinitions.

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