OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] reasons why an XML instance must be validated with a XML schema

On Sep 9, 2008, at 11:05 AM, ilango wrote:

I just started working on a project that uses JMS/WebSphere MQ with non-J2EE systems to build an enterprise system. We would be using XML for all the request/response message flows that take place between two system (for example, a JMS Listener and one or more than one queues.

I was posed with the following scenario: Our Listener Module submits document requests in XML formatted data into an input message queue monitored by a document generaton engine.
The need for validating the XML naturally arises.  Should the XML be validated against an XML schema.
The question they raised was:
If so, why should we use XML schema to validate XML?

It might be wise in the beginning (development/testing) to ensure your system is working as advertised, but I don't see why you would need to do it for every instance at runtime. The two systems you mention don't sound like you would be taking things from the wild, rather building the structures up in your own code that you control. So, probably parsing the document to find if there are inappropriate nulls or java types would be plenty.


So this is the question I am trying to answer for myself and for my team here.

Any suggestions, ideas are gratefully accepted.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS