Hi
We have started an attemt to integrate Turbine to our JMX (Java Management
eXtensions from Sun) based network agent framework. The framework includes
its own server and doesn't support servlets directly but a somewaht lighter
concept that we call request processors. It was a straightforward task to
convert the Turbine servlet into a processor and get the system running.
However, two static classes caused some problems.
1) It would be useful if the static Log supported customizable instances
that could redirect log messages to whatever logging system is used in the
integrating environment.
2) TurbineServices implements nicely the ServiceBroker interface and
provides protected constructors. However, the instance member is private and
the getInstance method returns a reference to the class instance, not to the
implemented interface, although the getService method of the interface is
almost the only one needed outside the class. A possibility to extend and
customize the TurbineServices instance would make it possible to support
other service construction methods than Class.forName and additional broker
mechanisms.
Other components of Turbine, like assembler factories, seemed to be
extremely well configurable and customizable. The need to modify some of the
base classes arise from our JMX based object management and broker system
that we'd like to use for Turbine based objects also. One benefit of a
separate broker system is a possibility to use different instances of the
same Turbine module class depending on the context, e.g. pages maintaining
state of a group of users and supporting several simultaneous groups.
Ilkka
--
Ilkka Priha
Nokia Networks
http://www.nokia.com/networks
mail: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
