Revision as of 06:46, 11 April 2010 edit Tabletop (talk \| contribs) Extended confirmed users, Pending changes reviewers 177,774 edits m Spell acess => access ← Previous edit		Revision as of 21:20, 5 May 2010 edit undo Pmerson (talk \| contribs) 99 edits java ee filters; aop Next edit →
Line 6: Typical users of this pattern are web-servers<ref name="tomcat">[http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html Apache Software Foundation: Tomcat 6.0 Channel Interceptor Reference, accessed 2009-Nov-24]</ref> (as mentioned above), object-<ref name="CORBA-PI">[http://www.omg.org/spec/CORBA/3.1/ OMG, "CORBA v3.1, Part I: Interfaces", Chapter 16 "Portable Interceptors", January 2008]</ref> and message-oriented middleware<ref name="MOM">[http://www.edwardcurry.org/web_publications/curry_DEBS_04.pdf E. Curry, D. Chambers, and G. Lyons, “Extending Message-Oriented Middleware using Interception”, presented at Third International Workshop on Distributed Event-Based Systems (DEBS '04), ICSE '04, Edinburgh, Scotland, UK, 2004.]</ref> An example of implementation of this pattern is the ''javax.servlet.Filter'' interface, which is part of [[Java Platform, Enterprise Edition]]. [[Aspect-oriented programming \| Aspect-Oriented Programming (AOP)]] can also be used in some situations to provide the capability of an interceptor, although AOP doesn't use the elements typically defined for the interceptor pattern. == References ==

Interceptor pattern: Difference between revisions