On Sun, 2003-01-26 at 13:20, Quinton McCombs wrote: > I would like to propose that we drop stop using the strutum lifecyle > interfaces altogether in favor of Avalon's interfaces.
+1 They should never have been used. I should have used Avalon's lifecycle interfaces from the start. I have a different opinion of Avalon now :-) > Right now > Turbine only using the component loader (Stratum based) for loading > Torque and Fulcrum. To replace this, we should use ECM for loading of > Torque and Fulcrum. Using an existing container for loading components/services is a far better idea. Remember there is also Plexus which currently supports the newer Avalon lifecycle (the only change being Serviceable for Compose) and will be augmented to run ECM and Phoenix components. There's a Maven plugin for Plexus which allows you to assemble runtimes from configuration. The plugin also has stubs for components and testing mechanism for each component you generate using the plugin. Plexus can run as the whole environment, like an application server, or you can embed it in something like a servlet. Summit, the refactoring of t3, can run inside Plexus or have Plexus work inside it which is how Turbine currently works. > Torque would need to implement Avalon's lifecycle interfaces instead of > Stratum's. A separate message was just posted to the torque-dev about > this. The more Avalon the better. > Turbine's core services could also be loaded as components. This would > virtually do away with the current service loading scheme. All of the > current logic in TurbineServices (and all related service management > code) would be handled by ECM (Avalon's component manager). You could probably get rid of it all together. > > > The next issue is that of logging. Although ECM 4.1 will not make use > of log4j, the latest development version does appear to do so. I have > played around with this a little but I don't have that working yet. Log4j is supported in Plexus. I haven't taken a look at Fulcrum in a while, but I have ported the XMLRPC service to Plexus, there's a Scheduler based on Quartz. An EbXml capable Messenger, a Petrinet-based Workflow Engine, Summit of course, a Velocity component, and a Jetty component. > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
