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 par
As Jake pointed out Xerces-J 1.2.0 is ancient. It was released over 12
years ago. It's unlikely that you'll find anyone here who still uses it or
remembers how it behaves. It is more likely that someone would respond to
your questions if you were using a recent version.
Michael Glavassevich
XML
At the very least, you should try it with the latest version of Xerces1, which
is 1.4.4. Asking Xerces developers and users to spend precious time
investigating a strange issue in an ancient release of a project that the
Xerces site lists as a "Hibernated project" is not in good form.
You n
Hi jake,
Thanks for the reply.
But we want to know whether it is an issue in 1.2.0 ?
Only if we make sure that is an issue in xerces 1.2.0 itself , only then
we can take steps to move to the latest version.
Thanks,
karthik.
From: karthikeyan...@polarisft.com
To: j-users@xerces.apache.org,
Hi jake,
Thanks for the reply.
But we want to know whether it is an issue in 1.2.0.
Only if we make sure that is an issue in xerces 1.2.0 itself , only then
we can take steps to move to the latest version.
Thanks,
karthik.
From: "Jacob Kjome"
To:
Date: 11/01/2012 09:15 PM
Subject:
If you are using Xerces 1.2.0, then you are using an ancient version... of
Xerces1. That hasn't been actively developed for many years.
You should upgrade and see if your issue exists in the latest release of
Xerces2, which is version 2.11.0.
Jake
On Thu, 1 Nov 2012 18:44:27 +0530
karth
Hi xerces users,
Correcting this mail with xml that is very similar to the one that gets
parsed.
12345
12345
BDFRESFGG
In the beginning stage the attribute 'type' for tag itself
gets missed.
It looks like [Here the attribute 'type' is mis
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
