The vendor implements the web service that we described in our OrderService.wsdl. This is just documentation of our API. Any vendor that is going to integrate with us must provide the CreateOrder end point. It is not the one used in the web service call.The other wsdl was the end result of the vendor's implementation of the CreateOrder service and is what is used in the service call.
We are having troubles calling the CreateOrder service that the vendor implemented. They are one of several vendors that have a CreateOrder service we call. We use the same client code to connect to all vendors. This is the first one that has had issue with our client call. It reports that the xml contains an undefined type because of the mismatch in case between orderItem and OrderItem. We could get around this error if we disabled sending of xsi:type. Thanks for the advice on the nillable, I follow that. Thanks, -Mike >>> [EMAIL PROTECTED] 11/14/05 2:27 PM >>> Please clarify. The vendor provides the service -- implemented in VB.NET <http://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 > > > > >
