Sorry, yes I had the ID in the HTML <span> holding the second component, but that span didn't get rendered so no I didn't have the id in the HTML! Sorry to waste your time. This morning I had that ID on an encapsulating DIV and had seen it in the view-source so I hadn't looked again.
Thanks so much. I needed that to wake me up.
- Michael
On 12/2/05, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Just the tree state set for me.
Are you sure about the element you are trying to refresh really already existing on the page?
I know at some point a while back I was doing some forced render stuff for specifically this purpose. It could be what you're running into but it's hard to tell. I'll debug some more, maybe create a quick test page to see if I see the same thing.
On 12/2/05, Michael Waluk <[EMAIL PROTECTED]> wrote:Jesse,When I do refresh the page, the ajax links work fine on the tree. I wonder what makes those links refresh but my link does not? The structure of my ajax call looks good (the updateId is right) but it doesn't re-render.Btw, what components of the Tree do you typically make persistent (session) properties? The provider instance? The data object the provider is wrapping? Just the state Set? Just the ID of the data object that the provider wraps?Thanks!
On 12/2/05, Jesse Kuhnert <[EMAIL PROTECTED] > wrote:This sounds familiar somehow. I'm looking at it now..
On 12/2/05, Michael Waluk <[EMAIL PROTECTED]> wrote:I'm hoping someone can remind me of what to do to. Here is the scenario I am trying to get working...One component on my page contains an AjaxDirectLink whose listener updates a value in my ASO.Another component on my page contains a tacos:Tree and its pageBeginRender reads the ASO value, creates a new ITreeContentProvider instance and sets it into one of its properties.I was hoping that this component would then actually render (and the Tree would pick up its new provider instance) and I would see the new tree displayed. The AjaxDirectLink's updateComponents is set to the div around the Tree (in the 2nd component).What I have found is that the value does get set into the ASO and the pageBeginRender does get called and the new provider is set, but doesn't refresh on the screen. Within pageBeginRender of that second component isRendering() is returning false so I guess that is why. So how do I get it to render the page again so that the Ajax response can contain the new tree? If I refresh the page then I see the new tree displayed, so I know that part is working, I just need to render it into the Ajax response.Thanks for any advice you might have. It is probably something obvious that I have forgotten. (I'm using T4-beta13 and a fairly recent Tacos CVS version)- Michael
