[morph-developer] Out of date BeanUtils comparison page on the Morph website

[Niall P. <nia...@gm...>]

With the release of BeanUtils 1.8.0[1] the comparison page[2] on the
Morph site is now out of date and states some things that are now
inaccurate. I'm sure there are many reasons why Morph is superior -
just not some of the ones currently listed. Specifically:

 - BeanUtils LongConverter can convert a java.util.Date into a
java.lang.Long (and the date converters can do Long to java.util.Date)
 - BeanUtils still only offers one language implementation, but this
can be changed to a certain extent by plugging in a custom Resolver[3]
implementation.
 - While BeanUtils does have a special syntax for maps (using
brackets), you can use the same dot notation, as with normal POJO
properties. So, for example, you can use either
"somepojo.mymap.mapkey" or "somepojo.mymap(mapkey)". One advantage of
the map syntax is that you can access map values that contain dot
notation.

I'm not that familiar with Morph (took a peek a long while ago) - but
for conversion one way Morph is superior is that it included Locale in
its Converter interface (BeanUtils has "localized" converters, but
they're a mess and unusable IMO).

Niall

[1] http://commons.apache.org/beanutils/v1.8.0/RELEASE-NOTES.txt
[2] http://morph.sourceforge.net/alternatives/beanutils.html
[3] http://svn.apache.org/repos/asf/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/expression/Resolver.java