There is some code in axis2-jaxws that in a particular case leads to the replacement of a SOAPFault by an OMSourcedElement. It turns out that that only worked because of a bug in Axiom that I fixed yesterday: the SOAPBody#hasFault() implementation attempted to cache the result, but the cached value was not reset if the content of the SOAPBody changed. I'm preparing a fix that avoids the substitution of a SOAPFault by an OMSourcedElement so that the result of hasFault() is consistent.
Andreas On Fri, Jul 6, 2012 at 9:29 AM, Sagara Gunathunga <[email protected]> wrote: > Any idea on following test failures ? > > On Fri, Jul 6, 2012 at 2:03 AM, Apache Jenkins Server > <[email protected]> wrote: >> See >> <https://builds.apache.org/job/Axis2/org.apache.axis2$axis2-jaxws-integration/1615/> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Sagara Gunathunga > > Blog - http://ssagara.blogspot.com > Web - http://people.apache.org/~sagara/ > LinkedIn - http://www.linkedin.com/in/ssagara > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
