hivemind-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta HiveMind Wiki] Updated: PojoServices
Date Mon, 02 Aug 2004 14:29:37 GMT
   Date: 2004-08-02T07:29:37
   Editor: HowardLewisShip <>
   Wiki: Jakarta HiveMind Wiki
   Page: PojoServices

   no comment

Change Log:

@@ -27,3 +27,6 @@
 Interceptor support should be extended to support both POJOs (without final methods) and
interfaces. This can be achieved by switching from inheritance to composition. 
 For example a LoggingInterceptor shouldn't specialize AbstractLoggingInterceptor but hold
a reference to a LoggingInterceptor (non abstract counterpart of AbstractLoggingInterceptor)
and delegate all the work to this instance. 
+= Discussion =
+HowardLewisShip: '''-1''' !HiveMind already has a facility for creating POJOs (BeanFactory).
However, !HiveMind  is also supposed to be about ''best practices'' including coding to interfaces.
I'm not interested in ''nice-to-haves'' I'm interested in '''specifically useful''' constructs.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message