Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 55380 invoked by uid 500); 7 Sep 2001 03:07:57 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 55337 invoked from network); 7 Sep 2001 03:07:56 -0000 User-Agent: Microsoft-Entourage/9.0.2509 Date: Fri, 07 Sep 2001 04:07:58 +0100 Subject: Re: xsl by extension From: Pier Fumagalli To: Message-ID: In-Reply-To: Mime-version: 1.0 Organization: Sun Microsystems - Apache Software Foundation Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N "cmanolache@yahoo.com" wrote: > Another ( and better ) solution - extend JspInterceptor ( well, the code > needs some cleanup - again I would recomend you do that in j34 workspace > ). > > Then you can add the dependencies and avoid any overhead - your XSP pages > will run as fast as a servlet, without any extra dispatching or > intermediary servlet. > > BTW, I'm happy I'm not alone on xsl and jasper :-) > > Let me know if I can help. Of course none of this is portable across servlet containers, but we seem to easily forget about that :) Being Tomcat the Reference Implementation, as an ASF member, and Servlet JSR member, I'll never stop stressing out that IMNSO relying on container-specific features IS to any extent WRONG unless this can not in ANY WAY done otherwise. One alternative I might be suggesting is Cocoon, which is fully portable across platforms, and deals with XML data more or less in the way that Javi needs to, but also that somehow is tricky, as you might get tied to the Cocoon architecture. Remember, never get down to compromises with your container unless you're forced to, and absolutely ready to be tied to that particular container for a very long time (I could understand sticking to Cocoon, since it runs in any servlet container, I wouldn't be so sure for certain Servlet API extensions, such as interceptors in TC3.x, or Valves -for what that matters- in TC4.x)... That's just my 0.02$, but wearing the hats I'm wearing, I believe I'm fairly on the fair side here... Pier