[ http://issues.apache.org/jira/browse/AXIS2-314?page=all ]
Eran Chinthaka resolved AXIS2-314:
----------------------------------
Resolution: Fixed
This is now implemented and committed to the code base.
Now users can do like this.
Options options = new Options();
options.setTo(toEPR);
options.setProperty(key,value);
options.setXXX(foo);
........
.......
Call call = new Call();
call.setClientOptions(options);
..................
................
Please keep in mind that this is not only for Call, but for all the derivatives
of MEPClient like InOnlyMEPClient, InOutMEPClient, etc.,
> Introduce Options to clients
> ----------------------------
>
> Key: AXIS2-314
> URL: http://issues.apache.org/jira/browse/AXIS2-314
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: client-api
> Reporter: Eran Chinthaka
> Assignee: Eran Chinthaka
> Fix For: 0.93
>
> There are some inconsistencies in the client package, especially Call and
> Stub. And the Call api and the MEPClient api seems not that consistent.
> Lets introduce Options bean in to the client api, so that user sets all the
> properties to that and pass that to the MEPClient or to a derived class of
> that.
> The related maling thread on this can be found here :
> http://marc.theaimsgroup.com/?l=axis-dev&m=113320384108037&w=2
--
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
