this has nothing to do with visibility. for some reason wicket cannot find
the reference to the component in markup. are you sure you added the
component to the right parent?

can you reproduce this in quickstart?

-igor


On 4/7/07, Wouter de Vaal <[EMAIL PROTECTED]> wrote:

Hi,

I have the following problem when using enclosures in development mode

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. [MarkupContainer [Component id = buyDatePicker, page =
<mypackage>EditEntry, path =
5:entryForm:productInformationPanel:buyDatePicker.DatePicker,
isVisible = true, isVersioned = false]]
2. [MarkupContainer [Component id = trigger, page =
<mypackage>EditEntry, path =
5:entryForm:productInformationPanel:buyDatePicker:
trigger.DatePicker$TriggerButton,
isVisible = true, isVersioned = false]]
<more removed>
at wicket.DebugHelper.checkRendering(DebugHelper.java:166)
        at wicket.DebugHelper.onEndComponentRender(DebugHelper.java:91)
        at wicket.Page.renderPage(Page.java:1095)
<more removed>

The relevant html part:
<wicket:enclosure child="productInformation.buyDate">
        <tr>
                <td class="p-label">
                <label wicket:id="buyDateLabel">
                                Aankoop datum
                        </label>
                        :
                </td>
                <td>
                        <input type="text" wicket:id="
productInformation.buyDate" />
                        <span wicket:id="buyDatePicker"></span>
                </td>
        </tr>
</wicket:enclosure>


It seems the debug helper doesn't hold into account when someone is
using <wicket:enclosure child="xxx"> to hide other wicket components
than the child. In the above code productInformation.buyDate is set
invisible.

When I add the following to the application class all works just fine,
so it seems that only the debug class needs some updating to support
enclosures.
getDebugSettings().setComponentUseCheck(false);


Wouter

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to