Please clarify.
The vendor provides the service -- implemented in VB.NET?
You are trying to access it using an Axis client?
But you are giving the vendor the WSDL?
I would expect it to be the other way around.
So what is the WSDL from the vendor used for?
.NET might have a problem with this WSDL.
1- it has lots of nillable elements. They should be defined as minOccurs="0" instead.
2- your ArrayOfArrayOf_xsd_float defines a second element called "item" which has a different type from the previously define element called "item". (It shouldn't be a problem, but they are both qualified names, and perhaps .NET objects.)
So-- is the vendor reporting problems implementing a service based on the WSDL you've provided?
Anne
On 11/14/05, Michael Wille <[EMAIL PROTECTED]> wrote:
Anne,
Thanks for the response. The Service1.wsdl is the wsdl that was created
by the vendor. OrderService.wsdl is our documented API that the Vendor
must implement.
Thanks!
-Mike
Michael Wille
Applications Development Manager
Doner Advertising
248.827.8442
248.827.8323 FAX
>>> [EMAIL PROTECTED] 11/14/05 7:32 AM >>>
It's sending type infor for a doc/literal message? That doesn't make any
sense at all.
Please provide the complete WSDL and your client code.
Thanks.
Anne
On 11/13/05, Michael Wille <[EMAIL PROTECTED]> wrote:
>
> >>> [EMAIL PROTECTED] 11/13 9:34 PM >>>
> >Hello All,
> >
> >I'm at my wits end and decided to see if anyone can help. I'm a few
days
> past a deadline and
> >can't figure this one out.
> >...
> >Now, I saw one reply in all of the messages that I looked at that
said
> their problem was cause by
> >them setting an undefined QName type for a parameter.
> Sorry, I meant to finish that sentence before sending. I checked, and
I
> am setting QNames for parameters and a return type, but they all
appear
> valid.
> -Mike
>
