You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Nick Airey <ni...@ihavemoved.com> on 2002/05/21 10:57:56 UTC
Crimson parser and cocoon202
Hello everyone,
Does anyone know a reason if cocoon202 will work with the crimson
parser?
I have tried it and it seems to work. Is something bad going to come and
bite me when all seems ok?
(I am having various jboss problems which makes it necessary for me to
use crimson rather than xerces.)
Regs,
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Crimson parser and cocoon202
Posted by Berin Loritsch <bl...@apache.org>.
As long as the current Crimson parser is JAXP 1.1 compliant,
and supports namespaces as the spec states then there is no
problem.
Crimson _used_ to violate the spec on namespace handling, but
I *think* it has since been fixed. If something bites you,
it will most likely be in this area.
> -----Original Message-----
> From: Nick Airey [mailto:nick.airey@ihavemoved.com]
> Sent: Tuesday, May 21, 2002 4:58 AM
> To: Cocoon dev
> Subject: Crimson parser and cocoon202
>
>
> Hello everyone,
>
> Does anyone know a reason if cocoon202 will work with the
> crimson parser?
>
> I have tried it and it seems to work. Is something bad going
> to come and bite me when all seems ok?
>
> (I am having various jboss problems which makes it necessary
> for me to use crimson rather than xerces.)
>
>
> Regs,
> Nick
>
>
>
> ---------------------------------------------------------------------
> 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