Re: Migrations and Application's finishInitialization()
Re: Migrations and Application's finishInitialization()
- Subject: Re: Migrations and Application's finishInitialization()
- From: Farrukh Ijaz <email@hidden>
- Date: Sun, 19 Sep 2010 17:14:09 +0300
Hi Johann,
Thanks for the suggestion. This fixes the issue nicely.
Farrukh
On 2010-09-19, at 4:58 PM, Johann Werner wrote:
> Hi Farrukh,
>
> you should use the method didFinishLaunching (look at ERXApplication). This method should be called after all init/migration/etc stuff has been done.
>
> jw
>
> Am 19.09.2010 um 11:28 schrieb Farrukh Ijaz:
>
>> Hi again,
>>
>> How can I control the execution of finishInitialization() method of my application to execute after the all the models have been upgraded using Migrations?
>>
>> Right now what happens, our applications use some entities in the finishInitialization() method however the application breaks with exception that relationship blah blah does not exist, as Migrations's upgrade method have not yet called. This I've tested also placing some debugging information and break points in the upgrade and finishInitialization() method.
>>
>> Do we need to use Notifications? If so, what would be the appropriate place to post notification?
>>
>> Thanks,
>>
>> Farrukh
_______________________________________________
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