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 ji...@apache.org on 2004/04/27 15:05:55 UTC
[jira] Created: (AXISCPP-64) generated port-type code has unitialized variable problem
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-64
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-64
Summary: generated port-type code has unitialized variable problem
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis-C++
Components:
WSDL generation
Versions:
1.1 Final
Assignee:
Reporter: benson@basistech.com
Created: Tue, 27 Apr 2004 6:05 AM
Updated: Tue, 27 Apr 2004 6:05 AM
Environment: Windows
Description:
In the following, Ret is unitialized if m_pCall->Invoke fails. Seems to me that Ret should be assigned to the result of m_pCall->Invoke.
xsd__string InteropTestPortType::echoString(xsd__string Value0)
{
xsd__string Ret;
if (AXIS_SUCCESS != m_pCall->Initialize(CPP_RPC_PROVIDER, NORMAL_CHANNEL)) return Ret;
m_pCall->SetTransportProperty(SOAPACTION_HEADER , "base#echoString");
m_pCall->SetSOAPVersion(SOAP_VER_1_1);
m_pCall->SetOperation("echoString", "http://soapinterop.org/");
m_pCall->AddParameter((void*)&Value0, "inputString", XSD_STRING);
if (AXIS_SUCCESS == m_pCall->Invoke())
{
if(AXIS_SUCCESS == m_pCall->CheckMessage("echoStringResponse", ""))
{
Ret = m_pCall->GetElementAsString("return", 0);
}
}
m_pCall->UnInitialize();
return Ret;
}
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXISCPP-64) generated port-type code has unitialized variable problem
Posted by ax...@ws.apache.org.
Message:
The following issue has been closed.
Resolver: Samisa Abeysinghe
Date: Fri, 8 Oct 2004 4:39 AM
WSDL tool was changed to init the simple type variables in the generated code. (However time/date related structs - tm struct - is not inited)
In case invoke of Call class returns an error, it will retun a value inited either to NULL (in case of char*) or to 0 (in case of inits/floats etc.) - Note that this code was already there - I chaned only the WSDL2WS tool
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-64
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-64
Summary: generated port-type code has unitialized variable problem
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Axis-C++
Components:
WSDL generation
Fix Fors:
1.3 Final
Versions:
1.1 Final
Assignee:
Reporter: Benson Margulies
Created: Tue, 27 Apr 2004 6:05 AM
Updated: Fri, 8 Oct 2004 4:39 AM
Environment: Windows
Description:
In the following, Ret is unitialized if m_pCall->Invoke fails. Seems to me that Ret should be assigned to the result of m_pCall->Invoke.
xsd__string InteropTestPortType::echoString(xsd__string Value0)
{
xsd__string Ret;
if (AXIS_SUCCESS != m_pCall->Initialize(CPP_RPC_PROVIDER, NORMAL_CHANNEL)) return Ret;
m_pCall->SetTransportProperty(SOAPACTION_HEADER , "base#echoString");
m_pCall->SetSOAPVersion(SOAP_VER_1_1);
m_pCall->SetOperation("echoString", "http://soapinterop.org/");
m_pCall->AddParameter((void*)&Value0, "inputString", XSD_STRING);
if (AXIS_SUCCESS == m_pCall->Invoke())
{
if(AXIS_SUCCESS == m_pCall->CheckMessage("echoStringResponse", ""))
{
Ret = m_pCall->GetElementAsString("return", 0);
}
}
m_pCall->UnInitialize();
return Ret;
}
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira