[ http://issues.apache.org/jira/browse/AXISCPP-704?page=all ]
Mark Whitlock closed AXISCPP-704:
---------------------------------
Resolution: Fixed
I have now fixed problems 2 and 3. Problem 1 results in a useful SOAP fault
being returned from the server, so there is no need to police this in the Axis
client. I have commented out the code that triggers problem1 but uncommented
the code that used to cause problems 2 and 3.
> Problem in setSOAPMethodAttribute API in Call class
> ---------------------------------------------------
>
> Key: AXISCPP-704
> URL: http://issues.apache.org/jira/browse/AXISCPP-704
> Project: Axis-C++
> Type: Bug
> Components: Client - API
> Reporter: James Jose
> Assignee: Mark Whitlock
>
> Observed following problems in setSOAPMethodAttribute in Call class
> 1. API will create duplicate attribute.
> If I use API twice with same argument , it will create two
> attributes with same name.
> But an element cannot have two attributes with same name.
> 2. AxisEngine fails to generate SOAP message if NULL is passed as argument.
> Results in abnormal program termination.
> 3.AxisEngine fails to generate SOAP message if an undeclared namespace prefix
> is
> passed as argument. Results in abnormal program termination.
> In case2 and 3 it should provide some proper error message.
> DynamicSetSOAPMethodAttr1Test1 & DynamicSetSOAPMethodAttr1Test2 addreses
> these problems
>
>
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira