I was going to try converting it to a list of Entry type objects but
with a getter for key and value. I spent a few hours confusing myself
but couldn't find the appropriate place to do the conversion. I
suppose the tricky part is that there's actually two values and the
default field handlers are only geared for one (whether it's a bean or
a primitive). I'm thinking with a tricky model that converts output
to a collection of Entry beans and converts input into proper map
entries it could be made to squeeze into the existing beadgrid. But
of course that assumes WWB won't try an work on the object directly
and probably stop any smart handling like paging etc in it's tracks
since you need to treat the collection/map as a monolithic object.
On May 23, 11:33 am, Dan Syrstad <
dsyrs...@gmail.com> wrote:
> There is no built-in field to handle maps. The question would be: How do you
> want to handle your map? Display keys, values, both? In what presentation
> format?
> -Dan
>
>
>
> On Fri, May 21, 2010 at 10:52 PM, shadders <
shadders....@gmail.com> wrote:
> > I'm pretty new to WWB so there may be an easy answer to this.
>
> > Currently when I display a bean that has a map property it just shows:
> > <No Field for java.util.Map>
>
> > Is there any built in support for maps or will I need to build my own?
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Wicket Web Beans" group.
> > To post to this group, send email to
wicket-w...@googlegroups.com.
> > To unsubscribe from this group, send email to
> >
wicket-web-bea...@googlegroups.com<
wicket-web-beans%2Bunsu...@googlegroups.com>
> > .
> For more options, visit this group athttp://
groups.google.com/group/wicket-web-beans?hl=en.