Re: Passing null arguments using the undefined variable called something like nullArg does not seem to work for me any more

There shouldn't be any difference between any 2.3.x versions and
2.3.17 in that regard. I can only imagine that you are using a
different or differently configured ObjectWrapper now (like a
BeansWrapper or its subclass with a "NullModel"), or that
"classic_compatible" was accidentally set to true (if that has such
effect anyway). The last could be checked by calling
isClassicCompatible() on the freemarker.template.Configuration object.


Sunday, July 10, 2011, 6:47:42 AM, Geoff Shuetrim wrote:

> I have upgraded to use Freemarker 2.3.17 and am finding that
> passing null arguments using the undefined variable nullArg does not
> seem to work for me any more.  In particular I am finding that
> Freemarker cannot match up a function call where some of the
> parameters have null values (given as nullArg variables that have
> not been previously defined) to any existing method signature.  Is
> there some change that I should be adapting my templates to?
>
> Regards
>
> Geoff S
-- 
Best regards,
 Daniel Dekany


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2