[jira] Created: (CONFIGURATION-419) EventSource as an interface

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (CONFIGURATION-419) EventSource as an interface

JIRA jira@apache.org
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


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.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (CONFIGURATION-419) EventSource as an interface

JIRA jira@apache.org

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

Oliver Heger updated CONFIGURATION-419:
---------------------------------------

    Fix Version/s: 2.x

Setting fix version to 2.x: This is an incompatible change which can only happen in a major release.

Which methods should be contained in the interface exactly?

> 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.
-
You can reply to this email to add a comment to the issue online.