On Sun, Mar 23, 2008 at 5:47 PM, Johan Compagner <[EMAIL PROTECTED]> wrote: > hmm for 1.3 i will test it that i will always just give a cloned version > Then we can keep the map and the method just fine. > > That fix is fine by me then >
That sounds like it will work. I don't know what would be faster, but perhaps you could benchmark it. You could try a few approaches... 1. Cloning the "prototype" DecimalFormat object. 2. Just saving the pattern and DecimalFormatStrings from the passed in DecimalFormat and use those to construct a new one each time. 3. Synchronization (one one DecimalFormat instance). They're not used for that long. 4. ThreadLocal (does Wicket have any sort of facility for clearing thread locals at the end of a request cycle like Tapestry does/did?) 5. Some sort of "pool"
