[
https://issues.apache.org/jira/browse/WICKET-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Makundi updated WICKET-2872:
-----------------------------------
Description:
I Just upgraded from 1.4-rc7 to 1.4.8 and I found a bug with enclosures:
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.
Specifically, THE BUG OCCURS WHEN PAGE HAS <wicket:extend> tag. See attached
quickstart.
was:
I Just upgraded from 1.4-rc7 to 1.4.8 and I found a bug with enclosures:
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.
Specifically, THE BUG OCCURS WHEN PAGE HAS <wicket:extend> tag. See attached
quickstart.
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
> Wicket:enclosure does not work properly on <wicket:extend> pages
> ----------------------------------------------------------------
>
> Key: WICKET-2872
> URL: https://issues.apache.org/jira/browse/WICKET-2872
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.8
> Reporter: Martin Makundi
> Attachments: Wicket-Quickstart.zip
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> I Just upgraded from 1.4-rc7 to 1.4.8 and I found a bug with enclosures:
> 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.
> Specifically, THE BUG OCCURS WHEN PAGE HAS <wicket:extend> tag. See attached
> quickstart.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
