Hi,
you wrote
/ ... you should pass the
form as parent container of the fragment instance. /
The problem is that I have multiple fragments within my form.
And if I pass the form as parent container for each fragment I get an
... child already exists... exception.
That's why I'm inserted
Hi,
By 'parent' I really meant 'markupProvider'. See the javadoc of
org.apache.wicket.markup.html.panel.Fragment#Fragment(String, String,
MarkupContainer).
See the source of for the example at
Thanks for your hints, Martin!
Now I found the solution.
Two changes I had to do:
*1)*
The difference now is, that the parent component passed to the fragment must
be the exact parent.
e.g.
I used the same fragments for display and edit mode.
I passed the page as parentComponent to fragment.
/new
I changed my app from wicket 1.4.18 to 1.5.4
Now I get a MarkupNotFound Exception.
In 1.4. the app was running without warnings/errors
Does somebody have a hint?
I'm using a form within a page. The form has a fragment child.
*MarkupCode*:
/div wicket:id=contentFragment1/
wicket:fragment
Hi,
Make sure that wicket:fragment is inside wicket:child
On Wed, Feb 29, 2012 at 1:03 PM, rawe ralph.wey...@dachser.com wrote:
I changed my app from wicket 1.4.18 to 1.5.4
Now I get a MarkupNotFound Exception.
In 1.4. the app was running without warnings/errors
Does somebody have a hint?
Martin, do you mean something like ??
/
div wicket:id=contentFragment1/
wicket:child
wicket:fragment wicket:id=orderFragment1
fieldset
...
/fieldset
/wicket:fragment
/wicket:child
/
Doesn't work!
But normally I don't need a child tag due I don't include markup from a
subclass
I mean that wicket:fragment should be in wicket:extend,
wicket:panel or wicket:border if any of those is used.
Your pasted code is not easy to follow but I think you should pass the
form as parent container of the fragment instance.
On Wed, Feb 29, 2012 at 2:12 PM, rawe ralph.wey...@dachser.com
