DefaultConverter should be taken out of OSCore -- it's just confusing that it's in there. Later we can look in to Jason's DelegatingSaxParser which uses OGNL, but I wanted it all out for the OSCore release.
And yes, XWork does support specifiying your own converters. Look at the source to XWorkTypeConverter and you'll see that it calls out to other TypeConverters. You can do this by proving a ClassName-conversion.properties file and with "property=full.class.name" and that property will always run through that converter. I'm planning to also add support for xwork-conversion.properties support such that you can define default conversion behavior by doing "full.class.name=full.class.name.of.converter" -Pat ----- Original Message ----- From: "Cameron Braid" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, July 24, 2003 6:14 AM Subject: RE: [OS-webwork] Xwork converter - XWorkConverter and DefaultConverter whats going on ? SO which is the one that is to be kept ? DefaultConverter ? Also, any thoughts on allowing a user specified Converter in xwork.xml ? In our projects, we use jakarta ConvertUtils, and we already have a lot of converters written. Currently I have hacked DefaultConverter to place a hook to call ConvertUtils.convert(object), which is less than prety :) I would rather provide subclass DefaultConverter (or create a totally new calss) and specify a classname for xwork to use - though I wasn't sure the best place to put it into xwork.xml Is there a prefrence ? Cheers, Cameron -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Carreira Sent: Wednesday, 23 July 2003 10:32 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Xwork converter - XWorkConverter and DefaultConverter whats going on ? Oops. That's my bad. I was in the process of moving over the Ognl and Valuestack stuff from XWork to OSCore.... I moved it back because Patrick needed to release OSCore, but I must have missed that bit. -----Original Message----- From: Cameron Braid [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 12:25 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Xwork converter - XWorkConverter and DefaultConverter whats going on ? A new converter class has appeared com.opensymphony.xwork.util.DefaultConverter, which is now the converter that seems to be used everywhere. The old com.opensymphony.xwork.util.XWorkConverter is still there, but it doesn't seem to be used. What are the future plans with converters ? Are there plans to specify a DefaultConverter class in xwork.xml ??? If not, can there be ? Taa, Cameron ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
