Hello All, Just want to express my gratitude to all developers who is working on the project. You have done a great job !
While browsing AXIS2 code-base and mailing list I noticed some minor issues that any project has, they are insignificant and fixable, but also I noticed one large issue that (AFAIK) hasn't been addresses well enough. And I can be mistaken, but I just want to point to it. I noticed that AXIS2 does not have defined service impl. lifecycle. We can see bit's and pieces from it all over, but no concrete definition (I refer to init() method, ServiceLifeCycle interface, etc.) From mailing list I can see that many users are confused by absence of defined lifecycle. I belive that this can be solved easy with little (or none) code refactoring. For instance let's take Apache Avalon framework, and we don't even need an implementation, just interfaces (just 28k jar). Or if dev. team don't want to bring on board one more framework, just create AXIS2 own lifecycle interfaces. Now when service impl want to be aware of different events it should implement an interface. So init() method will be defined in Initializable interface, ConfigurationContext will be given when service implement Configurable interface, when service want to know about MessageContext it implement Contextualizable. Also the great asset is to serve impl. with binding events (not data binding) when impl. bound to the request, axis session or transport session. So the beauty of this approach that existing services with just a business method will be unaffected, but it will give an extra power to the AXIS2 since developers will benefit from defined lifecycle. Anyway I would like to hear if developers are interesting in proposed solution. -- Best regards, Ivan mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
