Andreas > I didn't express my idea clearly. What I meant was that in my proposal, only > the transports coming from Synapse will have new package names, so there is > no impact on the Axis2 community in general and the package renames will > only be a concern for Synapse.
My only concern is that this is meant to be unifying the transports. The history of this was that we somehow ended up with two sets of transports instead of just one. I think it would be a big shame to end up with one set of transports, finally, but have the package names somehow continue to propagate the old view and old disjoint structure. That is why I really liked your delegate proposal. In fact I personally wouldn't put the delegates into Synapse. I don't think Synapse users are really using the Axis2 transports and I think most of them can handle changing the axis2.xml. I would save the delegates for the Axis2 1.5 release when there are no more transports in the core Axis2 build. Paul PS Sorry everyone to cause such fun over what I thought was simple :) Maybe we should have spent the hours on hacking towards an Axis2 1.5 release instead :) -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
