commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Prishchepov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONFIGURATION-419) EventSource as an interface
Date Thu, 02 Jun 2011 18:48:47 GMT

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

Alexander Prishchepov commented on CONFIGURATION-419:
-----------------------------------------------------

So far, I think functionality with listeners should go there:
-------------------------------------------------------------
public void addConfigurationListener(ConfigurationListener l)
public boolean removeConfigurationListener(ConfigurationListener l)
public void addErrorListener(ConfigurationErrorListener l)
public boolean removeErrorListener(ConfigurationErrorListener l)

> EventSource as an interface
> ---------------------------
>
>                 Key: CONFIGURATION-419
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-419
>             Project: Commons Configuration
>          Issue Type: Improvement
>          Components: Events & Notifications
>    Affects Versions: 1.6
>            Reporter: Alexander Prishchepov
>            Priority: Minor
>             Fix For: 2.x
>
>
> I think that would be much better if EventSource was an interface and not class.
> Because currently events functionality starts from AbstractConfiguration and there is
no way to get down to simple Configuration.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message