Actually this is good question :) - selected items are being stored on server
somehow I missed the fact I can do all processing on server Thanks a lot for the pointer! On Thu, Jan 19, 2017 at 6:10 PM, Sebastien <seb...@gmail.com> wrote: > Hi Maxim, > > Depending of your selection logic, you have 2 ways: > - a behavior based solution > - a component based solution > > If you can have a wicket component holding the selection (trough its > model) then opt for a component based solution. The component will be > passed to #onDrop so its easy to retrieve the selection (because it's the > component's model). You can use the draggable "helper" to enhance the > visual dnd ui (example here [1]). > > If the selection is client side only, then I think you need to deal with a > behavior based solution (no wicket component involved). Tell me if it's > your case, I can try to help out. > > Best regards, > Sebastien. > > [1] https://github.com/sebfz1/wicket-jquery-ui/blob/master/ > wicket-jquery-ui/src/main/java/com/googlecode/wicket/ > jquery/ui/interaction/selectable/SelectableDraggableFactory.java#L38 > > -- WBR Maxim aka solomax
