> I wanted to avoid using the Formatter interface, it looked 
> like a lot more work to develop a custom formatter than the 
> ICustomFormatter. The interface is deliberately minimal so 
> that a new instance only takes a few lines of code. In my use 
> I just needed to display ids in the form ###-###-###, when 
> they are stored in db as numbers.
That could be done with the pattern attribute without any coding! I think
the advantage of your custom formatter is that you can do formatting wich
can not be done by patterns.

You do not need to implement the whole stuff - you can derived it from the
DefaultFormatterImpl.
And it's just a suggestion to minimize the interfaces - IMHO it's better to
reuse an interface than to build a new one..

Henner



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
DbForms Mailing List

http://www.wap-force.net/dbforms

Reply via email to