I can of course only answer this for my self, but the main reason is Struts is an 
implementation of a specific pattern. When I started writing J2EE applications some 
time ago, struts was not fully grown. I had a pattern in my mind that I wanted to have 
an implementation of. The main thing in this pattern is the servlet chaining mechanism 
(btw, filters had not be introduced (to tomcat or other app servers) when I wrote this 
chaining mechanism).
I have to admitt the fact that I have never used struts, and I have not really spent a 
lot of time on checking it out. 
The functionality I wanted in my servlet-chains is the ability to create streamlines, 
that have can have multiple starting nodes and an multiple stop nodes. This means I 
need to be able to build in some "flow logic" into the servlet chain mechanism, I 
can't see how that would be done with filters, at least not in the way I want. 
Each servlet in a chain has some specific purpouse such as determine the user who is 
logged on, determine some data that will be used in the presentation layer below the 
chain. If anyone has seen Intershops Enfinity Pipelines my application does similar 
things, in similar ways except less propriatary.

So I think servlet chaining, struts and filters all describe sepperate patterns even 
though there isn't much difference between them. 

-reynir

Ps.
 - Just saw your reply about barracuda, it's cool, I would say a different 
implementation of a similar functionality. 



> -----Original Message-----
> From: Jacob Hookom [mailto:[EMAIL PROTECTED]] 
> Sent: 16. jan�ar 2003 19:44
> To: 'Tomcat Users List'
> Subject: RE: Servlet channing
> 
> 
> Instead of chaining servlets, why not look at filters, whose 
> specific purpose is to work on a chain.  There is even some 
> talk of switching struts over from a servlet to a filter in a 
> later release.
> 
> Jacob
> 
> | -----Original Message-----
> | From: Reynir H�bner [mailto:[EMAIL PROTECTED]]
> | Sent: Thursday, January 16, 2003 1:29 PM
> | To: Tomcat Users List
> | Subject: RE: Servlet channing
> | 
> | Some people would recommend to you that you look into 
> struts, which is
> an
> | web-application framework.
> | 
> | Servlet chaining in it's most simple way is a servlet that forwards
> the
> | request to another servlet. This can be achived by using the 
> | RequestDispatcher, be aware that using the 
> RequestDispatcher may slow
> your
> | application down a little bit because (I've heard) it's not fully 
> | optimized in tomcat.
> | 
> | I wrote servlet-chaining mechanism, it was not hard to do, so I
> recommend
> | that if this is something you really think you need, you 
> should write
> your
> | own servlet chianing API.
> | 
> | -reynir
> | 
> | 
> | > -----Original Message-----
> | > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> | > Sent: 16. jan�ar 2003 18:29
> | > To: Tomcat Users List
> | > Subject: Re: Servlet channing
> | >
> | >
> | >
> | >
> | > On Thu, 16 Jan 2003, nitin mandolkar wrote:
> | >
> | > > Date: Thu, 16 Jan 2003 05:45:12 +0000 (GMT)
> | > > From: nitin mandolkar <[EMAIL PROTECTED]>
> | > > Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> | > > To: [EMAIL PROTECTED]
> | > > Subject: Servlet channing
> | > >
> | > >
> | > > How to achive servlet channing with tomcat
> | >
> | > Servlet chaining (in the manner you describe) is not supported by 
> | > the servlet spec.  However, you can accomplish something very 
> | > similar using filters instead (Tomcat 4.x or later).
> | >
> | > Craig
> | >
> | >
> | >
> | > --
> | > To unsubscribe, e-mail:
> | > <mailto:tomcat-user-> [EMAIL PROTECTED]>
> | > For
> | > additional commands,
> | > e-mail: <mailto:[EMAIL PROTECTED]>
> | >
> | >
> | 
> | --
> | To unsubscribe, e-mail:   <mailto:tomcat-user-
> | [EMAIL PROTECTED]>
> | For additional commands, e-mail: <mailto:tomcat-user- 
> | [EMAIL PROTECTED]>
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:tomcat-user-> [EMAIL PROTECTED]>
> For 
> additional commands, 
> e-mail: <mailto:[EMAIL PROTECTED]>
> 
> 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to