Re: Sharing a Model using Eclipse
Re: Sharing a Model using Eclipse
- Subject: Re: Sharing a Model using Eclipse
- From: Chuck Hill <email@hidden>
- Date: Mon, 2 Nov 2009 10:59:25 -0800
On Nov 2, 2009, at 7:55 AM, David Avendasora wrote:
On Oct 28, 2009, at 7:59 PM, Chuck Hill wrote:
On Oct 28, 2009, at 4:55 PM, David LeBer wrote:
...the same EOModel and associated java classes ... are stored in
a separate folder and were being referenced by each of the app
projects in XCode.
I don't have an answer as to whether you can reference a separate
model in multiple apps, because I've never tried, and the thought
gives me the willies.
+10,000
I have to go wash my mind out now.
Not that this is going to shock anyone, but I do this. Sort of.
I have a framework that has the model and the server-side EOF
classes in it, just as Chuck and David LeBer are suggesting. I also
have a D2JC application that does not have the model in it but it
does have the client-side (EOF) classes in it. In the D2JC app
the .eogen file points to the model in the framework project in
order to generate the client-side EOF classes.
In the end the D2JC app does have the framework, and therefore the
model, in its classpath, but that's not enough to get EOGenerator to
generate the client-side classes inside WOLips.
But this doesn't really apply at all to what you are talking about.
I mostly just wanted to post to torment Chuck. :-D
It is Monday. I am not even going to think about this.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
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