> -----Urspr�ngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Im Auftrag von Craig McClanahan > Gesendet: Sonntag, 19. Dezember 2004 23:28 > An: Jakarta Commons Developers List; [EMAIL PROTECTED] > Betreff: Re: AW: AW: AW: [proposal] avoiding jar version nightmares > > On Sun, 19 Dec 2004 23:25:30 +0100, Oliver Zeigermann > <[EMAIL PROTECTED]> wrote: > > On Sun, 19 Dec 2004 22:17:10 -0000, Stephen Colebourne > > <[EMAIL PROTECTED]> wrote: > > > I would also -1. Versioned packages is not an acceptable solution. > > > > What is an acceptable solution then? > > Do what I said already ... create subordinate class loaders *within* > your application, and load the offending subordinate modules into > their own class loaders, with their own dependencies.
Simple example: If you have two libraries: Library A using component-1.x Library B using component-2.x Both libraries provide some servlets that need to live in the same webapp and get initialized at startup. How to make this work (for users with average java knowledge)? This is a simple example, but I could give you many others where libraries depend on each other and need to share the same classloader. So your proposal won't work. Daniel > > > > > Oliver > > > > Craig > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
