Hi All, It's been a long time. We are trying to upgrade to the latest Axis2 and have run into a serious issue. Axis2 now uses various MIN_VALUE's and NaN's as the marker for unset values in ADB binding code, rather than the previous behavior of using 0.
Our server needs to either have wsdl-declared defaults used, which axis2 adb message parsing code does not do, or to implement its own defaulting, which is what it has been doing. However, testing for the specific axis2 implementation market for unset values, e.g. Integer.MIN_VALUE, to discover a parameter has not been set seems too hackish. A simple solution would be to add a new method to the automatically generated ADB binding class. There are already protected localTracker boolean variables that are true iff the value has been set. Adding an is accessor for the property, e.g. is<Property>Set(), would resolve the issue simply and fully. Does this seem a reasonable thing to do or am I missing something? If it is reasonable, even though I'm now out of date on the code base, the ADBBindingTemplate.xsl is familiar ground from before. I could make this extension if no one objects, else we'll probably patch this locally. Please advise. Thanks, Chuck --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
