I met the same problem, how you adjust your markup?

And I found that if the listView is a  part of a table markup(as your code
above) and  when it's updated via Ajax by target.addComponent(container),
the original container in the page can not be replaced , a same new one will
show in the page.

That means in the table markup, if WebMarkupContainer of listView is the
<table>, everything will be Ok,
but if the WebMarkupContainer of listView is a <div>, things weird happened
.

Why it happens? browser?



freak182 wrote:
> 
> Hello,
> 
> thank you for your. i already make it work. (need to adjust some markup
> thing :) )
> 
> thanks a lot.
> cheers.
> 
> 
> michael mosmann wrote:
>> 
>> Hmm,..
>> 
>> can you post your markup? this code does work with my own markup..
>> 
>> did you use <div wicket:id="resultcontainer"> or did you use
>> <wicket:container wicket:id="resultcontainer"> .. do you see something
>> in wicket-ajax-debug panel? any error-message? any ajax-response?
>> 
>>> ...and im pretty sure that i already some code in previous version of
>>> wicket
>>> and it work..but i dont know what im missing right now. maybe worst case
>>> i
>>> will do is to go back to old version of wicket but i want the latest
>>> version.
>> 
>> if this does not work with wicket 1.4.1, then it does not work with any
>> wicket version.. 
>> 
>> mm:)
>> 
>> -- 
>> Michael Mosmann - http://www.wicket-praxis.de/blog 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Update-ListView-using-ajax-tp25310457p26635790.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to