• 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

wsdl schema validation and validation message

 
Ranch Hand
Posts: 125
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
All,

I am using the WSDL first approach for web services development using Apache CXF.
A number of element is the xml schema are mandatory and I have implemented validation using the handler.xml.

The issue I face is I am not able to get which field in the payload is causing the validation error
I get a message something like

<faultstring>cvc-datatype-valid.1.2.1: 'q' is not a valid value for 'integer'.</faultstring>




Let me know your thoughts on how can I go about trapping the exact xml element names in the error message as part of the validation.


Regards,
 
Mohit Sinha
Ranch Hand
Posts: 125
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can someone provide any pointers on how this can be achieved.
I searched a lot but did not seem to be find any helpful example.
 
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi!
First I would use soapUI to test the web service - if it can issue requests and receive responses then the problem is most likely with the client.
If you need to examine requests and responses to/from the web service, then you can use WireShark or some TCP monitoring tool.
A third alternative is to implement a SOAP message logging handler on the web service side. Such a handler can log incoming and outgoing SOAP messages and thus let you discover where the problem is.
Best wishes!
 
Ranch Hand
Posts: 491
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Here is the link http://articles.carbonrider.com/2010/03/21/apache-cxf-code-first-schema-validation-demystified/

supporting Ivan's suggestion on using TCP Mon or SOAP UI.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic