My mistake, thanks for your patience.

- Aaron

-----Original Message-----
From: Michael Glavassevich [mailto:[email protected]] 
Sent: Thursday, April 07, 2011 11:58 AM
To: [email protected]
Cc: [email protected]
Subject: Re: Xerces builds - Why don't they include line number
attributes?

Aaron,

You picked the wrong mailing list. c-users@ is for Xerces-C. I'm sure
you
meant to post this to the Java users list.

Also, please see previous discussion on this topic in the archives [1].

Thanks.

[1] http://markmail.org/thread/qkbaup5dzjrx5ffj

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [email protected]
E-mail: [email protected]

"Pieper, Aaron" <[email protected]> wrote on 04/07/2011 11:40:16
AM:

> Hello,
>
>
>
> Is it possible that when building Xerces builds for Java in the
future,
> you could turn the line number attributes on? It makes it easier for
> developers to set breakpoints and trace through code. Currently, any
> Java stack traces involving xerces look something like this (with line
> number information not available):
>
>
>
>
>
org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLInputSource[])
> line: not available
>
>
> org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(Source[])
> line: not available
>
>
>
org.springframework.xml.validation.SchemaLoaderUtils.loadSchema(Resource
> [], String) line: 73
>
>
>
org.springframework.xml.validation.Jaxp13ValidatorFactory.createValidato
> r(Resource[], String) line: 40
>
>
>
> You can see that the SpringFramework JARs include line numbers, making
> their code easier to trace; the Xerces JARs do not, which means we can
> only see the class/method names. The last time I built Xerces, I
> remember this behavior was already integrated into the Xerces build,
but
> was disabled by default. Not sure if this is by design or simply an
> oversight. Maybe it should be enabled by default, or maybe whatever
> process or person builds these final releases could be
updated/educated
> to include this flag?
>
>
>
> Thanks,
>
>
>
> - Aaron

Reply via email to