Hi Scott
From: "Scott Willy" <[EMAIL PROTECTED]>
> It sounds like the best solution is the specialized factories.
>
> ValidatingDocumentFactory for guys (even gals) who how a XML view of the
> world and just want to protect themselves from bad things. And an
> EncodingDocumentFactory for guys who
James,
It sounds like the best solution is the specialized factories.
ValidatingDocumentFactory for guys (even gals) who how a XML view of the
world and just want to protect themselves from bad things. And an
EncodingDocumentFactory for guys who want a more Java interpretation of
String and not
Hi Scott
From: "Scott Willy" <[EMAIL PROTECTED]>
> My concern is that it is easy to create a DOM in Java which contains
invalid
> XML characters (those outside the range of: #x9 | #xA | #xD |
[#x20-#xD7FF]
> | [#xE000-#xFFFD] | [#x1-#x10]). So the question is when/where do
> you catch in
Hi Scott
> We have been using JDOM for a year or so and now you have to confuse the
world with dom4j
> which has all the bits we now know JDOM should have.hm
Sorry about that Scott ;-)
> Anyway, one of the problems not solved by JDOM is the transparent encoding
of values represented as
> Ja
James,
We have been using
JDOM for a year or so and now you have to confuse the world with dom4j which has
all the bits we now know JDOM should have.hm
Anyway, one of the
problems not solved by JDOM is the transparent encoding of values represented as
Java Strings (e.g. Attribute val