There is no error in Tomcat logs. Everything seems to be normal - it
just looks like C# client does not understand the results. Or said in
other way, service does not provide sufficient information to interpret
those according to wsdl.
I was hoping the order of elements does not matter in xml, or does it?
I'm not in position to learn all about WS stuff and am searching for
easiest way to expose java classes I have on one machine, to MS
environment. I could not solve this using Netbeans created web services
deployed to Tomcat (only workswhen deployed to Sun Java System
Application Server), not I'm having trouble using Beehive. Any other
suggestions? 

Bojan

-----Original Message-----
From: Chad Schoettger [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 20, 2005 8:40 PM
To: Beehive Users
Subject: Re: Web service not returning array to MS C# client

I took a quick look at your wsdl and I noticed was that in the traffic
file
the <izdaja> and <koda> elements appear to be reversed from the order
the
are defined in the wsdl for the Dok complex type.

Perhaps the service definition has changed since the client was created?

I was able to run a simliar test case without any issues using the
beehive
webservice system control. I don't currently have a setup to test with a
C#
client but may have time to set one up in the next couple of days. Also
if
you are getting any errors in the Tomcat logs they might help to
diagnose
the problem.

- Chad


On 10/20/05, Furlan Bojan ITWET2 <[EMAIL PROTECTED]> wrote:
>
>  Using Behive, I have 'successfully' deployed web service on Tomcat
5.5server. I have also been able to use the wsdl produced this way, as
input to
> create MS Visual C# web client for this service. The problem is, that
the
> array I receive in a client always contains only one element with null
> attribute values. When observing the traffic, I can see more objects
being
> returned, all with appropriate values.
>
> Attached are the files with wsdl and traffic. Can anyone help me?
>
>  Regards
>
> Bojan Furlan
>
>

Reply via email to