[ http://issues.apache.org/jira/browse/AXISCPP-207?page=history ]
Samisa Abeysinghe updated AXISCPP-207:
--------------------------------------
Component: Client - Stub
(was: Basic Architecture)
> Problems with Attributes and Stubs
> ----------------------------------
>
> Key: AXISCPP-207
> URL: http://issues.apache.org/jira/browse/AXISCPP-207
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.3 Final
> Reporter: Mark Whitlock
> Assignee: Mark Whitlock
> Fix For: 1.4 Alpha
>
> Stub::setSOAPMethodAttribute(const AxisChar* pLocalName, const AxisChar*
> pPrefix, const AxisChar* pValue) looks to see if an attribute of that
> localName already exists, and if so, deletes it first before creating the new
> Attribute. But setSOAPMethodAttribute(const AxisChar* pLocalName, const
> AxisChar* pPrefix, const AxisChar* pUri, const AxisChar* pValue) doesn't look
> for duplicate localNames before it creates the new Attribute. This looks like
> a bug. I can fix it but I'm not familiar with this area of the code so I'm
> not sure whether it's deliberate. Anyone know? Otherwise I'll assume it's a
> bug and fix it.
> Currently it is up to the client application to delete the Attributes that it
> created using Stub::setSOAPMethodAttribute, because the application may want
> to reuse these Attributes on another Stub. But there is no
> Stub::setSOAPMethodAttribute(IAttribute *pAttribute), so reusing an Attribute
> is impossible. Also deleting these Attributes is awkward since there is no
> method that deletes all the Attributes. So I propose deleting all Attributes
> in ~Stub.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
