Re: Prototypes and Inheritance
Re: Prototypes and Inheritance
- Subject: Re: Prototypes and Inheritance
- From: Dev WO <email@hidden>
- Date: Fri, 26 Aug 2005 02:33:23 +0200
I really feel I did a mistake in my prototypes frameworks...
I'll try to recap what I've done so maybe you'll see where I did a
mistake:
-I created an eomodel named EOPrototypes with no connection (none
selected between "jdbc, odbc, none")
-I created an entity named EOJDBCPrototypes
-I created a couple attributes in this entity
I created a framework only for this prototypes and named it
EOMySQLPrototypes.framework
I built this framework and add the built to /Library/Frameworks
I added the frameworks to my application Framework project (let's
name it application.framework)
I edited the application eomodel and selected the different
prototype for each attributes, made sure everything has an
external name.
Then built the application.framework and put it in /Library/
Frameworks/
Then opened my application project, and ran it
The application project has the application.framework and
JavaJDBCAdaptor.framework.
Should it have the EOMySQLPrototypes.framework too?
Yes. The application needs to include all the frameworks that it
used directly or indirectly.
This is the key:)
I know it sounds almost stupid to not do that, but as the application
framework referenced the EOPrototypes I thought I didn't need to add
it somewhere else... And I was wrong:)
Thanks a lot Chuck:)
Putting all that back into production and time to go to sleep:) (it's
2:30 in the morning here)
Xavier
_______________________________________________
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