Thanks Pradeep, for the info - I've just read now the doc pointer you've
supplied me, and it is very helpfull, yet, it raises additional questions:
1. The client related piece of manual you have referred me to, contains
several code snippets that are using Axiom classes
(notably OMElement) to create a tree structure which I guess mimics SOAP
message. This seems to me as novice, going into low
level. Is this the only way to do it? what are the merits of using Axiom
on building the soap message tree by hand?
2. Assuming that I always have the WSDL of the target web services, Is it
possible that instead of creating the Axiom based tree, a
runtime generated proxy (from the WSDL) can be used (and reused later on)
to call the Web service ?
3. Can Axis2 inter-operate successfully with WCF based web services using
the ServiceClient/OperationClient APIs?
If AXIS2 client cannot inter-operate "out of the box" with WCF based
services (I assume due to the WS-* protocols besides perhaps
WS-Addressing), can WSIT project come to rescue ? if so how ?
(an example will be helpful here too)
4. Can someone elaborate on the advantages of using Axis2 for Web-Services
consumer relative to using JAX-WS Proxy or JAX-WS
Dispatch APIs) ?
Thanks,
Avi
On Thu, Feb 26, 2009 at 1:56 PM, Pradeep Fernando <[email protected]>wrote:
> hi Avi,
>
> I'll be much obliged if someone can tell me that whether Axis2 is suitable
>> for one who *does not care about building web services* but only in
>> *consuming
>> them dynamically*
>
>
> may be what you are looking for is Axis2 dynamic client, where you can give
> the WSDL of the service as a argument during service client creation. Please
> refer to the article given [1] for more details. There is a sub heading
> called "Creating Dynamic client. ".
> Note that service client only supports WSDL1.1 at the moment.
>
> hope this helps,
> .
>
> [1]
> http://today.java.net/pub/a/today/2006/12/13/invoking-web-services-using-apache-axis2.htmlby
> Deepal jayasinghe.
>
