You are right... Good idea... but it may be challenging as the
performParentAction() calls an action in a parent component and then
that component also calls performParentAction()... and it's a long
chain. So I need to look at all of them to find out... Hey, I did
not write those components hehehe... but it's clear to me it is
overly complex from the way I usually do things in WebObjects. And
it's one of legacy components which seems to be screaming for re-
design. :-)
Thanks for the suggestions.. I'll try them to find out WHERE and
WHY...
The deep call trace is why i suggest putting a try/catch in your base
component's performParentAction -- so all your components have to pass
through yours ... SOMEONE in that chain is going to throw out -- it's
required for this to fail. If it DOESN'T, then there's something else
going on.
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]
