Re: Migrations problem with FrontBase
Re: Migrations problem with FrontBase
- Subject: Re: Migrations problem with FrontBase
- From: Ângelo Andrade Cirino <email@hidden>
- Date: Wed, 19 Dec 2012 10:00:00 -0200
| Hi Cheong,
I meant in my specific case, where is WO looking for the prototypes? Searching in my disk I only found the EOPrototypes class file. In my project the MySQLPlugin was removed from the class file and the FrontBasePlugIn was put before EOPrototypes in the class path order. My model specifies FrontBase prototypes. That's why I am not able to understand why WO is taking the MySQL prototypes and not the FrontBase ones. I will try the EOPrototypesToHide hint with a MySQL attribute and let you know the outcome.
One more thing about my problem. It seems to only have affected the prototypes used by the migrations system. My entities were not affected at all.
Cheers,
Angelo Em 19/12/2012, às 02:16, Cheong Hee (Gmail) escreveu: Found this original WO doc to share and hope it helps. Not sure if this still hold water after integrating with Wonder: "When resolving a prototype name, Enterprise Objects Framework looks for prototypes in EO<adaptor-name>Prototypes, then in EOPrototypes, and finally in the adaptor for your model. This search path allows you to override the prototypes provided by each adaptor. Furthermore, if you don't want to use the adaptor-defined prototypes at all, you can hide them. Create an entity named EOPrototypesToHide. For each prototype you want to hide, create an attribute with that name; you don't need to specify other attribute properties." Cheers Cheong Hee
|
_______________________________________________
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