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 Richard Bolen <bo...@GretagMacbeth.com> on 2002/05/22 16:37:35 UTC
RE: IllegalArgumentException in processing server exceptions on client side
Did you ever find a solution to this issue? I'm having the same problem.
Thanks,
Rich
-----Original Message-----
From: Jim Cross [mailto:jimcross@jimcross.com]
Sent: Friday, May 03, 2002 09:24
To: soap-user@xml.apache.org
Subject: IllegalArgumentException in processing server exceptions on
client side
I'm running SOAP 2.2 with WebLogic 6.1 SP2.
Whenever an exception gets generated on the server side, the fault
information is not processed correctly on the client side.
The problem is in the unmarshall code of Fault.
The problem is this:
String namespaceURI = tempEl.getNamespaceURI();
// other code
if (namespaceURI == null
|| namespaceURI.equals(Constants.NS_URI_SOAP_ENV))
{
// do logic to retrieve fault code and other fault information
// this code never executes because namespaceURI is zero length string not null
}
// therefore faultCodeEl is null
if (faultCodeEl != null)
{
String faultCode = DOMUtils.getChildCharacterData(faultCodeEl);
fault.setFaultCode(faultCode);
}
else
{
// this exception gets thrown
throw new IllegalArgumentException("A '" + Constants.Q_ELEM_FAULT +
"' element must contain a: '" +
Constants.ELEM_FAULT_CODE +
"' element.");
}
Any ideas?
Jim Cross
Jim Cross Java News!
http://www.jimcross.com
404 271 2571