[JBoss JIRA] (RTGOV-289) Improve mechanism for obtainng core components where injection not possible
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-289?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-289:
-----------------------------
Fix Version/s: 2.1.0.Final
(was: 2.0.0.Final)
> Improve mechanism for obtainng core components where injection not possible
> ---------------------------------------------------------------------------
>
> Key: RTGOV-289
> URL: https://issues.jboss.org/browse/RTGOV-289
> Project: RTGov (Run Time Governance)
> Issue Type: Enhancement
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.1.0.Final
>
>
> Currently components within the overlord-rtgov.war can use CDI injection to resolve references.
> However there are other places where the core components need to be accessed, that are outside this war, and therefore cannot benefit from CDI.
> The current approach is to gets these components to register themselves with an 'accessor' class that manages a singleton reference. The problem is that due to startup initialisation order ambiguity, if the singleton has not been set, the caller must be blocked for a period of time.
> Rather than block the deployer, it would be better to find an asynchronous approach to resolve these references.
> Previously EJBs were being used to provide access to these components - and with the injection of those EJB resource, the dependencies were automatically managed by the container. However use of EJBs resulted in client proxies, which affected performance.
> Need to rethink how these references are resolved in a way that is generally applicable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (RTGOV-289) Improve mechanism for obtainng core components where injection not possible
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-289?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-289:
----------------------------------
Need to also investigate the overlord-commons services work, to see if that can be used.
> Improve mechanism for obtainng core components where injection not possible
> ---------------------------------------------------------------------------
>
> Key: RTGOV-289
> URL: https://issues.jboss.org/browse/RTGOV-289
> Project: RTGov (Run Time Governance)
> Issue Type: Enhancement
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
>
> Currently components within the overlord-rtgov.war can use CDI injection to resolve references.
> However there are other places where the core components need to be accessed, that are outside this war, and therefore cannot benefit from CDI.
> The current approach is to gets these components to register themselves with an 'accessor' class that manages a singleton reference. The problem is that due to startup initialisation order ambiguity, if the singleton has not been set, the caller must be blocked for a period of time.
> Rather than block the deployer, it would be better to find an asynchronous approach to resolve these references.
> Previously EJBs were being used to provide access to these components - and with the injection of those EJB resource, the dependencies were automatically managed by the container. However use of EJBs resulted in client proxies, which affected performance.
> Need to rethink how these references are resolved in a way that is generally applicable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months