RE: Problem calling Axis WS from .Net

2005-05-13 Thread Eugene Shershnev 
Thanks for looking into this for me Anne.
As always really appreciate your help. 

We're using Microsoft .Net Framework 1.1 (version 1.1.4322 SP1)

-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] 
Sent: Friday, May 13, 2005 10:13a
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: Problem calling Axis WS from .Net

What version of .NET are you using? At one point .NET had trouble dealing
with imported schemas.

On 5/12/05, Eugene Shershnev <[EMAIL PROTECTED]> wrote:
>  
> 
> OK, I found a way to make .Net to understand the response. 
> If I put all type definitions under one schema everything works. 
> 
> Does anybody have a clue what's wrong with multiple schema definitions? 
> 
> Thanks,
> Eugene
> 
> _ 
> From:   Eugene Shershnev [mailto:[EMAIL PROTECTED] 
> Sent:   Thursday, May 12, 2005 11:49a 
> To: 'axis-user@ws.apache.org' 
> Subject:Problem calling Axis WS from .Net 
> 
> Hi All,
> 
> We're having problem between .Net client (C#) and Axis service. 
> Axis version is 1.2
> 
> The WSDL defined 2 operations: login and logout. 
> Login returns LoginResult object that contains 3 strings - that simple. 
> 
> The WSDL is attached. 
> 
>  << File: MyWSDL.wsdl >>
> 
> In the server-config.wsdd the service is defined like this: 
> 
>  
> 
> 
> MyWSDL.wsdl 
>  
>  
>  
>  
>  languageSpecificType="java:mydomain.myservice.LoginResult" 
> qname="ns1:LoginResult" 
> xmlns:ns1="urn:type.myservice.mydomain"/> 
> 
> languageSpecificType="java:mydomain.myservice.UnexpectedErrorFault"
> qname="ns2:UnexpectedErrorFault" 
> xmlns:ns2="urn:fault.myservice.mydomain"/> 
> urn:myservice.mydomain
> 
> 
> And the response looks like this: 
> 
>   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>  
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
>  
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> 
>
>  
>
> MySite1 
> EXPIRES:20050513111757-0400
> UID:domain\uid 
> 600 
>
>  
>   
> 
> 
> Now here is the problem - when .Net client calls login() it get 
> LoginResult object back, but all its elements are null.
> 
> Any help and pointers will be highly appreciated! 
> 
> --
> Eugene

Re: Problem calling Axis WS from .Net

2005-05-13 Thread Anne Thomas Manes 
What version of .NET are you using? At one point .NET had trouble
dealing with imported schemas.

On 5/12/05, Eugene Shershnev <[EMAIL PROTECTED]> wrote:
>  
> 
> OK, I found a way to make .Net to understand the response. 
> If I put all type definitions under one schema everything works. 
> 
> Does anybody have a clue what's wrong with multiple schema definitions? 
> 
> Thanks, 
> Eugene 
> 
> _ 
> From:   Eugene Shershnev [mailto:[EMAIL PROTECTED] 
> Sent:   Thursday, May 12, 2005 11:49a 
> To: 'axis-user@ws.apache.org' 
> Subject:Problem calling Axis WS from .Net 
> 
> Hi All, 
> 
> We're having problem between .Net client (C#) and Axis service. 
> Axis version is 1.2 
> 
> The WSDL defined 2 operations: login and logout. 
> Login returns LoginResult object that contains 3 strings - that simple. 
> 
> The WSDL is attached. 
> 
>  << File: MyWSDL.wsdl >> 
> 
> In the server-config.wsdd the service is defined like this: 
> 
>  
> 
> 
> MyWSDL.wsdl 
>  
>  
>  
>  
>  languageSpecificType="java:mydomain.myservice.LoginResult" 
> qname="ns1:LoginResult" 
> xmlns:ns1="urn:type.myservice.mydomain"/> 
> 
> languageSpecificType="java:mydomain.myservice.UnexpectedErrorFault"
> qname="ns2:UnexpectedErrorFault" 
> xmlns:ns2="urn:fault.myservice.mydomain"/> 
> urn:myservice.mydomain 
>  
> 
> And the response looks like this: 
> 
>  
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
>  
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
>  
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> 
>
>  
>
> MySite1 
> EXPIRES:20050513111757-0400
> UID:domain\uid 
> 600 
>
>  
>
>  
> 
> Now here is the problem - when .Net client calls login() it get LoginResult
> object back, but all its elements are null. 
> 
> Any help and pointers will be highly appreciated! 
> 
> -- 
> Eugene

RE: Problem calling Axis WS from .Net

2005-05-12 Thread Eugene Shershnev 
Title: RE: Problem calling Axis WS from .Net






OK, I found a way to make .Net to understand the response.

If I put all type definitions under one schema everything works.


Does anybody have a clue what's wrong with multiple schema definitions?


Thanks,

Eugene


_ 

From:   Eugene Shershnev [mailto:[EMAIL PROTECTED]] 

Sent:   Thursday, May 12, 2005 11:49a

To: 'axis-user@ws.apache.org'

Subject:    Problem calling Axis WS from .Net


Hi All,


We're having problem between .Net client (C#) and Axis service.

Axis version is 1.2


The WSDL defined 2 operations: login and logout.

Login returns LoginResult object that contains 3 strings - that simple.


The WSDL is attached.


 << File: MyWSDL.wsdl >> 

In the server-config.wsdd the service is defined like this:




    MyWSDL.wsdl

    

    

    

    

    

    languageSpecificType="java:mydomain.myservice.LoginResult"

    qname="ns1:LoginResult"

    xmlns:ns1="urn:type.myservice.mydomain"/>

    

    languageSpecificType="java:mydomain.myservice.UnexpectedErrorFault"

    qname="ns2:UnexpectedErrorFault"

    xmlns:ns2="urn:fault.myservice.mydomain"/>

    urn:myservice.mydomain




And the response looks like this:




http://schemas.xmlsoap.org/soap/envelope/"

  xmlns:xsd="http://www.w3.org/2001/XMLSchema"

  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  

    

  

    MySite1

    EXPIRES:20050513111757-0400 UID:domain\uid

    600

  

    

  




Now here is the problem - when .Net client calls login() it get LoginResult object back, but all its elements are null.


Any help and pointers will be highly appreciated!


--

Eugene