Now that I have a small bit of time to return to this... Correct me if I'm wrong, but assuming ESQL is being invoked, the following XSP page should return either an error, or no output at all:
--- <?xml version="1.0"?> <xsp:page xmlns:xsp="http://apache.org/xsp" xmlns:esql="http://apache.org/xsp/SQL/v2" > <esql:connection> </esql:connection> </xsp:page> --- Unfortunately, the content generated from the above: --- <esql:connection xmlns:xsp="http://apache.org/xsp" xmlns:esql="http://apache.org/xsp/SQL/v2"> </esql:connection> --- The ESQL XSL page should transform that into something else. The .java file generated for the XSP page does not pull in any of the imports that the XSL specifies. I can't see any alternative other than Cocoon isn't invoking the XSL for the ESQL taglib. -- John R. Daily [EMAIL PROTECTED] Director of Technology Progeny Linux Systems Master of the ephemeral epiphany --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>