cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ed Staub" <est...@mediaone.net>
Subject RE: URGENT: Bug/special case in document() function when Xalan is used in Cocoon
Date Tue, 01 Aug 2000 16:42:21 GMT
I took a look at this in Cocoon 1.7.4/Xalan 1.0.1.

It looks like this should be handled by a fairly experienced Cocoon
contributor.
I was looking at it from the Xalan perspective.

Here are some notes for anyone digging on this:

Cocoon's XalanTransformer.XMLParser extends Xalan's XMLParserLiaisonDefault.

In order to support document(), Xalan needs the source URI to be associated
with the document within the XMLParserLiaisonDefault, using code like that
in Xalan's XSLTEngineImpl.setSourceDocument().

There probably should be a setSourceDocument() method on
XMLParserLiaisonDefault.

XalanTransformer never sets the source URI, but it can't anyway because the
URI is not accessible to it, either.  The Transformer interface might have
to be modified to support this.

I'm still digging upstream into Cocoon, to try to come up with a suggested
fix.
-Ed

-----Original Message-----
From: Edwards, Jayme [mailto:JCEdwards@software.rockwell.com]
Sent: Monday, July 31, 2000 4:39 PM
To: 'cocoon-dev@xml.apache.org'; 'xalan-dev@xml.apache.org';
'tomcat-dev@jakarta.apache.org'
Subject: URGENT: Bug/special case in document() function when Xalan is
used in Cocoon


Folks,

I've posted this issue a couple times in various forms. At this point I
cannot continue using Cocoon/Xalan for UI development until this is fixed. I
would really appreciate any cooperation I can get to get this into a dev
build in a timely manner.

Mime
View raw message