From dev-return-95664-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Fri Jul 13 20:59:04 2007 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 48272 invoked from network); 13 Jul 2007 20:59:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Jul 2007 20:59:02 -0000 Received: (qmail 52788 invoked by uid 500); 13 Jul 2007 20:59:04 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 52726 invoked by uid 500); 13 Jul 2007 20:59:04 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 52715 invoked by uid 99); 13 Jul 2007 20:59:04 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jul 2007 13:59:04 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [216.86.168.179] (HELO mxout-04.mxes.net) (216.86.168.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jul 2007 13:59:00 -0700 Received: from [192.168.0.129] (unknown [80.240.191.89]) by smtp.mxes.net (Postfix) with ESMTP id 0D35DA321C for ; Fri, 13 Jul 2007 16:58:38 -0400 (EDT) Message-ID: <4697E777.4030806@apache.org> Date: Fri, 13 Jul 2007 22:58:31 +0200 From: Grzegorz Kossakowski User-Agent: Thunderbird 2.0.0.4 (X11/20070604) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: JSP integration References: <46951373.6050507@gmx.de> <4695F507.4080708@apache.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Joerg Heinicke pisze: > On 12.07.2007 05:31, Grzegorz Kossakowski wrote: > > How is that supposed to work with JSPs where Jasper (when using Tomcat) needs to > kick in and compile the JSPs? From what I understand other servlets need to be > registered in Cocoon (or the underlying Spring container). Doesn't that make it > a servlet container in a servlet container? This approach still seems to suffer > from the "almighty Cocoon" syndrome (doing everything itself, not delegating > stuff to e.g. the servlet container). Your impression seems to be right. However, I believe that one of main goals while designing cocoon-servlet-service was to stay as transparent as possible. I guess that if we let servlet container to manage servlets we wouldn't get enough flexibility we need but it would be better if Daniel could comment as a creator of whole stuff. 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. 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 ? -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/