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
