On Fri, 2005-12-02 at 08:28 -0500, Davanum Srinivas wrote:
> Eran,
>
> Just working with call is ok. Problem is when u start working with
> Stubs (WSDL2Java Generated code!!!), Let me give u an example.
>
> testFoo()
> {
> _clientOptions.setXXX()
> _clientOptions.setYYY()
> }
>
> testBar()
> {
> _clientOptions.setXXX()
> }
I assume you're doing stub.getClientOptions() and storing as an instance
var in the test case first?
BTW, can we s/clientOptions/options/g ? Otherwise the concept is named
differently for stubs from the DII .. which is unnecessary user pain.
> If the user uses the stub like this, only XXX is set.
> stub.testBar()
>
> If the user calls foo first, then in the Bar call both XXX and YYY are set.
> stub.testFoo()
> stub.testBar()
The issue is what you're setting options on. IMO you're setting options
on the entire stub. Thus, if you do setYYY on the stub you expect it to
remember it! So in this case, I'd expect the behavior you find
unacceptable.
Sanjiva.
