Michael,
Thanks a lot.
We were actually using the serializer provided by xalan ( version 1.0.28).
Now it is working fine when we use the one comes with
xerces.(serialize.*).
Thanks
From: Michael Glavassevich
To: j-users@xerces.apache.org
Date: 02/02/2013 03:21 AM
Subject:Re: I
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
within
CDATA section of an element.
For ex,
WAS6
WAS7
Can anyone please assist us to
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.
Hi Jake,
We have been using this version of xerces since 2001. Mid of last year
(2011), we moved to powerful server. After this started seeing problem with
XML few times.
One of them is below mentioned. This happened twice in production
environment but we could not reproduce in test environment.
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:
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
Hi Mukul,
Thanks for your reply
We are coming up with the test cases,standalone api isolating the problem.
BTW, can anyone please let me know if there is any link available to get
the xerces parsers source code, any books available in market especially
about the xerces parsers or any other source
Dear Guys,
Please help me to get this sorted out.This issue is haunting us for
months..
We had the below code in place for cloning a node.
Node outNode = inNode.cloneNode(deep);
And then we found that clone node in xerces may sometimes delete a
attribute, so we added below piece of cod
Dear Guys,
Can anyone please help me to get this clarified.
We had the below code in place for cloning a node.
Node outNode = inNode.cloneNode(deep);
And then we found that clone node in xerces may sometimes delete a
attribute, so we added below piece of code but this is still not work
Dear Guys,
Can anyone please help me to get this clarified.
We had the below code in place for cloning a node.
Node outNode = inNode.cloneNode(deep);
And then we found that clone node in xerces may sometimes delete a
attribute, so we added below piece of code but this is still not wor
Dear Guys,
We had the below code in place for cloning a node.
Node outNode = inNode.cloneNode(deep);
And then we found that clone node in xerces may sometimes delete a
attribute so we added below piece code but this is still not working. Can
you please let us know the issue?
"My guess
Dear Guys,
Can anyone please help me to get this clarified.
We had the below code in place for cloning a node.
Node outNode = inNode.cloneNode(deep);
And then we found that clone node in xerces may sometimes delete a
attribute, so we added below piece of code but this is still not work
Apache Team,
Major concern for us with DOM parser in multi thread environment. Can you
please review this and provide your inputs? Thanks.
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 envir
15 matches
Mail list logo