Hiranya Jayathilaka <[email protected]> wrote on 06/02/2010 11:54:02 PM:
>> On Thu, Jun 3, 2010 at 1:06 AM, Holger Hoffstaette < >> [email protected]> wrote: >> >> Hi, >> >> I'm very glad that Xerces-J is showing signs of life and gearing for a >> 2.10 release. I know it's a bit late in the release cycle, but I'd like to >> contribute an IMHO very important piece: proper OSGi integration. >> >> The recently released OSGi spec 4.2 has support for proper registration of >> JAXP-compliant parsers into the OSGi service registry. This integration is >> extremely minimal and requires merely two things: >> >> - addition of a single ready-made class (a bundle activator) >> - addition of a handful of entries to the MANIFEST file >> >> That's all. While the single new class has a compile-time dependency on >> the OSGi framework, it is only a *compile* dependency that has no impact >> on the run-time behaviour of xerces outside of OSGi; users will likely not >> even see it as it can be made as "private" as possible. >> >> The process for adding this integration is explained in the 4.2 Compendium >> and Enterprise specs which are freely available from www.osgi.org. >> >> The necessary additions to the build took me ~10 minutes - all I did was >> add the Activator (available as source under ASL license), an Apache Felix >> framework jar as OSGi compile-time dependency, and the necessary bundle >> headers to the manifest.xerces. >> >> These additions have no impact on non-OSGi users, license restrictions, >> runtime overhead or any other effect that would "endanger" a release or the >> stability of the code. Therefore I'd really like to see this considered >> for the upcoming release...pleeease? :) >> > > I'm not sure if we can get this into the upcoming release at this > point. But I'd certainly like to have a look at your patch. So > please file a JIRA and attach the patch. Xerces usually causes a lot > of problems when integrating into OSGi environments. So this would > be a very good improvement. I did commit a bug fix today, but we really are trying to get a build and testing done right now, along with the remaining doc updates. Khaled did propose another release for later in the year, so perhaps OSGi support could be part of that and would also give folks ample time to reflect on the feature, rather than rushing something new in without a good understanding of what it is / does and its implications. > Thanks, > Hiranya, > > >> If this is of interest I'll file a JIRA and attach patches & instructions >> there. >> >> Holger >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com Thanks.> Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [email protected] E-mail: [email protected]
