On Wed, 2006-04-12 at 05:30 -0400, Richard S. Hall wrote: > [EMAIL PROTECTED] wrote: > >> Perhaps there are other possible diagnostics that could help developers > >> when they encounter a class loading error. > >> > >> -> richard > >> > > > > Sounds like a very good idea to me. > > I also think the suggested checks cover most cases, but I'll try to think > > of other cases we might check for. > > Still the danger of people adding things to the boot delegation property > > while they could've/should've made it work without it, but that can't be > > helped I'm afraid.
Have the latest release and have tested the org.osgi.framework.bootdelegation property - it 'works' fine. Note: if this property was previously implemented and set to the current default of org.osgi.framework.bootdelegation=sun.*,com.sun.* I would not have experienced the problem and the associated stress and so would not have sent an email, learned my lesson, and joined the mod squad. Instead when encountering my classloading problems with javax.* packages in a rush I would probably have set it to org.osgi.framework.bootdelegation=sun.*,com.sun.*,javax.* to avoid cleaning up my non-modular bundles with the correct imports declarations. In retrospect I am thankful for the learning experience and recognizing the advantages will now set it to: # org.osgi.framework.bootdelegation=sun.*,com.sun.*,javax.* Perhaps the should be the default? thanks again, John
