Re: WOInject: harmed twice by classloader manipulation
Re: WOInject: harmed twice by classloader manipulation
- Subject: Re: WOInject: harmed twice by classloader manipulation
- From: Henrique Prange <email@hidden>
- Date: Wed, 27 Jun 2012 11:32:38 -0300
Hi Joseph,
On 25/06/2012, at 10:57, Joseph Pachod wrote:
>
> HI Henrique
>
> I finally had the time to test your changes, launching my app from
> another class than the application one.
>
> It works smoothly, so well done, thanks :)
>
Good to hear! :)
> Only issue left is how to tackle the integration of this fix. Indeed
> we have something like 300 launchers currently, all being in their
> application's class. I've to figure out a way to cleanly migrate them
> all. Or maybe you've a better way, if so let me know.
>
That's the drawback of this solution. I'll write a more general e-mail to the WO-dev list explaining the problem and asking for suggestions. I may be missing something obvious. For instance, maybe we could do something on the WOBootstrap level, but I'm not sure.
> Thanks again !
>
> As a side note: how are you able to figure out which class get loaded
> when precisely? I
>
I've enabled the log of class loading by passing the -verbose argument when running the app. The _NSUtilities class is loaded during the static initialization of ERXApplication or WOApplication when running the application through the main method of the Application class. So, it is too late to load the custom _NSUtilities even doing this as soon as possible. When running the application through the AppRunner the static initialization of those classes is delayed and it's possible to load a custom _NSUtilities without conflicts.
Cheers,
Henrique
_______________________________________________
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