Re: Exceptions due to freemarker's use of non-thread-safe DOM library

Tuesday, July 19, 2011, 10:16:35 AM, Daniel Dekany wrote:

[snip]
>> I'll revisit the proxy solution, maybe I can get that to work
>> somehow..  I have an idea.  If not I'm going to be hacking at your library pure and simple.
>
> And if you sign a Contributor License Agreement then you could commit
> that.

Actually, you don't even have to do that. A point of object wrapping
in FM is customizability after all. So you can copy the
freemarker.ext.dom package and rename it to, say,
com.d3onc.freemarker.dom and do the other changes (the license allows
that), then extend the DefaultObjectWrapper (if you are using that) so
that it uses your DOM wrapper instead of the built-in one. Of course,
if you do this, it would be good if you release the wrapper with a
Free licence so others can use it, and even better if you sign a CLA
and we can integrate it (as freemarker.ext.syncdom or like, then it
can become the default DOM wrapper in 2.4 or something, and a
recommended choice in 2.3.x).

-- 
Best regards,
 Daniel Dekany


------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/