A nice feature would be to convert values with a converter inheritance model. To convert java.sql.date -> String, XWorkConverter looks up a java.sql.date converter, and if it is not present, XWorkConverter could try to load a java.util.date converter, and so on... It could minimize the entries in xwork-conversion.properties. Another interest would be to implement generic converters for entities ( a single line in xwork-conversion.properties to convert a base entity or an interface) ...
Richard HALLIER Chef de projet [EMAIL PROTECTED] 01.40.12.41.52 www.uniclick.org UNICLICK -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Drew McAuliffe Envoye : mardi 7 octobre 2003 04:02 A : [EMAIL PROTECTED] Objet : RE: [OS-webwork] Converters not used on property get? That would be cool. I don't have much control over what the JDBC driver returns as an implementation of Date, but I would think that Timestamp would be pretty common. This is on Oracle 9i, by the way, if it matters. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Carreira Sent: Monday, October 06, 2003 5:47 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Converters not used on property get? It's probably because it's a timestamp, and not a Date. While a timestamp "is a" date, the type conversion is using the class name for looking up converters. We could add this to the XworkBasicConverter and have it treat it the same as a date? Jason > -----Original Message----- > From: Drew McAuliffe [mailto:[EMAIL PROTECTED] > Sent: Monday, October 06, 2003 8:41 PM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] Converters not used on property get? > > > I'm having trouble with OGNL outputting date values from a > database read. Date fields in my object get populated with > Timestamp objects (a sql specific subclass of Date). If I try > to output field "dateLogged" on object "myObject" using the > following call, $!{ognl.findValue("dateLogged", $myObject)} I > don't get any type conversion. Note that this expression is > in velocity, meaning that "$ognl" refers to the webwork > OgnlTool class (under util). It makes the following call: > > return Ognl.getValue(OgnlUtil.compile(expr), context); > > (OgnlUtil is an xwork specific class). > > It doesn't appear that this uses the xwork conversion > properties at all, even though those properties specifically > contain conversion information for Date fields. The xwork > framework doesn't appear to get called at all for output > conversion, although it does get called by OgnlUtil when > setting properties. > > Is this an oversight, or am I missing something? As it is, > I'm completely stuck because Ognl is ALWAYS converting the > value to a string, which for date display is pretty useless. > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
