DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10473>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10473 Adding your own builtin-logicsheets does not work properly ------- Additional Comments From [EMAIL PROTECTED] 2002-09-27 13:53 ------- Sorry to ask, but are you sure "hello.xsl" isn't in one of the jars? (Which jar file holds the sample logicsheets?) Could you try it after renaming "hello.xsl" to something else (and using a different namespace), to make sure you're not picking up the file that came with Cocoon? I'm using a new cocoon and tomcat (see "2.)" below) for the 1.4 V.M., and at least I don't have Matthias' problem any more. 1.) What is the "context" in the <parameter name="href" value="context://logicsheets/hello.xsl"/> ---I tried it with my logicsheet, and I got an error message indicating that I had screwed up the <xsp:page>'s xmlns declarations, because the error message said that it was impossible to find the component for the hint "xsp". Was "context" just a misprint for "resource"? 2.) Now using JDK1.4 (from j2sdk1.4.0_02), and the vm1.4-specific tomcat4.10 and cocoon 2.0.3's, still under Win2K...I still don't seem to pick up the logicsheet without the per-page processor directive. The logicsheet file is definitely not listed in the "dependencies" list in the processed _xsp.java file when I don't do the per-page invocation. (Incidentally, it doesn't seem to matter if the xconf reference is done using "resource://" or "file://".) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
