Hi, Todd,

Thanks for your quick reply.

Yes, I use the "is" notation quite frequently. Until now, I have been
twisting my language to fit this notation, but it is starting to bother me a
bit. At times, it is not very natural and I prefer to use variables (and
corresponding getters/setters) as descriptive and appropriate as possible.

I was just wondering if it is possible, without too much difficultly, to get
Tapestry to understand "non-is" style boolean getters/setters.


:dml



> -----Original Message-----
> From: Todd O'Bryan [mailto:[EMAIL PROTECTED]
> Sent: 2 April 2005 15:32
> To: Tapestry users
> Subject: Re: Modifying values of getters/setters
>
>
> Actually, "is" is supported by OGNL for booleans. So you could use
> isVisible() or isInitialized() (I assume that or something like it is
> what hasValue() means) for the cases you mention.
>
> Todd
>
> On Apr 2, 2005, at 1:21 AM, David Leangen wrote:
>
> >
> > Is it possible to change what Tapestry considers a valid getter/setter
> > name?
> >
> > Specifically, I have boolean values such as:
> >
> >  - showComponent
> >  - hideComponent
> >  - hasValue
> >
> > etc.
> >
> >
> > It appears that I have to use getters/setters such as:
> >
> >  - getShowComponent
> >  - getHideComponent
> >  - getHasValue
> >
> >
> > This is kinda ugly... can this be changed so I can use getters/setters
> > like:
> >
> >  - showComponent()
> >  - hideComponent()
> >  - hasValue()
> >
> >
> > For instance:
> >
> >  if(hasValue())
> >  {
> >     doSomething();
> >  }
> >
> >
> >
> > Thanks!
> >
> > Dave
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to