I believe, and the spec concurs, that the isFoo pattern is optional:
http://java.sun.com/products/javabeans/docs/beans.101.pdf

8.3.2 Boolean properties
In addition, for boolean properties, we allow a getter method to match the
pattern:

  public boolean is< PropertyName>();

This "is<PropertyName>" method may be provided instead of a
"get<PropertyName>" meth-od,

or it may be provided in addition to a "get<PropertyName>" method.

---

But that is kind of beside the point. The key thing is that isFoo() is
legit.

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 19, 2003 12:53
Subject: DO NOT REPLY [Bug 17218] - wsdl2java tool prefixes boolean
accessors with "is"


> 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"
>
> [EMAIL PROTECTED] changed:
>
>            What    |Removed                     |Added
> --------------------------------------------------------------------------
--
>              Status|NEW                         |RESOLVED
>          Resolution|                            |INVALID
>
>
>
> ------- Additional Comments From [EMAIL PROTECTED]  2003-02-19
20:53 -------
> Um, no. :)
>
> Go read the JavaBeans spec, it actually requires that boolean accessors
are
> named "is" and not "get".  The names of the XML elements/attributes are
opaque
> to us, which is as they should be.  We just generate getters/setters based
on
> type.  We could, I suppose, say IF the element is an xsd:boolean AND
starts
> with "is" then don't double the is... but then you'd get <element
> name="isildorWasStupid" type="xsd:boolean"/> and things would break.
>
> So I'm marking this INVALID.
>

Reply via email to