You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Sanjiva Weerawarana <sa...@watson.ibm.com> on 2001/05/22 17:41:12 UTC
DO NOT USE Xerces 1.3.1 with Apache SOAP
Xerces 1.3.1 has a bug in its namespace handling code that breaks
Apache SOAP. Please use an older version of Xerces or a nightly
build.
Note that v2.2RC1 is fully JAXP enabled. As such you can now use
any JAXP enabled, namespace aware parser.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: DO NOT USE Xerces 1.3.1 with Apache SOAP
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
No, I haven't seen that particular problem come from Xerces 1.3.1
so I don't know whether switching to a different version of
Xerces will solve this for you. Are you doing anything
special to config the parser?
Sanjiva.
----- Original Message -----
From: "Kartheek Hirode" <ka...@centegy.com>
To: <so...@xml.apache.org>
Sent: Tuesday, May 22, 2001 3:17 PM
Subject: RE: DO NOT USE Xerces 1.3.1 with Apache SOAP
> I might have a related problem. When I try to access a SOAP-Header element
> in the RPCRouterServlet, am getting this Exception message:
> org.apache.xerces.dom.DeferredElementNSImpl
>
> Is this one of the problems that you're talking about?
> I have sent another email to this mailing-list with a more elaborate
> description of the
> problem.(Subject-line: API to access SOAP-Headers in RPCRouterServlet)
> Thanks much,
> --KH
>
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
> Sent: Tuesday, May 22, 2001 8:41 AM
> To: soap-user@xml.apache.org
> Subject: DO NOT USE Xerces 1.3.1 with Apache SOAP
>
>
> Xerces 1.3.1 has a bug in its namespace handling code that breaks
> Apache SOAP. Please use an older version of Xerces or a nightly
> build.
>
> Note that v2.2RC1 is fully JAXP enabled. As such you can now use
> any JAXP enabled, namespace aware parser.
>
> Sanjiva.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: DO NOT USE Xerces 1.3.1 with Apache SOAP
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
No, I haven't seen that particular problem come from Xerces 1.3.1
so I don't know whether switching to a different version of
Xerces will solve this for you. Are you doing anything
special to config the parser?
Sanjiva.
----- Original Message -----
From: "Kartheek Hirode" <ka...@centegy.com>
To: <so...@xml.apache.org>
Sent: Tuesday, May 22, 2001 3:17 PM
Subject: RE: DO NOT USE Xerces 1.3.1 with Apache SOAP
> I might have a related problem. When I try to access a SOAP-Header element
> in the RPCRouterServlet, am getting this Exception message:
> org.apache.xerces.dom.DeferredElementNSImpl
>
> Is this one of the problems that you're talking about?
> I have sent another email to this mailing-list with a more elaborate
> description of the
> problem.(Subject-line: API to access SOAP-Headers in RPCRouterServlet)
> Thanks much,
> --KH
>
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
> Sent: Tuesday, May 22, 2001 8:41 AM
> To: soap-user@xml.apache.org
> Subject: DO NOT USE Xerces 1.3.1 with Apache SOAP
>
>
> Xerces 1.3.1 has a bug in its namespace handling code that breaks
> Apache SOAP. Please use an older version of Xerces or a nightly
> build.
>
> Note that v2.2RC1 is fully JAXP enabled. As such you can now use
> any JAXP enabled, namespace aware parser.
>
> Sanjiva.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: DO NOT USE Xerces 1.3.1 with Apache SOAP
Posted by Kartheek Hirode <ka...@centegy.com>.
I might have a related problem. When I try to access a SOAP-Header element
in the RPCRouterServlet, am getting this Exception message:
org.apache.xerces.dom.DeferredElementNSImpl
Is this one of the problems that you're talking about?
I have sent another email to this mailing-list with a more elaborate
description of the
problem.(Subject-line: API to access SOAP-Headers in RPCRouterServlet)
Thanks much,
--KH
-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
Sent: Tuesday, May 22, 2001 8:41 AM
To: soap-user@xml.apache.org
Subject: DO NOT USE Xerces 1.3.1 with Apache SOAP
Xerces 1.3.1 has a bug in its namespace handling code that breaks
Apache SOAP. Please use an older version of Xerces or a nightly
build.
Note that v2.2RC1 is fully JAXP enabled. As such you can now use
any JAXP enabled, namespace aware parser.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: DO NOT USE Xerces 1.3.1 with Apache SOAP
Posted by Kartheek Hirode <ka...@centegy.com>.
I might have a related problem. When I try to access a SOAP-Header element
in the RPCRouterServlet, am getting this Exception message:
org.apache.xerces.dom.DeferredElementNSImpl
Is this one of the problems that you're talking about?
I have sent another email to this mailing-list with a more elaborate
description of the
problem.(Subject-line: API to access SOAP-Headers in RPCRouterServlet)
Thanks much,
--KH
-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
Sent: Tuesday, May 22, 2001 8:41 AM
To: soap-user@xml.apache.org
Subject: DO NOT USE Xerces 1.3.1 with Apache SOAP
Xerces 1.3.1 has a bug in its namespace handling code that breaks
Apache SOAP. Please use an older version of Xerces or a nightly
build.
Note that v2.2RC1 is fully JAXP enabled. As such you can now use
any JAXP enabled, namespace aware parser.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org