Oops! Got the tags wrong; the filter names
should match. One more error this week,
but who's counting?
>
>
> XSLT Filter for Skin1
> XSLTFilter
>
> xsltFileName
> skin1.xsl
>
>
>
>
> Skin1Command
> command
>
XSLT Filter for Skin1
XSLTFilter
xsltFileName
skin1.xsl
XSLT
Craig R. McClanahan wrote:
>
> Yep, you've got the pattern down. It's also legal to use
> HttpServletResponseWrapper if you're wrapping HTTP responses. And, of
> course, you can wrap the request if you want to do input filtering, in
> pretty much the same manner.
>
> Craig
>
>
>
Ok, than
pply on the original request -- they do
not get invoked when a servlet or JSP page is accessed through a
RequestDispatcher.
> thanks.
>
Craig
>
> > -Original Message-
> > From: Bob Jamison [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, April 25, 2001 9:14 AM
>
On Wed, 25 Apr 2001, Bob Jamison wrote:
> Amy Roh wrote:
>
> > Servlet spec 2.3 has changed to support init(FilterConfig config) and
> > destroy() methods instead of getFilterConfig() and
> > setFilterConfig(FilterConfig config) after discussion to change filter cycle
> > to be similar to the
; From: Bob Jamison [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 25, 2001 9:14 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Future of Filter?
>
>
> Amy Roh wrote:
>
> > Servlet spec 2.3 has changed to support init(FilterConfig
> config) and
> > destroy(
Amy Roh wrote:
> Servlet spec 2.3 has changed to support init(FilterConfig config) and
> destroy() methods instead of getFilterConfig() and
> setFilterConfig(FilterConfig config) after discussion to change filter cycle
> to be similar to the servlet life cycle in the expert group. The recent
> c
Servlet spec 2.3 has changed to support init(FilterConfig config) and
destroy() methods instead of getFilterConfig() and
setFilterConfig(FilterConfig config) after discussion to change filter cycle
to be similar to the servlet life cycle in the expert group. The recent
changes will be reflected i
Servlet spec 2.3 has changed to support init(FilterConfig config) and
destroy() methods instead of getFilterConfig() and
setFilterConfig(FilterConfig config) after discussion to change filter cycle
to be similar to the servlet life cycle in the expert group. The recent
changes will be reflected i
nd something about a "head start" on IIS and Netscape?
This could mean anything... does anyone know the scoop?
Thanks,
Steve
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 01, 2001 7:01 AM
> To: '[EMAIL PROTECTED]
>
> I noticed that isapi_redirect.dll uses ajp12, but ajp13 is already out (and
> better than ajp12), and there are talks of ajp14 and mod_webapp and other
> new Connector
> ideas...
Are you sure ?
I thought isapi_redirect is built from the same sources as mod_jk, and has
all the protocols ( a
Another overwhelming diplomacy lesson... I guess.
Have fun,
Paulo Gaspar
> -Original Message-
> From: Jon Stevens [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 20, 2000 01:21
> To: tomcat-dev
> Subject: future questions
>
>
> Lets see how many of these questions come up in the
on 12/21/2000 1:44 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>>> Speaking of future, the same thing can happen when the next servlet spec
>>> is released - and again you could use tomcat3.3 to have a smooth future.
>>> I know how painfull it is to upgrade a production server - how many s
> > Speaking of future, the same thing can happen when the next servlet spec
> > is released - and again you could use tomcat3.3 to have a smooth future.
> > I know how painfull it is to upgrade a production server - how many small
> > things will stop working and many things will be different.
>
Hi again, Jon.
> I downloaded the latest J2EE and it includes Tomcat. However, when I looked
> on your website, it says that you have two versions of Tomcat. Which one
> comes with J2EE? Which one should I be using?
I'm sure J2EE will have a README telling you what version it includes.
As for "
[EMAIL PROTECTED] wrote:
> 1+
>
> The problem, of course, is that the critical functionality is evolving so
> rapidly, that most "users" prefer the developer list, since that is where
> the action is. This is the downside of a Open Source project such as Tomcat
> (as opposed to the Apache Server
> From: Jon Stevens [mailto:[EMAIL PROTECTED]]
>
> on 12/19/2000 4:26 PM, "David Rees" <[EMAIL PROTECTED]> wrote:
>
> > How about forwarding them or pointing them to the tomcat-user list where
> > these questions will be answered?
>
> Because not everyone wants to subscribe to a mailing list to ju
"David Rees"
c.com> cc:
Subject: RE:
on 12/19/2000 4:26 PM, "David Rees" <[EMAIL PROTECTED]> wrote:
> How about forwarding them or pointing them to the tomcat-user list where
> these questions will be answered?
>
> -Dave
Because not everyone wants to subscribe to a mailing list to just get a
simple question answered.
-jon
> From: Jon Stevens [mailto:[EMAIL PROTECTED]]
>
> p.s. Costin, I had a great idea. I'm going to forward to you all of the
> personal email based Tomcat support questions that I get. Have
> fun answering
> them. :-)
How about forwarding them or pointing them to the tomcat-user list where
these q
19 matches
Mail list logo
