Felix Meschberger wrote > Hi, > > Well, I have been experimenting with the Apache ServiceMix wrapper > bundles and was successful. So I think, instead of actually creating > some system bundle fragments for the XML APIs we should probably rather > add the ServiceMix bundle(s) from the start. > > See SLING-1958 [1] and the proposed patch. > > WDYT ?
Yes, this sounds like the best approach: +1 Carsten > > Regards > Felix > > [1] https://issues.apache.org/jira/browse/SLING-1958 > > Am Mittwoch, den 19.01.2011, 14:50 +0000 schrieb Felix Meschberger: >> Hi all, >> >> We currently add a whole bunch of Java Extension APIs in the javax.* >> arena to the export list of the system bundle by virtue of actually >> providing in the framework, what is provided in the JDK. >> >> While we (at Adobe) are now confronted with real-life use of such API >> (javax.xml, etc.) we run in to a number of issues, like class loading >> but also incompleteness of the API packages provided by the platform. >> >> I am thus considering the following as a potential idea: >> >> * We remove the extension API (mostly around XML and DOM stuff) >> from the sling.properties file and thus do not by default >> provide it in the framework any longer >> * As a replacement we create a system extension fragment bundle >> which re-adds these packages >> * For more demanding applications the fragment bundle can be >> replaced with a bundle containing and exporting the full API >> packages -- thus effectively hiding what is provided by platform. >> >> WDYT ? >> >> Regards >> Felix >> > > > -- Carsten Ziegeler [email protected]
