axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Dick (JIRA)" <>
Subject [jira] Commented: (AXISCPP-904) undeclared xml namespaces
Date Wed, 01 Mar 2006 22:03:13 GMT
    [ ] 

Adrian Dick commented on AXISCPP-904:


There are still some issues regarding namespaces when creating HeaderBlocks.

As a workaround, have you tried explicitely declaring namespaces?
INamespace *nsp=phb->createNamespaceDecl("ns1","");

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:
>      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
> The problem occurs only if i set soap:header elements for inclusion in the SOAP message.
> Possibility 1
> IHeaderBlock* phb = pegs->createSOAPHeaderBlock("Token", "");
> 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", "",
> 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:
For more information on JIRA, see:

View raw message