Mike Pogue wrote:
>
> If that's the case, then why did Stefano's case fail? His input files
> caused Xalan to try to insert a single text node under the Document
> node, which was disallowed.
All right.
Everyone of you has a solution (thank Andy, that might do the job), a
design issue, some noise and lots of words... but the problem remains.
Scott, you're saying that Xalan allows this operation. It might be the
case with your internal formatters, but I'm using Assaf's so I must be
able to do something like this
document -> process -> document -> serialize
even if the output of the process is _not_ XML (could be code, VRML,
simple text, you name it!)
If DOM doesn't allow this, then XSLT wrong. But since this is a rather
useful functionality and DOM was _not_ designed for XML, I suggest the
DOM designers to think again about this.
Anyway, why a DOM should not have a text node as first node?
Pier, we should hurry up with the SAX port for Cocoon2: I'm getting sick
and tired of DOM limitations...
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
