not really sure what you mean when you say marking components as dirty... have you seen ajaxfallback* components? those will use ajax when its there, and fallback on regular requests when its not. so you dont even need a factory necessarily.
-igor On 8/23/07, Sam Hough <[EMAIL PROTECTED]> wrote: > > > Thanks Igor, > > Because we have to support Ajax and non-Ajax version I was wondering about > hiding details of making components Ajax friendly in the factory. so > setOutputMarkupId(true) etc and hiding Ajax specific handlers where > possible. Have you seen anybody automatically marking components as dirty > so > they can be sent back via Ajax (Echo like)? I think that would handle 90% > of > our Ajax like stuff. > > Cheers > > Sam > -- > View this message in context: > http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12290179 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
