axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roshan Weerasuriya (JIRA)" <>
Subject [jira] Resolved: (AXISCPP-212) Conflict in const/non-const method calls for Basic Node objects
Date Fri, 03 Dec 2004 06:28:38 GMT
     [ ]
Roshan Weerasuriya resolved AXISCPP-212:

    Resolution: Fixed


> Conflict in const/non-const method calls for Basic Node objects
> ---------------------------------------------------------------
>          Key: AXISCPP-212
>          URL:
>      Project: Axis-C++
>         Type: Improvement
>   Components: Basic Architecture
>     Versions: 1.3 Beta
>  Environment: Windows 2000 Professional, with Visual C++ IDE/compiler
>     Reporter: Sharanka Perera
>     Assignee: Roshan Weerasuriya

> Some of the methods in the basic node object return a constant 
> value, and some don't. In my case I'm writing a security handler that needs to access
and parse the Security header (if any) of a SOAP message. Since the security header can contain
varying content, it is better to assume that the content is unknown and parse each header
element from the top and process it accordingly. For this, a couple of generic basic node
objects would be utilized, and with the aid of a loop each parsed value would be assigned
to the basic node objects for analysis. Unfortunately, at this point, some of the methods
of the basic node object that have to be called require that the calling object be constant,
and some of the other methods that must be called require that it *not* be. Since a generic
object used for parsing cannot be both constant and not constant, this should probably be

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