gmane.text.xml.xerces-j.user

debugging tools?

Jim Barnett — 2013-05-09T14:12:46

Are there tools that will help me debug a complex assertion?  I've tried using trace, but it doesn't seem to print out messages when it's inside an 'every' or a 'some'.   I've attached the example I'm trying to debug.  The assertion in line 26 of the schema should reject the <transition> in line 7 of sample.scxml, but it doesn't (so validation succeeds).  I can't tell if there's a logical error in my schema, or if I'm not using some element correctly.  Can someone give me some hints on how to debug the assertion's application?

Thanks in advance,
Jim Barnett
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe< at >xerces.apache.org
For additional commands, e-mail: j-users-help< at >xerces.apache.org

validating a XML file using XSD 1.1 with Xerces-J

Roberto Marabini — 2013-04-22T00:22:32

Hi,

    I am trying to write a XSD 1.1 schema that uses  XSD 1.1
assertions. I am able to repeat the examples described in the URL:
http://mukulgandhi.blogspot.com.es/2009/11/xsd-11-some-xsd-11-samples-running-with.html
so I guess my xerces-j installation is OK.

   When I tried to include an assert in my schema (I reproduce part of
it in the email and attach the full file) I got the error message:

[Error] kk.emx:33:14: cvc-assertion.3.13.4.1: Assertion evaluation
('defocusU ge defocusV') for element 'particle' with type '#anonymous'
did not succeed.

but defocusU is indeed greater than defocusV

Note that the commented lines

<!-- <xsd:assert test="t34 le 3" />-->
<!-- <xsd:assert test="< at >index le 3" />-->

work properly when uncommented

but

        <xsd:assert test="defocusU ge defocusV" />

does not. I guess the problem is that defocusU and defocusV are complextypes

any help will be welcomed

    thanks

               Roberto
=================

Schema

<?xml version="1.1" encoding="UTF-8"?>
<xsd:sche

problems using tokenize()

Jim Barnett — 2013-04-18T15:30:04

I'm having trouble getting tokenize() to behave the way I expect it to.  As before, I have an element with an attribute < at >target with type idrefs.  I want to split the value into the individual idrefs (I will run more complicated tests on them, but for the moment I'm just trying to get access to them).  In the attached document and schema, I have two assertions.  The first, using matches() succeeds, but the second, using tokenize(), fails:

<xsd:assert test="matches(string(< at >target), '\S+(\s+\S+)+')" xpathDefaultNamespace="##targetNamespace"/>
<xsd:assert test="boolean(tokenize(string(< at >target), '\s+'))"  xpathDefaultNamespace="##targetNamespace"/>

What am I doing wrong?

Thanks,
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe< at >xerces.apache.org
For additional commands, e-mail: j-users-help< at >xerces.apache.org

regular expression matching in

Jim Barnett — 2013-04-16T18:42:07

Are matches() and tokenize() supported inside <assert> when doing schema validation?  I am applying an assertion to an element with a 'target' attribute whose value is "s1 s2", yet the following assertion is failing:

<xsd:assert test="if (matches(< at >target, '.*')) then true()  else false()"  xpathDefaultNamespace="##targetNamespace"/>

Any guidance would be appreciated.

Thanks,
Jim

Validate XML by XSD failes with jDOM and Xerces 2.10.0

Ronny — 2013-04-05T14:11:39

Hi list,

I've got a problem validating a xml by a xsd.

A short preview about the xsd:

<complexType name="MyType2">
 <attribute name="MyAttribute" type="string" use="required" />
</complexType>

<complexType name="MyType1 ... />

<element name="MyRoot">
 <complexType>
  <choice>
   <element name="MyType1" ... />
   <element name="MyType2" type="MyType2" minOccurs="1" maxOccurs="1" />
  </choice>
 </complexType>
</element>


Ok, my XML file looks like this:

<MyRoot xmlns="..." ...>
 <MyType2 MyAttribute="something">
  ...
 </MyType2>
</MyRoot>


Now I try to validate this with jDOM by using xerces. Then I got the
following error:
 - Error on line 6: cvc-complex-type.3.2.2: Attribute "MyAttribute" must
not occur in element "MyType2".


I validated the same xml with the same xsd with oXygen (which also uses
xerces) and with some online validators. All told me that the xml is valid.

So my question is, why does the JAVA implementation gives tells me that
the xml is not valid.

I'm grateful for some hints.

Th

fPreviousChunk == NULL exception on parsing a 2 GB XML file

Hector Barragan — 2013-04-01T19:03:11

Hi there

In the below version, has the 2 GB file size bug been fixed?






Xerces2 Java Parser 2.11.0 Release 






The sax parser wont read/handle a XML file more than 2 GB, populating the 
below exception

java.lang.RuntimeException: Internal Error: fPreviousChunk == NULL
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1094)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:223)

Currently we have this version

Sax version is 2009 xercesImpl-2.2.1.jar 2009 xerces.jar
Thanks in advance



_______________________________________________________________________________
Hector Barragan | Contractor | Derivatives Technology 
801 S. Canal Chicago IL, 60607 USA||Cell 1 (312) 285 4793 hb58< at >ntrs.com 
Please visit northerntrust.com

Problem with apache-xerces.2.9.1.jar file

Miron, Radu — 2013-04-01T09:50:23

Hello,

I would want to subscribe in order to notify you that you have an issue with your latest apache-xerces.2.9.1.jar file. The JAR file cannot be opened and introduces problems during our build process.

Repository Path:
/apache-xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar
Uploaded by:
deployment
Size:
168 Bytes
Uploaded Date:
Mon Apr 01 2013 09:50:10 GMT+0300 (GTB Daylight Time)
Last Modified:
Mon Apr 01 2013 09:50:10 GMT+0300 (GTB Daylight Time)










SHA1
d3b963c1d3e2ff326632c5f5a02fdb44cfaaea77
MD5
f48a70649b86c40ebb4c86ff0ce8a070

The file you have now is 168 bytes, but the file from yesterday has 1,229,125 bytes. This last file is the correct one.
Please notify me of a fix when fixed.

Thanks,
Radu

Schema Grammar validity question.

Chris Simmons — 2013-03-14T10:37:02

I've got three grammars with a potentially dubious substitution group chain.

In a.xsd we have an attribute group declaring ##other.

In b.xsd we have an extension of a type from c.xsd declaring an ID 
attribute.

In c.xsd we have the base type, which declares a single attribute and 
##other.

Now the question is, is this valid according to point 1.3 of this section?

http://www.w3.org/TR/xmlschema-1/#cos-ct-extends

The reason I ask is that I'm getting conflicting answers.  Xerces says 
its valid, but XSD 
(http://www.eclipse.org/modeling/mdt/?project=xsd#xsd) claims that it 
isn't valid.

So who's right and why?

Regards,

Chris Simmons.


---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe< at >xerces.apache.org
For additional commands, e-mail: j-users-help< at >xerces.apache.org

Trouble compiling XSD 1.1 branch

Jorge Williams — 2013-03-04T21:30:10

Hey guys,

I'm on the latest xml-schema-1.1-dev branch in SVN. Trying to compile with 

./build.sh clean jars-schema11

I'm getting all sorts of errors:

compile-schema11:
     [copy] Copying 23 files to /Users/jorgew/projects/xercesj/build/classes
   [xjavac] Compiling 776 source files to /Users/jorgew/projects/xercesj/build/classes
   [xjavac] /Users/jorgew/projects/xercesj/build/src/org/apache/xerces/impl/xs/alternative/Test.java:38: package org.eclipse.wst.xml.xpath2.processor does not exist
   [xjavac] import org.eclipse.wst.xml.xpath2.processor.DynamicContext;
   [xjavac]                                            ^
   [xjavac] /Users/jorgew/projects/xercesj/build/src/org/apache/xerces/impl/xs/alternative/Test.java:39: package org.eclipse.wst.xml.xpath2.processor.ast does not exist
   [xjavac] import org.eclipse.wst.xml.xpath2.processor.ast.XPath;
   [xjavac]                                                ^
   [xjavac] /Users/jorgew/projects/xercesj/build/src/org/apache/xerces/impl/xs/AbstractPsychoPat

support for xpointer

2013-02-21T17:03:44

Hello all

I am a user of Xerces-J and plan to use the Xpointer feature which from 
the specification i read seems to be very powerfull. 
However after few tries, i realized that not all is yet completly 
supported. 

What is the strategy of Xerces in regard to this Xpointer feature ?
Will it be implemented or is there other solutions ?

Thank you 
Best regards
Philippe Favrais

Info regarding XML Serializer property setting

2013-01-28T08:32:50

Dear users,

We recently moved to IBM  WAS 6 to WAS 7.We have a code printing the xml
file which uses the serializer jar provided by IBM.

Problem noticed in WAS7 is that Carriage Return is converted to &#13 within
CDATA section of an element.

For ex,

WAS6

<MsgTyp><![CDATA[other
Document]]></MsgTyp>

WAS7

<MsgTyp><![CDATA[other]]>&#13;<![CDATA[
Document]]></MsgTyp>

Can anyone please assist us to get this fixed.

Thanks,
karthik




This e-Mail may contain proprietary and confidential information and is sent for the intended recipient(s) only.  If by an addressing or transmission error this mail has been misdirected to you, you are requested to delete this mail immediately. You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message, contents or its attachment other than by its intended recipient/s is strictly prohibited.

Visit us at http://www.polarisFT.com

Caching grammars

Robert Huffman — 2013-01-12T22:04:17

I must parse documents that may use a large number of fairly large XSDs.
However, the large majority of documents will not use most of those XSDs.
Therefore, I would like to use a custom LSResourceResolver to resolve the
target namespaces to local resources during parsing rather than building a
Schema object that has all the grammars loaded up front.

Unfortunately, as nearly as I can tell, grammars loaded through the use of
a LSResourceResolver are never cached in the grammar pool. Is that correct?
Is there some nuance I'm missing?

[ANN] Balisage 2013 Call for Participation

Tommie Usdin — 2013-01-10T01:02:34

Balisage is where people interested in descriptive markup meet each year in August for informed technical discussion, occasionally impassioned debate, good coffee, and the incomparable ambience of one of North America's greatest cities, Montreal. We welcome anyone interested in discussing the use of descriptive markup to build strong, lasting information systems.  

Practitioner or theorist, tool-builder or tool-user, student or lecturer -- you are invited to submit a paper proposal for Balisage 2013. As always, papers at Balisage can address any aspect of the use of markup and markup languages to represent information and build information systems. Possible topics include but are not limited to:

  * XML and related technologies
  * Non-XML markup languages
  * Big Data and XML 
  * Implementation experience with XML parsing, XSLT processors, XQuery processors, 
    XML databases, XProc integrations, or any markup-related technology
  * Semantics, overlap, and other complex fundamental issues for markup lan

Validating CSV against XSD

kamal kaur — 2013-01-08T18:27:17

Hi all,

We have a flat XSD, so instead of storing the data in XML we are thinking
of storing in CSV format as the data can be really huge. Assuming we know
the Element Type of each record in CSV, is there a way to validate these
records in CSV against XSD?

thanks

Kamal

Node typw being imported is not supported

2012-12-26T12:23:53

Hi xerces team,

We are getting the below exception after upgrading from old xerces 1.2 jar
to the latest xercesImpl.jar (2.9 version).Can u please help on why this
exception occurs.

JRE : 1.6

Stack Trace:
org.w3c.dom.DOMException: Node type being imported is not supported
 at org.apache.xerces.dom.CoreDocumentImpl.importNode
(CoreDocumentImpl.java:1051)
 at org.apache.xerces.dom.CoreDocumentImpl.cloneNode
(CoreDocumentImpl.java:348)
 at org.apache.xerces.dom.DocumentImpl.cloneNode(DocumentImpl.java:202)


Thanks,
karthik



This e-Mail may contain proprietary and confidential information and is sent for the intended recipient(s) only.  If by an addressing or transmission error this mail has been misdirected to you, you are requested to delete this mail immediately. You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message, contents or its attachment other than by its intended recipient/s

assert with count function does not work

Cronemberger, Constantino — 2012-12-07T17:12:19

Hi,

I have the following snippet in my XSD 1.1:

    <xs:complexType name="columns">
        <xs:sequence>
            <xs:element name="column" type="xs:string" maxOccurs="unbounded"/>
        </xs:sequence>
        <xs:attribute name="count" type="xs:int" use="required"/>
        <xs:assert test="< at >count eq count(./column)" />
    </xs:complexType>

And when I try to validate this XML it fails:

    <columns count="3">
        <column>Description</column>
        <column/>
        <column>Name</column>
    </columns>

with the following message:

org.xml.sax.SAXParseException; lineNumber: 12; columnNumber: 15; cvc-assertion: Assertion evaluation ('< at >count eq count(./column)') for element 'columns' on schema type 'columns' did not succeed.

When I replace "< at >count" by "0" it works, so it looks like the count function is not working. I tried to call the function "countX" and got the error message: "XPST0017 - Function does not exist: countX arity: 1."

I have used the revision 1418386 on https://svn.apache.org

document.cloneNode() copies identifiers map but fails to apply IDness to relevant attribute nodes

Jacob Kjome — 2012-12-06T19:13:15

Last week I submitted a bug report [1] entitled "document.cloneNode() copies 
identifiers map but fails to apply IDness to relevant attribute nodes".  I 
even provided a patch for it, but I've gotten no takers so far.

Can someone review the patch please?  I'd like to see it get into the next 
release if at all possible.

[1] https://issues.apache.org/jira/browse/XERCESJ-1597


Thanks,

Jake

taskdef class org.apache.xerces.util.XJavac cannot be found

Albretch Mueller — 2012-12-06T15:03:10

 While tryinng to compile xerces sources, I am getting that
"util.XJavac cannot be" found error. Why is it happening? How can I
troubleshoot it?
~
 thanks
 lbrtchx
~
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
~
$ ant -verbose
Apache Ant(TM) version 1.8.4 compiled on October 13 2012
Trying the default build file: build.xml
Buildfile: /media/sdb1/prjx/kd/java/SAX2/xerces-2_11_0/build.xml
Detected Java version: 1.7 in: /media/sdb1/inst/sw/jdk/x86/1.7.0_07/jre
Detected OS: Linux
parsing buildfile
/media/sdb1/prjx/kd/java/SAX2/xerces-2_11_0/build.xml with URI =
file:/media/sdb1/prjx/kd/java/SAX2/xerces-2_11_0/build.xml
Project base dir set to: /media/sdb1/prjx/kd/java/SAX2/xerces-2_11_0
parsing buildfile
jar:file:/media/sdb1/inst/sw/apache-ant-1.8.4/lib/ant.jar!/org/apache/tools/ant/antlib.xml
with URI = jar:file:/media/sdb1/inst/sw/apache-ant-1.8.4/lib/ant.jar!/org/apache/tools/ant/antlib.xml
from a zip file
dropping /media/sdb1/prjx/kd/java/SAX2/xerces-2_11_0/tools/bin/xjavac.jar
from path as

Disabling XML External Entites

Daniel Amodio — 2012-12-05T15:35:25

Hello,

 

We recently did some testing to verify the proper way of disabling
external entity resolution, as a security recommendation.

 

Through some unit testing, we came up with a couple findings which I
wanted to verify were intended functionality:

 

*             Not validating XML did not stop XXE attacks in the JAXP
and StAX implementation; It expanded external entities.

*             .setExpandEntityReferences(false) also did not stop XXE
attacks in the JAXP implementation;  It also expanded external entity
references.

 

Should this be the case, or should those settings disable the
resolution? I've included some more details of our test results below.

We're willing to contribute the test cases if that's at all useful.

 

Thanks,

Dan

 

Tested Xerces 2.10.0 and 1.4.4

 

DocumentBuilderFactory (JAXP)

Implementation

Stop XXE?

.setValidating(false);

Xerces 1 or Xerces 2

NO

.setExpandEntityReferences(false)

Xerces 1 or Xerces 2

NO

.setFeature("http://apache.org/xml/features/disallow-d

Thread safe wrapper for the DOM?

Dave Crooke — 2012-11-01T19:12:29

Hi folks

I know this is an old chestnut, but I have a new question about it .....

As we all know, the Xerces DOM implementations are not thread safe, and
this is intentional to maximise performance.

However, there is a very useful pattern we use in a number of places in our
products where we parse and cache XML documents as Xerces DOM trees, and
then hand them out to callers. Right now, since we have multi[ple readers,
we clone a fresh copy of the DOM for each caller.

It would be nice to have a package of wrapper classes that would implement
thread safe access for multiple readers by simply wrapping the underlying
Xerces calls in synchronized(document), and of course wrap any returned
Xerces handles. It wouldn't be Xerces specific, just a generic wrapper that
implements the DOM API both as provider and consumer, c.f. Apache DBCP or
Collections.unmodifiableX() .... I'd envisaged it as read only but in
principle it could be made read-write. I'm aware there will be issues with
things like Iterators.

I know

Xerces clone node issue in production environment (Multi threaded). Help needed ...

2012-11-01T13:14:27

Hi Xerces users,

Greetings!.

We have an issue in the xerces parsers and specifically in cloning a
node.We browsed in apache's site and bugzilla to find if anyone had
reported any issues or bugs relevant to the one we are facing in our
production environment.

We were able to find info about few issue that were reported already and
that is more or less similar to the one we are facing now.

Let me brief out the environment wherein we are facing this issue.

OS: Sun Solaris 10
Server: Websphere 6
JDK: 1.4
Xerces version: Xerces_Version_1_2_0
Number of Daemon threads per JVM: 3

Scenario:

In our Production environment when 3 daemon threads run under a JVM.

When 3 similar type of XML messages gets parsed at same second
(concurrently) under a JVM, we notice some attribute gets missed.

Here is sample XML that gets parsed.

<?xml version="1.0"?>
<!DOCTYPE InTemplate SYSTEM "feed_dd.dtd" >
<InTemplate>
  <Header>
    <DataDictionary>
      <element XMLName="NumberOfTxn" CFCName="NO_TRANS"
CFCType="TYPE_STRING"