This has been discussed in these lists before.
I agree with you that having the Writer constructor is a pitfall, since
it is normally the wrong thing to do. It's a particularly easy mistake
to make because developers who aren't familiar with encoding issues
(which is most developers) will almost a
Can anyone explain why calling
as opposed to
Should cause parameter values (even unrelated literal ones) not to get passed?
If I have
and
In my experience, Catalogs is a standard that hardly anyone actually
uses. To do this in a JAXP compatible way, without using Xerces-specific
functionality, I would stick to the JAXP parser interfaces
http://xerces.apache.org/xerces2-j/javadocs/api/javax/xml/parsers/package-summary.html
and inste
Has this (maven pom) not happened yet, or am I just looking in the wrong
place?
If it hasn't happened yet, this is just a friendly nudge from someone
trying to maximize his own laziness. :^)
Eric
Nathan Beyer wrote:
> Sure, I can try to write something up. I'll post the candidate POM files to
>
I'm sending some old school dtd-based XML through a SAX parser mostly
just to assemble it from the dozens of xml files included in the
top-level file as entities, using the old
identity-transform-to-serialize techique:
t.transform(new SAXSource(parser, new InputSource(inStream)), new
StreamRes
Right, I'm using the built-in identity-tranformation support...I'm
pretty much just performing SAX serialization as recommended in the
Xerces FAQ
http://xerces.apache.org/xerces2-j/faq-general.html#faq-6
I realized an easy answer to my third question which is to invert the
use of quotes to
wan
The parser is resolving these character entities to the actual
character--it should be the correct character though it may not be
displayable by whatever you're viewing your output in.
I believe you can enable the feature
"http://apache.org/xml/features/scanner/notify-char-refs"; and then if a
if
Isn't a billion characters far more that you could ever load into a DOM
in any practical environment?
The question I find more interesting that of the feasibility of VTD as
general DOM / Xerces competitor, is could some of the underlying
techniques [1] they use in processing the XML be used to mak
I take it this hasn't happened yet? I'm not finding it, but maybe you've
switched to using a different path?
Michael Glavassevich wrote:
> I'll be vacationing over the next two weeks. Hopefully someone will step
> up to the plate if they really need this in the repo before the new year.
>
> Mich
This sounds like kind of a circular project dependency... Shouldn't this
be eliminated, perhaps by serializer moving to commons or some such?
Michael Glavassevich wrote:
> Nathan,
>
> I'm not sure what Maven users expect the repository layout to look like
> but the second option sounds like it co
x27;t
> think it had the critical mass (i.e. too few committers) to survive as a
> separate subproject.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: [EMAIL PROTECTED]
> E-mail: [EMAIL PROTECTED]
>
> "Eric J. Schwarzenbach" <[EMA
My first vote would be for _Complex Type Restriction_. I've spent
countless hours in the past bashing my head against the spec when trying
to do something with restriction that intuitively made sense (and would
be valid according to subset logic) but which ran afoul of the byzantine
rules that gove
If you really can't force the source of your documents to give you
correct XML, and you know for sure every & is meant as a literal & and
is not part of some actual entity reference, you could simply a custom
implementation of java.io.FilterInputStream that replaces every & with
&. Then wrap th
If performance, or scalability in terms of memory usage with large files
is at all a concern, I'd recommend using SAX rather than DOM or one of
those binding frameworks. To accommodate requirement #3, you'd need to
do something like create your own system of handler classes for collada
features, an
Is it to be expected that adoptNode (on Document object) should drop
namespace declaration attributes? (I saw something about a bug with
attributes when adopting between Documents with and without deferred
node expansion, but I flipped that flag and it didn't make any
difference...and it is car
Nevermind... It does adopt over the namespace prefix declaration
attributes just fine when the adopted-from Document is created by a
namespace aware DocumentBuilder (I'd thought the one I been using was
so, but I was mistaken).
On 12/02/2014 08:59 PM, Eric J. Schwarzenbach wrote:
Is it
One might expect "commiter" to imply a coder, but could someone who is
not going to actually work on xerces code be made a committer? If so,
what skills would such a person need in order to help get the release out?
On 01/11/2018 01:42 PM, Michael Glavassevich wrote:
A lot of what needs to get
On 05/10/2018 02:39 AM, Mukul Gandhi wrote:
Hi Dave,
On Thu, May 10, 2018 at 11:23 AM, Dave Brosius
mailto:dbros...@mebigfatguy.com>> wrote:
Yes, but if i want to publish an artifact to maven, and my
artifact depends on xerces, are you expecting all the users of my
artifact to do
ds on xerces, my users will come at me with pitch forks.
Original message
From: "Eric J. Schwarzenbach"
Date: 5/10/18 5:28 PM (GMT-05:00)
To: j-users@xerces.apache.org
Subject: Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
On 05/10/2018 02:39 AM, Mukul Ga
Thank you. It seems as though this information should be provided on
this page, as well as on the downloads page. I'd like to post a bug
about this, as well as a few related items that seem to make it
surprisingly difficult to know what you are getting wrt schema 1.1
support, but I'd like to ma
20 matches
Mail list logo
