Architectural question regarding WOComonent Actions and Frameworks
Architectural question regarding WOComonent Actions and Frameworks
- Subject: Architectural question regarding WOComonent Actions and Frameworks
- From: Ute Hoffmann <email@hidden>
- Date: Wed, 22 Sep 2004 21:07:40 +0200
Hi,
I'm currebtly splitting a Framework and run into the issue, that I
somehow need some Component Actions to hand over values but can no
longer see their target components, because they will be in a framework
which must be "above" the framework which makes the call.
I use to hand over values in WOComponent Links via nextPage.setX. But
as soon as the component I'm linking to is not visible to the framework
I will get a compiler error, of course.
Is there a way to hand over values in the function and have the target
component only as string in the action to make this compile (yes, it
should run as well, but I will make sure that the component is visible
from the application level). I cannot hand over anything in Actions
which are of the beyound type, right?:
public WOComponent test(){
return pageWithName("xx");
}
All possible workarounds (Parent Components, for example) seem to be
not what I really would like.
I know I could use Direct Actions perhaps, but in at least one case I
would rather not.
Perhaps someone had the same issue and has a suggestion what could be
done in place of making those components into partial components
calling parent Actions, which reside in the framework where also the
components are sitting.
Thanks for some input,
Regards
Ute
P.S. Propably what I want to do is bad design.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden