Stefan Pietschmann wrote:
Hmm, i'm not really into this, so it is as simple as exchanging the
XMLSerializer with the 2.1.5 version before building, or are there other
dependencies?
Cheers,
Stefan
I went and did diffs on XMLSerializer and its base classes. Only
AbstractTextSerializer changed
Stefan Pietschmann wrote:
Hmm, i'm not really into this, so it is as simple as exchanging the
XMLSerializer with the 2.1.5 version before building, or are there other
dependencies?
We have two different XML serializers. IIRC we changed
the the default implementation recently. All you need
to do is
I have the same problem.Using tab is to make xml file look nice.
- Original Message -
From: Torsten Curdt [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, December 06, 2004 5:54 PM
Subject: Re: AW: XMLSerializer replaces tabs with #9;
Stefan Pietschmann wrote:
Hmm, i'm
I have the same problem.Using tab is to make xml file look nice.
Well ...no problem using spaces for that over here ;-)
...even makes them look nice in every editor
cheers
--
Torsten
Torsten Curdt wrote:
Stefan Pietschmann wrote:
Hmm, i'm not really into this, so it is as simple as exchanging the
XMLSerializer with the 2.1.5 version before building, or are there other
dependencies?
We have two different XML serializers. IIRC we changed
the the default implementation recently.
So the question remains: when using tabs (and I do use them cause they're
used by default in XMLSpy and I cannot convert all my xml files to
whitespaces) - is it the intended behavior of the (new implementation of
the) XMLSerializer to replace all of them with the #9; entity?
Stefan
Hi Torsten,
I tried replacing
xml-serializer
class=org.apache.cocoon.components.sax.XMLByteStreamCompiler
logger=core.xml-serializer pool-grow=4 pool-max=32 pool-min=8/
with
xml-serializer class=org.apache.cocoon.components.sax.XMLSerializer
logger=core.xml-serializer pool-grow=4 pool-max=32
Stefan Pietschmann wrote:
So the question remains: when using tabs (and I do use them cause they're
used by default in XMLSpy and I cannot convert all my xml files to
whitespaces) - is it the intended behavior of the (new implementation of
the) XMLSerializer to replace all of them with the #9;
I tried replacing
xml-serializer
class=org.apache.cocoon.components.sax.XMLByteStreamCompiler
logger=core.xml-serializer pool-grow=4 pool-max=32 pool-min=8/
with
xml-serializer class=org.apache.cocoon.components.sax.XMLSerializer
logger=core.xml-serializer pool-grow=4 pool-max=32 pool-min=8/
FYI, my default sitemap has:
map:serializer logger=sitemap.serializer.xml mime-type=text/xml
name=xml src=org.apache.cocoon.serialization.XMLSerializer/
and
map:serializer logger=sitemap.serializer.exml
mime-type=text/xml name=exml
Micah Dubinko wrote:
FYI, my default sitemap has:
map:serializer logger=sitemap.serializer.xml mime-type=text/xml
name=xml src=org.apache.cocoon.serialization.XMLSerializer/
and
map:serializer logger=sitemap.serializer.exml mime-type=text/xml
name=exml
Hmm, i'm not really into this, so it is as simple as exchanging the
XMLSerializer with the 2.1.5 version before building, or are there other
dependencies?
Cheers,
Stefan
-Ursprüngliche Nachricht-
Von: Torsten Curdt [mailto:[EMAIL PROTECTED]
Gesendet: Sonntag, 5. Dezember 2004 22:15
12 matches
Mail list logo
