axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Jose <>
Subject Re: [jira] Commented: (AXISCPP-360) compilation error when using APIs in BasicNode
Date Thu, 06 Jan 2005 13:58:45 GMT
Hi Roshan,
    I was referring an old API documentation. In that the return type of 
getFirstChild() was const BasicNode *. That's why I used  const BasicNode* 
 Now my problem is solved. 

 Thanks & Regards
James Jose
Messaging Clients Team, WMQDDC
IBM Software Labs, India
Direct: 91-80- 25094331  Ext :2331

"Roshan Weerasuriya (JIRA)" <> 
06/01/2005 15:46
Please respond to
"Apache AXIS C Developers List"


[jira] Commented: (AXISCPP-360) compilation error when using APIs in 

Roshan Weerasuriya commented on AXISCPP-360:

The methods in the BasicNode are not constant methods. The BasicNode 
object which you have creted is a constant object, so you can't call non 
constant methods (such as getLocalName() etc) of the BasicNode. Can you 
create your BasicNode pointer as non constant? Then this will solve your 
problem. Do you have a requirement to create it as a constant pointer, if 
so we have to see what we could do? Please respond

> compilation error when using APIs in BasicNode
> ----------------------------------------------
>          Key: AXISCPP-360
>          URL:
>      Project: Axis-C++
>         Type: Bug
>     Reporter: James Jose
>     Assignee: Roshan Weerasuriya

> IHeaderBlock *phb=ws.createSOAPHeaderBlock("Test","");
>                                BasicNode 
>                                const BasicNode 
>                                printf("%s",bn1->getLocalName());
> gives the following compilation error.
> error C2662: 'axiscpp::BasicNode::getLocalName' : cannot convert 'this' 
pointer from 'const axiscpp::BasicNode' to 'axiscpp::BasicNode &'
> The same error occurs if we call other APIs also.
> This compilation problem occurs only when the calling object is of type 
'const BasicNode *'.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message