EOModeler and EOProtoypes Question
EOModeler and EOProtoypes Question
- Subject: EOModeler and EOProtoypes Question
- From: James Cicenia <email@hidden>
- Date: Sat, 11 Dec 2004 09:25:57 -0600
Hello -
I have an EOModel that I originally created seemingly eons ago. As
such, it didn't use
prototypes extensively. So now that I have the opportunity (demand) to
also port our
application to DB2 I am a bit confused on what to do.
It was originally done using EOPrototypes and not EOJDBCPrototypes.
What is the best
approach here? I am using Eclipse 3.
Should I first extend my original prototype to cover all attribute
types and make ALL attributes reference the prototype?
Do I then create a second prototype with the exact same names but with
the different types and put this in a new
framework?
I am reading Practical Webobjects but have never used multiple
frameworks before so I am confused.
How does EOModeler find the prototypes if they are not in the model but
in a different framework? Does
EOModeler see the frameworks?
Thanks again,
James Cicenia
_______________________________________________
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