On Fri, Oct 29, 2010 at 12:39 AM, Clint Checketts <checke...@gmail.com>wrote:
> Elegant! I'd been trying to think of ways to add my own markup ID and > piggyback off any render requests that redraw the component to trigger and > render the feedback, just using the component markupId will work great! > > Instead of setOutputMarkupId(false), I'll detect that to decide to add the > ID or not and just remove the ID attribute in the onComponentTag() method. > I'll code it up tomorrow. I've got a good feeling about this. > > Thanks for the help. Also I'll check out the IAjaxRegionMarkupIdProvider. > Always good to check out the new interfaces. > Yeah, using the IAjaxRegionMarkupIdProvider you can eliminate all the aforementioned complexity. The markup ID of your component stays the same. In the interface, you just create an ID that will be rendered in your behavior's markup. You render that in your behavior-generated markup, and then Wicket will use the same ID for when it replaces the markup for that component - thus replacing both together. -- Jeremy Thomerson http://wickettraining.com *Need a CMS for Wicket? Use Brix! http://brixcms.org*
