You and me both! I find I'm actually disapointed that it's not following the spec... after all, how else do we ensure that our portable code can run on Geronimo?
Who do I have to poke, bug and generally hastly to get this choice reviewed? Yes, I can be mouthy, and I do appreciate all the hardwork thats gone into Geronimo, but I'd also like to be able to use it and as I mentioned in another post, not a single webapp that I've tried runs without major surgery... not a good situation. Anyway, the key here is *isolation*... don't share anything with the webapp unless specifically configured to do so. I suspect this has security implecations as well, but don't have the time at the moment to dig for them. - Brill Pappin On 3/20/06, Aaron Mulder <[EMAIL PROTECTED]> wrote: [...] > To Brill: > > It wouldn't break my heart to see Geronimo default to the spec > behavior for class loading. I'm not sure that would solve this > problem (e.g. if the class is already loaded it may not load it > *again* from the web app loader), but I'd have to check the spec to be > sure.
