[news.eclipse.technology.equinox] Re: Integrating Swing apps on top of E

[Dann Martens <dann@xxxxxxxxxxx>]

Hi Eva,

Well, of course, I know that managers never listen to any engineering 
advice and you might be forced to do the unthinkable anyway.

I agree that modifying the app which introduces the least effort in 
terms of adopting a new Look and Feel would be a more sane thing to do!

Otherwise, even by manipulating the class loader hierarchy using two 
separate instances of an older version of swingall.jar, the trusted 
classes which come bundled with any post-1.2 JRE would be loaded first.

You'd have to break the parent delegation behavior in the same way web 
applications (.war) do.

Actually, except for this system property:

-- SNIP --
osgi.compatibility.bootdelegation
if set to "true" then the parent (boot by default) classloader is 
delegated to as a last resort if a class or resource cannot be found. 
The default value is "true".
-- SNIP --

I haven't looked into the features of Equinox to do this at the level of 
an individual bundle.

Best regards,
 Dann


Eva Troels wrote:
> Thank you for you honest reply! I have printed out the 
> square-peg-round-hole image and will be sure to staple it to my letter 
> of resignation :-)
>
> I think that we will continue with just one look and feel for both 
> application and in a most democratic way, the most picky application 
> will have its way.
>
> In earlier version of java, Swing DID have its own swingall.jar.
> It seems to me that it would be a good decision to go back to this. 
> rt.jar would be smaller (something that some people seem to care about) 
> and it would give implementers a choice with regards to GUI platform.
>
> Oh well...
>
> Eva