On Jun 26, 2009, at 11:39 AM, Mike Schrag wrote:
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.
Yep... working on this... I'm first making sure all the components
extend my base class MPVWOComponent (who is a subclass of ERXComponent).
then I'll put the performParentAction() in MPVWOComponent to try to
catch the exception assuming it's happening.
Thanks
_______________________________________________
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]
