cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank Ridderbusch <>
Subject Re: [HELP TO FIX BUG] XMLForm # 9567
Date Thu, 13 Jun 2002 19:37:59 GMT
On Sat, 8 Jun 2002 14:15:17 -0500
"Ivelin Ivanov" <> wrote:

> Frank Ridderbusch submitted a bug on XMLForm & Saxon.
> Any brave souls willing to work with Frank on this one?

It appears, that this no simple one. 

I'm wondering, if it would be an option to really allow for more than one
XSLT processor. It would be something of a kludge I guess, but anyway. Or
include it in form of documentation as a workaround, where the one 
XSLT processor doesn't quite fullfills all requirements.

IIRC there was some message exchange on cocoon-users, where somebody wanted
exactly this, because Saxon worked better with DOCBOOK and Xalan worked 
better in some other area. I think, he also achieved a working setup by
including the appropiate 'things' in the sitemap. However I didn't exactly
understand, what was required.

I know of two other areas, where Saxon apparently does not work. I just tried
to login into the portal sample and got an exception starting like this:

  The org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode notifies
       that java.lang.UnsupportedOperationException says:

  The Saxon DOM cannot be updated

  More precisely:

  java.lang.UnsupportedOperationException: The Saxon DOM cannot be updated

And the SQLTransformer does also not work with Saxon. Here I'm also getting
the "The Saxon DOM cannot be updated".

I'm not expert enough to judge if this can "simply be fixed".

Frank Ridderbusch

Since I have taken all the Gates out of my computer, it finally works!!

Please check that your question  has not already been answered in the
FAQ before posting.     <>

To unsubscribe, e-mail:     <>
For additional commands, e-mail:   <>

View raw message