I've always just created Entities for these types of things so all
relationships work the same.
Is there substantial savings to doing things this way over simply having EOs?
Dave
On Apr 8, 2010, at 4:52 AM, Mark Wardle wrote:
> Hi all, please forgive a very simple question but I'd like to create a
> lightweight (non-EO) to-one relationship from an EO. I make heavy use
> of D2W so I want to fulfil the WO/EOF rules and use to-one
> relationship components....
>
> I usually create a new entity and have a genuine heavyweight EOF
> relationship but I have several properties for which this seems
> excessive.
>
> I have an entity (FormEdssFull) which can have a visual field score
> for both right and left eye.
>
> Can I do this with a java enum?
>
> public enum VisualAcuity {
> NORMAL(0, "Normal"),
> SIGNS_ONLY(1, "Signs only:"),
> MODERATE(2, "Moderate"),
> MARKED(3, "Marked");
>
> /* insert enum constructor etc... */
> }
>
> and then create the appropriate accessor and mutator in the entity?
>
> What do other people do in these situations?
>
> Many thanks,
>
> Mark
>
> --
> Dr. Mark Wardle
> Specialist registrar, Neurology
> Cardiff, UK
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com
>
> This email sent to webobje...@avendasora.com
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
