-
Input:
Output (Now)
2009-11-12 04:10:59 UTC by asfak
-
I am using dom4j 1.6.1. When I write the following input document to an output location using the following code the output changes the location of processing instruction and DOCTYPE. In the input processing instruction comes before DOCTYPE. But in the output it comes after the DOCTYPE. I want my output should be as it is in input.
INPUT:
<?xml version="1.0" encoding="UTF-8"?>
...
2009-11-12 04:04:15 UTC by asfak
-
Followup: RE: SaxReader throws Exception?
Do you mean this type of error ?
Caused by: org.hibernate.MappingException: Could not parse mapping document in input stream
at org.hibernate.ejb.Ejb3Configuration.addXMLEntities(Ejb3Configuration.java:499)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:369)
at...
2009-10-14 21:09:55 UTC by jamestansf
-
I have a program that reads from a big xml file, and it have a big list of complex tags.
For some nodes in the xml list i get only a portion of the text, just to check if it was really a bug, i try to put some spaces inside xml and this affects the text that is cut.
I am using valueOf(xpath); to get the value.
2009-08-21 17:13:28 UTC by kulhas
-
When an XPathException gets caused by another exception, only the message gets remembered, all the rest of the information that comes with the cause exception gets discarded. This is especially tragic when the cause again had a cause. In one case, it took me a whole day to find out that the real cause of an XPathException was a FileNotFoundException.
2009-08-03 14:32:14 UTC by ipreuss
-
I am suffering exactly the same issue when using dom4j + android. Every call to obtain an attribute returns always the same (the first obtained) attribute.
It can be fixed doing :
if (qualifiedName == null && !qualifiedName.equals("")) {
qualifiedName = localName;
}
But as Matthias said, I don't know if that is the right solution.
2009-07-31 09:40:32 UTC by guigar
-
This is possibly related to the other bug I filed yesterday, which also breaks XSLT when there's a top-level comment: .
2009-06-24 07:20:09 UTC by szegedia
-
For now, worked around it with a private build of dom4j. NOTE: I didn't find and fix the bug, I worked around it. What I did is I took the SAXReader.read(InputSource) method and doctored it so that it removes any top-level comments from the document before returning it. Would still prefer a proper fix.
2009-06-24 07:18:22 UTC by szegedia
-
It's possibly related to .
2009-06-23 11:22:33 UTC by szegedia
-
I have a trivial document (saved as "id.xml"):
And a trivial XSLT file (saved as "ad.xslt") that's just an identity transform:
2009-06-23 11:20:42 UTC by szegedia
