On Thu, 6 Sep 2001, javi . wrote:
> Date: Thu, 06 Sep 2001 21:45:46 +0000
> From: javi . <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: xsl by extension
>
> Thanks, craig, but i'm working with version 3.3. żisn't any
> alternative avalaible?
Nope ... if you map your extension to your servlet, you cannot also map it
to the JSP servlet.
> it seems it should be a quite common
> problem...
>
That's why filters were added in servlet 2.3 :-).
> jv
>
Craig
>
> >From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: <[EMAIL PROTECTED]>
> >Subject: Re: xsl by extension
> >Date: Thu, 6 Sep 2001 14:37:43 -0700 (PDT)
> >
> >In a servlet 2.3 environment (i.e. Tomcat 4) you can do this sort of thing
> >with a Filter. You would map *.xtp to the JSP servlet, and then apply
> >your filter as well to the response.
> >
> >Craig
> >
> > >
> > > i'm trying to add to tomcat a nice feature of resin:
> > > automatically apply a xsl transformation over all files
> > > with .xtp extension (xml templates).
> > >
> > > i've already done it, simply associating that extension
> > > to my servlet. the servlet read the xsl path
> > > from the .xtp itself.
> > >
> > > the problem is that i want to allow the jsp code in the
> > > xtp file to be executed, so i must retrieve it via http and not from
> > > the os file system... but when i do it, of course, my
> > > xtp servlet catch de call and began a recursive loop!
> > >
>
>
> _________________________________________________________________
> Descargue GRATUITAMENTE MSN Explorer en http://explorer.msn.es/intl.asp
>
>
