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, such as the getter, it will not look for the other one, in
this case the setter. The basic reason is to allow some fields to be
"read-only" or "write-only", depending on which method was specified.
--Keith
Nick Stuart wrote:
>
> 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 mapping file. Is there any reason why we cant
> default to the isSomething format when we have a boolean? It is the
> standard way to do it that I know of. I'm just wondering if anyone has
> been down this road before and found it couldn't be done cleanly. If
> not, I'll file an enhancement request pronto and get to modifying. :)
>
> -Nick
>
> P.s. Another thing I find weird is that if I only supply the get-method
> castor still complains about no set method. Is this expected? It works
> fine when I specify it, but I don't think I should have to.
>
> ------------------------------------------------------------------------
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
