I don't think we should support SOAP Encoding in Axis2. The encoding framework needs to die.
On 2/2/07, Harish Hirasave <[EMAIL PROTECTED]> wrote:
I tried migrating from axis 1 to axis 2 but had to stop after a month's effort as our clients are not ready for it. Axis 2 does not support soap encoding and this involves changes on our client's side and they are not ready for it. Axis 2 has better features compared to axis 1 in terms of documentation, deployment, tools etc. and I really wanted to upgrade to axis 2 but cannot due to business reasons as axis 2 does not support soap encoding. So did we do right thing by not supporting soap encoded messages when not everybody is ready for it? Would it not have been better if we had supported soap encoding in axis2? Experts like Anne and others should have an answer. Thanks Harish
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
