Re: java.lang.Boolean undefined

Brian Pontarelli <[email protected]>
Newsgroups gmane.comp.web.freemarker.user
Message-ID <[email protected]>
FM really should have its own property handling to ensure it can  
handle all these cases. You can then add support for other cases like:

	addFoo(Foo foo);
	removeFoo(Foo foo);
	removeFoo(int i);

Those are nice for collections. I would imagine it a simple task to  
write a custom property handle or borrow someone else's. I wrote one  
for JCatapult and it took about a day to cover all the cases.

-bp


On Jun 30, 2009, at 10:11 AM, Attila Szegedi wrote:

> Truth be told, get/set works for boolean, so if you stick with get/
> set, you can't go wrong. I sort-of agree with the sentiment, but
> that's the way it is. FreeMarker is not doing property discovery on
> its own, it uses the Java standard "java.beans.Introspector" class
> which implements the JavaBeans property protocol, and it is what it
> is...
>
> Attila.
>
> On 2009.06.30., at 18:06, Newman, John W wrote:
>
>> Try renaming isObjectBoolean to getObjectBoolean.  Gotta love such a
>> quirky convention, I've got burnt by this a few times: boolean=is/
>> set, Boolean=get/set...
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Ben Storey [mailto:[email protected]]
>> Sent: Tuesday, June 30, 2009 11:48 AM
>> To: [email protected]
>> Subject: [FreeMarker-user] java.lang.Boolean undefined
>>
>> Hi,
>>
>> I am having some problems with freemarker 2.3.14 and 2.3.15 when I
>> am trying to extract a value that returns a java.lang.Boolean value
>> and get this exception.
>>
>> Expression model.objectBoolean is undefined on line 1, column 64 in
>> testObjectBoolean.ftl.
>> The problematic instruction:
>> ----------
>> ==> ${model.objectBoolean?string} [on line 1, column 62 in
>> testObjectBoolean.ftl]
>> ----------
>>
>> Java backtrace for programmers:
>> ----------
>> freemarker.core.InvalidReferenceException: Expression
>> model.objectBoolean is undefined on line 1, column 64 in
>> testObjectBoolean.ftl.
>> 	at freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:
>> 124)
>>
>>
>> For example I have attached a test case that I have been running and
>> the second test always fails even though the value has been set. Any
>> help on how to resolve this issue would be greatly appreciated.
>>
>> Cheers
>>
>> Ben
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> FreeMarker-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freemarker-user


------------------------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.