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 Muralidharan <vi...@consultant.com> on 2001/04/04 15:37:45 UTC
The Fatal FAULT Exception
Hi everyone,
The same question seems to be severely active, and pardon me If I'm
repeating, Has there been a solution for the
'Caught SOAPException(SOAPENV:Client):
'http://schemas.xmlsoap.org/soap/envelope/:Fault' element must contain a:
'faultcode' element'
Exception?
I'm trying with Weblogic 5.1 + JDK 1.3 + Xerces 1.3.1 + Apache SOAP 2.1. Is
there anyone who's running this same setup already?
Reading previous mails, I've configured Xerces to be the first entry in Java
Classpath, and I'm sure that org.w3c.dom.* interfaces load from Xerces.
Many Thanks,
Murali
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
AW: The Fatal FAULT Exception
Posted by Christian Wurbs <cw...@inf.tu-dresden.de>.
Hi Murali,
some mails earlier you could find that a downgrade of Xerces should solve
the problem, for me it does( xerces 1.2.3 ) .
-----Ursprüngliche Nachricht-----
Von: Muralidharan [mailto:vishnuprasadc@consultant.com]
Gesendet: Mittwoch, 4. April 2001 15:38
An: Apache SOAP
Betreff: The Fatal FAULT Exception
Hi everyone,
The same question seems to be severely active, and pardon me If I'm
repeating, Has there been a solution for the
'Caught SOAPException(SOAPENV:Client):
'http://schemas.xmlsoap.org/soap/envelope/:Fault' element must contain a:
'faultcode' element'
Exception?
I'm trying with Weblogic 5.1 + JDK 1.3 + Xerces 1.3.1 + Apache SOAP 2.1. Is
there anyone who's running this same setup already?
Reading previous mails, I've configured Xerces to be the first entry in Java
Classpath, and I'm sure that org.w3c.dom.* interfaces load from Xerces.
Many Thanks,
Murali
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
---------------------------------------------------------------------
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
AW: The Fatal FAULT Exception
Posted by Christian Wurbs <cw...@inf.tu-dresden.de>.
Hi Murali,
some mails earlier you could find that a downgrade of Xerces should solve
the problem, for me it does( xerces 1.2.3 ) .
-----Ursprüngliche Nachricht-----
Von: Muralidharan [mailto:vishnuprasadc@consultant.com]
Gesendet: Mittwoch, 4. April 2001 15:38
An: Apache SOAP
Betreff: The Fatal FAULT Exception
Hi everyone,
The same question seems to be severely active, and pardon me If I'm
repeating, Has there been a solution for the
'Caught SOAPException(SOAPENV:Client):
'http://schemas.xmlsoap.org/soap/envelope/:Fault' element must contain a:
'faultcode' element'
Exception?
I'm trying with Weblogic 5.1 + JDK 1.3 + Xerces 1.3.1 + Apache SOAP 2.1. Is
there anyone who's running this same setup already?
Reading previous mails, I've configured Xerces to be the first entry in Java
Classpath, and I'm sure that org.w3c.dom.* interfaces load from Xerces.
Many Thanks,
Murali
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
---------------------------------------------------------------------
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