Along similar lines I've been asked to have geronimo distribute the ee6 schemas to go with our spec jars. I've been wondering how to do this in an osgi friendly way. I haven't actually tried anything yet but have been thinking about trying to come up with an osgi-friendly xml catalog implementation that might look for an appropriate manifest header in bundles and add the schemas in the bundle to the xml catalog.
It's been several years since I messed around with xml catalog but IIRC despite if being documented as only working for dtd based xml, in actual fact xml parsers use it for locating schemas from xml namespaces. Does anyone know of any existing work along these lines? thanks david jencks On Jul 27, 2010, at 10:41 AM, Graham Charters wrote: > Hi Lin, > > I'm not sure this is the right thing to do. Including a > schemaLocation implies we will host the schema at that location, but I > wouldn't think we want to commit to that. I know many standards that > don't even make this commitment (e.g. the OSGi Alliance). Also, > schemaLocation is just a hint and not required to be used and if I'm > working offline, I still want it to work. > > I think we need some other way for this to function without > schemaLocation, but don't have a good suggestion at the moment. > > Regards, Graham. > > > On 27 July 2010 16:05, Lin Sun <[email protected]> wrote: >> Hi Graham >> >> I intended to use it in the message-driven schema where I need to >> specify the schema location of the transaction.xsd file, like below >> >> <xsd:import >> namespace="http://aries.apache.org/xmlns/transactions/v1.0.0"; >> >> schemaLocation="http://svn.apache.org/repos/asf/incubator/aries/trunk/transaction/transaction-blueprint/src/main/resources/org/apache/aries/transaction/parsing/transaction.xsd"; >> /> >> >> The source of mds.xsd is avail here >> http://svn.apache.org/repos/asf/incubator/aries/sandbox/linsun/mds/mds-blueprint/src/main/resources/org/apache/aries/mds/blueprint/mds.xsd >> >> >> In this case, I don't know how to refer to the schema file in a jar. >> I see no issue of publishing our transaction schema 1.0.0, as it is >> being released. I am in fact making changes to the transaction >> schema for bundle wide transaction configuration but I plan to make >> the new schema version 1.1.0. >> >> Thanks >> Lin >> >> >> >> On Tue, Jul 27, 2010 at 6:01 AM, Graham Charters <[email protected]> wrote: >>> Hi Lin, >>> >>> I'm wondering how you intend to use the schema once published. If >>> you're going to load it from that location, that seems a little >>> brittle, and we wouldn't want people relying on us hosting it there. >>> Should it not be packaged in a transactions "api" bundle and loaded >>> out of there by the message-driven services component? >>> >>> Regards, Graham >>> >>> On 22 July 2010 15:43, Lin Sun <[email protected]> wrote: >>>> Hi >>>> >>>> I'd like to publish the transaction.xsd from the blueprint transaction >>>> project to the aries web site. I know it is not final yet but it is >>>> pretty much done and I need to use it in the message-driven service >>>> schema to allow users to easily demarcate transactions for the >>>> message-driven service. Currently I am referring to the svn location >>>> which is rather length. >>>> >>>> Does anyone know how to do this? I tried to attach the file to our >>>> cwiki but that didn't work for me. >>>> >>>> Thanks >>>> >>>> Lin >>>> >>> >>
