cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <>
Subject Re: Bug in JSPReader?
Date Mon, 04 Aug 2003 17:21:01 GMT
Anyone is always the first ;-) Maybe the others port their code to 
Cocoon processing instead of reusing legacy JSP.

But the HttpServletRequest implementation is only minimalistic in the 
So if you know what to do ...


Marc Baumgartner wrote:

> Hello
>>There was something like a JSPFilter or so some time ago in Cocoon that
>>could be configured to be run on *.jsp requests (it is called at the end of
>>Cocoon processing), this can solve the problems with includes/forwards, but
>>you will be a little bit limiting compared to the current approach, though,
>>it's much more servlet spec. friendly.
>>Another possible solution could be rewrite the HttpServletRequest wrapper
>>in JSPEngine (or JSPReader/JSPEngine, don't remember exactly) to substitue
>>Cocoon's paths with webapp context relative paths, so the JSP could work as
>>usual. This one is just a suggestion, I'm not sure that it's possible to do
> That sounds not good. First, it seems that Joergs patch works fine. But I am 
> not able to include and forward other jsp's. 
> What have I to do to use the JSPFilter? If this does not work is there any 
> other solution than rewriting the HttpServletRequest? I really need a working 
> jsp-block :-(
> Is there anybody else with the same problems? I can't imagine that nobody 
> wants to use jsp's in cocoon...
> regards
> 	Marc

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message