Yeah this would be great ... One of the bug frustrations was that
WOApplication does a System.exit(0) when it fails to start, which made
debugging really rough (every time it didn't work it would quit out of
my debug eclipse).
ms
On Nov 15, 2007, at 5:39 PM, Pierre Frisch wrote:
> I think I know what is going on. We need to change the code so that
> the application does not inherit from WOApplication then we can
> build it as a regular jar with classpath.
>
> Pierre
>
> On Nov 15, 2007, at 14:13, Mike Schrag wrote:
>
>>> As far as starting a WO App, I spent several days trying to get WO
>>> 5.4 and JavaEOGenerator to deploy inside of wolips as a plugin
>>> (and Apple was kind enough to grant permission to release it), but
>>> I was never able to get this to behave properly. The classloaders
>>> involved in WO consistently fought me when combined with the
>>> already crazy classloading going on with OSGi plugins in Eclipse.
>>> But if someone can figure out a way to make this work properly,
>>> I'm certainly willing to take a look at it more.
>>
>> ms
>>
>>
>
This archive was generated by hypermail 2.0.0 : Thu Nov 15 2007 - 17:54:36 EST