There is one caveat to the above. I must use
org.osgi.framework.bundle.parent=framework otherwise, I return to the same original problem. But I'm ok with setting this. - Ray On Wed, Aug 6, 2014 at 11:02 AM, Raymond Auge <[email protected]> wrote: > On Wed, Aug 6, 2014 at 4:27 AM, Neil Bartlett <[email protected]> > wrote: > >> Hmm… *if* that is the case then I *might* agree with you. I’d like to >> know who actually depends on these packages, ultimately? >> >> I think it would be worth going back to the beginning. If you neither >> import the com.sun.apache.* packages, nor bootdelegate them either, exactly >> how does the system fail? >> > > Actually, as it turns out when I "fix" the offending bundle so it does not > import the com.sun.* packages AND I do NOT bootdelegate those packages, > everything just works AND I remove the system bundle exports I had added to > satisfy those bad imports everything starts to work as it should. > > There were apparently side effects to other bundles using Java SE provided > xml parsing because of the exports. > > *Summary* > Fixing the "bad" bundle's imports and removing the system bundle exports > solved the problem for me. > > Thanks everyone! > - Ray > > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay)
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
