Reusable Component Tricks...
Reusable Component Tricks...
- Subject: Reusable Component Tricks...
- From: LD <email@hidden>
- Date: Tue, 2 Aug 2005 15:31:34 +1000
Hi all,
I've just been having a look through the developer examples for
Reusable components here...
/Developer/Examples/JavaWebObjects/Frameworks/WOComponentElements
... and I'm just trying to understand a couple of things. e.g.,
In EXHyperlink you've got:
--WXHyperlink.html--
<WEBOBJECT NAME=HyperlinkContainer><WEBOBJECT NAME=String></
WEBOBJECT><WEBOBJECT NAME=Content></WEBOBJECT></WEBOBJECT>
--WXHyperlink.wod--
Content: WOComponentContent {}
HyperlinkContainer: WOGenericContainer {
elementName = "a";
invokeAction = invokeAction;
href = context.componentActionURL;
}
String: WOString {
value = ^string;
}
If I understand the WOGenericContainer correctly, after invokeAction
is called href will be the returned component's componentActionURL, yes?
What's the deal, however, with having both the WOString and
WOComponentContent as child elements? And where exactly is the
^string pulling its info from? I understand that the caret symbol is
analogous to a call to super but WOGenericContainer doesn't have a
'string' binding nor does WOComponent...
As for other tricks, I'll need to spend some time looking through
Chapters 6-7 of Practical WebObjects, but in the mean time - how do
others take advantage of WOGenericContainer and co?
with regards,
--
LD
_______________________________________________
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