I have a pipeling that has the following pattern:
<map:match pattern="login">
<map:generate type="serverpages" src="docs/login.xsp" />
<map:transform src="stylesheets/login-page2html.xsl"/>
<map:serialize/>
</map:match>
I though what happened her was that a file 'login_xsp.java' was
generated from 'login.xsp' which would fire SAX events that are then
transformed by 'login-page2html.xsl'.
But in tracking down a bug it looks more like the login.xsp page has the
login-page2html.xsl applied, and then it is compiled into a .java file.
I concluded this because the problem was that the root tag was not being
matched, and the java file only had a few tags in it. When I go the name
of the tag right in login-page2html.xsl then the resulting java file
produced had all the bits and pieces.
I'm confused.
Mark Miller
Web Architect
Logica
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
