I have a link followed by a container.
The container contains a component which has an NSArray that it
iterates over.
Your Ajax action method should return null, not the component you're
trying to update. I don't know if this is what you're doing, but it
will definitely cause terrible problems. When you use Ajax framework,
think about how you would write your page if you weren't allowed to
ever return another page (i.e. consider all your action methods
returning null). This is how the framework works -- with every
update, you're doing state transitions on the current page, not going
to another page. This explains why you shouldn't be returning the
updated component from an action. If you did this in a non-ajax
action, you would just end up on a "page" that is the single
subcomponent you returned. Basically this same thing is happening in
an Ajax update, but with slightly weirder side-effects.
I'm hoping there's something obvious I'm missing.
Definitely something you're doing that's a bit off ... Every
conceivable insane way of using these components is pretty much
covered :)
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
