Hi!
I think the JspGenerator is broken in that it cannot resolve cocoon:/... type urls in the src attribute.
That's true. You might already have read the following comment in the JspGenerator:
// TODO (KP): Should we exclude not supported protocols, say 'context'?
I have looked in the JspGenerator src code and it passes the path to the jsp to the (tomcat) JSPEngine as a string and since JSPEngine does not know anything about cocoon:/ it is no wonder that it won't work, but I am hesitant about hacking the tomact jsp engine just to make this work.
Not quite correct. It's our JSPEngine. If you used the default configuration org.apache.cocoon.components.jsp.JSPEngineImpl is used. But this one can also not resolve cocoon:/ or context:// paths. It's also in the JSP block.
What I need to do is to execute a JSP that has dynamically generated by a XSLT transformation. My idea was to do the transformation in one pipeline (lets say transformed.jsp)and than use the JspGenerator like:
<generate type="jsp" src="cocoon:/transformed.jsp">
Anyone got an idea how to fix JspGenerator or make this work differently?
There were already several threads about fixing source resolving in the JspGenerator (resp. JSPReader). The best hints were given by Konstantin in this thread: http://marc.theaimsgroup.com/?t=105967319200003&r=1&w=2.
I would like to commit any patch you send :-)
Joerg
-- System Development VIRBUS AG Fon +49(0)341-979-7419 Fax +49(0)341-979-7409 [EMAIL PROTECTED] www.virbus.de
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
