Turbine is growing and will continue to grow. Is there any interest in making the use of these additions more dynamic? I suggest adding a service manager, and implementing something like cocoon's manager. In cocoon, there's an interface called actor. The manager can create an instance of an actor. If the actor implements the configurable interface the manager initializes it. Each actor has a "role", a name, so you can retrieve the actor from the manager by name. With this implementation, you wouldn't need to hard-code initializations for the Turbine scheduler or OPaL in the init method. You could also take care of destroying services. I'm willing to provide the code for this. It would be nice to be able to build turbine without using village. It's possible now but you have to edit the code. Would it be much trouble to divide data access so interfaces are in one directory and implementations are in another? With this approach and some cooperation from developers, it would be easy to use ant to build either with or without village. I'm would be willing to do this work also. - george __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
