DO NOT REPLY [Bug 17218] New: - wsdl2java tool prefixes boolean accessors with "is"

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17218>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17218

wsdl2java tool prefixes boolean accessors with "is"

           Summary: wsdl2java tool prefixes boolean accessors with "is"
           Product: Axis
           Version: 1.1RC1
          Platform: Macintosh
        OS/Version: MacOS X
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Deployment / Registries
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: jwinshell@bearriver.com


When I use xsd:boolean type as part of a complexType in WSDL,  wsdl2java tool
generates as a member in a bean class.  If I give the element a name that
implies it's type <element name="isSender" type="xsd:boolean" />
the wsdl2java will generate an getter for the field called "isIsSender" and a
setter for the field "setIsSender". 

The only way to get rid of the double "isIs" in the getter is to rename the
element to <element name="sender" type="xsd:boolean>.  My problem with this
workaround is the type of the element can no longer be deduced from the name of
the element.  I want to be able to name my xsd:boolean elements so they are
readable, i.e. "hasProperty", "isSomething", etc. with accessors named
getHasProperty, getIsSomething.  Can you please drop the generation of the "is"
prefix for boolean accessors.  That way I can control the names of boolean
accessors.