struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d..@struts.apache.org
Subject [Apache Struts Wiki] Updated: StrutsCatalogBaseAction
Date Mon, 17 May 2004 02:43:53 GMT
   Date: 2004-05-16T19:43:53
   Editor: 211.93.110.199 <>
   Wiki: Apache Struts Wiki
   Page: StrutsCatalogBaseAction
   URL: http://wiki.apache.org/struts/StrutsCatalogBaseAction

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -35,3 +35,4 @@
 I have been using this idea on mid-size project and finally changed my mind. It's fine but
sooner or later you 'll realize that it would be cool to use built-in struts actions like
DispatchAction and others that provide useful functionalities. Then, as java does still not
provide multiple inheritance, you are forced to  either build a full hierarchy of abstract
actions (with one abstract actions for each kinda of built-in action you want to reuse), or
you end up adding more and more functionality to your base class. It seems to me that the
only real interest of this method is when you want to enforce the execution of a given piece
of code on each action execution (like verifying that the user is logged in), but infact to
do this a proper customization of the ActionServlet or RequestProcessor should be better (or
even a Servlet filter but this a more tedious job).
 
 -- Nicolas JOUVE from France
+[[&#12424;&#12429;&#12375;&#12367;]]

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message