Re: [FM3] Remove BeansWrapper and some of its settings

These all sound like good changes, and clarify what is really going on. Removing object wrapping IMO is more important than removing the *Template*Model* interfaces. These interfaces don't have the same runtime and GC overhead as object wrapping and they can be nice for type checking to

[FM3] Remove BeansWrapper and some of its settings

In FM3, I propose removing some legacy complexity: - Remove BeansWrapper, which is the super class of DefaultObjectWrapper, and add its functionality directly to DeafultObjectWrapper. That we have this class hierarchy has purely historical reasons. (Even if FM2, using pure BeansWrapper is

Re: About a Freemarker template evaluator service

I'd probably add something (like tester) as just -online doesn't seem to say what it is. On Fri, Feb 24, 2017 at 9:07 AM, Daniel Dekany wrote: > I will request a Git repo for the evaluator service. Then I will ask > Kenshoo to submit an ICLA, and make a pull request on

Re: About a Freemarker template evaluator service

I will request a Git repo for the evaluator service. Then I will ask Kenshoo to submit an ICLA, and make a pull request on that repository. What should be the name of the repository? If nobody says otherwise, it will be incubating-freemarker-online. (See our currently existing repos here: