Re: Question on WOContext.elementID
Re: Question on WOContext.elementID
- Subject: Re: Question on WOContext.elementID
- From: Kieran Kelleher <email@hidden>
- Date: Fri, 21 Jan 2005 17:00:34 -0500
Chuck, Thanks for the reassurance. I've implemented that and it works
great. .... how nice to have a mechanism for validation message
persistence in stateless subcomponents across the RR loop phases :-)
On Jan 21, 2005, at 2:25 PM, Chuck Hill wrote:
Yes, it will remain constant. This is what WO uses itself to uniquely
identify the component. In fact, I once tried to find some
combination of conditionals, code, and loops that would result in two
different components getting the same element ID in two different
generations of the page. I was unable to do so. It may still be
possible, but it isn't easy.
Chuck
On Jan 21, 2005, at 11:17 AM, Kieran Kelleher wrote:
Hello to all,
Would it be true to say that every WOComponent subcomponent within a
page has a constant WOContext.elementID() during the three phases of
takeValuesFromRequest, invokeAction and appendToResponse in the
situation where the same page is returned and the page layout
visibility and arrangement of all subcomponents remains the same?
I want to use reusable components (stateless with manual binding
synchronization) for all if not most sub-components and I want to use
a key (such as WOContext.elementID) that remains constant during
takeValuesFromRequest, invokeAction and appendToResponse to
temporarily store component specific validation error messages in a
Dictionary in the root parent "page" component which is "stateful".
If WOContext.elementID is not a good candidate, any suggestions?
-Kieran
________________________________________________________________
Dev Config = OS X 10.3.5 / Java 1.4.2_05 / WO 5.2.3 / XCode v1.5 /
MySQL 4.0.20 / Connector-J 3.0.11
Deploy Config = OS X 10.3.7 Server / Java 1.4.2_05 / WO 5.2.3 / MySQL
4.0.20 / Connector-J 3.0.11
My Blog: http://webobjects.webhop.org/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
village.net
This email sent to email@hidden
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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