axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Praveen Peddi" <>
Subject Re: calling MessageService sample with .NET client
Date Thu, 10 Feb 2005 18:12:43 GMT
I just deployed the sample MessageService that came with Axis and tried to 
access it from .NET client.

My service name is GoogleAccessConnector. But for now I only have the method 
that was provided by message sample of Axis. Here is the WSDL anyway. It is 
generated by Axis. I am new Message style services. So you can assume I am 
dumb and the approach may be wrong :)
<?xml version="1.0" encoding="UTF-8"?>


<!--WSDL created by Apache Axis version: 1.2RC2

Built on Feb 08, 2005 (12:11:21 PST)-->


<schema targetNamespace="" 

<element name="echoElements" type="xsd:anyType"/>



<element name="echoElementsReturn" type="xsd:anyType"/>



<wsdl:message name="echoElementsResponse">

<wsdl:part element="impl:echoElementsReturn" name="echoElementsReturn"/>


<wsdl:message name="echoElementsRequest">

<wsdl:part element="tns1:echoElements" name="part"/>


<wsdl:portType name="GoogleAccessConnector">

<wsdl:operation name="echoElements">

<wsdl:input message="impl:echoElementsRequest" name="echoElementsRequest"/>

<wsdl:output message="impl:echoElementsResponse" 



<wsdl:binding name="GoogleAccessConnectorSoapBinding" 

<wsdlsoap:binding style="document" 

<wsdl:operation name="echoElements">

<wsdlsoap:operation soapAction=""/>

<wsdl:input name="echoElementsRequest">

<wsdlsoap:body use="literal"/>


<wsdl:output name="echoElementsResponse">

<wsdlsoap:body use="literal"/>




<wsdl:service name="GoogleAccessConnectorService">

<wsdl:port binding="impl:GoogleAccessConnectorSoapBinding" 





----- Original Message ----- 
From: "Paul Callahan" <>
To: <>
Sent: Thursday, February 10, 2005 12:16 PM
Subject: Re: calling MessageService sample with .NET client

> Praveen,
> This really depends on how you have structured your wsdl for the
> service.  If you are using message style services, then in most cases,
> you are providing your own XML Schema to define the types that are
> passed via the method you expose as a "message-based" service.
> Whether you use JAXB, Castor, or some manual dom/sax code on your end
> of the Java web service, you must publish the manner in which .NET can
> (de)serialize your objects.
> Whats your wsdl look like?
> -pc
> On Thu, 10 Feb 2005 11:58:05 -0500, Praveen Peddi
> <> wrote:
>> I have looked at the MessageService sample (both server and the client). 
>> It
>> passes Element[] as the argument and also returns the same. This is fine 
>> for
>> java based clients. But if I want to invoke it using non java clients 
>> like
>> .NET, how does it work? Are Axis's "message-style" services interoperable
>> with .NET?
>> In short, I want to send raw xml in soap-body and be able to call the 
>> method
>> by java and non java clients. How do I do that? I thought "message-style"
>> web service is the way to go but I tried with .NET and it didn't work. 
>> .NET
>> is able to import the MessageService WSDL but I could not succeed calling
>> that method yet.
>> Thanks
>> Praveen
>> **************************************************************
>> Praveen Peddi
>> Sr Software Engg, Context Media, Inc.
>> Tel:  401.854.3475
>> Fax:  401.861.3596
>> web:
>> **************************************************************
>> Context Media- "The Leader in Enterprise Content Integration"

View raw message