On 9/9/10 6:43 PM, Igor Vaynberg wrote:
very strange indeed. do you have any behaviors that write directly to
the response? even that, i dont think, would cause this. create a
quickstart and attach it to a jira issue.
I guess I found the error. I have a UI engine which takes an XML
formatted document and renders a Wicket based page from it (we call it
Gozer, you know what it means if you know what XUL means :) ). All
events are handled by a Controller which checks what state the page is
in (edit, readonly) and which manages the content. Now we have a special
component we can use, this is a listdetail. Basically it is a component
which can toggle between a list and a detail view. The list is just a
normal Wicket list, the detail is a repeater which dynamically renders
the correct amount of captions and fields.
We had some strange problem where the detail component was not rendered
correctly after some events. We solved this with calling
> DetailPanel.renderComponent()
whenever something changed.
Now that worked quite nicely. Until we started to introduce Ajax based
commands. Now the call to renderComponent is called before the
AjaxRequestTarget.addComponent(). Which means, that there is some text
in the response before Wicket starts with the XML formatted ajax response.
Which brings me to the question. How should we handle the
renderComponent? How can we make sure, that components do rerender, but
not doing so ourselves but have the Wicket framework ask for the rendering.
Thanks,
Adrian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
