the use case is to expose in JSON a different structure than the object
(saw object being seens as arrays)
or simply: handler.writeArray(asList(new Property("name", user.getName(),
new Property("id", user.getId())) using a UserPropertyListConverter front
oriented (to match a front framework).
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
2016-04-28 19:04 GMT+02:00 Reinhard Sandtner <[email protected]>:
> hey,
>
> sry for the late response but your mail was in my spam folder grrrrrr :(
>
> do we really need writeArray? internal we only need writeObject and check
> if it’s a Collection or Array afaik...
>
> what’s the use case for virtual list? do we have a unit test which i can
> use as sample to try it with ObjectConverter?
>
> lg
> reini
>
>
> > Am 27.04.2016 um 15:56 schrieb Romain Manni-Bucau <[email protected]
> >:
> >
> > Do we miss writeArray API? think so otherwise it is hard to create a
> > virtual list
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
>
>
