axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Illsley" <>
Subject Re: [Axis2] Loosing backward compatibility with 1.1
Date Tue, 13 Feb 2007 13:59:12 GMT
Agreed. I was worried about this when I saw the MEP constants change
but I assumed someone had checked things still work.

Maybe we should have a prebuilt axis2 1.1 aar and client as part of
the integration tests as a quick way of catching this kind of problem?


On 13/02/07, Thilina Gunarathne <> wrote:
> Hi all,
> While doing development for the Kandula2, I noticed that we are
> increasingly loosing the backwards compatibility with Axis2 1.1..
> Kandula2 build which was fully up and running two weeks back is
> continuously failing now..
> While the missing SOAPAction issues in the codegen were fixed today,
> again now I was struck with the MEP validation done by the
> getAxisSpecifMEPConstant method of the o.a.a.util.Utils method which
> was called by the AddressingValidationHandler. This method throws an
> error if the service.xml contains the old MEP URI's which Axis2 had
> prior to the wsdl2.0 merge.. AFAIK it was decided in this[1] thread to
> support the old name spaces until 1.2.
> I accept that I can change these things in Kandula2. But IMHO we need
> to think seriously about the losing of backward compatibility with
> services deployed with Axis2 1.1...
> Thanks,
> Thilina
> [1]
> --
> Thilina Gunarathne
> WSO2, Inc.;
> Home page:
> Blog:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

David Illsley - IBM Web Services Development

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

View raw message