[ http://issues.apache.org/jira/browse/AXISCPP-505?page=comments#action_60584 ] Mark Whitlock commented on AXISCPP-505: ---------------------------------------
This JIRA was unassigned and it's high priority for us so I'll fix it. There are several cases here: where the offending name is an operation name, a parameter name or a field in a generated class. Also where the offending name clashes with a STL type, or a C++ primitive type, or is a C++ reserved keyword. All these should be valid in the WSDL. > WSDL2Ws doesn't cope with WSDL complex types matching c/c++ types > ----------------------------------------------------------------- > > Key: AXISCPP-505 > URL: http://issues.apache.org/jira/browse/AXISCPP-505 > Project: Axis-C++ > Type: Bug > Components: WSDL processing > Reporter: Adrian Dick > Assignee: Mark Whitlock > > 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); > } > ... > } -- 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
