[equinox-dev] ContextFinder stops at first bundle class loader
Hi, Is there a specific reason why the ContextFinder stops at the first bundle class loader? I'm trying to integrate an existing framework into the SSE world. During de-serialization it wants to load classes and the ContextFinder would be really helpful here but it stops at the first bundle class loader which prevents a good bundle architecture. Example: * ConcreteServlet definied in mybundle * ConcreteServlet extends BaseServlet * BaseServlet defined in frameworkbundle * mybundle imports package for BaseServlet from frameworkbundle * BaseServlet#decode(Request) calls code in frameworkbundle which uses context class loader which triggers ContextFinder to load classes (defined in mybundle) * ContextFinder stops at frameworkbundle's class loader but frameworkbundle does not see classes in mybundle. If ContextFinder would simply look further and try additional bundle class loaders up in the stack it would eventually get to mybundle's class loader and everything would work. Is there a specific reason for this design? I could imagine that there could by some circularity or other problems. But if there was no specific reason I wonder if I should open an enhancement request for ContextFinder? -Gunnar -- Gunnar Wagenknecht [EMAIL PROTECTED] http://wagenknecht.org/ ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] naming examples
I agree with John. Use org.eclipse.equinox.examples.* Tom From: John Arthorne [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date: 11/21/2007 07:51 AM Subject:Re: [equinox-dev] naming examples My vote would be for sticking with the Eclipse project naming conventions [1] and using org.eclipse.equinox.examples.*. This convention is consistently following in platform and JDT, and it would look odd if someone downloaded the examples from the welcome page and the Equinox examples didn't match. [1] - http://wiki.eclipse.org/Naming_Conventions Jeff McAffer/Ottawa/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] To [EMAIL PROTECTED] 11/20/2007 09:26 PM se.org cc Please respond to Subject Equinox development mailing list [equinox-dev] equinox-dev@eclipse.org naming examples We have talked a few times about the need for a comprehensive set of examples in Equinox. We may be able to get some folks to work on this so it is interesting to look at the bundle/package namespace to use. The immediate choice that springs to mind is org.eclipse.equinox.examples.* This follows the precedence of org.eclipse.sdk.examples org.eclipse.jface.examples It has also been suggested that we use org.eclipse.equionox.eg.* to shorten things up. Let me know if you have other suggestions and I'll put together an email poll. Thanks Jeff___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] High-level design posted
I just posted a high-level design for the 'Trusted Bundles' or load-time security work that Tom and I have been working on in the Security Incubator: http://wiki.eclipse.org/Trusted_Bundles Comments and questions are greatly appreciated. Thanks! -matt --- Matt Flaherty Security Project Lead, Lotus Notes Eclipse Equinox External: http://www.eclipse.org/equinox/incubator/security/ Internal: https://cs.opensource.ibm.com/projects/eclipsesec/___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
