Okay, thanks again Michael.
On 6/21/10 9:52 PM, Michael Glavassevich wrote:
Hi Chad,
Chad La Joie wrote on 06/21/2010 08:56:00 PM:
> Hey Michael, I also meant to ask, while the Xerces serializer is
> deprecated, do you happen to know if any significant issuer were found
> and fixed in the
Hi Chad,
Chad La Joie wrote on 06/21/2010 08:56:00 PM:
> Hey Michael, I also meant to ask, while the Xerces serializer is
> deprecated, do you happen to know if any significant issuer were found
> and fixed in the Xalan-resident code? Just wondering if we'd be trading
> on potential problem fo
Hey Michael, I also meant to ask, while the Xerces serializer is
deprecated, do you happen to know if any significant issuer were found
and fixed in the Xalan-resident code? Just wondering if we'd be trading
on potential problem for one or more known problems.
Thanks again.
On 6/21/10 1:57 P
Thanks Michael,
I don't consider it dire yet, though the people with the broken code
might. :) I'll give your suggestion a shot and see what happens.
Would be nice to have an optional switch though. So hopefully it'll get
added.
On 6/21/10 1:57 PM, Michael Glavassevich wrote:
Hi Chad,
C
Hi Chad,
Chad La Joie wrote on 06/21/2010 10:18:58 AM:
> Let me preface this by saying that to my understanding Xerces-J and
> Xalan-J now share a common LSSerializer implementations and that this
> implementation is held and maintained by Xalan.
That's correct.
> If that's not true let
> me
Hi Tommaso,
I've tried this out myself and it appears to be a bug in the Xalan
serializer. You can report the issue here [1]. It is possible to work
around the problem by removing serializer.jar from your classpath. Xerces
will fall back to using its old deprecated serializer if it cannot find th
Hi Michael,
thanks for your reply.
Actually you are right, I will try to explain with an example:
This is the whole document:
__
http://www.normeinrete.it/nir/2.2/"; xmlns:dsp="
http://www.normeinrete.it/nir/disposizioni/2.2/"; xmlns:h="
http://
Hi Tommaso,
tommaso.agnol...@gmail.com wrote on 03/16/2009 02:16:33 PM:
> Hi,
>
> I need to use the LSSerializer provided by xerces to serialize a DOM
> document subtree without namespaces completion processing, i.e., the
> desired output is just the xml serialization of the subtree as one
> cou
I mentioned this issue in the xalan list.
See http://www.nabble.com/Fomatting-question-serializing-DOM-with-
pretty-print-tf3252607.html
If you don't want to use the deprecated xerces serializer you can
filter out the whitespace first.
This filter was already mentioned in the forum which can
I'm using Xerces 2.9.0. any idea about this version and my problem?
Should I use other mailing list (xalan)?
Michael Glavassevich wrote:
> You haven't said what release you tried this with (assuming it's Xerces).
> Note that "format-pretty-print" has only been implemented since Xerces
> 2.8.0. I
You haven't said what release you tried this with (assuming it's Xerces).
Note that "format-pretty-print" has only been implemented since Xerces
2.8.0. If you're using Xerces 2.9.0 the LSSerializer is based on Xalan
which has different behaviour with respect to pretty-printing.
Michael Glavasse
Andy Kriger <[EMAIL PROTECTED]> wrote on 08/30/2005 10:18:09 AM:
> Does LSSerializer have a way to control whether empty elements are
> written as or ? We have an application
> that requires empty elements to be written in the first manner (even
> though they're both equivalent, it makes a diffe
12 matches
Mail list logo
