using a recent CVS version,
> but I've noticed this happening in older versions as well.
> Any ideas? What am I doing wrong that its not looking for the write
> methods?
>
> Thanks!
> -Nick
>
> ---Original Message-
> --From: Keith Visco [mailto:[EMAIL PROTE
ECTED]
--Subject: Re: [castor-dev] Get/set for booleans
--
--
--This one time, at band camp, Nick Stuart said:
--
--NS>The get/set methods make sense. But I'm not having any
--luck with the
--NS>boolean. Here's an example of what I'm doing...
--NS&g
This one time, at band camp, Nick Stuart said:
NS>The get/set methods make sense. But I'm not having any luck with the
NS>boolean. Here's an example of what I'm doing...
NS>
NS> identity="id"
NS>depends="com.vort.ads.vortsentry.beans.VortSentryDims"
NS>key-generator="IDENTITY">
NS>.
IL PROTECTED]
--Sent: Tuesday, July 13, 2004 4:00 PM
--To: [EMAIL PROTECTED]
--Subject: Re: [castor-dev] Get/set for booleans
--
--
--
--Hi Nick,
--
--Castor supports "isSomething" for booleans, it's working for me.
--
--As for specifying only a getter and not the setter. The
--behavi
Hi Nick,
Castor supports "isSomething" for booleans, it's working for me.
As for specifying only a getter and not the setter. The behavior in
Castor is that if you don't specify any accessor methods, Castor will
look for them and try and determine them automatically. But if you only
specify one
Ok, this has kind of been annoying me for awhile now and was wondering
if anyone else had the same issue. When ever I do boolean get/set method
the standard get format is
Public boolean isSomethingBlah(){...}
But castor complains when I don't supply specific get-method=""
set-method="" in the ma
