You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Artem Portnoy <ar...@ibi.com> on 2000/09/12 16:34:16 UTC
DOM Element serializer/deserializer
Hi,
I have a question about the use of DOM Element serializer/deserializer.
In the Address Book sample they use the following declaration to support
DOM:
call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
I tried to use this in my own code. I have a method which returns a DOM
Element object, but the difference is that the method also accepts two
String parameters. Now, when I tried to run this code, I got a message
like the following "Caught SOAPException (SOAP-ENV:Client): I only know
how to serialize an 'org.w3c.dom.Element'."
How do I go about solving this problem? I mean how do I tell the SOAP to
use one encoding style for the parameters, and a different one for the
return value?
Thanks in advance,
Artem
Re: DOM Element serializer/deserializer
Posted by Cory Isaacson <ci...@capita2.com>.
George,
I'd be happy to contribute this to the samples. I'll make a stripped down
version as a simple SOAP client.
Cory
----- Original Message -----
From: "George I Matkovits" <ma...@uswest.net>
To: <so...@xml.apache.org>
Sent: Tuesday, September 12, 2000 3:01 PM
Subject: Re: DOM Element serializer/deserializer
> When you complete this project, could we add it to the Soap Samples,
please.
> Thank you - George
>
> Cory Isaacson wrote:
>
> > I'm not 100% certain, but I think if you use the literal XML
serialization,
> > you need to send and receive a DOM as parameters and return values. I
did
> > this by building one DOM for parameters and getting another back.
Obviously
> > you can then embed whatever you need inside the DOM that you send and it
> > works fine.
> >
> > Thanks,
> >
> > Cory
> > ----- Original Message -----
> > From: "Artem Portnoy" <ar...@ibi.com>
> > To: <so...@xml.apache.org>
> > Sent: Tuesday, September 12, 2000 10:34 AM
> > Subject: DOM Element serializer/deserializer
> >
> > > Hi,
> > > I have a question about the use of DOM Element
serializer/deserializer.
> > > In the Address Book sample they use the following declaration to
support
> > > DOM:
> > > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > > I tried to use this in my own code. I have a method which returns a
DOM
> > > Element object, but the difference is that the method also accepts two
> > > String parameters. Now, when I tried to run this code, I got a message
> > > like the following "Caught SOAPException (SOAP-ENV:Client): I only
know
> > > how to serialize an 'org.w3c.dom.Element'."
> > > How do I go about solving this problem? I mean how do I tell the SOAP
to
> > > use one encoding style for the parameters, and a different one for the
> > > return value?
> > > Thanks in advance,
> > > Artem
> > >
>
Re: DOM Element serializer/deserializer
Posted by Cory Isaacson <ci...@capita2.com>.
George,
I'd be happy to contribute this to the samples. I'll make a stripped down
version as a simple SOAP client.
Cory
----- Original Message -----
From: "George I Matkovits" <ma...@uswest.net>
To: <so...@xml.apache.org>
Sent: Tuesday, September 12, 2000 3:01 PM
Subject: Re: DOM Element serializer/deserializer
> When you complete this project, could we add it to the Soap Samples,
please.
> Thank you - George
>
> Cory Isaacson wrote:
>
> > I'm not 100% certain, but I think if you use the literal XML
serialization,
> > you need to send and receive a DOM as parameters and return values. I
did
> > this by building one DOM for parameters and getting another back.
Obviously
> > you can then embed whatever you need inside the DOM that you send and it
> > works fine.
> >
> > Thanks,
> >
> > Cory
> > ----- Original Message -----
> > From: "Artem Portnoy" <ar...@ibi.com>
> > To: <so...@xml.apache.org>
> > Sent: Tuesday, September 12, 2000 10:34 AM
> > Subject: DOM Element serializer/deserializer
> >
> > > Hi,
> > > I have a question about the use of DOM Element
serializer/deserializer.
> > > In the Address Book sample they use the following declaration to
support
> > > DOM:
> > > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > > I tried to use this in my own code. I have a method which returns a
DOM
> > > Element object, but the difference is that the method also accepts two
> > > String parameters. Now, when I tried to run this code, I got a message
> > > like the following "Caught SOAPException (SOAP-ENV:Client): I only
know
> > > how to serialize an 'org.w3c.dom.Element'."
> > > How do I go about solving this problem? I mean how do I tell the SOAP
to
> > > use one encoding style for the parameters, and a different one for the
> > > return value?
> > > Thanks in advance,
> > > Artem
> > >
>
Re: DOM Element serializer/deserializer
Posted by George I Matkovits <ma...@uswest.net>.
When you complete this project, could we add it to the Soap Samples, please.
Thank you - George
Cory Isaacson wrote:
> I'm not 100% certain, but I think if you use the literal XML serialization,
> you need to send and receive a DOM as parameters and return values. I did
> this by building one DOM for parameters and getting another back. Obviously
> you can then embed whatever you need inside the DOM that you send and it
> works fine.
>
> Thanks,
>
> Cory
> ----- Original Message -----
> From: "Artem Portnoy" <ar...@ibi.com>
> To: <so...@xml.apache.org>
> Sent: Tuesday, September 12, 2000 10:34 AM
> Subject: DOM Element serializer/deserializer
>
> > Hi,
> > I have a question about the use of DOM Element serializer/deserializer.
> > In the Address Book sample they use the following declaration to support
> > DOM:
> > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > I tried to use this in my own code. I have a method which returns a DOM
> > Element object, but the difference is that the method also accepts two
> > String parameters. Now, when I tried to run this code, I got a message
> > like the following "Caught SOAPException (SOAP-ENV:Client): I only know
> > how to serialize an 'org.w3c.dom.Element'."
> > How do I go about solving this problem? I mean how do I tell the SOAP to
> > use one encoding style for the parameters, and a different one for the
> > return value?
> > Thanks in advance,
> > Artem
> >
Re: DOM Element serializer/deserializer
Posted by George I Matkovits <ma...@uswest.net>.
When you complete this project, could we add it to the Soap Samples, please.
Thank you - George
Cory Isaacson wrote:
> I'm not 100% certain, but I think if you use the literal XML serialization,
> you need to send and receive a DOM as parameters and return values. I did
> this by building one DOM for parameters and getting another back. Obviously
> you can then embed whatever you need inside the DOM that you send and it
> works fine.
>
> Thanks,
>
> Cory
> ----- Original Message -----
> From: "Artem Portnoy" <ar...@ibi.com>
> To: <so...@xml.apache.org>
> Sent: Tuesday, September 12, 2000 10:34 AM
> Subject: DOM Element serializer/deserializer
>
> > Hi,
> > I have a question about the use of DOM Element serializer/deserializer.
> > In the Address Book sample they use the following declaration to support
> > DOM:
> > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > I tried to use this in my own code. I have a method which returns a DOM
> > Element object, but the difference is that the method also accepts two
> > String parameters. Now, when I tried to run this code, I got a message
> > like the following "Caught SOAPException (SOAP-ENV:Client): I only know
> > how to serialize an 'org.w3c.dom.Element'."
> > How do I go about solving this problem? I mean how do I tell the SOAP to
> > use one encoding style for the parameters, and a different one for the
> > return value?
> > Thanks in advance,
> > Artem
> >
Re: DOM Element serializer/deserializer
Posted by George I Matkovits <ma...@uswest.net>.
You have the code and you could always add to it. JSoap is open source. (Just
less sleep?)
Regards - George
Artem Portnoy wrote:
> That's true, but I don't want to pass DOM as parameters. I would like to pass
> primitive type params, and have the return value as DOM. Maybe it's a flaw in
> the Apache implementation, and this actually can't be done?
> Thanks,
> Artem
>
> Cory Isaacson wrote:
>
> > I'm not 100% certain, but I think if you use the literal XML serialization,
> > you need to send and receive a DOM as parameters and return values. I did
> > this by building one DOM for parameters and getting another back. Obviously
> > you can then embed whatever you need inside the DOM that you send and it
> > works fine.
> >
> > Thanks,
> >
> > Cory
> > ----- Original Message -----
> > From: "Artem Portnoy" <ar...@ibi.com>
> > To: <so...@xml.apache.org>
> > Sent: Tuesday, September 12, 2000 10:34 AM
> > Subject: DOM Element serializer/deserializer
> >
> > > Hi,
> > > I have a question about the use of DOM Element serializer/deserializer.
> > > In the Address Book sample they use the following declaration to support
> > > DOM:
> > > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > > I tried to use this in my own code. I have a method which returns a DOM
> > > Element object, but the difference is that the method also accepts two
> > > String parameters. Now, when I tried to run this code, I got a message
> > > like the following "Caught SOAPException (SOAP-ENV:Client): I only know
> > > how to serialize an 'org.w3c.dom.Element'."
> > > How do I go about solving this problem? I mean how do I tell the SOAP to
> > > use one encoding style for the parameters, and a different one for the
> > > return value?
> > > Thanks in advance,
> > > Artem
> > >
Re: DOM Element serializer/deserializer
Posted by Artem Portnoy <ar...@ibi.com>.
I guess you are right.
Artem
Cory Isaacson wrote:
> It could be as I don't see how you can specify one type of encoding for
> input and another for output. It would be interesting to review the SOAP 1.1
> spec and see if this is intended (I don't recall).
>
> Cory
> ----- Original Message -----
> From: "Artem Portnoy" <ar...@ibi.com>
> To: <so...@xml.apache.org>
> Sent: Tuesday, September 12, 2000 12:57 PM
> Subject: Re: DOM Element serializer/deserializer
>
> > That's true, but I don't want to pass DOM as parameters. I would like to
> pass
> > primitive type params, and have the return value as DOM. Maybe it's a flaw
> in
> > the Apache implementation, and this actually can't be done?
> > Thanks,
> > Artem
> >
> > Cory Isaacson wrote:
> >
> > > I'm not 100% certain, but I think if you use the literal XML
> serialization,
> > > you need to send and receive a DOM as parameters and return values. I
> did
> > > this by building one DOM for parameters and getting another back.
> Obviously
> > > you can then embed whatever you need inside the DOM that you send and it
> > > works fine.
> > >
> > > Thanks,
> > >
> > > Cory
> > > ----- Original Message -----
> > > From: "Artem Portnoy" <ar...@ibi.com>
> > > To: <so...@xml.apache.org>
> > > Sent: Tuesday, September 12, 2000 10:34 AM
> > > Subject: DOM Element serializer/deserializer
> > >
> > > > Hi,
> > > > I have a question about the use of DOM Element
> serializer/deserializer.
> > > > In the Address Book sample they use the following declaration to
> support
> > > > DOM:
> > > > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > > > I tried to use this in my own code. I have a method which returns a
> DOM
> > > > Element object, but the difference is that the method also accepts two
> > > > String parameters. Now, when I tried to run this code, I got a message
> > > > like the following "Caught SOAPException (SOAP-ENV:Client): I only
> know
> > > > how to serialize an 'org.w3c.dom.Element'."
> > > > How do I go about solving this problem? I mean how do I tell the SOAP
> to
> > > > use one encoding style for the parameters, and a different one for the
> > > > return value?
> > > > Thanks in advance,
> > > > Artem
> > > >
> >
Re: DOM Element serializer/deserializer
Posted by Artem Portnoy <ar...@ibi.com>.
I guess you are right.
Artem
Cory Isaacson wrote:
> It could be as I don't see how you can specify one type of encoding for
> input and another for output. It would be interesting to review the SOAP 1.1
> spec and see if this is intended (I don't recall).
>
> Cory
> ----- Original Message -----
> From: "Artem Portnoy" <ar...@ibi.com>
> To: <so...@xml.apache.org>
> Sent: Tuesday, September 12, 2000 12:57 PM
> Subject: Re: DOM Element serializer/deserializer
>
> > That's true, but I don't want to pass DOM as parameters. I would like to
> pass
> > primitive type params, and have the return value as DOM. Maybe it's a flaw
> in
> > the Apache implementation, and this actually can't be done?
> > Thanks,
> > Artem
> >
> > Cory Isaacson wrote:
> >
> > > I'm not 100% certain, but I think if you use the literal XML
> serialization,
> > > you need to send and receive a DOM as parameters and return values. I
> did
> > > this by building one DOM for parameters and getting another back.
> Obviously
> > > you can then embed whatever you need inside the DOM that you send and it
> > > works fine.
> > >
> > > Thanks,
> > >
> > > Cory
> > > ----- Original Message -----
> > > From: "Artem Portnoy" <ar...@ibi.com>
> > > To: <so...@xml.apache.org>
> > > Sent: Tuesday, September 12, 2000 10:34 AM
> > > Subject: DOM Element serializer/deserializer
> > >
> > > > Hi,
> > > > I have a question about the use of DOM Element
> serializer/deserializer.
> > > > In the Address Book sample they use the following declaration to
> support
> > > > DOM:
> > > > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > > > I tried to use this in my own code. I have a method which returns a
> DOM
> > > > Element object, but the difference is that the method also accepts two
> > > > String parameters. Now, when I tried to run this code, I got a message
> > > > like the following "Caught SOAPException (SOAP-ENV:Client): I only
> know
> > > > how to serialize an 'org.w3c.dom.Element'."
> > > > How do I go about solving this problem? I mean how do I tell the SOAP
> to
> > > > use one encoding style for the parameters, and a different one for the
> > > > return value?
> > > > Thanks in advance,
> > > > Artem
> > > >
> >
Re: GetAddress
Posted by Frederic POIROT <po...@yahoo.com>.
Hello !
I get the same problem. But if you look in the source code the "x:" is added
when formatting the xml document (look in DeploymentDescriptor.java).
When deploying, on the local part field simply put "phone" or "address" not
"x:phone" or "x:address".
Be sure after to have the correct classpath when running the client. Mine is
set
CLASSPATH=e:\xerces-1_2_0\xerces.jar;e:\soap-2_0;e:\soap-2_0\lib\soap.jar;c:
\jdk1.3\jre\lib\rt.jar;
Don't forget to put the xerces.jar first.
and enjoy !
Regards
Fred
----- Original Message -----
From: "Chanan Braunstein" <CB...@knovel.com>
To: <so...@xml.apache.org>
Sent: Tuesday, September 12, 2000 10:48
Subject: GetAddress
> Hello,
> I got GetAllListings to work, but when I try to run GetAddress I got
the
> following error:
> Caught SOAPException (SOAP-ENV:Client): No mapping found for
> 'urn:xml-soap-address-demo:x:address' using encoding style
> 'http://schemas.xmlsoap.org/soap/encoding/'.
>
> I looked in the SOAP admin and here is my listing from Type Mapping:
> [TypeMapping
>
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/,elementType=urn:xml-
>
soap-address-demo:x:address,javaType=samples.addressbook.Address,java2XMLCla
>
ssName=org.apache.soap.encoding.soapenc.BeanSerializer,xml2JavaClassName=org
> .apache.soap.encoding.soapenc.BeanSerializer]
> [TypeMapping
>
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/,elementType=urn:xml-
>
soap-address-demo:x:phone,javaType=samples.addressbook.PhoneNumber,java2XMLC
>
lassName=org.apache.soap.encoding.soapenc.BeanSerializer,xml2JavaClassName=o
> rg.apache.soap.encoding.soapenc.BeanSerializer]
>
> To me, the novice, it seems correct. What am I doing wrong?
> Thanks,
>
> Chanan Braunstein
> http://knovel.com
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Re: GetAddress
Posted by Frederic POIROT <po...@yahoo.com>.
Hello !
I get the same problem. But if you look in the source code the "x:" is added
when formatting the xml document (look in DeploymentDescriptor.java).
When deploying, on the local part field simply put "phone" or "address" not
"x:phone" or "x:address".
Be sure after to have the correct classpath when running the client. Mine is
set
CLASSPATH=e:\xerces-1_2_0\xerces.jar;e:\soap-2_0;e:\soap-2_0\lib\soap.jar;c:
\jdk1.3\jre\lib\rt.jar;
Don't forget to put the xerces.jar first.
and enjoy !
Regards
Fred
----- Original Message -----
From: "Chanan Braunstein" <CB...@knovel.com>
To: <so...@xml.apache.org>
Sent: Tuesday, September 12, 2000 10:48
Subject: GetAddress
> Hello,
> I got GetAllListings to work, but when I try to run GetAddress I got
the
> following error:
> Caught SOAPException (SOAP-ENV:Client): No mapping found for
> 'urn:xml-soap-address-demo:x:address' using encoding style
> 'http://schemas.xmlsoap.org/soap/encoding/'.
>
> I looked in the SOAP admin and here is my listing from Type Mapping:
> [TypeMapping
>
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/,elementType=urn:xml-
>
soap-address-demo:x:address,javaType=samples.addressbook.Address,java2XMLCla
>
ssName=org.apache.soap.encoding.soapenc.BeanSerializer,xml2JavaClassName=org
> .apache.soap.encoding.soapenc.BeanSerializer]
> [TypeMapping
>
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/,elementType=urn:xml-
>
soap-address-demo:x:phone,javaType=samples.addressbook.PhoneNumber,java2XMLC
>
lassName=org.apache.soap.encoding.soapenc.BeanSerializer,xml2JavaClassName=o
> rg.apache.soap.encoding.soapenc.BeanSerializer]
>
> To me, the novice, it seems correct. What am I doing wrong?
> Thanks,
>
> Chanan Braunstein
> http://knovel.com
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
GetAddress
Posted by Chanan Braunstein <CB...@knovel.com>.
Hello,
I got GetAllListings to work, but when I try to run GetAddress I got the
following error:
Caught SOAPException (SOAP-ENV:Client): No mapping found for
'urn:xml-soap-address-demo:x:address' using encoding style
'http://schemas.xmlsoap.org/soap/encoding/'.
I looked in the SOAP admin and here is my listing from Type Mapping:
[TypeMapping
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/,elementType=urn:xml-
soap-address-demo:x:address,javaType=samples.addressbook.Address,java2XMLCla
ssName=org.apache.soap.encoding.soapenc.BeanSerializer,xml2JavaClassName=org
.apache.soap.encoding.soapenc.BeanSerializer]
[TypeMapping
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/,elementType=urn:xml-
soap-address-demo:x:phone,javaType=samples.addressbook.PhoneNumber,java2XMLC
lassName=org.apache.soap.encoding.soapenc.BeanSerializer,xml2JavaClassName=o
rg.apache.soap.encoding.soapenc.BeanSerializer]
To me, the novice, it seems correct. What am I doing wrong?
Thanks,
Chanan Braunstein
http://knovel.com
GetAddress
Posted by Chanan Braunstein <CB...@knovel.com>.
Hello,
I got GetAllListings to work, but when I try to run GetAddress I got the
following error:
Caught SOAPException (SOAP-ENV:Client): No mapping found for
'urn:xml-soap-address-demo:x:address' using encoding style
'http://schemas.xmlsoap.org/soap/encoding/'.
I looked in the SOAP admin and here is my listing from Type Mapping:
[TypeMapping
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/,elementType=urn:xml-
soap-address-demo:x:address,javaType=samples.addressbook.Address,java2XMLCla
ssName=org.apache.soap.encoding.soapenc.BeanSerializer,xml2JavaClassName=org
.apache.soap.encoding.soapenc.BeanSerializer]
[TypeMapping
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/,elementType=urn:xml-
soap-address-demo:x:phone,javaType=samples.addressbook.PhoneNumber,java2XMLC
lassName=org.apache.soap.encoding.soapenc.BeanSerializer,xml2JavaClassName=o
rg.apache.soap.encoding.soapenc.BeanSerializer]
To me, the novice, it seems correct. What am I doing wrong?
Thanks,
Chanan Braunstein
http://knovel.com
Re: DOM Element serializer/deserializer
Posted by Cory Isaacson <ci...@capita2.com>.
It could be as I don't see how you can specify one type of encoding for
input and another for output. It would be interesting to review the SOAP 1.1
spec and see if this is intended (I don't recall).
Cory
----- Original Message -----
From: "Artem Portnoy" <ar...@ibi.com>
To: <so...@xml.apache.org>
Sent: Tuesday, September 12, 2000 12:57 PM
Subject: Re: DOM Element serializer/deserializer
> That's true, but I don't want to pass DOM as parameters. I would like to
pass
> primitive type params, and have the return value as DOM. Maybe it's a flaw
in
> the Apache implementation, and this actually can't be done?
> Thanks,
> Artem
>
> Cory Isaacson wrote:
>
> > I'm not 100% certain, but I think if you use the literal XML
serialization,
> > you need to send and receive a DOM as parameters and return values. I
did
> > this by building one DOM for parameters and getting another back.
Obviously
> > you can then embed whatever you need inside the DOM that you send and it
> > works fine.
> >
> > Thanks,
> >
> > Cory
> > ----- Original Message -----
> > From: "Artem Portnoy" <ar...@ibi.com>
> > To: <so...@xml.apache.org>
> > Sent: Tuesday, September 12, 2000 10:34 AM
> > Subject: DOM Element serializer/deserializer
> >
> > > Hi,
> > > I have a question about the use of DOM Element
serializer/deserializer.
> > > In the Address Book sample they use the following declaration to
support
> > > DOM:
> > > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > > I tried to use this in my own code. I have a method which returns a
DOM
> > > Element object, but the difference is that the method also accepts two
> > > String parameters. Now, when I tried to run this code, I got a message
> > > like the following "Caught SOAPException (SOAP-ENV:Client): I only
know
> > > how to serialize an 'org.w3c.dom.Element'."
> > > How do I go about solving this problem? I mean how do I tell the SOAP
to
> > > use one encoding style for the parameters, and a different one for the
> > > return value?
> > > Thanks in advance,
> > > Artem
> > >
>
Re: DOM Element serializer/deserializer
Posted by Cory Isaacson <ci...@capita2.com>.
It could be as I don't see how you can specify one type of encoding for
input and another for output. It would be interesting to review the SOAP 1.1
spec and see if this is intended (I don't recall).
Cory
----- Original Message -----
From: "Artem Portnoy" <ar...@ibi.com>
To: <so...@xml.apache.org>
Sent: Tuesday, September 12, 2000 12:57 PM
Subject: Re: DOM Element serializer/deserializer
> That's true, but I don't want to pass DOM as parameters. I would like to
pass
> primitive type params, and have the return value as DOM. Maybe it's a flaw
in
> the Apache implementation, and this actually can't be done?
> Thanks,
> Artem
>
> Cory Isaacson wrote:
>
> > I'm not 100% certain, but I think if you use the literal XML
serialization,
> > you need to send and receive a DOM as parameters and return values. I
did
> > this by building one DOM for parameters and getting another back.
Obviously
> > you can then embed whatever you need inside the DOM that you send and it
> > works fine.
> >
> > Thanks,
> >
> > Cory
> > ----- Original Message -----
> > From: "Artem Portnoy" <ar...@ibi.com>
> > To: <so...@xml.apache.org>
> > Sent: Tuesday, September 12, 2000 10:34 AM
> > Subject: DOM Element serializer/deserializer
> >
> > > Hi,
> > > I have a question about the use of DOM Element
serializer/deserializer.
> > > In the Address Book sample they use the following declaration to
support
> > > DOM:
> > > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > > I tried to use this in my own code. I have a method which returns a
DOM
> > > Element object, but the difference is that the method also accepts two
> > > String parameters. Now, when I tried to run this code, I got a message
> > > like the following "Caught SOAPException (SOAP-ENV:Client): I only
know
> > > how to serialize an 'org.w3c.dom.Element'."
> > > How do I go about solving this problem? I mean how do I tell the SOAP
to
> > > use one encoding style for the parameters, and a different one for the
> > > return value?
> > > Thanks in advance,
> > > Artem
> > >
>
Re: DOM Element serializer/deserializer
Posted by George I Matkovits <ma...@uswest.net>.
You have the code and you could always add to it. JSoap is open source. (Just
less sleep?)
Regards - George
Artem Portnoy wrote:
> That's true, but I don't want to pass DOM as parameters. I would like to pass
> primitive type params, and have the return value as DOM. Maybe it's a flaw in
> the Apache implementation, and this actually can't be done?
> Thanks,
> Artem
>
> Cory Isaacson wrote:
>
> > I'm not 100% certain, but I think if you use the literal XML serialization,
> > you need to send and receive a DOM as parameters and return values. I did
> > this by building one DOM for parameters and getting another back. Obviously
> > you can then embed whatever you need inside the DOM that you send and it
> > works fine.
> >
> > Thanks,
> >
> > Cory
> > ----- Original Message -----
> > From: "Artem Portnoy" <ar...@ibi.com>
> > To: <so...@xml.apache.org>
> > Sent: Tuesday, September 12, 2000 10:34 AM
> > Subject: DOM Element serializer/deserializer
> >
> > > Hi,
> > > I have a question about the use of DOM Element serializer/deserializer.
> > > In the Address Book sample they use the following declaration to support
> > > DOM:
> > > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > > I tried to use this in my own code. I have a method which returns a DOM
> > > Element object, but the difference is that the method also accepts two
> > > String parameters. Now, when I tried to run this code, I got a message
> > > like the following "Caught SOAPException (SOAP-ENV:Client): I only know
> > > how to serialize an 'org.w3c.dom.Element'."
> > > How do I go about solving this problem? I mean how do I tell the SOAP to
> > > use one encoding style for the parameters, and a different one for the
> > > return value?
> > > Thanks in advance,
> > > Artem
> > >
Re: DOM Element serializer/deserializer
Posted by Artem Portnoy <ar...@ibi.com>.
That's true, but I don't want to pass DOM as parameters. I would like to pass
primitive type params, and have the return value as DOM. Maybe it's a flaw in
the Apache implementation, and this actually can't be done?
Thanks,
Artem
Cory Isaacson wrote:
> I'm not 100% certain, but I think if you use the literal XML serialization,
> you need to send and receive a DOM as parameters and return values. I did
> this by building one DOM for parameters and getting another back. Obviously
> you can then embed whatever you need inside the DOM that you send and it
> works fine.
>
> Thanks,
>
> Cory
> ----- Original Message -----
> From: "Artem Portnoy" <ar...@ibi.com>
> To: <so...@xml.apache.org>
> Sent: Tuesday, September 12, 2000 10:34 AM
> Subject: DOM Element serializer/deserializer
>
> > Hi,
> > I have a question about the use of DOM Element serializer/deserializer.
> > In the Address Book sample they use the following declaration to support
> > DOM:
> > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > I tried to use this in my own code. I have a method which returns a DOM
> > Element object, but the difference is that the method also accepts two
> > String parameters. Now, when I tried to run this code, I got a message
> > like the following "Caught SOAPException (SOAP-ENV:Client): I only know
> > how to serialize an 'org.w3c.dom.Element'."
> > How do I go about solving this problem? I mean how do I tell the SOAP to
> > use one encoding style for the parameters, and a different one for the
> > return value?
> > Thanks in advance,
> > Artem
> >
Re: DOM Element serializer/deserializer
Posted by Artem Portnoy <ar...@ibi.com>.
That's true, but I don't want to pass DOM as parameters. I would like to pass
primitive type params, and have the return value as DOM. Maybe it's a flaw in
the Apache implementation, and this actually can't be done?
Thanks,
Artem
Cory Isaacson wrote:
> I'm not 100% certain, but I think if you use the literal XML serialization,
> you need to send and receive a DOM as parameters and return values. I did
> this by building one DOM for parameters and getting another back. Obviously
> you can then embed whatever you need inside the DOM that you send and it
> works fine.
>
> Thanks,
>
> Cory
> ----- Original Message -----
> From: "Artem Portnoy" <ar...@ibi.com>
> To: <so...@xml.apache.org>
> Sent: Tuesday, September 12, 2000 10:34 AM
> Subject: DOM Element serializer/deserializer
>
> > Hi,
> > I have a question about the use of DOM Element serializer/deserializer.
> > In the Address Book sample they use the following declaration to support
> > DOM:
> > call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> > I tried to use this in my own code. I have a method which returns a DOM
> > Element object, but the difference is that the method also accepts two
> > String parameters. Now, when I tried to run this code, I got a message
> > like the following "Caught SOAPException (SOAP-ENV:Client): I only know
> > how to serialize an 'org.w3c.dom.Element'."
> > How do I go about solving this problem? I mean how do I tell the SOAP to
> > use one encoding style for the parameters, and a different one for the
> > return value?
> > Thanks in advance,
> > Artem
> >
Re: DOM Element serializer/deserializer
Posted by Cory Isaacson <ci...@capita2.com>.
I'm not 100% certain, but I think if you use the literal XML serialization,
you need to send and receive a DOM as parameters and return values. I did
this by building one DOM for parameters and getting another back. Obviously
you can then embed whatever you need inside the DOM that you send and it
works fine.
Thanks,
Cory
----- Original Message -----
From: "Artem Portnoy" <ar...@ibi.com>
To: <so...@xml.apache.org>
Sent: Tuesday, September 12, 2000 10:34 AM
Subject: DOM Element serializer/deserializer
> Hi,
> I have a question about the use of DOM Element serializer/deserializer.
> In the Address Book sample they use the following declaration to support
> DOM:
> call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> I tried to use this in my own code. I have a method which returns a DOM
> Element object, but the difference is that the method also accepts two
> String parameters. Now, when I tried to run this code, I got a message
> like the following "Caught SOAPException (SOAP-ENV:Client): I only know
> how to serialize an 'org.w3c.dom.Element'."
> How do I go about solving this problem? I mean how do I tell the SOAP to
> use one encoding style for the parameters, and a different one for the
> return value?
> Thanks in advance,
> Artem
>
Re: DOM Element serializer/deserializer
Posted by Cory Isaacson <ci...@capita2.com>.
I'm not 100% certain, but I think if you use the literal XML serialization,
you need to send and receive a DOM as parameters and return values. I did
this by building one DOM for parameters and getting another back. Obviously
you can then embed whatever you need inside the DOM that you send and it
works fine.
Thanks,
Cory
----- Original Message -----
From: "Artem Portnoy" <ar...@ibi.com>
To: <so...@xml.apache.org>
Sent: Tuesday, September 12, 2000 10:34 AM
Subject: DOM Element serializer/deserializer
> Hi,
> I have a question about the use of DOM Element serializer/deserializer.
> In the Address Book sample they use the following declaration to support
> DOM:
> call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
> I tried to use this in my own code. I have a method which returns a DOM
> Element object, but the difference is that the method also accepts two
> String parameters. Now, when I tried to run this code, I got a message
> like the following "Caught SOAPException (SOAP-ENV:Client): I only know
> how to serialize an 'org.w3c.dom.Element'."
> How do I go about solving this problem? I mean how do I tell the SOAP to
> use one encoding style for the parameters, and a different one for the
> return value?
> Thanks in advance,
> Artem
>