Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Im starting a Restful architecture (using JBoss Resteasy and Spring), i already did the basic setup (division of layers, configuration, content negotiation, URI design, etc). Its almost OK, to finish it, i still need clear some questions, that are:
Should i use a XMLSchema validation for my services? When i need it? Its OK with the REST good practices ?
What about your opinion?
Thanks!
A simple way to think of XML Schemas (XSD) would be as strong typing for your XML definitions. The biggest advanage being that you could provider the XSD in place of WSDL so that people understand your message/payload definitions. The biggest downside being you have a much tighter platform so partial fragments could be much more difficult. If you are consuming your own stuff and not providing public APIs then XSD may or may not be useful.
As I do more with XML I have started to write the related XSD files so members of my team see the options in a known way. We can also use tooling to validate that inputs and outputs are formatted correctly and the XSD files even provider Intellisence for the related XML files within Visual Studio (I work primarily with .Net)
Long story short, it’s up to you.