Re: Relationships across frameworks
Re: Relationships across frameworks
- Subject: Re: Relationships across frameworks
- From: Florijan Stamenkovic <email@hidden>
- Date: Wed, 06 Aug 2008 10:14:53 -0400
Why? No one keeps you from adding the methods to your classes? You
just shouldn't call them when you don't actually have the
relationship...
I was also thinking yesterday evening that I could easily define a
class that would encapsulate relationship information, use that info
during runtime to create the necessary relationships, and also to
obtain valid relationship keys if I declare instances publicly. As
far as I can see it would limit the relationship definition to one
place, and give me compile time checking, since I don't use getter/
setter methods directly, due to the way JBND works.
And with some tweaks to JBND I might be able to shift the event
firing mechanism from setters to overridden EOEnterpriseObject
methods, thereby eliminating the need to manually write the methods
for custom relationships. It could work, and be reasonably clean as
well.
I guess the only issue would be that I'd lose relationship and
foreign key info on the database level, but we use only EOF to access
it anyway.
F
_______________________________________________
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