is responsible for calling managing the stubs, is I guess on
> instance per thread, if on erequest to the web app equals one thread.
> Hence
> one stub per service per thread.
>
> One way to go is a pool of stunbs I guess shared by the web application.
>
>
> cheers, Håkon
>
>From memory (apologies in advance if this is off the mark), I think it's the
axis2 client stub that will serialize multiple calls - i.e. will finish one
request/response before beginning another. So if you want to parallelize the
calls, what's needed is multiple client stubs, and multiple threads
General observation on NPE. Might apply to your case, Shalk, or it might not.
I sometimes found NPEs in the execution of generated code when I wasn't
careful to exactly match the axis2 version used for generation with the
version used at runtime. (missing/renamed member variables, missing/renamed
