I can try the patch and test, but I only have the wicket 1.4.17 jars.
So can I do a code checkout from somewhere? :D
Or get a jar that has the patch in it ?
On 05/16/2011 05:50 PM, Martin Grigorov wrote:
Sounds like https://issues.apache.org/jira/browse/WICKET-3719
Can you try the patch there and give feedback ?
If it still fails then a quickstart app or a test case would help us to
improve it.
On Mon, May 16, 2011 at 4:43 PM, Alexandru Artimon<
aarti...@developmentgateway.org> wrote:
Hello,
I have a custom wicket html tag that is handled by a component resolver to
automatically generate a component for it. And these components only exist
at the render phase and aren't stored in the page tree.
Now when Ajax is used to update a fragment of the web page, looks like the
components for these wicket html tags were not rendered. So instead of
getting the desired markup I get only the contents of the original markup.
Might this be a bug? It looks like the component resolver doesn't work when
the response is built for the ajax update.
Any ideas/workarounds ?
Thanks again,
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
