When using an AjaxRequestTarget to render a component, it calls Component:renderComponent() to do the actual rendering.
In the former 2.0, that component could be a component that has no own markup (because it was generated by a repeater). In the current thrunk, using an AjaxRequestTarget to render such a component fails, because Component.renderComponent() uses a MarkupFragmentFinder to find the markup for the component, and that MarkupFragmentFinder throws an exception because it did not find any markup with the id of the component (which does not exist, since the component has been generated dynamically). Is this no longer possible in Wicket ? It was working fine in 2.0, and allowed us to do ajax refresh of dynamic content of tables or menus. Jan. -- View this message in context: http://www.nabble.com/Backporting-from-2.0%3A-renderComponent%28%29-fails-if-there-is-no-markup-tf3703472.html#a10356568 Sent from the Wicket - Dev mailing list archive at Nabble.com.
