--- On Tue, 2/24/09, Adam Hardy <[email protected]> wrote:
> From: Adam Hardy <[email protected]>
> Subject: Re: [beanutils] converting HTTP params into an arbitrary object model
> To: "Commons Users List" <[email protected]>
> Date: Tuesday, February 24, 2009, 3:19 AM
> Matt Benson on 23/02/09 16:23,
> wrote:
> --- On Sat, 2/21/09, Adam Hardy wrote:
> > > >> I have spent a day researching and
> prototyping with various open-source
> >> options available which facilitate converting an
> HTTP request's parameters into an object model of javabeans
> in a JPA persistence framework.
> >>
> >
> > You may want to check out Morph @ http://morph.sourceforge.net . OOTB, it
> > can
> "reflect" ServletRequest parameters as bean properties and
> do a straight copy, as long as the servlet API is found on
> the classpath.
>
> I had a look at morph (following the link from the
> beanutils wiki) but their
> website didn't really enlighten me and what I did find
> didn't look very helpful,
> so I made a management decision not to pursue it.
>
> The problem is that there are that many little details to
> check for, e.g. can it handle sets, can it deduce the
> javabean items on generics, can it handle indexed lists of
> ".0, .1, .2" notation etc
>
Morph is not generics-enabled; it can handle most of your basic non-generic
constructs (e.g. Sets) right out of the box and just about anything else you
can throw at it if you want to implement its API here and there for custom
transformations, and while I am 100% sure it can handle [n] index notation I am
about 90% sure it also handles indices as property names as you have described
(.n)--if not, that is pluggable. But this isn't the Morph list and, as you
said, you made a management decision not to pursue it. As a Morph team member
I will take your "documentation didn't look very helpful" criticism under
advisement as well.
Regards,
Matt
> Regards
> Adam
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
