Axis 1.2 RC1
OK, this release of Axis is worse than we previously thought. We're in the process of changing the name of an operation, and thought the easiest way to manage the change was to bring in another operation (being the new name), switch the tests over to the new operation, then remvoe the old operation. Simple.
Turns out Axis doesn't like two operations on the same port (my teminology may be wrong) with the same parameters. It generates code just fine, but ignores the SOAPAction
header, selecting the first operation defined in the WSDL, instead of the one specified by the action header.
Nice one.
Update: Turns out that the I cannot reproduce this again on a different machine. We've changed the WSDL subtely (namespaces and element names), again which scares me.
0 Comments:
Post a Comment
<< Home