Rickard �berg wrote: > marc fleury wrote: >> >> what above "reasoning"... the fact that I don't put in XML the >> dependencies?... > > Yes. The classloader tree needs to be explicit as it cannot be inferred > from any other info in the applications. Is this really true? Would it not be possible to figure out what classes need to be shared from ejb-refs and then pull all of those out of the individual EARs (so that they're not picked up by the leaf classloaders) and put them in the logical application's parent classloader? Just a thought. Toby.
- [jBoss-Dev] The Dumbo problem (Big EARs) marc fleury
- Re: [jBoss-Dev] The Dumbo problem (Big EARs) Rickard �berg
- RE: [jBoss-Dev] The Dumbo problem (Big EARs) marc fleury
- Re: [jBoss-Dev] The Dumbo problem (Big EARs) Mike Lueders
- RE: [jBoss-Dev] The Dumbo problem (Big EARs... marc fleury
- Re: [jBoss-Dev] The Dumbo problem (Big EARs) Rickard �berg
- Re: [jBoss-Dev] The Dumbo problem (Big EARs... Toby Allsopp
- Re: [jBoss-Dev] The Dumbo problem (Big... Rickard �berg
- RE: [jBoss-Dev] The Dumbo problem ... marc fleury
- Re: [jBoss-Dev] The Dumbo prob... Rickard Oberg
- RE: [jBoss-Dev] The Dumbo prob... marc fleury
- RE: [jBoss-Dev] The Dumbo problem (Big... marc fleury
- RE: [jBoss-Dev] The Dumbo problem (Big EARs... marc fleury
- RE: [jBoss-Dev] The Dumbo problem (Big EARs) Jay Walters
- RE: [jBoss-Dev] The Dumbo problem (Big EARs) marc fleury
