why dont you look at what markup the palette generates and how it submits to the server. maybe that will help you to understand how to accomplish what you want.
-igor On Fri, Dec 25, 2009 at 10:04 AM, Martin Dietze <d...@fh-wedel.de> wrote: > I desperately need to find out which entries in a Palette's two > Choices components are selected, e.g. to allow additional > operations on them using Ajax. > > As I attached an OnChangeAjaxBehaviour to both of them I expect > to be able to access this information just as after a form > submit, but of course, the component must support this which it > currently does not seem to do. > > I also subclassed Choices to add some of my own custom stuff, > so I could as well set a default model and implement things like > updateModel() and convertInput(), but having done so I find > myself unable to find out how to set the right stuff in my > code, the request parameters do not seem to contain anything > usable. > > Could anybody give me a hint on what I need to do to support > tracking the selected entries while still maintaining the > Palette component's original functionality? > > Cheers, > > M'bert > > -- > ----------- / http://herbert.the-little-red-haired-girl.org / ------------- > =+= > i'll beleave this seams to be som curios behaviour. > (from a bug tracker) > > --------------------------------------------------------------------- > 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
