Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: 11 Mar 2004 14:13:33 -0000
Message-ID: <20040311141333.29073.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@cocoon.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 27604]  -
    Cocoon Forms stylesheet reports error if xsltc used

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27604>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27604

Cocoon Forms stylesheet reports error if xsltc used


------- Additional Comments From joerg.heinicke@gmx.de  2004-03-11 14:13 -------
Yes, we know this one. Jeremy has already reported about these problems on the
developers list. Unfortunately the stylesheets are completely ok, it's XSTLC the
blame should be put on.

Of course we could fix it in a way that XSLTC works too (this means removing the
variables/parameters in included/imported stylesheets). But I implemented the
stylesheet dependencies in a easily extensible way and with the aim, that you
can use all stylesheets "as they are" independently in your own extension.

IMO we should not fix our stylesheets in a processor dependent way and force the
users to change the stylesheets if they don't want to use them "as a whole" but
separately (the variable/parameter declaration would be missing then). So we
should just make the XSLTC team aware of this problem.

WDYT?