Thank you Frank and Igor,
this is where wicket differs from a lot of other frameworks and
sometimes its hard to wrap your mind around it: the components are
persistent across requests, they keep their state.
Yes, it is somewhat hard !
In fact, I started from an example I found that used a
On 8/9/06, Pierre-Yves Saumont [EMAIL PROTECTED] wrote:
myList = DataObjectsFactory.getMyList();myListView = new MyListView(id, myList);myListView.setOutputMarkupId(true);target.addComponent(myListView);It doesn't look like you add/replace that myListView to a parent. OutputMarkupId can't be
but why even create a new listview? the old one should just refresh and show new data, if it doesnt you need to use a detachable model.this is where wicket differs from a lot of other frameworks and sometimes its hard to wrap your mind around it: the components are persistent across requests, they
