Hi all,
I hope somebody can tell me just wether it is possible or not to create
the next soapmessage with Axis. For two weeks I'm trying to create the
message and I failed to do so. The message I try to create is:
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XML
> Actually, I think the empty interfaces are not the problem. It seems to
me that they are just marker interfaces for subclassing whatever
[de]serializer(s) you want to use and store in a TypeMappingRegistry.
Well, they're a syptom of a deeper problem--JAX-RPC doesn't specify the
semantics of the
Actually, I think the empty interfaces are not the problem. It seems to me that they
are just marker interfaces for subclassing whatever [de]serializer(s) you want to use
and store in a TypeMappingRegistry. The real problem is that there is no way, through
the JAXRPC API to get to the TypeMapp
This is an eccentricity of DOM. When you call
nodes.item(0), it returns an Element node that represents the
element. To get the textual content of an element, you can't call getNodeValue()
directly on the Element node; rather, you have to have to get a TextNode object,
which is a child of t
JAX-RPC 1.0/1.1 defines Serializer and Deserializer interfaces. However,
both are empty except for a getMechanismType() method that returns a String.
The meaning of the return value is not defined.
In other words, you're out of luck. :-(
- Rob
- Original Message -
From: "Anne Thomas Ma
Hi
I have written a soap client(using apache soap api) and the structure of the response from the server is similar to this:
...
...
valueOf9
valueOf10
...
...
Now, I am retrieving the value of 'name10' like this:
Parameter result = response.getReturnValue();
Element root = (Element) resu
Mark,
I don't believe that the JAX-RPC spec defines a standard way to do custom
[de]serialization. The Axis classes are used by many vendors (IBM, Borland,
Macromedia, Pramati, etc), but I wouldn't say that it has been established
as a defacto standard. There are lots of other implementations that
Naresh has answered only one half of the question (the server side). From
the server's perspective, the return is an XML element, but if I understand
Hengel's question, his client wants the XML element translated into a Java
class. Which is fine.
Naresh is correct that you want to use a document-s
Hi Hengel,
If all you are trying to do is to return an XML document in the SOAP
body, use a document-style Web service, specifically Axis's "message
service-style". This is documented in the Axis user's guide. You can see
an example of such usage in the Simple Messaging Framework at
smfw.sourcefor
