[ http://issues.apache.org/jira/browse/AXISCPP-904?page=comments#action_12368375 ]
Adrian Dick commented on AXISCPP-904: ------------------------------------- Hi, There are still some issues regarding namespaces when creating HeaderBlocks. As a workaround, have you tried explicitely declaring namespaces? eg: INamespace *nsp=phb->createNamespaceDecl("ns1","http://www.pegs-pegstour.com/API/XMLSchema/1.0.2"); It may also be worth considering explicitely providing a namespace prefix, but avoiding the common convention of ns<n>, as the serializer automatically assigns these, but in certain situations (like this one) doesn't correctly detect them going out of scope. > undeclared xml namespaces > ------------------------- > > Key: AXISCPP-904 > URL: http://issues.apache.org/jira/browse/AXISCPP-904 > Project: Axis-C++ > Type: Bug > Components: Client - Engine > Versions: 1.6 Alpha > Environment: WIN2KSP4 JDK1.5.0_06 MSVC6SP6 > Reporter: Franz Fehringer > Attachments: SearchRoomsRequest.xml, vakanz.cpp, vakanz.wsdl, vakanz.xsd, > vakanz2.wsdl > > For me AxisC (both 1.5 and 1.6) generates invalid SOAP messages referring to > undeclared namespaces. > The problem occurs only if i set soap:header elements for inclusion in the > SOAP message. > Possibility 1 > IHeaderBlock* phb = pegs->createSOAPHeaderBlock("Token", > "http://www.pegs-pegstour.com/API/XMLSchema/1.0.1"); > i.e. no namespace explicitely given. > In this case a correct soap:body containing only ns1 as prefix and declaring > it beforehand is created. > But the soap:header is wrong using the ns1 prefix without declaring it. > Possibility 2 > IHeaderBlock* phb = pegs->createSOAPHeaderBlock("Token", > "http://www.pegs-pegstour.com/API/XMLSchema/1.0.1", "ns1"); > i.e. namespace explicitely given. > In this case a correct soap:header containing ns1 as prefix and declaring it > beforehand is created. > But the soap:body is wrong using an additional ns2 prefix without declaring > it. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira