The context is the mechanism for accessing other
components within a dashboard. By setting an "id" attribute
on the component tag, the dashboard factory will construct
and register the component in the context at that name. It
would then be accessible to other components.
Note, that currently, the setContext method is called on a
dashboard component as the components are built in order of
parsing. In the future, I'll probably fix this to happen in a
second pass as components are added to the component
tree a la addNotify allowing dependencies on components
above the reference.
Also, it should be possible to set the dependency on the
component by creating a Java Bean setter method and using
the "Attribute" tag to reference the component by id.
Perhaps an MBeanSelectionListener interface would be
helpful in the future, but for now, you can at least access the
component.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=773314
The context is the mechanism for accessing other
components within a dashboard. By setting an "id" attribute
on the component tag, the dashboard factory will construct
and register the component in the context at that name. It
would then be accessible to other components.
Note, that currently, the setContext method is called on a
dashboard component as the components are built in order of
parsing. In the future, I'll probably fix this to happen in a
second pass as components are added to the component
tree a la addNotify allowing dependencies on components
above the reference.
Also, it should be possible to set the dependency on the
component by creating a Java Bean setter method and using
the "Attribute" tag to reference the component by id.
Perhaps an MBeanSelectionListener interface would be
helpful in the future, but for now, you can at least access the
component.