You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/09/14 03:52:48 UTC

[jira] Created: (MRM-949) changing the consumers requires a restart

changing the consumers requires a restart
-----------------------------------------

                 Key: MRM-949
                 URL: http://jira.codehaus.org/browse/MRM-949
             Project: Archiva
          Issue Type: Improvement
          Components: web application
    Affects Versions: 1.1.2
            Reporter: Brett Porter
             Fix For: 1.1.x


it seems that at present the configuration notification is not reaching the consumer delegation. The specific one I was enabling was the repository purge.

This may be best targeted at 1.2 and a review of configuration and particularly change notification since there are a few gaps occurring. I believe rather than using a text string it would be better to simply inspect the relevant configuration on every change and let the configured object decide how to handle the event.

It would be best aligned to the upcoming event architecture as well

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (MRM-949) changing the consumers requires a restart

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.

     [ http://jira.codehaus.org/browse/MRM-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-949:
-----------------------------

    Fix Version/s: 1.1.x

> changing the consumers requires a restart
> -----------------------------------------
>
>                 Key: MRM-949
>                 URL: http://jira.codehaus.org/browse/MRM-949
>             Project: Archiva
>          Issue Type: Improvement
>          Components: web application
>    Affects Versions: 1.1.2
>            Reporter: Brett Porter
>             Fix For: 1.1.x
>
>
> it seems that at present the configuration notification is not reaching the consumer delegation. The specific one I was enabling was the repository purge.
> This may be best targeted at 1.2 and a review of configuration and particularly change notification since there are a few gaps occurring. I believe rather than using a text string it would be better to simply inspect the relevant configuration on every change and let the configured object decide how to handle the event.
> It would be best aligned to the upcoming event architecture as well

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira