Re: Another plea for help from a newbie
Re: Another plea for help from a newbie
- Subject: Re: Another plea for help from a newbie
- From: Justin Tocci <email@hidden>
- Date: Fri, 4 Jun 2004 08:14:26 -0500
You are right Art. I am going to re-work this to do it the right way, I
was wrong about using it for this data.
I am still happy to know how to do it though because there are other
records that need to be displayed on this screen which cannot be
modeled because the relationship is too complex for EOF. Fortunately,
this pattern will work for that.
thanks Art.
Justin Tocci
Fort Wayne, IN
This still looks like you're doing things the old relational database
client way rather than the object-oriented EOF way. I.e., this object
seems to be being used to explicitly fetch a related object when you
should be able to merely follow the relationship path and let EOF do
the fetching for you, but only if it needs to. In an earlier message
that I no longer have, I think you mentioned that kitNumber was the
foreign key of a relationship. Primary and foreign keys are normally
not class properties and should not be accessed in one's Java code. If
that relationship is named "kit" in your eomodel, part.kit() would be
the appropriate way to access the kit related to the part.
Also, you're setting a Session instance variable rather than passing
the object directly to the next component. Normally, Session shouldn't
be cluttered with such objects, but there are situations in which this
is appropriate.
But maybe I don't understand your situation...
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.