>>>>> "cj" == c jones <[EMAIL PROTECTED]> writes:
cj> Hello all, I need some clarification. I am relatively new to
cj> SOAP development and am unable to differentiate between two
cj> scenarios...
cj> I have a client java class which invokes a call across SOAP
cj> and calls a method of a particular class with its respective
cj> parameters. now, in the examples, ive seen this parameter
cj> passing done two ways (there are probably more, however).
cj> 1) the method on the server side is implemented with the
cj> parameters as they are set in
cj> the parameters vector, for example
cj> call.setMethodName("MyMethod"); Vector params = new Vector();
cj> Parameter nameParam = new Parameter("name",
cj> java.lang.String.class, name, null);
cj> params.addElement(nameParam);
cj> nameParam = new Parameter("othername", java.lang.String.class,
cj> name2, null); params.addElement(nameParam);
cj> call.setParams(params);
cj> ... then the call is invoked. Now on the server side, the
cj> method MyMethod would be public String MyMethod (String name1,
cj> String name2) throwing appropriate exceptions
cj> 2) the second case, the same scenario is used above, except
cj> that the method on the server
cj> side would be implemented as public String MyMethod(Envelope
cj> env, SOAPContext reqCtx, SOAPContext resCtx) throwing
cj> appropriate exceptions
cj> how do these two scenarios differ?
Scenario 1 is referred to as SOAP-RPC.
Scenario 2 is referred to as SOAP-Messaging.
SOAP-RPC is just that, Remote Procedure Call. It has special encoding
rules.
Soap Messaging is just moving a body of XML from one place to
another. This XML can look like anything you want.
At least that's how I understand it.
- Bob
--
SynXis Corporation | [EMAIL PROTECTED] | Obstacles are those frightful
1610 Wynkoop, Suite 400 | Ph: (303)595-2511 | things you see when you take your
Denver, CO 80202 | Fax:(303)534-4257 | eyes off your goal. -Henry Ford
