[ http://issues.apache.org/jira/browse/BEEHIVE-784?page=all ]
Rich Feit updated BEEHIVE-784:
------------------------------
Assign To: Rich Feit
I can look at this. Right now, the only way to do this is to create a custom
ServletContainerAdapter, and override the default behavior for
getControlBeanContext(). I agree that it would be nice to be able to specify a
class name in beehive-netui-config.xml.
> implementation of the ControlContainerContext used in JPF should be
> externally configurable
> -------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-784
> URL: http://issues.apache.org/jira/browse/BEEHIVE-784
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: TBD
> Reporter: Eddie O'Neil
> Assignee: Rich Feit
> Fix For: TBD
>
> When using controls, it's often the case that one wants to register services
> that are available to all controls running in a given context. One way to
> facilitate this in NetUI would be to allow the ControlContainerContext used
> to contain all controls in JPFs to be configured by the user. Then, services
> (interceptors for example) could be wired-up by writing and registering a new
> CCC subclass.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
