You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Bill Mitchell (JIRA)" <ji...@apache.org> on 2008/01/08 01:49:34 UTC
[jira] Created: (AXIS2C-889) misleading error message from
generated stub deserialize routine when SOAP fault received
misleading error message from generated stub deserialize routine when SOAP fault received
-----------------------------------------------------------------------------------------
Key: AXIS2C-889
URL: https://issues.apache.org/jira/browse/AXIS2C-889
Project: Axis2-C
Issue Type: Bug
Components: code generation
Affects Versions: Current (Nightly)
Environment: Windows XP, Visual Studio 2005, libxml, libcurl
Reporter: Bill Mitchell
Priority: Trivial
As you can see from the following line from the axis2.trace file, the error message when a SOAP fault message is received instead of the expected response, is misleading in that it indicates the SOAP fault was expected, and the response message was received:
[Sat Jan 05 21:32:21 2008] [error] .\adb_browseResponse.c(160) Failed in building adb object for browseResponse : Expected Fault|http://schemas.xmlsoap.org/soap/envelope/|SOAP but returned browseResponse|http://frameware.xcentrisity.com/services/
In the generated code, for example in the following code, the first qname_to_string actually computes the response received, and the qname_to_string of the _browseResponse->qname indicates the expected value.
AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
"Failed in building adb object for browseResponse : "
"Expected %s but returned %s",
axutil_qname_to_string(qname, env),
axutil_qname_to_string(_browseResponse-> qname, env));
Inverting the last two lines to read as follows would correct this problem:
AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
"Failed in building adb object for browseResponse : "
"Expected %s but returned %s",
axutil_qname_to_string(_browseResponse-> qname, env),
axutil_qname_to_string(qname, env));
These lines appear to be at line 759 in CADBBeanTemplateSource.xsl.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Resolved: (AXIS2C-889) misleading error message from
generated stub deserialize routine when SOAP fault received
Posted by "Dimuthu Gamage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dimuthu Gamage resolved AXIS2C-889.
-----------------------------------
Resolution: Fixed
Fixed. Thanks for pointing out this.
> misleading error message from generated stub deserialize routine when SOAP fault received
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2C-889
> URL: https://issues.apache.org/jira/browse/AXIS2C-889
> Project: Axis2-C
> Issue Type: Bug
> Components: code generation
> Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, libxml, libcurl
> Reporter: Bill Mitchell
> Priority: Trivial
>
> As you can see from the following line from the axis2.trace file, the error message when a SOAP fault message is received instead of the expected response, is misleading in that it indicates the SOAP fault was expected, and the response message was received:
> [Sat Jan 05 21:32:21 2008] [error] .\adb_browseResponse.c(160) Failed in building adb object for browseResponse : Expected Fault|http://schemas.xmlsoap.org/soap/envelope/|SOAP but returned browseResponse|http://frameware.xcentrisity.com/services/
> In the generated code, for example in the following code, the first qname_to_string actually computes the response received, and the qname_to_string of the _browseResponse->qname indicates the expected value.
> AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
> "Failed in building adb object for browseResponse : "
> "Expected %s but returned %s",
> axutil_qname_to_string(qname, env),
> axutil_qname_to_string(_browseResponse-> qname, env));
> Inverting the last two lines to read as follows would correct this problem:
> AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
> "Failed in building adb object for browseResponse : "
> "Expected %s but returned %s",
> axutil_qname_to_string(_browseResponse-> qname, env),
> axutil_qname_to_string(qname, env));
> These lines appear to be at line 759 in CADBBeanTemplateSource.xsl.
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org