On Dec 21, 2004, at 9:17 AM, Jeremy Boynes wrote:
Alan D. Cabrera wrote:Here's a use case. Let's say that I have a management console that is
managing a GBean. There are times when it would be nice to see what is
in its collection of references.
Wouldn't that be a static snapshot - you would't want the content changing as the UI page was rendering.
If you expose the collection, you just get a bunch of proxies. Don't you want the object names instead?
Another thing. It would be nice if GBean attributes had display names and descriptions in them. This way I could have a tool that could autogenerate a properties page by simply reading the GBean meta data.
I see that as a UI issue - for I18N wouldn't you want the tool to generate localized titles for the properties (which it can do based on the name) without the need to store all the variants in the metadata?
Go me. We do already have both a physical name and an exposed name. The exposed name is the name you invoke, get or set in the kernel.
-dain
