I don't like this behavior either...F-# what javabeans say, if you add the issue to http://jira.opensymphony.com/browse/OGNL I'll make sure it gets fixed.
On 3/13/07, Murray Collingwood <[EMAIL PROTECTED]> wrote:
Hi all Just trying to clarify my understanding. I had some code that looked like the following: @Persist public abstract Boolean isQuery(); The above code gives me an error, 'no implementation in class', and it took me a while but I finally figured the problem that the enhanced class was not identifying the Boolean. It took a while longer for me to realise it was because I didn't have a valid 'getter'. I had to change the above to: @Persist public abstract Boolean getQuery(); Suddenly everything started working! So, why doesn't the enhanced class identify these boolean style function names. I thought this was some standard that ALL property functions were fetched using get* and ALL boolean values fetched using is*. Question: 1. Should I code all of my booleans using get* in future? 2. How does OGNL now deal with a boolean value returned via a get*? Do I need to modify my OGNL conditions? Cheers mc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
