You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by "Anil Kumar, Anumakonda" <an...@profitera.com> on 2001/06/28 15:28:51 UTC
RE: Urgent(is there any limit for the size of data which can be t
ransported through SOAP)
Hi Scott,
is this a problem with Xerces 1.2.3. how SOAP internally parse and send
across .is SOAP internally created DOM structure and send it through client.
can you please help me how SOAP will transfer data.
Thanks & Regards
Anil
-----Original Message-----
From: Scott Nichol [mailto:snichol@computer.org]
Sent: Thursday, June 28, 2001 9:05 PM
To: soap-dev@xml.apache.org
Subject: Re: Urgent(is there any limit for the size of data which can be
transported through SOAP)
I was getting the same problem using Apache SOAP 2.1 and Xerces 1.2.3 and
1.3.0. Debugging led me to believe that Xerces was at fault, but I never
tracked it down to any particular code within Xerces. However, I got past
this by moving to a nightly build of Apache SOAP 2.1 that supported JAXP and
switching to Crimson for the parser. With Apache SOAP 2.2, I have continued
to use Crimson.
I do not know how you will be able to fix this without moving to a newer
version of Apache SOAP. Earlier versions only work with Xerces. While
Xerces 1.4 may fix the problem, I do not think that prior to Apache SOAP 2.2
there is any support for that version of Xerces.
Scott
----- Original Message -----
From: "Anil Kumar, Anumakonda" <an...@profitera.com>
To: <so...@xml.apache.org>
Sent: Thursday, June 28, 2001 8:13 AM
Subject: Urgent(is there any limit for the size of data which can be
transported through SOAP)
>
> Hi ,
>
> If i send huge data through SOAP(hashtable which contains a lot of data),
i
> am getting this error.
> Is there any limit for the size of data which can be transported through
> SOAP. How to over come this problem.
> I am using SOAP 2.1.
>
> SOAPException: faultCode=SOAP-ENV:Client; msg=No Deserializer found to
> deserialize a 'http://www.w3.org/1999/XMLSchema:ur-type' using encoding
> style 'http://schemas.xmlsoap.org/soap/encoding/'.;
> targetException=java.lang.IllegalArgumentException: No Deserializer found
to
> deserialize a 'http://www.w3.org/1999/XMLSchema:ur-type' using encoding
> style 'http://schemas.xmlsoap.org/soap/encoding/'.]
>
> Thanks & regards,
> Anil Kumar
>
Re: Urgent(is there any limit for the size of data which can be transported through SOAP)
Posted by Scott Nichol <sn...@computer.org>.
As I said, I had tracked the error down to Xerces, but not the exact code
within Xerces. Switching to Crimson fixed the problem, which is further
evidence that Xerces is the culprit.
Yes, Apache SOAP creates a DOM of the messages it receives. This is true on
both client and server. It does not create a DOM for messages it sends.
Scott
----- Original Message -----
From: "Anil Kumar, Anumakonda" <an...@profitera.com>
To: <so...@xml.apache.org>
Sent: Thursday, June 28, 2001 9:28 AM
Subject: RE: Urgent(is there any limit for the size of data which can be
transported through SOAP)
> Hi Scott,
>
> is this a problem with Xerces 1.2.3. how SOAP internally parse and send
> across .is SOAP internally created DOM structure and send it through
client.
> can you please help me how SOAP will transfer data.
>
>
> Thanks & Regards
> Anil
>
> -----Original Message-----
> From: Scott Nichol [mailto:snichol@computer.org]
> Sent: Thursday, June 28, 2001 9:05 PM
> To: soap-dev@xml.apache.org
> Subject: Re: Urgent(is there any limit for the size of data which can be
> transported through SOAP)
>
>
> I was getting the same problem using Apache SOAP 2.1 and Xerces 1.2.3 and
> 1.3.0. Debugging led me to believe that Xerces was at fault, but I never
> tracked it down to any particular code within Xerces. However, I got past
> this by moving to a nightly build of Apache SOAP 2.1 that supported JAXP
and
> switching to Crimson for the parser. With Apache SOAP 2.2, I have
continued
> to use Crimson.
>
> I do not know how you will be able to fix this without moving to a newer
> version of Apache SOAP. Earlier versions only work with Xerces. While
> Xerces 1.4 may fix the problem, I do not think that prior to Apache SOAP
2.2
> there is any support for that version of Xerces.
>
> Scott
>
> ----- Original Message -----
> From: "Anil Kumar, Anumakonda" <an...@profitera.com>
> To: <so...@xml.apache.org>
> Sent: Thursday, June 28, 2001 8:13 AM
> Subject: Urgent(is there any limit for the size of data which can be
> transported through SOAP)
>
>
> >
> > Hi ,
> >
> > If i send huge data through SOAP(hashtable which contains a lot of
data),
> i
> > am getting this error.
> > Is there any limit for the size of data which can be transported through
> > SOAP. How to over come this problem.
> > I am using SOAP 2.1.
> >
> > SOAPException: faultCode=SOAP-ENV:Client; msg=No Deserializer found to
> > deserialize a 'http://www.w3.org/1999/XMLSchema:ur-type' using encoding
> > style 'http://schemas.xmlsoap.org/soap/encoding/'.;
> > targetException=java.lang.IllegalArgumentException: No Deserializer
found
> to
> > deserialize a 'http://www.w3.org/1999/XMLSchema:ur-type' using encoding
> > style 'http://schemas.xmlsoap.org/soap/encoding/'.]
> >
> > Thanks & regards,
> > Anil Kumar
> >