Exactly. I had a component with its own converter and my memory profiler showed that it ended up hogging 200 MB.
Ofcourse I can organize my own singleton library of converters.. but Wicket has its own ConverterLocator. I would like to hear if someone has made such an implementation of ConverterLocator that you can have 'tuned' converters - instead of just one converter per type. ** Martin 2009/2/8 Thomas Mäder <[email protected]>: > You can override getConverter() on a component to return any converter you > want. > > Thomas > > On Sun, Feb 8, 2009 at 6:53 PM, Martin Makundi < > [email protected]> wrote: > >> Hi! >> >> I am a bit confused with the converters in Wicket. I have some numbers >> which I want to display with two decimals and some other numbers with >> another amout of decimals. >> >> It appears like Wicket has only one instance of BigDecimalConverter, >> which is used everywhere. So if I adjust its NumberFormat, the effect >> will be seen everywhere. Is this true? >> >> Who knows of an flexible but elegant way to work with the Wicket >> converters? Creating new converters for each label or textfield >> results in a lot of garbage in the memory footprint... >> >> ** >> Martin >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Thomas Mäder > Wicket & Eclipse Consulting > www.devotek-it.ch > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
