StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POPerl XML::LibXML::Schema will stop validation on first error
primarykey
Id
3206672
data
AcceptedAnswerId
3223388
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-07-08T18:14:21.567
FavoriteCount
0
LastActivityDate
2010-07-11T14:30:45.513
LastEditDate
LastEditorUserId
0
OwnerUserId
386998
ParentId
0
PostTypeId
1
Score
1
ViewCount
1415
LastEditorDisplayName
text
Body
I'm trying to use the XML::LibXML::Schema to validate a xml file against a xsd. The problem is if my xml has multiple semantic issues the validation will die on the first one and not report the others. <pre><code> It finds the first error, no reference to <code><foobar/></code> bash-3.2$ ./test.pl test.xsd test.xml xmlfile <code><test.xml></code> failed validation: test.xml:14: Schemas validity error : Element 'foobar': This element is not expected. After I remove the first error, it finds another. "ten" is not an unsigned int xmlfile <code><test.xml></code> failed validation: test.xml:11: Schemas validity error : Element 'allocation': 'ten' is not a valid value of the atomic type 'xs:unsignedInt'. Changing "ten" to 10 fixes this issue bash-3.2$ ./test.pl test.xsd test.xml No issues found </pre></code> I would like to get a report of ALL the issues on a single run. Any ideas? Should I be using another module for this? Follows my Perl script and my xsd and xml files. Thanks for your help, Paulo <pre><code> xsd: <pre><code> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">  <xsd:element name="channel"> <xsd:complexType> <xsd:sequence> <xsd:element name="username" type="xsd:string"/> <xsd:element name="password" type="xsd:string"/> </xsd:sequence> <xsd:attribute name="name" use="required" type="xsd:string" /> </xsd:complexType> </xsd:element>  <xsd:element name="hotel"> <xsd:complexType> <xsd:sequence> <xsd:element name="date"> <xsd:complexType> <xsd:attribute name="from" use="required" type="xsd:string" /> <xsd:attribute name="to" use="required" type="xsd:string" /> </xsd:complexType> </xsd:element> <xsd:element ref="room" minOccurs="1"/> </xsd:sequence> <xsd:attribute name="id" use="required" type="xsd:unsignedInt" /> </xsd:complexType> </xsd:element>  <xsd:element name="room"> <xsd:complexType> <xsd:sequence> <xsd:element name="allocation" type="xsd:unsignedInt"></xsd:element> </xsd:sequence> <xsd:attribute name="id" use="required" type="xsd:string" /> </xsd:complexType> </xsd:element>  <xsd:element name="request"> <xsd:complexType> <xsd:sequence> <xsd:element ref="channel" maxOccurs="1"/> <xsd:element ref="hotel" maxOccurs="1"/> </xsd:sequence> <xsd:attribute name="type" use="required" type="xsd:string" /> </xsd:complexType> </xsd:element> </code></pre> xml: <pre><code><?xml version="1.0" encoding="UTF-8"?> <request type="test" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <channel name="channel"> <username>user</username> <password>pass</password> </channel> <hotel id="ten"> <date from="2009-07-07" to="2009-07-17"/> <room id="1"> <allocation>ten</allocation> </room> </hotel> </request> </code></pre> perl script: <pre><code>#!/usr/bin/perl use strict; use warnings; use Data::Dumper; #use Carp; use vars qw( $xsd $xml $schema $parser $doc ); use XML::LibXML; # # MAIN # my $xsd = $ARGV[0]; my $xml = $ARGV[1]; $schema = XML::LibXML::Schema->new(location => $xsd); $parser = XML::LibXML->new; $doc = $parser->parse_file($xml); eval { $schema->validate($doc) }; if ( $@ ) { warn "xmlfile <$xml> failed validation: $@" if $@; exit(1); } else { print "No issues found\n"; } </code></pre> </pre></code>
Tags
<xml><perl><xsd>
Title
Perl XML::LibXML::Schema will stop validation on first error
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPaulo SantAnna
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.