Hi!

I Just upgraded from 1.4-rc7 to 1.4.8 and I see strange behavior with
enclosures. Has the specification changed?

I used to have:
    <wicket:enclosure child="selectedCustomersLabel">
    <tr><th align="left"><wicket:container
wicket:id="customerSelectionLabel"/>:</th><td><wicket:container
wicket:id="selectedCustomersLabel"/></td></tr>
    </wicket:enclosure>

And in the code I was used to changing the visibility only for
selectedCustomersLabel

This worked fine with 1.4-rc7. Setting selectedCustomersLabel
invisible would hide also customerSelectionLabel.

Now with 1.4.8 I get an exception that customerSelectionLabel does not
have markup.... if I set it invisible it works, but that's a whole lot
of work if I have to change all enclosures to work like this. What's
the benefit of enclosure like that?

is it a bug, am I doing something wrong or is it a feature?

WicketMessage: The component(s) below failed to render. A common
problem is that you have added a component in code but forgot to
reference it in the markup (thus the component will never be
rendered).

1. [Component id = customerSelectionLabel]

Root cause:

org.apache.wicket.WicketRuntimeException: The component(s) below
failed to render. A common problem is that you have added a component
in code but forgot to reference it in the markup (thus the component
will never be rendered).

1. [Component id = customerSelectionLabel]

at org.apache.wicket.Page.checkRendering(Page.java:1182)
at org.apache.wicket.Page.renderPage(Page.java:922)
at 
org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.respond(BookmarkablePageRequestTarget.java:261)
at 
org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:105)
at 
org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1258)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428)

**
Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to