Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (herse.apache.org: domain of joerg.heinicke@gmx.de
 designates 213.165.64.20 as permitted sender)
Message-ID: <46984C91.7080605@gmx.de>
Date: Sat, 14 Jul 2007 00:09:53 -0400
From: Joerg Heinicke <joerg.heinicke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: JSP integration
References: <BAY121-W89F25F24A6163E94DACF5AD0C0@phx.gbl>
 <46951373.6050507@gmx.de> <4695F507.4080708@apache.org>
 <loom.20070713T214606-983@post.gmane.org> <4697E777.4030806@apache.org>
In-Reply-To: <4697E777.4030806@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 13.07.2007 16:58, Grzegorz Kossakowski wrote:

> I really have no experience with JSP and I don't know how its servlet is 
> initialized and how it works. If you could explain what could be a 
> possible problem I would try to answer according to my knowledge.

Me neither. My last project was the first with JSP and that's purely in 
the portlet environment. So no request dispatcher or other stuff.

You can have a look at the implementation of the 2.1's JSP block and the 
different JSPEngine implementations [1]. This kind of integration always 
caused many different kinds of problems, some things (forward and 
include) were not supported at all.

> As a side-note: If particular servlet must be managed by servlet 
> container can't we create servlet (as a Spring bean) that would forward 
> all requests to the JSP servlet using request dispatcher: 
> http://www.jguru.com/faq/view.jsp?EID=206736 ?

No idea. Never worked on that level.

Joerg

[1] 
http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/src/blocks/jsp/java/org/apache/cocoon/components/jsp/