Either WSDL or wsimport and wsdl (mono) are horribly broken

**EDIT** I started off with the example given below, but I have now: - Tried the example from the W3C spec. After fixing another error (binding was called `StockQuoteSoapBinding` in one place, `StockQuoteBinding` in another), it gives the same issue. - Tried the mono generator `wsdl` to see if `wsimport` was to blame. It gives an equivalent error. So it seems to me that despite all the hype about SOAP, it doesn't actually work - at least not as advertised. I can't believe nobody has run the most findable examples of wsdl through these generators. **Original Question** wsimport is failing on the following wsdl: With: parsing WSDL... [ERROR] Schema descriptor {http://example/schema/OrdersService}GetOrders in message part "parameters" is not defined and could not be bound to Java. Perhaps the schema descriptor {http://example/schema/OrdersService}GetOrders is not defined in the schema imported/included in the WSDL. You can either add such imports/includes or run wsimport and provide the schema location using -b switch. line 35 of file:test.wsdl
"... it doesn't actually work ..." -- I would have to agree. Every time I have to touch SOAP, I know I'm in for a programming clusterbomb. If this is the industry standard for interoperating over a wide area network, we're screwed.

以上就是Either WSDL or wsimport and wsdl (mono) are horribly broken的详细内容,更多请关注web前端其它相关文章!

赞(0) 打赏
未经允许不得转载:web前端首页 » JavaScript 答疑

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址

前端开发相关广告投放 更专业 更精准

联系我们

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

微信扫一扫打赏