Hi, I have started playing with some service refactoring for 2.2 so I wanted to mention a couple things. I am trying to refactor the services so that we can understand the code more clearly before we decide how to change it further. I think the first type of refactoring that needs to be done is the type which makes the code accessible to more developers. I definitely have problems tracing through the services code because of the hierarhical weirdness between Initable related classes and the rest of the service code. And I know that others have problems too. The services framework _works_ so a rewrite is not warranted nor do I think it necessary. But some clarifcation is definitely needed before we tackle anything like removing all late initialization code, or allow pluggable services. The goal is to be 100% backward compatible and give us a starting place for some useful additions. As I am making these changes I am also adding tests. So I propose the use of the system that is used in the commons. They have a src/java tree and there is a src/test tree. The src/test tree is laid out the same src/java tree so that package scope tests are possible but the test code is cleanly separated from rest of the code. I am planning to start adding this code in when I get back to Toronto, I would also like to start some serious work on 2.2 so I'd like to get some discussions going next week. So does anyone have any concerns about the services? Any thoughts? -- jvz. Jason van Zyl [EMAIL PROTECTED] http://jakarta.apache.org/velocity http://jakarta.apache.org/turbine http://jakarta.apache.org/commons http://tambora.zenplex.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
