+1 :)
On 11/10/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > On Thu, 2005-11-10 at 07:50 -0500, Srinath Perera wrote: > > I am bit worried about moving the Adressing module outside .. as it is > > used almost all the time and complete Async (transport level) can not > > work without it. If addressing is removed it remove half of the > > messaging capabilities. > > Right ... but that's possible anyway; support for WS-Addr is turned on > only if you engage the module so its an extension point. I'm not > disagreeing with *shipping* it with the std axis2 distros, what I'm > saying is that the evolution of the WS-Addr module and its release > cycles and the release cycles of the main Axis2 system do not have to be > tied together. > > For example, suppose we find a bug in the addressing module- right now > we can't release that unless we do a full release of Axis2. If that's > separate then we just release a new version and users who want the fix > simply drop the new .mar in, reboot and they're off and running with the > bugfix. > > IMO that's a very valuable feature of the Axis2 module arch which we > need to enable cleanly for addressing, which is clearly the most > fundamental module. The way to do that is to separate the module into > the addressing project. > > Sanjiva. > >
