Re: Why WOBuilder only displays EOModel attributes and not java properties
Re: Why WOBuilder only displays EOModel attributes and not java properties
- Subject: Re: Why WOBuilder only displays EOModel attributes and not java properties
- From: Art Isbell <email@hidden>
- Date: Fri, 25 Mar 2005 10:36:35 -1000
On Mar 25, 2005, at 10:17 AM, Art Isbell wrote:
By making these WOB properties the opaque Object type, all
implementation changes are now made in the Model class.
I should have stated:
By declaring these WOComponent properties to be the opaque Object type,
all implementation changes are now made in the Model class.
I'm not following eomodel relationship paths shown in WOB which are no
longer shown anyway because none of my WOComponent properties are
EOCustomObjects
I'm not following eomodel relationship paths shown in WOB which are no
longer shown anyway because none of my WOComponent properties is a
EOCustomObject
Instead, I set and get the values of these properties ideally only
once during each request-response cycle in awake(),
takeValuesFromRequest(), invokeAction(), appendToResponse(), and
sleep() in addition to the getter and setter methods for the variables
bound to "item" keys in WORepetition, WOPopUpButton, and their ilk.
Instead, I set and get the values of these properties ideally only once
during each request-response cycle in awake(), takeValuesFromRequest(),
invokeAction(), appendToResponse(), sleep(), or in the getter and
setter methods for the variables bound to "item" keys in WORepetition,
WOPopUpButton, and their ilk.
<Proofread before posting, proofread before posting, proofread before
posting, ...>
Aloha,
Art
_______________________________________________
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