On Wed, 24 Sep 2014 13:37:11 -0300, Daniel Jue wrote:
Your code works as is, but I still stuck it in a custom
MeaningfulBeanDisplay component in it's setupRender method, because I
don't want to write this logic for every model for every POJO.
Sometimes I'll
have 5-10 of these POJOs on one
Thiago, that was perfect! I had in-fact gone down the reflection route and
was getting into trouble since the propertyNames aren't really the method
or field names. I forgot about using conduits manually that way!
Your code works as is, but I still stuck it in a custom
MeaningfulBeanDisplay com
On Wed, 24 Sep 2014 10:59:50 -0300, Chris Mylonas
wrote:
Hi Daniel,
Hi, guys!
Disclaimer: I don't pretend to know anything about BeanModels,
BeanModelSources and Grids.however
I know a thing or two about them. :)
Sounds like a bit of reflection to get field names on your POJOs an
Hi Daniel,
Disclaimer: I don't pretend to know anything about BeanModels,
BeanModelSources and Grids.however
Sounds like a bit of reflection to get field names on your POJOs and
BeanModel.exclude().exclude().exclude().exclude() or a bit of
recursion til the end of an arraylist of
Thanks Lance, I think on the surface my problem seems like the one you gave
the answer for, but in my case it's different. I don't know which fields
I'll need to exclude until I know whether the value is null or empty-string
for the instance of the bean. For example, one of my classes is a POJO
g
BeanDisplay, BeanEditor and Grid all use a BeanModel to show the fields.
You could either set the "exclude" parameter to the component. Or you can
call BeanModel.exclude(...) explicitly.
It might be easiest to decorate the BeanModelSource service in tapestry-ioc
(used when you don't explicitly pr
Hey list! I have several dozen code-generated beans that I'd like to
display as bean models. Problem is, many of the beans' fields are either
null or empty string, so I don't want their labels to even show up,
much less the NotEmpty mixin putting a
The idea is to skip rendering any fields tha
