On Fri, Jun 19, 2009 at 6:55 PM, Karl Pauls <[email protected]> wrote:
> > * Strange issue with WebLogic 9.2 - > > https://issues.apache.org/jira/browse/FELIX-1158 > > I just commented on the issue as well but please retry with the latest > version of felix (or even better, on trunk) as I think this should be > fixed already. Yep, this looks good. I didn't yet test it with WebLogic, but I looked through the code and it looks like it'll do the trick. > We are planning a bugfix release and will look into your issues and > whether we can port them back or not. I don't think FELIX-712 would > need to wait for 2.0 but I have to discuss this with richard first. > Please try to look into verifying the issues I commented on asap so > that we know what to include or not. Also, I uncommented the parent classloading code in ModuleImpl and my tests passed like expected. Looking through the comments, it says something about the code needing to be there because of how the system can export packages, which worries me a bit. All my unit tests passed, though, so maybe I'm misunderstanding the comment. If it is indeed necessary, maybe the fix can just be to not support loading resources from the parent classloader that way. The resources loading is actually the bug that is biting me in 1.8.0, as the classloading is more an annoyance. In summary, if we get some sort of resolution to FELIX-712 and a backporting of the memory leak fix, I'd be happy to upgrade to 1.8.1. I'm really looking forward to bundle fragments, as I keep hitting reasons to use them every day. Today's reason was to workaround the super annoying jaxp issues that have me doing ugly stuff like boot delegating weblogic.* and xerces. Would love to have a bundle fragment automatically attached to every bundle that has META-INF/services files and package imports to ensure the lookups happen cleanly. Thanks for the help! Don
