Dims, The question of where to add in the catalog is a good one. Is the catalog config nothing more than a mapping of namespaces to document locations?
Cheers,
-Nick
Davanum Srinivas
<[EMAIL PROTECTED]
m> To
axis-dev@ws.apache.org
02/08/2008 02:09 cc
PM
Subject
Re: XML Catalog Support for JAX-WS
Please respond to
[EMAIL PROTECTED]
e.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Brian,
Where ever we read in a WSDL or a Schema is a potential spot for plugging
in a catalog resolver. Basically when we read
in a WSDL, one can add concrete implementation of WSDLLocator in WSDL4J
backed by the catalog. And similarly there is a
hook for XmlSchemaURIResolver in XmlSchema as well. So my bet is whereever
we have a WSDLReader.readWSDL or a
XMLSchemaCollection.read are good places to target for adding a catalog
Of course, we need to talk about where we can add the information for the
catalog as well. My initial thought is to add
an entry in axis2.xml (for example i think you will specify in axis2.xml to
pick up a particular wsdl from a particular
directory for a specific target namespace). Of course if there is no entry
in axis2.xml. We should fall back to the same
code that exists today.
thanks,
dims
Brian Murray wrote:
| I'm planning to add XML Catalog support to JAX-WS via AXIS2-3499. I
spoke
| with Dims, who advised me that there are places in the kernel where the
| catalog needs to be plugged in as well. Can anybody describe to me these
| needed changes?
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFHrLcVgNg6eWEDv1kRAkaKAKDbnhywKDVEowujS97Hfk9WPuq+TgCgvCt1
LLyQRVFHBcydtfPic6YjYKw=
=XLmy
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<<inline: graycol.gif>>
<<inline: pic10284.gif>>
<<inline: ecblank.gif>>
