ser is able to tell you what the error was. Even if parser showed
you only *one* error, you should correct that error (and similar
errors), and move forward.
--
Regards,
Mukul Gandhi
ee spurious integers appearing in the output at the end.
Can this be classified as a low priority bug ? Should I put this in Jira ?
Using the SAXParser, this problem doesn't come.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Jan 9, 2008 4:34 PM, Mukul Gandhi <[EMAIL PROTECTED]> wrote:
> NodeList nl = document.getElementsByTagName("QUANTITY");
> for (int i = 0; i < nl.getLength(); i++) {
> System.out.println(nl.item(i).getFirstChild().getNodeValue());
> }
I
ld I do to achieve this?
I would be thankful for the help to solve this problem.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
'll appreciate, how to approach this problem correctly with Xerces-J.
On Jan 11, 2008 10:38 PM, Mukul Gandhi <[EMAIL PROTECTED]> wrote:
> Following is the XML I want to create (in this lexical form only):
>
>
>
> ]>
>
> &x; world
>
--
Regards,
Mukul G
EMAIL PROTECTED]> wrote:
> Are you using a Transformer class to serialize the document ? If so,
> then try to use the LSSerializer instead to serialize the DOM and you
> will also have the DTD subset in your output.
>
>
> Regards
> Dick Deneer
--
Regards,
Mukul Gandhi
-
On Jan 13, 2008 10:34 PM, Dick Deneer <[EMAIL PROTECTED]> wrote:
> Have you tried to document.appendChild(docType) ?
This does not solve the problem. I am getting the same output (i.e.,
without the internal DTD subset).
--
Regards,
Muk
ment object, including the internal DTD
subset). Should we ask for such an API enhancement?
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Jan 14, 2008 9:35 AM, Mukul Gandhi <[EMAIL PROTECTED]> wrote:
> But LSSerializer.write has following signature (copied from Xerces javadocs):
>
> public boolean write(Node nodeArg, LSOutput destination)
> throws LSException
>
> Shoul
e.setInternalSubset("...");
> document = domImplementation.createDocument(null, rootName,
> documentType);
>
> Then Serialize the document object...
>
> -Prashant
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
istant) future
> but I think it's unlikely to change.
Thanks for the assurance ... Since this Xerces specific extension
fills a critical gap in DOM APIs, I request that Xerces preserves this
functionality in future releases.
--
Regards,
Mukul Gandhi
---
;... Three things see no end: A loop with exit code done wrong,
> A semaphore untested, And the change that comes along. ..."
> -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish
> (http://www.ovff.org/pegasus/songs/threes-rev-11.html)
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ease shift to Xerces-J 2.9.1 to have a better
compliance and performance.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ontent will be null.
I am presently not sure, what the SAX standard says. I'll leave it for
others to comment.
I'll try this scenario myself, and share my findings.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mai
:
> I suppose the SAX spec doesn't forbid that but Xerces doesn't do that.
> You'll get a startElement() event followed by an endElement() event. The
> only exception to that is if you're doing schema validation and the
> validator inserted a default element value. Then you'll get a characters()
> event.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!-start element-!
--end element--
##
##
#uvw#
!--end element--!
--characters--
!--characters--!
--end element--
##
##
#root#
!--end element--!
This looks perfectly ok to me.
(you wrote correctly
ver be null.
> This could also be deducted from the general principle if the
> contract doesn't explicitly state null values are permitted - they
> are not.
I agree to this. Thanks for the clarification.
--
Regards,
Mukul Gandhi
-
Yadav <[EMAIL PROTECTED]> wrote:
>
> I downloaded the latest version of Xerces that I suppose is 2.9.1
>
> Thanks
> Barun
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional com
ache.xerces.impl.Version
> Implementation-Version: 2.9.1
> Implementation-Vendor: Apache Software Foundation
> Implementation-URL: http://xerces.apache.org/xerces2-j/
>
>
> I am using JDK 1.5.
>
> Any other reason what could be wrong
> Thanks
> Barun
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
11:05 AM, Barun Kumar Yadav <[EMAIL PROTECTED]> wrote:
> The Xerces version is 2.9.1
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
; in the text node?
>
> I have no control of the source, so i need to make xerces to accept '&' .
>
> Thank you for any idea.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
is just dumped the doc
>
> for all these I see the return code as 0 (ie echo $? gives 0)
>
> and there are a couple of other examples which do not seem to do any thing
>
> What is one supposed to conclude from these examples ?
>
ema
grammar error flagged by Xerces.
1) Is it fine to use xs:choice to select one of two (or many) xs:sequence ?
2) Can this be a possible Xerces bug?
3) What will be the correct XSD 1.0 Schema for this requirement? Is
this problem solvable with XSD 1.0? If not, would XSD 1.1 bring some
f
[1] http://www.w3.org/TR/xmlschema-1/#cos-nonambig
> [2]
> http://xerces.apache.org/xerces2-j/features.html#validation.schema-full-checking
> [3] http://www.w3.org/TR/xmlschema11-1/#cAssertions
>
> Michael Glavassevich
> XML Parser De
at org.apache.xerces.jaxp.SAXParserImpl.getProperty(Unknown Source)
at SchmValidateSAX.parseFile(SchmValidateSAX.java:32)
at SchmValidateSAX.main(SchmValidateSAX.java:17)
It seems, the XML parser does not set this property after it has
parsed and validate
> Hi Mukul,
>
> The property name you're querying is incorrect. It should be
> "http://java.sun.com/xml/jaxp/properties/schemaSource"; not
> "http://java.sun.com/xml/properties/jaxp/schemaSource";.
>
> Thanks.
>
> Michael Glavassevich
> XML
On Mon, Jun 16, 2008 at 9:42 PM, Mukul Gandhi <[EMAIL PROTECTED]> wrote:
> But when I change the program to (and remove the hint,
> xsi:noNamespaceSchemaLocation from the XML document):
>
[1] - Sorry, this should be [2]
> parser.setProperty("http://java.sun.com/xml/jaxp/
am, File, Object[], etc...). If you want to get the values of
> schema location hints in the document then you need to write a
> ContentHandler which does the work.
>
> Thanks.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
&
7;m parsing a xml file and I need the xsd element type when parsing each
> element of the xml. The validation is easy but not accessing the xsd type
> when parsing the element. Is it possible to get that information?
>
> Regards and many thanks,
>
you can get location
of the error/problem as,
e.getLineNumber()
e.getColumnNumber()
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
column
numbers for the errors/warnings is not possible.
But I get the correct line numbers for errors/warnings if I use,
StreamSource as the XML document source.
So my below suggestion is wrong, for DOMSource. Sorry, it was not tested ...
On Mon, Oct 27, 2008 at 9:06 AM, Mukul Gandhi <[EM
e, some URIs don't point to a valid Schema (for e.g.,
http://www.w3.org/ns/wsdl). The Schema processor gives syntax errors
on these invalid Schema references.
Hope I am right ... :)
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Tue, Dec 16, 2008 at 4:15 AM, Shah Asrani wrote:
> I need to create a DOM from scratch using XPath expression.
I think this is not possible. A XPath expression selects a particular
nodeset from the XML tree. It does not represent the complete tree.
--
Regards,
Mukul Gan
read.
> /a/b/c
We can construct a small (perhaps very small) subset of the full DOM
tree for this XPath expression. With this XPath expression, we cannot
know how many b or c children are there.
--
Regards,
Mukul Gandhi
-
y of Schema documents. Only one
Schema will work fine in this case (which includes the child schema).
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail
erformance.
On Fri, Feb 20, 2009 at 6:35 PM, ajay bhadauria wrote:
>
> Hi,
>
> I would like to know that is there any upper limit on size of the XML file
> which can be parsed and also for Schema validation ? Any link or any
> documentation ?
>
> Thanks
t; Is there another interface that I can use that allows me to do some more
> specific error handling?
>
> Cheers,
>
> Uwe
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
mplex type.
Once you have the ElementPSVI object for the element, you can access
the element type information using the available APIs.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
Fo
System.setProperty("javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema","org.apache.xerces.jaxp.validation.XMLSchemaFactory";);
Michael, might be able to provide a more correct answer :)
--
Regards,
Mukul Gandhi
-
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Also the code that I am using is the same as the one Gunni has written in
> the fo
ElementPSVI class.
> However, it seems I have not found the right method to do it.
>
>
> maxOccurs="unbounded" />
>
>
> Is there a way I can tell the minOccurs and maxOccurs of the sequence of an
> element in using JAX
/external-noNamespaceSchemaLocation";,
> xsdFile);
> parser.parse(new FileInputStream(xmlFile), new DefaultHandler()
> {
> public void error(SAXParseException e) throws SAXException {
> final boolean status = false;
>
:
>
> Hello,
>
> I want to add namespaces declaration on parent if child and parent have
> different namespaces.
> My wish is to have output like that:
>
> http://test1";>
>
>
>
>
> instead of what i have actually
>
> http://test1&
anybody knows please reply asap whether it is possible or not ?
>
> AB
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
.
>
>
>
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="www.ncr.com/ocz PIDSchema.xsd"
> name="SAHI-EasyPoint 3XXX Series (5020 UEPP Upgrade)"
> createMode="both&qu
e solution for this problem ?Thanks in advance.
>
> Regards,
> Naga.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
er of the command line. Or is there a
> wrapper available where a method exist to get the errors as a string,
> callable from a java application?
>
> Greetings
>
> Hle
--
Regards,
Mukul Gandhi
--
includes, ideally should not repeat.
> 1) c.xsd gets included twice, is this allowed?
>From XSD syntax point of view, this may be correct. But from design
point of view, this is probably a bad practice.
--
Regards,
Mukul Gandhi
esn't look a
good design, as we are including a schema twice. Only once schema
inclusion should be sufficient, to get the required schema components
into the parent schema.
--
Regards,
Mukul Gandhi
-
To unsubscrib
gt; IBM Toronto Lab
> E-mail: mrgla...@ca.ibm.com
> E-mail: mrgla...@apache.org
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
he Xerces Java
> has xml Vulnerability issue.
> Whats your call on this.
>
> Regards
> Atul Parti
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
is using APIs, which are not
present in Xerces-J 2.9.1/2.10.0, which is most likely because
Xerces-J 2.9.1+ is vastly better than, 1.4.3).
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
suggest API usage optimizations.
I am also curious to know, how big a DOM structure you are trying to
produce (for e.g, if you'll serialize it, how much big a XML document
will be produced)? What is the size of physical memory of the box,
where you are running this
is not necessary.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
please, see:
http://xerces.apache.org/xerces2-j/faq-general.html#faq-1
On Wed, Feb 3, 2010 at 7:39 PM, Atul Parti wrote:
> Hi,
>
> which is the command to know which XERCES Java are we using.
>
> With Regards
> Atul
--
Reg
e to do before
> executing samples? Why are there two types of directories called
> "tests" and "samples"?
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
w3.org/1999/XMLSchema-instance";
> xmlns="http://www.cadit.it/SI/SIGS534";>
>
> …
>
>
>
> …
>
>
>
>
>
> Here is the XML Schema portion:
>
> …
>
>
>
> …
>
>
>
> Is it a Xerces Bug? (I use Xerces version that comes with JDK 1.5)
>
>
>
tance";.
Great eyes, Michael :) I missed that.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
revision and compiled it but had no luck
> with my schema.
> Any hints would be great. Thanks in advance,
>
> Felix
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
Fo
definition at a later
> point of that chain?
I don't know for sure, a right answer to this. But my feeling is, that
a chained specification of overridden components should be possible.
I suggest, please ask "XML Schema" language questions on "
a looks like this:
>
>
> http://www.w3.org/2001/XMLSchema";
> targetNamespace="http://www.zeec.de";
> xmlns="http://www.zeec.de";
> elementFormDefault="qualified">
>
>
>
>
On Fri, Feb 19, 2010 at 9:38 PM, Michael Glavassevich
wrote:
>> 2. Use the jaxp.SourceValidator sample, with -xsd11 flag
>
> This isn't really a second method. It's just a sample demonstrating the
> first.
You're right, Michael
ption
> {
>
> if( localName.equals( "items" ))
> {
> //inject namespace uri...
> super.startElement(
> "http://xml.prediggo.com/schema/ItemsSchema"; , localName, qName,
> attributes);
> }
>
your example), and all type alternatives evaluate
to false, then the element get's the default type for the element
(which in this case is, xs:anyType -- and therefore, the element will
be valid in this case, if all alternatives would evaluate to fa
ion-valid: Value 'value3' is not
> facet-valid with respect to enumeration '[value1, value2]'. It must be
> a value from the enumeration.
> ---
> (I get this using my own complexType errors. So something like this
> would be nice - it is easier to understand tha
>
at 10:19 AM, Hiranya Jayathilaka
wrote:
> I think most Java projects around are still on JDK 5. So I think JDK 5 is a
> more suitable target at this point.
> Thanks,
> Hiranya
--
Regards,
Mukul Gandhi
-
To unsub
y for a little confusion with wordings in my mail. I actually
meant JDK 1.4 support for XML Schema 1.1 branch.
So + 1 for that :)
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For addit
ried the
> XSSerializer sample.
>
> I modified the method main() it very slightly and commented out some things
> to get rid of all warnings:
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apach
n't
> account for that. The version altered by my co-worker suffers from the same
> problem.
>
> - Mikael
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.or
I'm glad the problem is solved :)
On Tue, Aug 10, 2010 at 5:14 PM, Mikael Åsberg wrote:
> Hi Mr Gandhi, yes, now it works. Thanks!
>
> - Mikael
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-
tps://www.ida.liu.se/~TDDD43/themes/theme3labmaterial/dataset/psimi/MIF254-sml.xsd
>
> Basically seems to be the same problem but for the first argument this time.
>
> - Mikael
--
Regards,
Mukul Gandhi
---
it looks like
XSSerializer has), a bug report helps Xerces team to track defects (to
assign/prioritize/resolve etc).
You may create a bug report here, selecting Xerces-J as a component
(and of-course signup for an account first).
http://issues.apache.org/jira/
--
Regards
en a bug report ourselves :)
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
now, unless you find any other
problem with XSSerializer :-)
On Wed, Aug 11, 2010 at 1:15 PM, Mikael Åsberg wrote:
> So no more fixes until a JIRA issue has been opened?
>
> - Mikael
--
Regards,
Mukul Gandhi
-
T
SSerializer :)
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
nd column numbers should be
sufficient.
[1]
http://xerces.apache.org/xerces2-j/javadocs/api/org/xml/sax/SAXParseException.html
[2]
http://xerces.apache.org/xerces2-j/javadocs/api/org/xml/sax/SAXException.html
--
Regards,
Mukul Gandhi
-
response to the
> client, that the element xy isn't valid. But if there is no way to get the
> element name by the sax exception i'll maybe parse the element by the line
> and column number out of the xml and send this and the exception back as the
> result.
>
> Best r
OP in a SAX way.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
etLocalName(Node_URI.java:64)
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
to use in Xerces for reading the Schema and determining
> the valid elements from an arbitrary context in the document, or perhaps an
> example of doing this with Xerces?
>
> Thanks,
>
> Don
--
Regards,
Mukul Gandhi
ns".
So we don't yet implement in Xerces-J "DOM Level 3 Validation API",
which you pointed. Were there any architectural reasons that "DOM
Level 3 validation API" was not found to be fit to be implemented in
Xerces-J? Or we haven't implemented this API in Xer
ch/?q=%22DOM+Level+3+Validation%22+order%3Adate-backward
> [2] http://markmail.org/message/vpu4yegi2yzzfekv
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrgla...@ca.ibm.com
> E-mail: mrgla...@apache.org
--
Regards,
Mukul Gandhi
--
ut using XSLT for example can save numerous design hours
and would help maintainability too.
> What is the proper way to transform the stream of SAX events into
> another stream of SAX events.
I would suggest to have a little design thinking, before emba
ng to me is not good (i.e working with Java objects
and more-so a graph of extension objects in XSLT layer can get hard).
It look to me that this kind of approach is not using XSLT or even
Xerces appropriately.
--
Regards,
Mukul Gandhi
--
ment. But I've heard of tools (please try a web
search) which can generate a sample set of XML documents given a
schema as input.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For ad
ce"
> xmlns:yours="your-namespace" elementFormDefault="qualified">
>
>
>
> maxOccurs="unbounded"/>
>
>
>
>
> yours:label="Name Label"/>
> type="xs:string"/>
>
>
>
>
> (A valid instance document for this is:
>
>
>
>
> XYZ Phone system
> A12345
>
>
> )
>
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
ava -> ElementModel.java & so on). This may be an application
issue. You may run a debug session to see, which object along this
stack trace is null and on what data it is dependent on.
--
Regards,
Mukul Gandhi
-
To un
NPE there. The application is merely
> passing in an int to the item() method. That either returns a Node or null
> if the index isn't valid.
Thanks, Michael for the thoughts.
--
Regards,
Mukul Gandhi
-
ation. You may consider using some form of RDBMS storage
(and/or coupled with XML storage). Or a quick fix may be to, try for a
better concurrency/locking programming within your application.
--
Regards,
Mukul Gandhi
-
To
rough the graph to process the
> data. I wanted to understand what are the most efficient structures for the
> representation of a graph, ie Hashtable, matrices, etc. ...
> In addition, you have to give me some suggestions on how I can use the sax
> parser to
a bug with jaxp.SourceValidator sample, since it
isn't evaluating this validation episode correctly when iterative
execution is asked for (but for singleton execution, I can see that
result of XSD validation in this case is correct). But we need to
investigate this issue further, to conclude that what is exactly
wrong.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
"main" java.lang.AssertionError
> at
> org.eclipse.wst.xml.xpath2.processor.internal.types.QName.namespace(QName.java:236)
> at
> org.eclipse.wst.xml.xpath2.processor.DefaultEvaluator.name_test(DefaultEvaluator.java:1407)
--
Regards,
Mukul Gandhi
---
On Sun, Feb 19, 2012 at 7:30 AM, Mukul Gandhi wrote:
> org.eclipse.wst.xml.xpath2.processor.internal.types.QName.namespace.QName.java
my apologies for wrong typing.
the file corrected was,
org.eclipse.wst.xml.xpath2.processor.internal.types.QName.java (the
method was namesp
peHelper.isSchemaTypesIdentical
>> (complexTypeDecl, enclosingCTDefn);
>> // do not add attributes, from the base type. they will
>> be serialized as part of the base type serialization.
>> if (complexTypesIdentical) {
>> addAttributeToSchemaCompo
idate(Validator.java:127)
> at jaxp.SourceValidator.validate(SourceValidator.java:162)
> at jaxp.SourceValidator.main(SourceValidator.java:571)
>
>
> Thanks,
>
> jOrGe W.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
ser.parse(XMLParser.java:108)
> at
> org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1198)
> at
> org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.validate(ValidatorHandlerImpl.java:816)
> at
> org.a
t error, but if I do
>
> java -cp $CLASSPATH jaxp.SourceValidator -fx -xsd11 -a assertion.xsd -i
> number_bad.xml
>
> I don't get an error at all.
>
> Thanks,
>
> jOrGe W.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
trates
this), but there looks a different issue which needs to be
investigated. Thanks for creating a Jira bug -- it'll be actioned
appropriately.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: j-users-unsub
1 - 100 of 220 matches
Mail list logo
