Actually, I'm not entirely following what you are doing, but I recently added support so that you could have a file called SomeObject-conversion.properties and then allow for a mapping between propertyName and Ognl TypeConverter. Is that what you want?
-Pat ----- Original Message ----- From: "Cameron Braid" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 29, 2003 8:32 PM Subject: [OS-webwork] Ognl and Type Conversion I have implemented my own type converters for my custom types to convert to and from string. These converters work perfectly when the Params Interceptor sets their values onto my actions. When I am using a custom UI input... either through a custom JSP tag that extends AbstractUITag, or using the ww:component tag, the $tag.ActualValue is the object version of the value. I wish to be able to use my (or any registered) type converter to get the currect "converter to string" version in a generic way. I would also like the default tag libraries to use the registered converters for the input tag's value. We have adopted a standard of using interfaces for our custom types, with javabean value objects (that are automatically generated) to contain the values, and the converter class converts from the interface to a string and form a string to a value objects instance, therefore I can't rely on the toString of the value objects to return the 'converted value' I hope I have made this concept clear enough :) ..Cam.. ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
