[AXISCPP-505] WSDL2Ws doesn't cope with WSDL complex types matching c/c++ types

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: WSDL processing - Doc, WSDL processing - RPC
• Assignee: Unassigned
• Reporter: Adrian Dick
• Created: 05/Mar/05 00:00
• Updated: 19/Dec/12 23:10

Description

WSDL2Ws produces generated stubs that cannot be compiled when WSDL contains types whose names match c/c++ types.
eg:
<complexType name="list">
<sequence>
<element maxOccurs="unbounded" name="item" nillable="true" type="xsd:string"/>
</sequence>
</complexType>

There are several potential fixes to this, including the rejection of c/c++ type, but I suggest the following would probably be the best fix:
Prefix all use user types with "::", eg:
::myReturnType* myPortType::myOperation(::myInput* Value0)
{
::myReturnType* pReturn = NULL;
...
if(AXIS_SUCCESS == m_pCall->checkMessage("myOperationResponse", "urn:amwebars"))

{ pReturn = (::myReturnType*)m_pCall->getCmplxObject((void*) Axis_DeSerialize_myReturnType, (void*) Axis_Create_myReturnType, (void*) Axis_Delete_myReturnType,"myOperationReturn", 0); }

...
}

Issue Links

• relates to: AXISCPP-882 Use C++ namespaces to prevent symbol collisions