Sanjiva Weerawarana wrote:
> If you want to do that then you have to support a model of allowing the
>
>user to get an anonymous operation client without having to give that a
>special name that we came up with. That is, it doesn't make sense to
>make the ANON_* stuff part of user's world- just a
On Fri, 2006-09-15 at 11:59 +0530, Deepal Jayasinghe wrote:
> >That doesn't make any sense IMO .. the reason we use the anon ops is to
> >make the simple case possible. If someone's getting at the operation
> >client and doing stuff there better know the name of the operation.
> >
> >
> Yes , I u
>That doesn't make any sense IMO .. the reason we use the anon ops is to
>make the simple case possible. If someone's getting at the operation
>client and doing stuff there better know the name of the operation.
>
>
Yes , I understand that. But the scenario I am talking about also making
the sim
On Thu, 2006-09-14 at 16:04 +0530, Deepal Jayasinghe wrote:
>
>
> >Hmmm. Good question- I also don't see why the ANON_* constants are
> >externally visible. We put those to create underlying anonymous
> >AxisOperation objects to make the simple API calls work right and hence
> >should be private
Thanks for the clarifications, Deepal and Sanjiva - I'll get the Javadoc
updates checked in later today, and add Jira issues on the other items.
- Dennis
Deepal Jayasinghe wrote:
Hmmm. Good question- I also don't see why the ANON_* constants are
externally visible. We put those to create
Deepal,Can I use this opportunity to clear my doubts about the operation client vs service client.This is still not documented properly other than to say that "if you are experianced with Axis2 use operation client"
I understand that Operation Client is more flexible and powerfull as you could deal
>Hmmm. Good question- I also don't see why the ANON_* constants are
>externally visible. We put those to create underlying anonymous
>AxisOperation objects to make the simple API calls work right and hence
>should be private IMO.
>
>Deepal?
>
>
>
If some one want to create an operationclient u
On Thu, 2006-09-14 at 13:23 +0530, Deepal Jayasinghe wrote:
> Hi Dennis:
> please see my comment in line.
>
> > I'm working on documentation for
> > org.apache.axis2.client.ServiceClient, and ran into a few questions.
> > First off, the constants ANON_OUT_ONLY_OP, ANON_ROBUST_OUT_ONLY_OP,
> > and
Hi Dennis;
please see my comment in line.
> I'm working on documentation for
> org.apache.axis2.client.ServiceClient, and ran into a few questions.
> First off, the constants ANON_OUT_ONLY_OP, ANON_ROBUST_OUT_ONLY_OP,
> and ANON_OUT_IN_OP; if I'm understanding these correctly they
> represent exa
Hi Dennis:
please see my comment in line.
> I'm working on documentation for
> org.apache.axis2.client.ServiceClient, and ran into a few questions.
> First off, the constants ANON_OUT_ONLY_OP, ANON_ROBUST_OUT_ONLY_OP,
> and ANON_OUT_IN_OP; if I'm understanding these correctly they
> represent exac
I'm working on documentation for org.apache.axis2.client.ServiceClient,
and ran into a few questions. First off, the constants ANON_OUT_ONLY_OP,
ANON_ROBUST_OUT_ONLY_OP, and ANON_OUT_IN_OP; if I'm understanding these
correctly they represent exactly the opposite of what you'd expect from
lookin
11 matches
Mail list logo
