Using XML Catalogs 14-5
14.2.2.2 Referencing an Embedded XML Catalog
The xmlcatalog child element of the clientgen or wsdlc Ant tasks enables you to reference an embedded XML catalog. To specify the xmlcatalog element, use
the following syntax:
xmlcatalog refid=id The id referenced by the xmlcatalog child element must match the ID of the
embedded XML catalog. The following example shows how to reference an embedded XML catalog using
clientgen. Relevant code lines are shown in bold.
target name=clientgen clientgen
type=JAXWS wsdl={wsdl}
destDir={clientclasses.dir} packageName=xmlcatalog.jaxws.clientgen.client
catalog=wsdlcatalog.xml xmlcatalog refid=wsimportcatalog
clientgen target
xmlcatalog id=wsimportcatalog entity publicid=http:helloservice.orgtypesHelloTypes.xsd
location={basedir}HelloTypes.xsd xmlcatalog
14.3 Disabling XML Catalogs in the Client Runtime
By default, when you define and reference XML catalogs in your build.xml file, as described in
Section 14.2, Defining and Referencing XML Catalogs , when you
execute the clientgen Ant task to build the client, the jax-ws-catalog.xml file is generated and copied to the client runtime environment. The jax-ws-catalog.xml
file contains the XML catalogs that are defined in the external XML catalog files andor embedded in the build.xml file. This file is copied, along with the referenced
XML targets, to the META-INF or WEB-INF folder for Enterprise or Web applications, respectively.
You can disable the generation of the XML catalog artifacts in the client runtime environment by setting the genRuntimeCatalog attribute of the clientgen to
false. For example:
clientgen type=JAXWS
wsdl={wsdl} destDir={clientclasses.dir}
packageName=xmlcatalog.jaxws.clientgen.client catalog=wsdlcatalog.xml
genRuntimeCatalog=false
In this case, the jax-ws-catalog.xml file will not be copied to the runtime environment.
If you generated your client with the genRuntimeCatalog attribute set to false, to subsequently enable the XML catalogs in the client runtime, you will need to create the
jax-ws-catalog.xml file manually and copy it to the META-INF or WEB-INF folder for Enterprise or Web applications, respectively. Ensure that the
jax-ws-catalog.xml file contains all of the entries defined in the external XML catalog files andor embedded in the build.xml file.
14-6 Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server
14.4 Getting a Local Copy of XML Resources
The wsdlget Ant task enables you to get a local copy of XML resources, such as WSDL and XSD files. Then, you can refer to the local version of the XML resources
using an XML catalog, as described in Section 14.2, Defining and Referencing XML
Catalogs .
The following excerpt from an Ant build.xml file shows how to use the wsdlget Ant task to download a WSDL and its XML resources. The XML resources will be
saved to the wsdl folder in the directory from which the Ant task is run.
target name=wsdlget wsdlget
wsdl=http:hostservice?wsdl destDir=.wsdl
target
15
Creating and Using SOAP Message Handlers 15-1
15
Creating and Using SOAP Message Handlers
The following sections provide information about creating and using SOAP message handlers:
■
Section 15.1, Overview of SOAP Message Handlers
Kategori