<snip/>
I had a deeper look at JXPath, and this doesn't seem to be so easy, as JXPath doesn't provide us a way to know the type of the data that has to be set.
Furthermore, JXPath relies on an internal type conversion mechanism in TypeUtils, which can be extended with a TypeConverter. But this TypeUtils accepts only one TypeConverter, which is stored in a static variable !!
Hmm, maybe best to fix that in JXPath. I think ideally we should be able
to provide a custom TypeConvertor on each setValue call.
Good idea! This would allows us to have full control on the conversion process, and shouldn't be too much difficult to plug into JXPath.
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
