XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Technical Forum » Command line option for your file Validator
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + Conerting Excel to XML (5)
-> + count the number of 1 appearin... (10)
-> + Import validation errors (2)
-> + Custom Validation Saxon (4)
-> + How Can i Check if else condit... (2)
-> + Stylus Studio 2009 Ent still b... (2)
-> + cannot download SS2009 (2)
-> + Use of import-schema wants sch... (4)
-> + Replacement Install Media/Bits (3)
-> + XML to Flat File (5)
-> + Select one of multiple attribu... (13)
-> + Web Service - SOAP Error (3)
-> + I find a BUG in stylus studio ... (8)
-> + Text to XML conversion issue (2)
-> + Fixed width flat files (3)
-> + Stylus Studio Crashes when val... (3)
-> + XSL Changes doesn't reflect in... (2)
-> + Custom Conversion Definition T... (6)
-> + Support for UK EDI Tradacoms ... (2)
-> + How to find and remove all ins... (2)
-> + XML to cobol Sequential file (2)
-> + Pipe delimited flat file conve... (2)
-> + Cannot Function Block > DataDi... (3)
-> + License Authentication failed (2)
-> + Flat File Conversion (3)
-> + Struzzo.exe sing 50% of CPU (2)
-> + Saxon9 Transformation error ha... (2)
-> + com.ddtek.xquery3.XQQueryExcep... (10)
-> + XML attribute name (2)
-> + JAVA and XML (2)
-> + DB Connection Error (3)
-> + Dicstionaty Librarys for other... (2)
-> + Passing parameters (3)
-> + Xmlconverter does not work (2)
-> + non-printing characters in Fil... (3)
-> + Including row nos while conve... (5)
-> + Getting Evaluation Copy except... (2)
-> + SS 2008 R2 Bug? (4)
-> + Java Heap Space (2)
-> + generate report from .xsl file... (3)
-> + Can't encode 0x4 in text (3)
-> + Recognize Japanese Characters (2)
-> + converting .xsl to xml using c... (2)
-> - Uninstall doesn't clean up reg... (1)
-> + CDISC (5)
-> - creating database from XML sch... (1)
-> + error: side-by-side configurat... (3)
-> - How to convert pdf into rdf fo... (1)
-> + Apache FOP (5)
-> + XPath Query Editor 'Buggy' (3)
-> - Feature request (1)
-> + XML Convertors (2)
-> + XMLConverters version 3.2.0.0 ... (2)
-> + JVM/stylus studio abort on sav... (3)
-> + using oasis catalog in pipelin... (6)
-> + Another whitespace issue with ... (2)
-> + saxon 9.1.0.2 (2)
-> + xslt change namespace (4)
-> - xslt change namespace (1)
-> + HL7 Conversion (3)
-> + mixed content mapping (2)
-> + HL7 to XML to HL7 (5)
-> + newest version of Saxon SA? (3)
-> + ORM / ORU Seqments (7)
-> + XSLT is causing Java.lang OutO... (3)
-> + Create POJOs from EDI (4)
-> - Embedded message (1)
-> + How to create Documentation fo... (2)
-> + xslt transformation (2)
-> - remove BOM (1)
-> + Changing data as it goes into... (5)
-> + How to (graphically) map one X... (2)
-> + Stylus Studio 2008 Release 2 -... (2)
-> + keyboard shortcuts to switch b... (2)
-> + Help with getting Output XML f... (8)
-> + Document created from schema (2)
-> + XSD Validation error (2)
-> + Set the value of an attribute ... (2)
-> + Saving as XML, Source Data Typ... (2)
-> + Own templates in file/new (4)
-> + Does Stylus Studio support the... (2)
-> - How to transform XML file to T... (1)
-> + Extract XML file from a HTML s... (2)
-> + Crashing, high cpu usage, larg... (6)
-> + Creating an xml document based... (2)
-> + Problem with restriction (2)
-> + EDI Invalid date time error (2)
-> + How to Compose a Web Service C... (5)
-> + Java Complie errors with XML C... (2)
-> + Creating xml file from CSV uss... (4)
-> + XML Converters (6)
-> + schema validation (15)
-> - 9/30 Customer Showcase Webinar... (1)
-> + ETL (2)
-> + xsd:sequence question (3)
-> + contains an invalid path (5)
-> - Custom converter to map flat f... (1)
-> + validating a 4.01 transitional... (2)
-> + Cannot Use Stylus Studio On Mu... (5)
-> + Missing DB to XML option (2)
-- Previous [901-920] [921-940] [941-960] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
(Deleted User) Subject: Command line option for your file Validator
Author: (Deleted User)
Date: 03 Sep 2003 10:30 AM
I have asked before, but do you have a command line version of the schema validator like you do for the xsl engine.

The reason I ask is that we have found your validator the most accurate and would like to do batches of files when we make lots of changes.

Thanks
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 04 Sep 2003 11:46 AM
At 04.53 03/09/2003, you wrote:
>From: "Martin Roberts"
>
>I have asked before, but do you have a command line version of the schema
>validator like you do for the xsl engine.

No, we don't have such a command line utility (yet).
If what you need is simply a valid/invalid report for an XML document, you
can try creating a dummy XQuery document (containing just a "Document is
valid" string - quotes included), and running

stylusxql Dummy.xquery xml-to-validate.xml stdout

You will see either the "Document is valid" message, or the first
validation error.

Hope this helps,
Alberto

Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 05 Sep 2003 07:10 AM
Does this do schema validation only if full schema location info is in the XML file? I want to validate files against schemas without having to refer to xsi:schemalocation in the file?
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 05 Sep 2003 10:21 AM
At 07.33 05/09/2003, you wrote:
>From: "Martin Roberts"
>
>Does this do schema validation only if full schema location info is in the
>XML file? I want to validate files against schemas without having to
>refer to xsi:schemalocation in the file?

Validation will be performed only if the source XML document refers to a
schema (either DTD or XSD). If you want to force validation against a
well-known schema, you need to change the dummy XQuery document to be:

import schema "http://www.mycompany.com/myNamespace" at "example.xsd"

if(validate { /element() }) then
"Validation succeeded"
else
"Validation failed"


Hope this helps,
Alberto

Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 11 Sep 2003 05:31 AM
Thanks for this, would it work if I imported several schemas associated with several namespaces?
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 11 Sep 2003 06:07 AM
I have attached a file showing multiple schemas being imported. I got the warning:

No caching of grammar set, a grammar with same key found in cache pool

What does this mean?


Applicationtesting.xquery
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 12 Sep 2003 04:00 PM
Hi Martin,
the file you attached is importing just one schema; also, can you send me
the XML document being validated and the schema named in the XQuery document?

Thanks,
Alberto
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 15 Sep 2003 11:41 AM
Sorry I uploaded the wrong file:


Applicationtesting1.xquery
Xquery File
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 15 Sep 2003 11:45 AM
And the Example that should validate


DocumentPurchaseOrderProvide.zip
Example XMl file that should validate
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 16 Sep 2003 01:00 PM
Hi Martin,
can you send me (privately, if you prefer) also the schemas? I tried
looking at the telcob2b website, but they don't seem to be publicly available.

Thanks,
Alberto
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 18 Sep 2003 05:33 AM
Schemas sent privately
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 18 Sep 2003 11:21 AM
Hi Martin,
the error is caused by the fact that one of the schemas is already
including the first one (Order.ServiceRequest.xsd imports Order.xsd), so
Xerces throws an exception when we try to add the second copy to the cache.
A workaround could be not to import the Order.xsd schema, relying on the
fact that it's referenced by Order.ServiceRequest.xsd.
We will work on finding a way to convince Xerces that this is not really an
error.

Hope this helps,
Alberto
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 23 Oct 2003 09:43 AM
Alberto,
Sadly removing the references to imported schemas does not resolve it as two of the lower level schemas import the same schema. This does not seem to be a problem with your client side validation, why should xerces throw it out when doing it within the XQuery?

I removed all bar the Notification and the Wholesale Calls but these both import the same schema. With out these imports you can not validate the schemas individually, so it seems strange that you can not validate the xml instances against these. Is this a known bug in xerces?
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 23 Oct 2003 10:09 AM
Hi Martin,

At 10.07 23/10/2003 -0400, you wrote:
>From: "Martin Roberts"
>
>Alberto,
>Sadly removing the references to imported schemas does not resolve it as
>two of the lower level schemas import the same schema. This does not seem
>to be a problem with your client side validation, why should xerces throw
>it out when doing it within the XQuery?
>
>I removed all bar the Notification and the Wholesale Calls but these both
>import the same schema. With out these imports you can not validate the
>schemas individually, so it seems strange that you can not validate the
>xml instances against these. Is this a known bug in xerces?

Yes, it is a known bug in Xerces; when the XQuery processor is adding all
the schemas to the single schema cache, an exception is thrown if a schema
happens to be already in the cache. This situation is not considered an
error when validating an XML file against a single schema document.

Alberto

Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 23 Oct 2003 12:14 PM
Alberto,
I can use your schema validator to validate xml instance documents against the schemas I sent you without the failure. This works if I do an explicit schemaLocation call. I suppose this does not attempt to load the cache?

Is there a proposal to fix this bug in xerces either by yourselves or others?

Thanks
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 23 Oct 2003 12:59 PM
At 12.38 23/10/2003 -0400, you wrote:
>From: "Martin Roberts"
>
>Alberto,
> I can use your schema validator to validate xml instance documents
> against the schemas I sent you without the failure. This works if I do
> an explicit schemaLocation call. I suppose this does not attempt to load
> the cache?

Yes; the schema cache is involved in the picture when you use the "import
schema" keyword. You want to use this keyword when you know that the XML
file you are going to validate doesn't have a reference to a schema, and
you want to assign one to the namespace it uses.


>Is there a proposal to fix this bug in xerces either by yourselves or others?

The fix has already been identified; but it's a change in the behavior of
the parser, and it's not still clear if this change would break something
else inside Xerces.

Alberto

Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 16 Jul 2004 11:12 AM
I have used the technique in the previous posting (finally) and I find I get the following error:

Warning: No caching of grammar set, a grammar with same key found in the cache pool.

I have attached the xquery file.


Documentvalidation.xquery
xquery to schema validate file

UnknownAddOrder-Cease.xml
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 16 Jul 2004 11:45 AM
I have sorted out the previous error as you had explained in the previous emails. unfortunately the validator is not picking up incorrect XML. Can you please confirm that the validate command actually checks against schemas and not just for well formedness?
Postnext
(Deleted User) Subject: Re: Command line option for your file Validator
Author: (Deleted User)
Date: 16 Jul 2004 12:15 PM
At 11.27 16/07/2004 -0400, stylus-studio-tech Listmanager wrote:
>From: "Martin Roberts"
>
>[...]
>I have attached the xquery file.

Hi Martin,
can you send me the XQuery file? It looks like the BBS software didn't
store it properly, as clicking on the link open a "file not found" page.

Thanks,
Alberto


Postnext
(Deleted User) Subject: Command line option for your file Validator
Author: (Deleted User)
Date: 16 Jul 2004 12:05 PM
I seem to have got it working by using the validate strict command.

However, it does not fail the if statement it bombs out altogether.
Is there a way to force it to fail gracefully?
Posttop
(Deleted User) Subject: Command line option for your file Validator
Author: (Deleted User)
Date: 16 Jul 2004 12:52 PM
Hi Martin,

>I seem to have got it working by using the validate strict
>command.
>
>However, it does not fail the if statement it bombs out
>altogether.
>Is there a way to force it to fail gracefully?

Unfortunately the "validate" command in XQuery is designed to report
an error when validation fails. The good news is that Stylus now ships
with a command line tool that exposes the internal validator.
Its syntax is:

usage: StylusValidator [-q] [-noval] [-schema file]* filename
-q: quiet mode (errors are not printed)
-noval: check only for the document to be well-formed
-schema: force validation of the document against this XML Schema

So you can run
StylusValidator -schema http://.../schema.xsd MySample.xml
to force the validation of the sample XML file against the given schema,
and have a list of the errors.

In a future release the capability of validating against non-bound
schemas will be available also from inside the IDE.

Hope this helps,
Alberto
   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.