You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Nodet (Commented) (JIRA)" <ji...@apache.org> on 2012/03/19 10:07:38 UTC

[jira] [Commented] (FELIX-3029) ArtifactListener/File dynamic issue

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

Guillaume Nodet commented on FELIX-3029:
----------------------------------------

I would consider this not a bug, but a "by design".  I'm really not sure any change on an ArtifactListener should lead to all bundles handled by the listener to be updated.   The main problem would be  that all bundles would always be reinstalled upon a system restart, which I think is not desirable.

                
> ArtifactListener/File dynamic issue
> -----------------------------------
>
>                 Key: FELIX-3029
>                 URL: https://issues.apache.org/jira/browse/FELIX-3029
>             Project: Felix
>          Issue Type: Bug
>          Components: File Install
>    Affects Versions: fileinstall-3.1.10
>            Reporter: Yann Diorcet
>
> FileInstall don't correctly handle the arrival(and maybe departure) of a ArtifactListener.
> I have one ArtifactListener and one file (abcd.xml)
> Indeed at the start of the platform, the first time that i provide a service implementing ArtifactListener, FileInstall call canHandle with abcd.xml as a File (and after install).
> But if i stop this service and if i restart it, FileInstall don't remake the call to canHandle.
> The only solution for calling canHandle of the restarted service is to update the file.
> Somehow, the Scanner object inside FileInstall doesn't have to be commonly used with all the listener but one Scanner by listener.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira