unbound(ed)
April 6th, 2008Axis 1, which I might as well call “Mrs. Picky of WSDL parsing which also gives completely delusive error messages” surprised me somewhat today. No, in principle it was not Axis 1 but XFire; I wanted to parse an old service developed for Globus Toolkit 4 – and thus Axis 1 – but received the following error message:
java.lang.NumberFormatException: For input string: “unbound”
At first I though it was as stupid as the normal Axis 1 exception – “Mystery error” and the like – but then it occurred to me that I once corrected some maxOccurs elements from unbound to unbounded, even though Axis 1 does not seem to mind. Indeed, the error was in the WSDL:
type="vo:VOMemberType" minOccurs="0" maxOccurs="unbound">
I have corrected it now, but I wonder why exactly Axis 1 is so lazy and does allow unbound instead of unbounded.
