This week's book giveaway is in the JavaScript forum.
We're giving away four copies of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js and have Paul Jensen on-line!
See this thread for details.
Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

WSDL schema verification  RSS feed

 
Viru Sagar
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Could anyone tell me how a WS run time environment (Axis,Systinet etc.) validate a WSDL file against the standard WSDL schema.
I think they do not bundle WSDL schema file, rather refer directly to the weblink.

I am asking this because I was reading "http://java.boot.by/wsd-guide/ch01.html#c1s1" study guide it mentions the following...

"If a document-literal binding in a DESCRIPTION does not specify the parts attribute on a soapbind:body element, the corresponding abstract wsdl:message MUST define zero or one wsdl arts."

Latest WSDL schema does not mention about parts atribute in "binding" element.Please let me know if this is related to XML schemas concept which i am not getting.
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That rule comes from the WS-I Basic Profile 1.0a:

R2201 A document-literal binding in a DESCRIPTION MUST, in each of its soapbind:body element(s), have at most one part listed in the parts attribute, if the parts attribute is specified.


XML Schema has no way of enforcing this rule.
 
Viru Sagar
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for your reply.
One more question.

How does runtime environment validate the wsdl xml file?
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Viru Sagar:
How does runtime environment validate the wsdl xml file?


In most cases there is no reason to reference the WSDL during runtime. WSDLs aren't supposed to change that often and if you change a WSDL drastically it is usually simpler to service the new WSDL over an endpoint on a new URI. WSDLs are most often referenced during compile-time when a WSDL-to-code (in the case of Java, WSDL-to-Java) code generator creates a representation that can be manipulated through the host programming language. Obviously the WSDL has to be well-formed XML, otherwise the XML parse would fail. However there may be little point in performing a full-blown XML validation on the (full) WSDL as the code generator will usually not support the complete WSDL functionality laid out in the WSDL XML Schema � so it will simply generate an error when it encounters an element or attribute that it does not understand (or that is missing).

Then of course there are other WSDL aspects not covered by XML validation, like the checking for WS-I Basic Profile compliance . These checks are not mandatory but can be handled by separate vendor tools; otherwise compliance can be checked through some kind of manual review process.
 
sasank ch
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think there is something called tcp/ip monitor in eclipse with which you can try to valiate , good tool to debug also
 
Ulf Dittmer
Rancher
Posts: 42972
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by sasank ch:
I think there is something called tcp/ip monitor in eclipse with which you can try to valiate , good tool to debug also


TCP/IP Monitor is used to observe textual TCP traffic (like HTTP, and SOAP on top of it) in transit. It has nothing to do with WSDL or schemas.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!