Oliver Kiessler wrote:
Please vote if you only want to support Java beans and don't want to
support POJO's.
I am not a big fan of the term "POJO". From what I know most people
say POJO and mean Java Bean... Does it make much sense to persist
anything else than class properties? Just wondering...
regards,
oliver
Good point. I think there is no exact definition how a bean differs to a
POJO.
In this case I guess the question is: Do we force the bean naming
conventions?
In contrast to my current mapping schema I don't think we need to
support more than one
parameter in the write method.
cheers,
Sandro