You are right. I found out the 'markupProvider' is null by debugging, thanks
to Tom to "fores" me to do it.
In Wicket 1.3 & 1.4, I overrided 'getAssociatedMarkupStream(boolean
throwException)' so that the class extends from Fragment doesn't have to
provide 'markupProvider'. After upgraded to Wic
Hi,
I guess 'markupProvider' is null.
This is improved in 1.5.7 to not fail with NPE.
But even in 1.5.7 your app will fail with :
throw new MarkupNotFoundException("No Markup found for Fragment " + markupId +
" in providing markup container " +
getMarkupProvider(co
Hm, put a breakpoint in FragmentMarkupSourcingStrategy.java:143 and see what
causes the NullPointerException.
-Tom
On 01.06.2012 at 19:08 paulstar wrote:
> Caused by: java.lang.NullPointerException
>at
> org.apache.wicket.markup.html.panel.FragmentMarkupSourcingStrategy.getMarkup(Fr
