Eran Chinthaka
<[EMAIL PROTECTED]
urce.lk> To
[email protected]
08/19/2006 12:02 cc
PM
Subject
Re: [Axis2] does client need to
Please respond to know MEP?
[EMAIL PROTECTED]
he.org
Hi Eran,
Thanks for the clarification. However, what do you mean by simple stuff?
Can you point me to the situations that demand such specialized operations?
or the use of operation clients? I am interested in knowing:
--whether ServiceClient is good enough for invoking doc/lit services,
taking one message part at the most, and with in-only or in-out MEPs? The
soapAction would be set in the Options. If so I would like to stick to the
ServiceClient usage.
--If ServiceClient can indeed handle the above, and blocking invocations
are fine, I should use fireAndForget() for in-only MEP and sendReceive()
for in-out MEP. Is that right?
Thanks a lot, I appreciate your help,
-Nirmit
Nirmit Desai wrote:
> Hi all,
>
> I was writing my client without using the generated stub (but mimicking
> what the stub does). I saw that the generated stub creates different
kinds
> of operations OutInAxisOperation, InOnlyAxisOpeepending on how the
message
> exchange pattern of the operation is on the sever side.
>
> But how does a client discover an MEP for a service operation? It is not
in
> WSDL.
MEP can always be deduced by the WSDL. Just look at the messages for an
operation. If you have
one input and one output - IN-OUT
one input - IN-Only.
Just identify the MEP and invoke either sendReceive or send depending on
that. No you don't need to juggle with OutInAxisOperation,
InOnlyAxisOperations if you are doing somple stuff.
-- Chinthaka
(See attached file: signature.asc)
signature.asc
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
