Are the new Interceptors defined in any dtd ?

[Arieh Markel <Ar...@Central.Sun.COM>]

> Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
> X-No-Archive: yes
> list-help: <ma...@jakarta.apache.org>
> list-unsubscribe: <ma...@jakarta.apache.org>
> list-post: <ma...@jakarta.apache.org>
> Delivered-To: mailing list tomcat-dev@jakarta.apache.org
> From: costin@eng.sun.com
> To: tomcat-dev@jakarta.apache.org, Arieh Markel <Ar...@central.sun.com>
> Subject: Re: Help with Interceptors
> 
> > The idea I have in mind, is that the Interceptor will look at the Properties
> > of the HttpServletRequest, and depending on its finding, do things like:
> > 
> > 	. add a property to the request
> > 	. selectively perform a servlet redirection
> > 	. return an error message
> > 
> > Would ServiceInterceptor, or SecurityInterceptor be good starting points ?
> 
> RequestInterceptor if you want to process the request.
> ContextInterceptor if you want "container"-event notifications.
> 
> ( we are still working on this - but I think there are stable now, 
> except configuration and few small details )
> 
> 
> Service and Security Interceptor are used by J2EE, will be part of the
> J2EE "adapter".

Has anybody incorporated a 'dtd' that includes the definitions of
the new Interceptors.

(The current server.dtd includes just an Interceptor object).

Arieh
--
 Arieh Markel		                Sun Microsystems Inc.
 Network Storage                        500 Eldorado Blvd. MS UBRM11-194
 e-mail: arieh.markel@sun.COM           Broomfield, CO 80021
 Let's go Panthers !!!!                 Phone: (303) 272-8547 x78547
 (e-mail me with subject SEND PUBLIC KEY to get public key)

Re: Are the new Interceptors defined in any dtd ?

[co...@eng.sun.com]

> Has anybody incorporated a 'dtd' that includes the definitions of
> the new Interceptors.
> 
> (The current server.dtd includes just an Interceptor object).

If you are talking about server.dtd, there are few other problems.

We need to do a lot of changes in server.xml ( to add logging, session
management, interceptors), and the main problem is that we _don't_ know
how to do it :-)

For 3.1 we will add the missing elements and change a bit the structure of
server.xml, but I don't think anyone can expect it to be "final".

( i.e. probably you'll be able to add intreceptors and configure
everything, but we'll need a lot of feedback and experiments before 
defining a DTD. It will be _very_ hard, and probably we need to discuss
that on many lists ! ) 



Costin