What about using the "NonVisual" annotation on your properties and
then manually adding the ones you want?
Alternatively, you could do something like:
define a "RemoveProperties" service with a method like:
removeModelProperties(BeanModel model, String... properties)
Then you could do:
BeanModel myModel =
removeProps
(beanModelSource.create(Foo.class),"prop1","prop2",..."propn");
At least then your "x.remove" calls are contained and neatly wrapped
in a single method.
Robert
On Nov 30, 2007, at 11/307:02 AM , Angelo Chen wrote:
Hi,
Is there a way not to include all fields in beanModelSource.create?
I know I
can use 'remove', but sometimes there are many fields in a bean,
might be
nice to have a way to tell BeanModelSource to include rather than
include
all then 'remove' later, and I notice I usually use only one field
in the
grid with 'parameter' option where I include other fields, seldom I
list all
fields. I was looking at ModelModelImpl to manually setup a one field
ModelSource, but looks a lot of work needed, any ideas? Thanks,
A.C.
--
View this message in context:
http://www.nabble.com/T5%3A-not-include-all-fields-in-BeanModelSource.create-tf4907540.html#a14052989
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
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]
