Hi,
do you use the same Wicket version on development and production
environments? Anyway the problem could be due to ListView which by
default replaces all child components with new instances each time is
rendered.
Try calling setReuseItems(true) on your ListView.
Hi,
i'm having the strangest issue with an AjaxRequest on one of our pages. The
situation is as follows:
We have a page which contains a panel. That panel is initially rendered
invisible with setOutputMarkupPlaceholderTag(true):
(Note: redenWijzigeinPanel is dutch but it's the variable that holds the
panel)
redenWijzigenPanel.setVisible(false);
redenWijzigenPanel.setOutputMarkupPlaceholderTag(true);
We also add a AjaxLink to the page which, when clicked on will render the
page visible.
item.add(new AjaxLink<Void>("redenWijzigen")
{
@Override
public void onClick(AjaxRequestTarget target)
{
redenWijzigenPanel.setVisible(!redenWijzigenPanel.isVisible());
target.addComponent(redenWijzigenPanel);
}
});
Note that both redenwijzigenPanel and the AjaxLink are added to a ListView.
Now here's where it gets weird. This works perfectly fine on my local
machine, however, it goes wrong on one of our environments with the
following Ajax error(I've tried on both enviroments with Wicket
configuration on development or on production).
ERROR: Wicket.Ajax.Call.processComponent: Component with id
[[redenWijzigenPanel139]] a was not found while trying to perform markup
update. Make sure you called component.setOutputMarkupId(true) on the
component whose markup you are trying to update.
(See below for the entire AjaxMessage)
This is weird because when I look at the HTML being generated it looks like
this:
<div id="redenWijzigenPanelf5" style="display:none"></div>
Which is what you expect except where does the wicket:id
redenwijzigenPanel139 come from?
So my problem is, why does this work on my local enviroment but not on the
other? Is there something I'm missing? Or does anyone know a workaround?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
