cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [vote] Removing namespace-prefixes feature on parsers
Date Fri, 21 Dec 2001 09:00:06 GMT
Sylvain Wallez wrote:
>
> Carsten Ziegeler a écrit :
> >
> > Vadim Gritsenko wrote:
> > >
> > > I'm not a namespace guru... ;)
> > > If this does not break anything, count me in: +1.
> > Same applies here: +1
> >
> > What about making the parser configurable for this setting like
> > it is configurable regarding validation?
>
> It is already configurable in PooledJaxpParser that I wrote to reuse
> parsers instead of just factories.
>
> I've been using it here for several weeks without problems. So I propose
> to move PooledJaxpParser code to JaxpPaser and not set
> "namespace-prefixes" by default.
>
This would remove the PooledJaxpParser, right? (Or better deprecate?).
+1

Carsten

> > Did you post this as a bug to SAXON?
>
> I'll do it.
>
> The Xalan bug is already identified, but marked as low priority :
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1831
>
> Sylvain.
>
> > Carsten
> >
> > >
> > > Vadim
> > >
> > > > -----Original Message-----
> > > > From: Sylvain Wallez [mailto:sylvain.wallez@anyware-tech.com]
> > > > Sent: Thursday, December 20, 2001 12:05 PM
> > > > To: cocoon-dev
> > > > Subject: [vote] Removing namespace-prefixes feature on parsers
> > > >
> > > > Hi team,
> > > >
> > > > The default behaviour of a SAX parser when encountering an xmlns:xxx
> > > > namespace declaration is to call
> ContentHandler.startPrefixMapping(),
> > > > and to remove this attribute from the Attributes object passed to
> > > > startElemnt().
> > > >
> > > > But Cocoon code also sets the "namespace-prefixes" feature each time
> > > it
> > > > creates a Parser. This has the effect of also passing
> xmlns:xxx in the
> > > > Attributes (see ContentHandler.startElement() javadocs for more
> > > > details).
> > > >
> > > > What is the reason for enabling this feature ? I guess this
> was a try
> > > to
> > > > circumvent a long-standing (still present) bug in Xalan's serializer
> > > > which doesn't output properly namespace declarations if they're not
> > > > present as attributes in the incoming SAX stream. However,
> this wasn't
> > > > the solution and I patched several months ago AbstractTextSerializer
> > > to
> > > > make Xalan happy.
> > > >
> > > > Now I'm using Saxon for some parts of our apps and this one barks on
> > > > each and every xmlns:xxx attribute it encounters when reading
> > > > stylesheets. So I locally removed the namespace-prefixes feature :
> > > this
> > > > fixes Saxon problems and doesn't hurt Xalan (it needs them only for
> > > > proper serialization).
> > > >
> > > > So, team, what about not enabling the "namespace-prefix" feature and
> > > > thus keep the default behaviour of SAX parsers ?
> > > >
> > > > +1 from me.
> > > >
> > > > Sylvain.
>
> --
> Sylvain Wallez
> Anyware Technologies - http://www.anyware-tech.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message