commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne" <>
Subject Re: [convert] description of project missing?
Date Mon, 15 Mar 2004 23:37:28 GMT
From: "Matthew Sgarlata" <>
> > > - Seamlessly integrates with BeanUtils.
> > Up to [beanutils]
> Actually I think the intention here was that [convert] would build this.
> For example, we could write a ConvertAdapterConverter class that conforms
> the BeanUtils Converter API but actually carries out the more powerful
> conversion mechanisms in [convert].  Register this class with BeanUtils
> you have the power of [convert] with the API of [BeanUtils].
[convert] cannot depend on [beanutils] in its core. However, I suspect that
[convert] will need an optional library design for things like this.

> I think this might have been Henri's idea, and I don't think he meant
> another XML config file.  I think the idea was to allow you to have more
> than one set of conversion rules in memory at once.  This would allow
> different conversions to be used in the same JVM.  That's better than
> [BeanUtils] because if you need different converters registered for
> different apps with [BeanUtils] then I think you're basically out-of-luck.
Multiple Converters differently setup is a must.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message