TYPES.XML for client generated stubs?

Question

Hello!
Does the types.xml file, generated by 'autotype' when the web service is created,
need to be bundled with the client? If so, where should it go? I tried placing
into the same package path as the generated client stubs, but that didn't have
an effect.
When I generate the web service, the type.xml shows up in WEB-INF/classes ...
so does that mean the client should have it in the root package?
Thanks
-- Jake

Answer 1

Hi Jacob,
There are no types generated, because the method of your "backend" component,
accepts (or returns) an org.w3c.dom.Document. Correct? This basically means that
the input argument (or return type) can be any XML document, which is why the
WSDL uses an xsd:anyType :-)
I don't know about WLS 8.1 SP2, but you will need weblogic.jar in the client's
CLASSPATH to call a WebLogic Web Service operation, which accepts or returns an
object that implements the org.w3c.dom.Document interface. This is because the
webserviceclient.jar (or webserviceclient+ssl.jar) file does not contain all the
classes needed to marshall/unmarshall an org.w3c.dom.Document. You may also have
some problems getting a "static" (i.e. stub) JAX-RPC client working. The JAX-RPC
"dynamic" (i.e. dii) JAX-RPC client will work, "out-of-the-box", if you load the
type mapping registry with the correct info from the WorkflowService.xml file.
I have attached a code extract that shows what the DII code should look like :-)
For the record, the org.w3c.dom.Document object does not travel over the wire
to the target web service. Just the XML inside it :-) This means that the target
web service implementation does not need to know that you use an org.w3c.dom.Document
object to marshall/unmarshall the arguments (or return value).
Regards,
Mike Wooten
"Jacob Anderson" <[email protected]> wrote:
>
I tried building the client classes using the web service EAR file, thinking
that
it would embed the type information into the client JAR file. Unfortunately,
no, that did not occur. The type mapping data in the WorkflowService.xml
found
in the generated client JAR file contains nothing:
<wsdd:type-mapping xmlns:wsdd="http://www.bea.com/servers/wls70"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
</wsdd:type-mapping>
On the console, when running the client, I see:
[java] javax.xml.rpc.JAXRPCException: web service invoke failed:
javax.xml.soap.SOAPException:
failed to serialize interface org.w3c.dom.Documentweblogic.xml.schema.binding.SerializationException:
mapping lookup failure. class=interface org.w3c.dom.Document class context=TypedClassContext{schemaType=['http://www.w3.org/2001/XMLSchema']:anyType}
Clearly the client is not able to understand the "anyType" that is used
in the
service WSDL to denote the org.w3c.dom.Document type.
Does the classpath have an impact here? I noticed that the webserviceclient.jar
is supposedly the only jar needed to run WS clients. Well, I call "setEnv.cmd"
before I run the ant task to build and test my web service - does that
have an
effect? It didn't seem to affect tutorial31 when I ran it this way.
Any help is greatly appreciated
-- Jake
"Jacob Anderson" <[email protected]> wrote:
Hello!
Does the types.xml file, generated by 'autotype' when the web service
is created,
need to be bundled with the client? If so, where should it go? I tried
placing
into the same package path as the generated client stubs, but that didn't
have
an effect.
When I generate the web service, the type.xml shows up in WEB-INF/classes
so does that mean the client should have it in the root package?
Thanks
-- Jake
[jacob-dii.txt]