axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roshan Weerasuriya (JIRA)" <>
Subject [jira] Assigned: (AXISCPP-224) conflict in const/non-const method calls for Basic Node objects
Date Thu, 04 Nov 2004 05:22:44 GMT
     [ ]

Roshan Weerasuriya reassigned AXISCPP-224:

    Assign To: Roshan Weerasuriya

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

> I'm writing a security handler that needs to access and parse the security header (if
present) of a SOAP message. Since a 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 according. For this, a couple of generic Base 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 objects 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, the handler architecture should probably be rectified to allow
this situation.

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