• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

ws-i compliance questions

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

It seems the wsi-tools@ws-i.org mailbox cannot be reached.
Is the mail address still correct?


Further, I have some questions about WS-I BP 1.1 Compliance Analyzer test results. It would be
nice to get response on it.

Background:
Our requirement is to be WS-I Basic Profile 1.1 compliant for our Web Service created
from a designed WSDL (generating all the classes through JAX-WS 2.0).
We performed all the steps including generating the SOAP message traces.
I see several "missing input" entries. These have been checked manually.

Issue:
Still some questions remain for 10 of the requirements showing "missing input".
I hope I can get clarification on them.

Requirement - Question
R1014 - What could be wrong in WSDL/XSD/message that would explain this "missing input"?
R1001 - What could be wrong in WSDL/XSD/message that would explain this "missing input"?
R1031 - <faultcode>soap:Server.ProcessingError</faultcode> should be changed to <faultcode>soap:ProcessingError</faultcode>, right?
R1132 - We are compliant, we are using POST method, right?
R1112 - Why is this reported as "missing input"?
R1114 - We are only using POST, so why is this reported as "missing input"?
R2213 - Why is this reported as "missing input"?
R2712 - What could be wrong in WSDL/XSD/message that would explain this "missing input"? Something with the fault exceptions?
R2740 - Is this a fault in our solution? There is no fault element inside soapbind.
R2744 - Is this "missing input" not applicable for us?

One more thing.
In our WSDL file we have the following, does this mean we are not compliant to WS-I BP 1.1?
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"


Below are the WSDL and XSD contents.


kind regards,
Rene







 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic