BTW, context().page() is better to return than null.
After much debate, review, and independent testing at WebObjects
National Laboratories, it has been in fact proven that returning
context().page() can, in general, be more efficient at runtime than
returning null. WOHyperlink (at least), though, actually just turns
null into context().page() for you, but if you ever use a component
that might not implement invokeAction in this same way, its siblings
will have their invokeActions called for no reason. Note that those
siblings will not actually DO anything because senderID will not
match their elementID, but you do process extra invokeActions for
nothing, so returning null will not break anything, it's just not the
ideal return value.
However, further testing has ALSO revealed that
"co<complete><enter>.p<complete><enter>", the fastest way to type
this in Eclipse (without defining a custom template mapped to a
single character :) ) is 8 keystrokes, whereas "null" is 4
keystrokes. That said, we're all writing Java, so obviously we don't
care about keystroke counts ......
Annnyhooo ... Back to work.
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]
