[ https://issues.apache.org/jira/browse/WICKET-4968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4968. ------------------------------------- Resolution: Fixed Fix Version/s: 6.5.0 Assignee: Martin Grigorov > NPE in FencedFeedbackPanel#onRemove > ----------------------------------- > > Key: WICKET-4968 > URL: https://issues.apache.org/jira/browse/WICKET-4968 > Project: Wicket > Issue Type: Bug > Components: wicket > Affects Versions: 6.4.0 > Reporter: Michael Frankerl > Assignee: Martin Grigorov > Fix For: 6.5.0 > > > There is a potential NPE in > FencedFeedbackPanel.onRemove(FencedFeedbackPanel.java:155). > If a FencedFeedbackPanel instance is used two times ( i.e. wizard is > replacing components on navigation) the MetaDataKey "FENCE_KEY" could be > null. This causes a NPE in any further call of "onRemove". > Example Stacktrace: > Caused by: java.lang.NullPointerException > at > org.apache.wicket.feedback.FencedFeedbackPanel.onRemove(FencedFeedbackPanel.java:155) > at org.apache.wicket.Component.internalOnRemove(Component.java:1102) > at > org.apache.wicket.MarkupContainer.removeChildren(MarkupContainer.java:1589) > at org.apache.wicket.Component.internalOnRemove(Component.java:1110) > at > org.apache.wicket.MarkupContainer.removeChildren(MarkupContainer.java:1589) > at org.apache.wicket.Component.internalOnRemove(Component.java:1110) > at > org.apache.wicket.MarkupContainer.removeChildren(MarkupContainer.java:1589) > at org.apache.wicket.Component.internalOnRemove(Component.java:1110) > at > org.apache.wicket.MarkupContainer.removeChildren(MarkupContainer.java:1589) > at org.apache.wicket.Component.internalOnRemove(Component.java:1110) > at > org.apache.wicket.MarkupContainer.removedComponent(MarkupContainer.java:1341) > at org.apache.wicket.MarkupContainer.replace(MarkupContainer.java:739) > at > org.apache.wicket.extensions.wizard.Wizard.onActiveStepChanged(Wizard.java:233) -- 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