You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2014/05/13 01:06:16 UTC

[jira] [Updated] (ISIS-779) Refactor EventBusService as a @RequestScoped service, and have it own the guava EventBus as a field.

     [ https://issues.apache.org/jira/browse/ISIS-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood updated ISIS-779:
-----------------------------

    Summary: Refactor EventBusService as a @RequestScoped service, and have it own the guava EventBus as a field.  (was: EventBus should not re-register services on open/close; this is not thread-safe.)

> Refactor EventBusService as a @RequestScoped service, and have it own the guava EventBus as a field.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-779
>                 URL: https://issues.apache.org/jira/browse/ISIS-779
>             Project: Isis
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: core-1.4.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Critical
>             Fix For: core-2.0.0
>
>
> Either it remains as a application-scoped service and registers all other services once (eg in the @PostConstruct init), or alternatively it should become a request-scoped service.  The former of these is probably the better.
> In addition, the EventBus instance (currently part of IsisTransaction) could instead be owned by the EventBusServiceDefault service.



--
This message was sent by Atlassian JIRA
(v6.2#6252)