Oh right, so are you adding an element that doesn't already exist on your client side page? Ie, if you did a view->source on your web browser (more likely dom inspector with firefox will be better since view source is only good for the original page render) would you be able to find the element who's id you are updating?
Basically, you can't refresh an item on a page using updateComponents if it doesn't already exist. One way to work around this is to do something like: <div jwcid="@Any" id="yourid" > <span jwcif="@If" condition="condition causing your element to display or not"> etc... </span> </div> The only reason I don't add elements to the page that don't already exist is that this would cause a whole new set of features that would allow people to specify ~where~ these elements should go, otherwise I'd just have to append it to the body or some other similar non likely place. Is this what you guys are experiencing? On 1/10/06, Edgar Chan Carrillo <[EMAIL PROTECTED]> wrote: > > Hi! something similar its happening to me. i add another element to the > updateComponents outside of PartialFor and that element works nice, but > the > inside one doesnt. > > The log4j says that AjaxDirectServiceImp is refreshing the 2 components > but > the DojoResponseBuilder only do cleanupAfterRender on the element outside > of > PartialFor. > > The ids of the generated document and debug info match but nothing happen. > >
