Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Sun, 25 Jan 2015 15:31:35 +0000 (UTC)
From: "Oliver Heger (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12769365.1421945912000.168246.1422199895110@Atlassian.JIRA>
In-Reply-To: <JIRA.12769365.1421945912000@Atlassian.JIRA>
References: <JIRA.12769365.1421945912000@Atlassian.JIRA>
 <JIRA.12769365.1421945912384@arcas>
Subject: [jira] [Commented] (CONFIGURATION-596) Allow event listener
 Collections to be lazily created in event.EventSource
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CONFIGURATION-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291143#comment-14291143 ] 

Oliver Heger commented on CONFIGURATION-596:
--------------------------------------------

bq. Do you mean 1.x branch?
No, I mean trunk.

bq. Any reasons for that?
Development has been ongoing for a longer while on version 2.0. There is not much interest any more on the 1.x branch. We are also short of developers who could maintain multiple branches.

bq. When a stable release is expected?
No concrete date yet. The purpose of the alpha releases was to get some feedback about the reworked API. Unfortunately, there was not much. So the next step would be a beta release and - if no more issues are detected - shortly afterwards the final 2.0 release.

> Allow event listener Collections to be lazily created in event.EventSource
> --------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-596
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-596
>             Project: Commons Configuration
>          Issue Type: Improvement
>          Components: Events & Notifications
>    Affects Versions: 1.9
>            Reporter: Vladimir Sitnikov
>         Attachments: CoWArrayList1.jpg, dataflow_commons_configuration_cowarraylist.png
>
>
> It turns out every instance of {{AbstractConfiguration}} creates a couple of {{CopyOnWriteAraryLists}} for {{event.EventSource}}.
> In our usage patterns in most of the cases the lists are not used.
> Can the lists be lazy-initialized? (that is created on the first addListener request)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)