You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by Kiran Devaram <sc...@rediffmail.com> on 2003/04/09 17:52:03 UTC
Capture the Client's request
Dear All,
I want to capture the SOAP Client's request(XML
payload) in the form of a string using SOAP libraries. After
looking at the SOAPAPI and in that, the class CALL and the method
invoke(..), I did not find any method using which I can capture
the request from the client. So, I would like to modify the SOAP
source code and see if its possible to add a method to capture the
request from client.
Please let me know if its possible. Also, I would appreciate
it if you can send me the link where I can download the SOAP
source code from.
Thanks,
Kiran
_______________________________________________________________________
Odomos - the only mosquito protection outside 4 walls -
Click here to know more!
http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&wn
RE: Capture the Client's request
Posted by Akhil Jain <ak...@baypackets.com>.
Hi,
Can you give me a sample code for how I can do the
serialization/deserialization. Also tell me where to put this interceptor in
the SOAP call.
Thanks
Akhil
-----Original Message-----
From: Scott Nichol [mailto:snicholnews@scottnichol.com]
Sent: Thursday, April 10, 2003 9:29 AM
To: soap-dev@ws.apache.org
Subject: RE: Capture the Client's request
The SOAP payload is encoded using UTF-8. Therefore, Unicode
characters in your Java strings should be translated to UTF-8 during
serialization, and then deserialization would do the reverse. Have
you tried using a tool to capture the message being transmitted over
the wire so that you can see the actual sequence of bytes?
On 10 Apr 2003 at 9:16, Akhil Jain wrote:
> Hi,
>
> Does SOAP implementation support internationalization?? I was trying to
send
> a Korean string in an XML Element. But I found that the SOAP server gave a
> DOM parsing error. It was not able to read the entire SOAP envelope. Can
you
> please help me on how to send a unicode string (containing Japanese or
> Korean characters) in a SOAP call?
>
> Thanks
> Akhil
>
> -----Original Message-----
> From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> Sent: Thursday, April 10, 2003 1:40 AM
> To: soap-dev@ws.apache.org
> Subject: Re: Capture the Client's request
>
>
> The current Apache SOAP code has this capability. You explicitly
> create an instance of SOAPHTTPConnection and call the setRequestCopy
> method to register a StringBuffer that will receive a copy of the
> request. You call the setSOAPTransport method on your Call instance
> to tell it to use the connection you have created. After calling
> invoke, a copy of the request will be in your StringBuffer.
>
> You can get a nightly build at
> http://cvs.apache.org/dist/soap/nightly/.
>
> On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
>
> > Dear All,
> >
> > I want to capture the SOAP Client's request(XML
> > payload) in the form of a string using SOAP libraries. After
> > looking at the SOAPAPI and in that, the class CALL and the method
> > invoke(..), I did not find any method using which I can capture
> > the request from the client. So, I would like to modify the SOAP
> > source code and see if its possible to add a method to capture the
> > request from client.
> >
> > Please let me know if its possible. Also, I would appreciate
> > it if you can send me the link where I can download the SOAP
> > source code from.
> >
> > Thanks,
> > Kiran
> > _______________________________________________________________________
> > Odomos - the only mosquito protection outside 4 walls -
> > Click here to know more!
> >
>
http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&w
> n
> >
> >
>
>
> Scott Nichol
>
> Do not reply directly to this e-mail address,
> as it is filtered to only receive e-mail from
> specific mailing lists.
>
>
>
>
>
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
RE: Capture the Client's request
Posted by Scott Nichol <sn...@scottnichol.com>.
Just to be sure I understand...
Is the server Apache SOAP as well as the client? What version of
Apache SOAP are you using? What is the exact error message(s) you
are seeing?
On 11 Apr 2003 at 8:41, Akhil Jain wrote:
> Scott,
>
> Can you help me on how can I serialize or deserialize my unicode data. I
> think the main problem is that the SOAP client is sending the packet in
> UTF-8 format whereas the content-length passed in the HTTP header is taken
> as the length of the java sring which is less as java string support 16 bit
> unicode character. How can I overcome this problem now.
>
> Akhil
>
>
> -----Original Message-----
> From: Manoj Mangla [mailto:manoj@in.fiorano.com]
> Sent: Thursday, April 10, 2003 10:23 AM
> To: soap-dev@ws.apache.org
> Subject: Re: Capture the Client's request
>
>
> Not sure about this. You might have see the documentation of the library you
> are using for creating SOAP message. Do some google :)
>
>
> ----- Original Message -----
> From: "Akhil Jain" <ak...@baypackets.com>
> To: <so...@ws.apache.org>
> Sent: Thursday, April 10, 2003 9:58 AM
> Subject: RE: Capture the Client's request
>
>
> > Can you tell me how can put this string in the SOAP header, Does SOAP
> > implementation provides APIs for doing this thing.
> >
> > Thanks
> > Akhil
> >
> > -----Original Message-----
> > From: Manoj Mangla [mailto:manoj@in.fiorano.com]
> > Sent: Thursday, April 10, 2003 9:57 AM
> > To: soap-dev@ws.apache.org
> > Subject: Re: Capture the Client's request
> >
> >
> > Akhil
> >
> > am not very sure but I guess writing "<?xml version="1.0"
> > encoding="UTF-8"?>" in the soap packet header might help. Encoding can be
> > deinfed by us as per your requirement.
> >
> > Hope it helps
> > Manoj
> >
> >
> > ----- Original Message -----
> > From: "Akhil Jain" <ak...@baypackets.com>
> > To: <so...@ws.apache.org>
> > Sent: Thursday, April 10, 2003 9:44 AM
> > Subject: RE: Capture the Client's request
> >
> >
> > > Hi,
> > > Thanks for your prompt reply.
> > > I could see the unicode characters being converted into UTF-8 during
> > > transfer. I was able to see some character in /337/338 etc form. My
> > question
> > > is that if I create an XML element and I put a Korean string in none of
> > the
> > > child text node. I think the Content-Length that is being sent in the
> > HTTP
> > > Header is the length of the string that contains the entire SOAP
> envelope
> > > whereas the actual data that is sent on the wire contains the unicode
> > > characters that are converted into UTF-8, hence increasing the Actual
> > packet
> > > length. I think this is the reason why the SOAP server is not able to
> > read
> > > the entire SOAP Evvelope, and so gives the DOM parsing error. Is there a
> > way
> > > I can tell SOAP implementation that I am sending the Strings in Unicode
> > > (Java String) and that it needs to convert the string into UTF-8 string
> > and
> > > send the correct Content-Length in the HTTP Header.
> > >
> > > Thanks
> > > Akhil
> > >
> > >
> > > -----Original Message-----
> > > From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> > > Sent: Thursday, April 10, 2003 9:29 AM
> > > To: soap-dev@ws.apache.org
> > > Subject: RE: Capture the Client's request
> > >
> > >
> > > The SOAP payload is encoded using UTF-8. Therefore, Unicode
> > > characters in your Java strings should be translated to UTF-8 during
> > > serialization, and then deserialization would do the reverse. Have
> > > you tried using a tool to capture the message being transmitted over
> > > the wire so that you can see the actual sequence of bytes?
> > >
> > > On 10 Apr 2003 at 9:16, Akhil Jain wrote:
> > >
> > > > Hi,
> > > >
> > > > Does SOAP implementation support internationalization?? I was trying
> to
> > > send
> > > > a Korean string in an XML Element. But I found that the SOAP server
> gave
> > a
> > > > DOM parsing error. It was not able to read the entire SOAP envelope.
> Can
> > > you
> > > > please help me on how to send a unicode string (containing Japanese or
> > > > Korean characters) in a SOAP call?
> > > >
> > > > Thanks
> > > > Akhil
> > > >
> > > > -----Original Message-----
> > > > From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> > > > Sent: Thursday, April 10, 2003 1:40 AM
> > > > To: soap-dev@ws.apache.org
> > > > Subject: Re: Capture the Client's request
> > > >
> > > >
> > > > The current Apache SOAP code has this capability. You explicitly
> > > > create an instance of SOAPHTTPConnection and call the setRequestCopy
> > > > method to register a StringBuffer that will receive a copy of the
> > > > request. You call the setSOAPTransport method on your Call instance
> > > > to tell it to use the connection you have created. After calling
> > > > invoke, a copy of the request will be in your StringBuffer.
> > > >
> > > > You can get a nightly build at
> > > > http://cvs.apache.org/dist/soap/nightly/.
> > > >
> > > > On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
> > > >
> > > > > Dear All,
> > > > >
> > > > > I want to capture the SOAP Client's request(XML
> > > > > payload) in the form of a string using SOAP libraries. After
> > > > > looking at the SOAPAPI and in that, the class CALL and the method
> > > > > invoke(..), I did not find any method using which I can capture
> > > > > the request from the client. So, I would like to modify the SOAP
> > > > > source code and see if its possible to add a method to capture the
> > > > > request from client.
> > > > >
> > > > > Please let me know if its possible. Also, I would appreciate
> > > > > it if you can send me the link where I can download the SOAP
> > > > > source code from.
> > > > >
> > > > > Thanks,
> > > > > Kiran
> > > > >
> > _______________________________________________________________________
> > > > > Odomos - the only mosquito protection outside 4 walls -
> > > > > Click here to know more!
> > > > >
> > > >
> > >
> >
> http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&w
> > > > n
> > > > >
> > > > >
> > > >
> > > >
> > > > Scott Nichol
> > > >
> > > > Do not reply directly to this e-mail address,
> > > > as it is filtered to only receive e-mail from
> > > > specific mailing lists.
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > Scott Nichol
> > >
> > > Do not reply directly to this e-mail address,
> > > as it is filtered to only receive e-mail from
> > > specific mailing lists.
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
RE: Capture the Client's request
Posted by Akhil Jain <ak...@baypackets.com>.
Scott,
Can you help me on how can I serialize or deserialize my unicode data. I
think the main problem is that the SOAP client is sending the packet in
UTF-8 format whereas the content-length passed in the HTTP header is taken
as the length of the java sring which is less as java string support 16 bit
unicode character. How can I overcome this problem now.
Akhil
-----Original Message-----
From: Manoj Mangla [mailto:manoj@in.fiorano.com]
Sent: Thursday, April 10, 2003 10:23 AM
To: soap-dev@ws.apache.org
Subject: Re: Capture the Client's request
Not sure about this. You might have see the documentation of the library you
are using for creating SOAP message. Do some google :)
----- Original Message -----
From: "Akhil Jain" <ak...@baypackets.com>
To: <so...@ws.apache.org>
Sent: Thursday, April 10, 2003 9:58 AM
Subject: RE: Capture the Client's request
> Can you tell me how can put this string in the SOAP header, Does SOAP
> implementation provides APIs for doing this thing.
>
> Thanks
> Akhil
>
> -----Original Message-----
> From: Manoj Mangla [mailto:manoj@in.fiorano.com]
> Sent: Thursday, April 10, 2003 9:57 AM
> To: soap-dev@ws.apache.org
> Subject: Re: Capture the Client's request
>
>
> Akhil
>
> am not very sure but I guess writing "<?xml version="1.0"
> encoding="UTF-8"?>" in the soap packet header might help. Encoding can be
> deinfed by us as per your requirement.
>
> Hope it helps
> Manoj
>
>
> ----- Original Message -----
> From: "Akhil Jain" <ak...@baypackets.com>
> To: <so...@ws.apache.org>
> Sent: Thursday, April 10, 2003 9:44 AM
> Subject: RE: Capture the Client's request
>
>
> > Hi,
> > Thanks for your prompt reply.
> > I could see the unicode characters being converted into UTF-8 during
> > transfer. I was able to see some character in /337/338 etc form. My
> question
> > is that if I create an XML element and I put a Korean string in none of
> the
> > child text node. I think the Content-Length that is being sent in the
> HTTP
> > Header is the length of the string that contains the entire SOAP
envelope
> > whereas the actual data that is sent on the wire contains the unicode
> > characters that are converted into UTF-8, hence increasing the Actual
> packet
> > length. I think this is the reason why the SOAP server is not able to
> read
> > the entire SOAP Evvelope, and so gives the DOM parsing error. Is there a
> way
> > I can tell SOAP implementation that I am sending the Strings in Unicode
> > (Java String) and that it needs to convert the string into UTF-8 string
> and
> > send the correct Content-Length in the HTTP Header.
> >
> > Thanks
> > Akhil
> >
> >
> > -----Original Message-----
> > From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> > Sent: Thursday, April 10, 2003 9:29 AM
> > To: soap-dev@ws.apache.org
> > Subject: RE: Capture the Client's request
> >
> >
> > The SOAP payload is encoded using UTF-8. Therefore, Unicode
> > characters in your Java strings should be translated to UTF-8 during
> > serialization, and then deserialization would do the reverse. Have
> > you tried using a tool to capture the message being transmitted over
> > the wire so that you can see the actual sequence of bytes?
> >
> > On 10 Apr 2003 at 9:16, Akhil Jain wrote:
> >
> > > Hi,
> > >
> > > Does SOAP implementation support internationalization?? I was trying
to
> > send
> > > a Korean string in an XML Element. But I found that the SOAP server
gave
> a
> > > DOM parsing error. It was not able to read the entire SOAP envelope.
Can
> > you
> > > please help me on how to send a unicode string (containing Japanese or
> > > Korean characters) in a SOAP call?
> > >
> > > Thanks
> > > Akhil
> > >
> > > -----Original Message-----
> > > From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> > > Sent: Thursday, April 10, 2003 1:40 AM
> > > To: soap-dev@ws.apache.org
> > > Subject: Re: Capture the Client's request
> > >
> > >
> > > The current Apache SOAP code has this capability. You explicitly
> > > create an instance of SOAPHTTPConnection and call the setRequestCopy
> > > method to register a StringBuffer that will receive a copy of the
> > > request. You call the setSOAPTransport method on your Call instance
> > > to tell it to use the connection you have created. After calling
> > > invoke, a copy of the request will be in your StringBuffer.
> > >
> > > You can get a nightly build at
> > > http://cvs.apache.org/dist/soap/nightly/.
> > >
> > > On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
> > >
> > > > Dear All,
> > > >
> > > > I want to capture the SOAP Client's request(XML
> > > > payload) in the form of a string using SOAP libraries. After
> > > > looking at the SOAPAPI and in that, the class CALL and the method
> > > > invoke(..), I did not find any method using which I can capture
> > > > the request from the client. So, I would like to modify the SOAP
> > > > source code and see if its possible to add a method to capture the
> > > > request from client.
> > > >
> > > > Please let me know if its possible. Also, I would appreciate
> > > > it if you can send me the link where I can download the SOAP
> > > > source code from.
> > > >
> > > > Thanks,
> > > > Kiran
> > > >
> _______________________________________________________________________
> > > > Odomos - the only mosquito protection outside 4 walls -
> > > > Click here to know more!
> > > >
> > >
> >
>
http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&w
> > > n
> > > >
> > > >
> > >
> > >
> > > Scott Nichol
> > >
> > > Do not reply directly to this e-mail address,
> > > as it is filtered to only receive e-mail from
> > > specific mailing lists.
> > >
> > >
> > >
> > >
> > >
> >
> >
> > Scott Nichol
> >
> > Do not reply directly to this e-mail address,
> > as it is filtered to only receive e-mail from
> > specific mailing lists.
> >
> >
> >
> >
> >
>
>
>
>
>
Re: Capture the Client's request
Posted by Manoj Mangla <ma...@in.fiorano.com>.
Not sure about this. You might have see the documentation of the library you
are using for creating SOAP message. Do some google :)
----- Original Message -----
From: "Akhil Jain" <ak...@baypackets.com>
To: <so...@ws.apache.org>
Sent: Thursday, April 10, 2003 9:58 AM
Subject: RE: Capture the Client's request
> Can you tell me how can put this string in the SOAP header, Does SOAP
> implementation provides APIs for doing this thing.
>
> Thanks
> Akhil
>
> -----Original Message-----
> From: Manoj Mangla [mailto:manoj@in.fiorano.com]
> Sent: Thursday, April 10, 2003 9:57 AM
> To: soap-dev@ws.apache.org
> Subject: Re: Capture the Client's request
>
>
> Akhil
>
> am not very sure but I guess writing "<?xml version="1.0"
> encoding="UTF-8"?>" in the soap packet header might help. Encoding can be
> deinfed by us as per your requirement.
>
> Hope it helps
> Manoj
>
>
> ----- Original Message -----
> From: "Akhil Jain" <ak...@baypackets.com>
> To: <so...@ws.apache.org>
> Sent: Thursday, April 10, 2003 9:44 AM
> Subject: RE: Capture the Client's request
>
>
> > Hi,
> > Thanks for your prompt reply.
> > I could see the unicode characters being converted into UTF-8 during
> > transfer. I was able to see some character in /337/338 etc form. My
> question
> > is that if I create an XML element and I put a Korean string in none of
> the
> > child text node. I think the Content-Length that is being sent in the
> HTTP
> > Header is the length of the string that contains the entire SOAP
envelope
> > whereas the actual data that is sent on the wire contains the unicode
> > characters that are converted into UTF-8, hence increasing the Actual
> packet
> > length. I think this is the reason why the SOAP server is not able to
> read
> > the entire SOAP Evvelope, and so gives the DOM parsing error. Is there a
> way
> > I can tell SOAP implementation that I am sending the Strings in Unicode
> > (Java String) and that it needs to convert the string into UTF-8 string
> and
> > send the correct Content-Length in the HTTP Header.
> >
> > Thanks
> > Akhil
> >
> >
> > -----Original Message-----
> > From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> > Sent: Thursday, April 10, 2003 9:29 AM
> > To: soap-dev@ws.apache.org
> > Subject: RE: Capture the Client's request
> >
> >
> > The SOAP payload is encoded using UTF-8. Therefore, Unicode
> > characters in your Java strings should be translated to UTF-8 during
> > serialization, and then deserialization would do the reverse. Have
> > you tried using a tool to capture the message being transmitted over
> > the wire so that you can see the actual sequence of bytes?
> >
> > On 10 Apr 2003 at 9:16, Akhil Jain wrote:
> >
> > > Hi,
> > >
> > > Does SOAP implementation support internationalization?? I was trying
to
> > send
> > > a Korean string in an XML Element. But I found that the SOAP server
gave
> a
> > > DOM parsing error. It was not able to read the entire SOAP envelope.
Can
> > you
> > > please help me on how to send a unicode string (containing Japanese or
> > > Korean characters) in a SOAP call?
> > >
> > > Thanks
> > > Akhil
> > >
> > > -----Original Message-----
> > > From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> > > Sent: Thursday, April 10, 2003 1:40 AM
> > > To: soap-dev@ws.apache.org
> > > Subject: Re: Capture the Client's request
> > >
> > >
> > > The current Apache SOAP code has this capability. You explicitly
> > > create an instance of SOAPHTTPConnection and call the setRequestCopy
> > > method to register a StringBuffer that will receive a copy of the
> > > request. You call the setSOAPTransport method on your Call instance
> > > to tell it to use the connection you have created. After calling
> > > invoke, a copy of the request will be in your StringBuffer.
> > >
> > > You can get a nightly build at
> > > http://cvs.apache.org/dist/soap/nightly/.
> > >
> > > On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
> > >
> > > > Dear All,
> > > >
> > > > I want to capture the SOAP Client's request(XML
> > > > payload) in the form of a string using SOAP libraries. After
> > > > looking at the SOAPAPI and in that, the class CALL and the method
> > > > invoke(..), I did not find any method using which I can capture
> > > > the request from the client. So, I would like to modify the SOAP
> > > > source code and see if its possible to add a method to capture the
> > > > request from client.
> > > >
> > > > Please let me know if its possible. Also, I would appreciate
> > > > it if you can send me the link where I can download the SOAP
> > > > source code from.
> > > >
> > > > Thanks,
> > > > Kiran
> > > >
> _______________________________________________________________________
> > > > Odomos - the only mosquito protection outside 4 walls -
> > > > Click here to know more!
> > > >
> > >
> >
>
http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&w
> > > n
> > > >
> > > >
> > >
> > >
> > > Scott Nichol
> > >
> > > Do not reply directly to this e-mail address,
> > > as it is filtered to only receive e-mail from
> > > specific mailing lists.
> > >
> > >
> > >
> > >
> > >
> >
> >
> > Scott Nichol
> >
> > Do not reply directly to this e-mail address,
> > as it is filtered to only receive e-mail from
> > specific mailing lists.
> >
> >
> >
> >
> >
>
>
>
>
>
RE: Capture the Client's request
Posted by Akhil Jain <ak...@baypackets.com>.
Can you tell me how can put this string in the SOAP header, Does SOAP
implementation provides APIs for doing this thing.
Thanks
Akhil
-----Original Message-----
From: Manoj Mangla [mailto:manoj@in.fiorano.com]
Sent: Thursday, April 10, 2003 9:57 AM
To: soap-dev@ws.apache.org
Subject: Re: Capture the Client's request
Akhil
am not very sure but I guess writing "<?xml version="1.0"
encoding="UTF-8"?>" in the soap packet header might help. Encoding can be
deinfed by us as per your requirement.
Hope it helps
Manoj
----- Original Message -----
From: "Akhil Jain" <ak...@baypackets.com>
To: <so...@ws.apache.org>
Sent: Thursday, April 10, 2003 9:44 AM
Subject: RE: Capture the Client's request
> Hi,
> Thanks for your prompt reply.
> I could see the unicode characters being converted into UTF-8 during
> transfer. I was able to see some character in /337/338 etc form. My
question
> is that if I create an XML element and I put a Korean string in none of
the
> child text node. I think the Content-Length that is being sent in the
HTTP
> Header is the length of the string that contains the entire SOAP envelope
> whereas the actual data that is sent on the wire contains the unicode
> characters that are converted into UTF-8, hence increasing the Actual
packet
> length. I think this is the reason why the SOAP server is not able to
read
> the entire SOAP Evvelope, and so gives the DOM parsing error. Is there a
way
> I can tell SOAP implementation that I am sending the Strings in Unicode
> (Java String) and that it needs to convert the string into UTF-8 string
and
> send the correct Content-Length in the HTTP Header.
>
> Thanks
> Akhil
>
>
> -----Original Message-----
> From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> Sent: Thursday, April 10, 2003 9:29 AM
> To: soap-dev@ws.apache.org
> Subject: RE: Capture the Client's request
>
>
> The SOAP payload is encoded using UTF-8. Therefore, Unicode
> characters in your Java strings should be translated to UTF-8 during
> serialization, and then deserialization would do the reverse. Have
> you tried using a tool to capture the message being transmitted over
> the wire so that you can see the actual sequence of bytes?
>
> On 10 Apr 2003 at 9:16, Akhil Jain wrote:
>
> > Hi,
> >
> > Does SOAP implementation support internationalization?? I was trying to
> send
> > a Korean string in an XML Element. But I found that the SOAP server gave
a
> > DOM parsing error. It was not able to read the entire SOAP envelope. Can
> you
> > please help me on how to send a unicode string (containing Japanese or
> > Korean characters) in a SOAP call?
> >
> > Thanks
> > Akhil
> >
> > -----Original Message-----
> > From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> > Sent: Thursday, April 10, 2003 1:40 AM
> > To: soap-dev@ws.apache.org
> > Subject: Re: Capture the Client's request
> >
> >
> > The current Apache SOAP code has this capability. You explicitly
> > create an instance of SOAPHTTPConnection and call the setRequestCopy
> > method to register a StringBuffer that will receive a copy of the
> > request. You call the setSOAPTransport method on your Call instance
> > to tell it to use the connection you have created. After calling
> > invoke, a copy of the request will be in your StringBuffer.
> >
> > You can get a nightly build at
> > http://cvs.apache.org/dist/soap/nightly/.
> >
> > On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
> >
> > > Dear All,
> > >
> > > I want to capture the SOAP Client's request(XML
> > > payload) in the form of a string using SOAP libraries. After
> > > looking at the SOAPAPI and in that, the class CALL and the method
> > > invoke(..), I did not find any method using which I can capture
> > > the request from the client. So, I would like to modify the SOAP
> > > source code and see if its possible to add a method to capture the
> > > request from client.
> > >
> > > Please let me know if its possible. Also, I would appreciate
> > > it if you can send me the link where I can download the SOAP
> > > source code from.
> > >
> > > Thanks,
> > > Kiran
> > >
_______________________________________________________________________
> > > Odomos - the only mosquito protection outside 4 walls -
> > > Click here to know more!
> > >
> >
>
http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&w
> > n
> > >
> > >
> >
> >
> > Scott Nichol
> >
> > Do not reply directly to this e-mail address,
> > as it is filtered to only receive e-mail from
> > specific mailing lists.
> >
> >
> >
> >
> >
>
>
> Scott Nichol
>
> Do not reply directly to this e-mail address,
> as it is filtered to only receive e-mail from
> specific mailing lists.
>
>
>
>
>
Re: Capture the Client's request
Posted by Scott Nichol <sn...@scottnichol.com>.
This always appears in the payload for Apache SOAP. You do not need
to do anything special to get it.
On 10 Apr 2003 at 9:57, Manoj Mangla wrote:
> Akhil
>
> am not very sure but I guess writing "<?xml version="1.0"
> encoding="UTF-8"?>" in the soap packet header might help. Encoding can be
> deinfed by us as per your requirement.
>
> Hope it helps
> Manoj
>
>
> ----- Original Message -----
> From: "Akhil Jain" <ak...@baypackets.com>
> To: <so...@ws.apache.org>
> Sent: Thursday, April 10, 2003 9:44 AM
> Subject: RE: Capture the Client's request
>
>
> > Hi,
> > Thanks for your prompt reply.
> > I could see the unicode characters being converted into UTF-8 during
> > transfer. I was able to see some character in /337/338 etc form. My
> question
> > is that if I create an XML element and I put a Korean string in none of
> the
> > child text node. I think the Content-Length that is being sent in the
> HTTP
> > Header is the length of the string that contains the entire SOAP envelope
> > whereas the actual data that is sent on the wire contains the unicode
> > characters that are converted into UTF-8, hence increasing the Actual
> packet
> > length. I think this is the reason why the SOAP server is not able to
> read
> > the entire SOAP Evvelope, and so gives the DOM parsing error. Is there a
> way
> > I can tell SOAP implementation that I am sending the Strings in Unicode
> > (Java String) and that it needs to convert the string into UTF-8 string
> and
> > send the correct Content-Length in the HTTP Header.
> >
> > Thanks
> > Akhil
> >
> >
> > -----Original Message-----
> > From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> > Sent: Thursday, April 10, 2003 9:29 AM
> > To: soap-dev@ws.apache.org
> > Subject: RE: Capture the Client's request
> >
> >
> > The SOAP payload is encoded using UTF-8. Therefore, Unicode
> > characters in your Java strings should be translated to UTF-8 during
> > serialization, and then deserialization would do the reverse. Have
> > you tried using a tool to capture the message being transmitted over
> > the wire so that you can see the actual sequence of bytes?
> >
> > On 10 Apr 2003 at 9:16, Akhil Jain wrote:
> >
> > > Hi,
> > >
> > > Does SOAP implementation support internationalization?? I was trying to
> > send
> > > a Korean string in an XML Element. But I found that the SOAP server gave
> a
> > > DOM parsing error. It was not able to read the entire SOAP envelope. Can
> > you
> > > please help me on how to send a unicode string (containing Japanese or
> > > Korean characters) in a SOAP call?
> > >
> > > Thanks
> > > Akhil
> > >
> > > -----Original Message-----
> > > From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> > > Sent: Thursday, April 10, 2003 1:40 AM
> > > To: soap-dev@ws.apache.org
> > > Subject: Re: Capture the Client's request
> > >
> > >
> > > The current Apache SOAP code has this capability. You explicitly
> > > create an instance of SOAPHTTPConnection and call the setRequestCopy
> > > method to register a StringBuffer that will receive a copy of the
> > > request. You call the setSOAPTransport method on your Call instance
> > > to tell it to use the connection you have created. After calling
> > > invoke, a copy of the request will be in your StringBuffer.
> > >
> > > You can get a nightly build at
> > > http://cvs.apache.org/dist/soap/nightly/.
> > >
> > > On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
> > >
> > > > Dear All,
> > > >
> > > > I want to capture the SOAP Client's request(XML
> > > > payload) in the form of a string using SOAP libraries. After
> > > > looking at the SOAPAPI and in that, the class CALL and the method
> > > > invoke(..), I did not find any method using which I can capture
> > > > the request from the client. So, I would like to modify the SOAP
> > > > source code and see if its possible to add a method to capture the
> > > > request from client.
> > > >
> > > > Please let me know if its possible. Also, I would appreciate
> > > > it if you can send me the link where I can download the SOAP
> > > > source code from.
> > > >
> > > > Thanks,
> > > > Kiran
> > > >
> _______________________________________________________________________
> > > > Odomos - the only mosquito protection outside 4 walls -
> > > > Click here to know more!
> > > >
> > >
> >
> http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&w
> > > n
> > > >
> > > >
> > >
> > >
> > > Scott Nichol
> > >
> > > Do not reply directly to this e-mail address,
> > > as it is filtered to only receive e-mail from
> > > specific mailing lists.
> > >
> > >
> > >
> > >
> > >
> >
> >
> > Scott Nichol
> >
> > Do not reply directly to this e-mail address,
> > as it is filtered to only receive e-mail from
> > specific mailing lists.
> >
> >
> >
> >
> >
>
>
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
Re: Capture the Client's request
Posted by Manoj Mangla <ma...@in.fiorano.com>.
Akhil
am not very sure but I guess writing "<?xml version="1.0"
encoding="UTF-8"?>" in the soap packet header might help. Encoding can be
deinfed by us as per your requirement.
Hope it helps
Manoj
----- Original Message -----
From: "Akhil Jain" <ak...@baypackets.com>
To: <so...@ws.apache.org>
Sent: Thursday, April 10, 2003 9:44 AM
Subject: RE: Capture the Client's request
> Hi,
> Thanks for your prompt reply.
> I could see the unicode characters being converted into UTF-8 during
> transfer. I was able to see some character in /337/338 etc form. My
question
> is that if I create an XML element and I put a Korean string in none of
the
> child text node. I think the Content-Length that is being sent in the
HTTP
> Header is the length of the string that contains the entire SOAP envelope
> whereas the actual data that is sent on the wire contains the unicode
> characters that are converted into UTF-8, hence increasing the Actual
packet
> length. I think this is the reason why the SOAP server is not able to
read
> the entire SOAP Evvelope, and so gives the DOM parsing error. Is there a
way
> I can tell SOAP implementation that I am sending the Strings in Unicode
> (Java String) and that it needs to convert the string into UTF-8 string
and
> send the correct Content-Length in the HTTP Header.
>
> Thanks
> Akhil
>
>
> -----Original Message-----
> From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> Sent: Thursday, April 10, 2003 9:29 AM
> To: soap-dev@ws.apache.org
> Subject: RE: Capture the Client's request
>
>
> The SOAP payload is encoded using UTF-8. Therefore, Unicode
> characters in your Java strings should be translated to UTF-8 during
> serialization, and then deserialization would do the reverse. Have
> you tried using a tool to capture the message being transmitted over
> the wire so that you can see the actual sequence of bytes?
>
> On 10 Apr 2003 at 9:16, Akhil Jain wrote:
>
> > Hi,
> >
> > Does SOAP implementation support internationalization?? I was trying to
> send
> > a Korean string in an XML Element. But I found that the SOAP server gave
a
> > DOM parsing error. It was not able to read the entire SOAP envelope. Can
> you
> > please help me on how to send a unicode string (containing Japanese or
> > Korean characters) in a SOAP call?
> >
> > Thanks
> > Akhil
> >
> > -----Original Message-----
> > From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> > Sent: Thursday, April 10, 2003 1:40 AM
> > To: soap-dev@ws.apache.org
> > Subject: Re: Capture the Client's request
> >
> >
> > The current Apache SOAP code has this capability. You explicitly
> > create an instance of SOAPHTTPConnection and call the setRequestCopy
> > method to register a StringBuffer that will receive a copy of the
> > request. You call the setSOAPTransport method on your Call instance
> > to tell it to use the connection you have created. After calling
> > invoke, a copy of the request will be in your StringBuffer.
> >
> > You can get a nightly build at
> > http://cvs.apache.org/dist/soap/nightly/.
> >
> > On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
> >
> > > Dear All,
> > >
> > > I want to capture the SOAP Client's request(XML
> > > payload) in the form of a string using SOAP libraries. After
> > > looking at the SOAPAPI and in that, the class CALL and the method
> > > invoke(..), I did not find any method using which I can capture
> > > the request from the client. So, I would like to modify the SOAP
> > > source code and see if its possible to add a method to capture the
> > > request from client.
> > >
> > > Please let me know if its possible. Also, I would appreciate
> > > it if you can send me the link where I can download the SOAP
> > > source code from.
> > >
> > > Thanks,
> > > Kiran
> > >
_______________________________________________________________________
> > > Odomos - the only mosquito protection outside 4 walls -
> > > Click here to know more!
> > >
> >
>
http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&w
> > n
> > >
> > >
> >
> >
> > Scott Nichol
> >
> > Do not reply directly to this e-mail address,
> > as it is filtered to only receive e-mail from
> > specific mailing lists.
> >
> >
> >
> >
> >
>
>
> Scott Nichol
>
> Do not reply directly to this e-mail address,
> as it is filtered to only receive e-mail from
> specific mailing lists.
>
>
>
>
>
RE: Capture the Client's request
Posted by Akhil Jain <ak...@baypackets.com>.
Hi,
Thanks for your prompt reply.
I could see the unicode characters being converted into UTF-8 during
transfer. I was able to see some character in /337/338 etc form. My question
is that if I create an XML element and I put a Korean string in none of the
child text node. I think the Content-Length that is being sent in the HTTP
Header is the length of the string that contains the entire SOAP envelope
whereas the actual data that is sent on the wire contains the unicode
characters that are converted into UTF-8, hence increasing the Actual packet
length. I think this is the reason why the SOAP server is not able to read
the entire SOAP Evvelope, and so gives the DOM parsing error. Is there a way
I can tell SOAP implementation that I am sending the Strings in Unicode
(Java String) and that it needs to convert the string into UTF-8 string and
send the correct Content-Length in the HTTP Header.
Thanks
Akhil
-----Original Message-----
From: Scott Nichol [mailto:snicholnews@scottnichol.com]
Sent: Thursday, April 10, 2003 9:29 AM
To: soap-dev@ws.apache.org
Subject: RE: Capture the Client's request
The SOAP payload is encoded using UTF-8. Therefore, Unicode
characters in your Java strings should be translated to UTF-8 during
serialization, and then deserialization would do the reverse. Have
you tried using a tool to capture the message being transmitted over
the wire so that you can see the actual sequence of bytes?
On 10 Apr 2003 at 9:16, Akhil Jain wrote:
> Hi,
>
> Does SOAP implementation support internationalization?? I was trying to
send
> a Korean string in an XML Element. But I found that the SOAP server gave a
> DOM parsing error. It was not able to read the entire SOAP envelope. Can
you
> please help me on how to send a unicode string (containing Japanese or
> Korean characters) in a SOAP call?
>
> Thanks
> Akhil
>
> -----Original Message-----
> From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> Sent: Thursday, April 10, 2003 1:40 AM
> To: soap-dev@ws.apache.org
> Subject: Re: Capture the Client's request
>
>
> The current Apache SOAP code has this capability. You explicitly
> create an instance of SOAPHTTPConnection and call the setRequestCopy
> method to register a StringBuffer that will receive a copy of the
> request. You call the setSOAPTransport method on your Call instance
> to tell it to use the connection you have created. After calling
> invoke, a copy of the request will be in your StringBuffer.
>
> You can get a nightly build at
> http://cvs.apache.org/dist/soap/nightly/.
>
> On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
>
> > Dear All,
> >
> > I want to capture the SOAP Client's request(XML
> > payload) in the form of a string using SOAP libraries. After
> > looking at the SOAPAPI and in that, the class CALL and the method
> > invoke(..), I did not find any method using which I can capture
> > the request from the client. So, I would like to modify the SOAP
> > source code and see if its possible to add a method to capture the
> > request from client.
> >
> > Please let me know if its possible. Also, I would appreciate
> > it if you can send me the link where I can download the SOAP
> > source code from.
> >
> > Thanks,
> > Kiran
> > _______________________________________________________________________
> > Odomos - the only mosquito protection outside 4 walls -
> > Click here to know more!
> >
>
http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&w
> n
> >
> >
>
>
> Scott Nichol
>
> Do not reply directly to this e-mail address,
> as it is filtered to only receive e-mail from
> specific mailing lists.
>
>
>
>
>
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
RE: Capture the Client's request
Posted by Scott Nichol <sn...@scottnichol.com>.
The SOAP payload is encoded using UTF-8. Therefore, Unicode
characters in your Java strings should be translated to UTF-8 during
serialization, and then deserialization would do the reverse. Have
you tried using a tool to capture the message being transmitted over
the wire so that you can see the actual sequence of bytes?
On 10 Apr 2003 at 9:16, Akhil Jain wrote:
> Hi,
>
> Does SOAP implementation support internationalization?? I was trying to send
> a Korean string in an XML Element. But I found that the SOAP server gave a
> DOM parsing error. It was not able to read the entire SOAP envelope. Can you
> please help me on how to send a unicode string (containing Japanese or
> Korean characters) in a SOAP call?
>
> Thanks
> Akhil
>
> -----Original Message-----
> From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> Sent: Thursday, April 10, 2003 1:40 AM
> To: soap-dev@ws.apache.org
> Subject: Re: Capture the Client's request
>
>
> The current Apache SOAP code has this capability. You explicitly
> create an instance of SOAPHTTPConnection and call the setRequestCopy
> method to register a StringBuffer that will receive a copy of the
> request. You call the setSOAPTransport method on your Call instance
> to tell it to use the connection you have created. After calling
> invoke, a copy of the request will be in your StringBuffer.
>
> You can get a nightly build at
> http://cvs.apache.org/dist/soap/nightly/.
>
> On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
>
> > Dear All,
> >
> > I want to capture the SOAP Client's request(XML
> > payload) in the form of a string using SOAP libraries. After
> > looking at the SOAPAPI and in that, the class CALL and the method
> > invoke(..), I did not find any method using which I can capture
> > the request from the client. So, I would like to modify the SOAP
> > source code and see if its possible to add a method to capture the
> > request from client.
> >
> > Please let me know if its possible. Also, I would appreciate
> > it if you can send me the link where I can download the SOAP
> > source code from.
> >
> > Thanks,
> > Kiran
> > _______________________________________________________________________
> > Odomos - the only mosquito protection outside 4 walls -
> > Click here to know more!
> >
> http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&w
> n
> >
> >
>
>
> Scott Nichol
>
> Do not reply directly to this e-mail address,
> as it is filtered to only receive e-mail from
> specific mailing lists.
>
>
>
>
>
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
RE: Capture the Client's request
Posted by Scott Nichol <sn...@scottnichol.com>.
Just to be sure I understand...
Is the server Apache SOAP as well as the client? What version of
Apache SOAP are you using? What is the exact error message(s) you
are seeing?
On 10 Apr 2003 at 9:16, Akhil Jain wrote:
> Hi,
>
> Does SOAP implementation support internationalization?? I was trying to send
> a Korean string in an XML Element. But I found that the SOAP server gave a
> DOM parsing error. It was not able to read the entire SOAP envelope. Can you
> please help me on how to send a unicode string (containing Japanese or
> Korean characters) in a SOAP call?
>
> Thanks
> Akhil
>
> -----Original Message-----
> From: Scott Nichol [mailto:snicholnews@scottnichol.com]
> Sent: Thursday, April 10, 2003 1:40 AM
> To: soap-dev@ws.apache.org
> Subject: Re: Capture the Client's request
>
>
> The current Apache SOAP code has this capability. You explicitly
> create an instance of SOAPHTTPConnection and call the setRequestCopy
> method to register a StringBuffer that will receive a copy of the
> request. You call the setSOAPTransport method on your Call instance
> to tell it to use the connection you have created. After calling
> invoke, a copy of the request will be in your StringBuffer.
>
> You can get a nightly build at
> http://cvs.apache.org/dist/soap/nightly/.
>
> On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
>
> > Dear All,
> >
> > I want to capture the SOAP Client's request(XML
> > payload) in the form of a string using SOAP libraries. After
> > looking at the SOAPAPI and in that, the class CALL and the method
> > invoke(..), I did not find any method using which I can capture
> > the request from the client. So, I would like to modify the SOAP
> > source code and see if its possible to add a method to capture the
> > request from client.
> >
> > Please let me know if its possible. Also, I would appreciate
> > it if you can send me the link where I can download the SOAP
> > source code from.
> >
> > Thanks,
> > Kiran
> > _______________________________________________________________________
> > Odomos - the only mosquito protection outside 4 walls -
> > Click here to know more!
> >
> http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&w
> n
> >
> >
>
>
> Scott Nichol
>
> Do not reply directly to this e-mail address,
> as it is filtered to only receive e-mail from
> specific mailing lists.
>
>
>
>
>
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
Re: soapexceptioin
Posted by Scott Nichol <sn...@scottnichol.com>.
When you specify literal XML encoding (Constants.NS_URI_LITERAL_XML),
your parameters and return values can only be of type
org.w3c.dom.Element. If you want to use other parameter types, they
must be specified as SOAP encoded.
On 9 Apr 2003 at 22:14, Yang Guang wrote:
> My question is simple:
>
> I got a service return org.w3c.dom.Element.
> when there is no parameter in service, everything is ok,
> but if there is parameter in service, say, a user define object.
> there is a error message when calling client program.
> " Soapexception(env:client): I only know how to serialize org.w3c.dom.Element".
>
> what cause the error massage?
>
> any response will be appriciated!
>
> Sincerely,
>
> Yang Guang
>
> Keynes Tower 5/13
> University of Essex
> Wivenhoe Park
> Colchester
> Essex CO4 3SQ
>
> Tel: +44 (0)1206 535808
> E-mail: gyang@essex.ac.uk
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
soapexceptioin
Posted by Yang Guang <gy...@essex.ac.uk>.
My question is simple:
I got a service return org.w3c.dom.Element.
when there is no parameter in service, everything is ok,
but if there is parameter in service, say, a user define object.
there is a error message when calling client program.
" Soapexception(env:client): I only know how to serialize org.w3c.dom.Element".
what cause the error massage?
any response will be appriciated!
Sincerely,
Yang Guang
Keynes Tower 5/13
University of Essex
Wivenhoe Park
Colchester
Essex CO4 3SQ
Tel: +44 (0)1206 535808
E-mail: gyang@essex.ac.uk
RE: Capture the Client's request
Posted by Akhil Jain <ak...@baypackets.com>.
Hi,
Does SOAP implementation support internationalization?? I was trying to send
a Korean string in an XML Element. But I found that the SOAP server gave a
DOM parsing error. It was not able to read the entire SOAP envelope. Can you
please help me on how to send a unicode string (containing Japanese or
Korean characters) in a SOAP call?
Thanks
Akhil
-----Original Message-----
From: Scott Nichol [mailto:snicholnews@scottnichol.com]
Sent: Thursday, April 10, 2003 1:40 AM
To: soap-dev@ws.apache.org
Subject: Re: Capture the Client's request
The current Apache SOAP code has this capability. You explicitly
create an instance of SOAPHTTPConnection and call the setRequestCopy
method to register a StringBuffer that will receive a copy of the
request. You call the setSOAPTransport method on your Call instance
to tell it to use the connection you have created. After calling
invoke, a copy of the request will be in your StringBuffer.
You can get a nightly build at
http://cvs.apache.org/dist/soap/nightly/.
On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
> Dear All,
>
> I want to capture the SOAP Client's request(XML
> payload) in the form of a string using SOAP libraries. After
> looking at the SOAPAPI and in that, the class CALL and the method
> invoke(..), I did not find any method using which I can capture
> the request from the client. So, I would like to modify the SOAP
> source code and see if its possible to add a method to capture the
> request from client.
>
> Please let me know if its possible. Also, I would appreciate
> it if you can send me the link where I can download the SOAP
> source code from.
>
> Thanks,
> Kiran
> _______________________________________________________________________
> Odomos - the only mosquito protection outside 4 walls -
> Click here to know more!
>
http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&w
n
>
>
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
Re: Capture the Client's request
Posted by Scott Nichol <sn...@scottnichol.com>.
The current Apache SOAP code has this capability. You explicitly
create an instance of SOAPHTTPConnection and call the setRequestCopy
method to register a StringBuffer that will receive a copy of the
request. You call the setSOAPTransport method on your Call instance
to tell it to use the connection you have created. After calling
invoke, a copy of the request will be in your StringBuffer.
You can get a nightly build at
http://cvs.apache.org/dist/soap/nightly/.
On 9 Apr 2003 at 15:52, Kiran Devaram wrote:
> Dear All,
>
> I want to capture the SOAP Client's request(XML
> payload) in the form of a string using SOAP libraries. After
> looking at the SOAPAPI and in that, the class CALL and the method
> invoke(..), I did not find any method using which I can capture
> the request from the client. So, I would like to modify the SOAP
> source code and see if its possible to add a method to capture the
> request from client.
>
> Please let me know if its possible. Also, I would appreciate
> it if you can send me the link where I can download the SOAP
> source code from.
>
> Thanks,
> Kiran
> _______________________________________________________________________
> Odomos - the only mosquito protection outside 4 walls -
> Click here to know more!
> http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&wn
>
>
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.