axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "robert lazarski" <>
Subject Re: Just a thought
Date Fri, 29 Dec 2006 20:24:25 GMT
Is this an example of what you may have in mind?


On 12/29/06, Ivan Latysh <> wrote:
> 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,
>   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
>   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                
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message