You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "David Hay (JIRA)" <ji...@apache.org> on 2010/11/17 16:23:14 UTC

[jira] Created: (FELIX-2702) File Install should be smarter about starting failed bundles

File Install should be smarter about starting failed bundles
------------------------------------------------------------

                 Key: FELIX-2702
                 URL: https://issues.apache.org/jira/browse/FELIX-2702
             Project: Felix
          Issue Type: Improvement
          Components: File Install
    Affects Versions: fileinstall-3.0.2
            Reporter: David Hay
            Priority: Minor


When the File Install bundle tries to start a bundle and there are errors (e.g. unresolved imports), it keeps trying to start that bundle even though nothing about the system has changed.  It seems like File Install could check if the contents of the felix.fileinstall.dir have changed since the last time it checked as well as installing a BundleListener to determine if it's worth trying to start a bundle that failed before.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FELIX-2702) File Install should be smarter about starting failed bundles

Posted by "David Hay (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933008#action_12933008 ] 

David Hay commented on FELIX-2702:
----------------------------------

Right...that's why I was suggesting a BundleListener as well.  If some other mechanism somehow changes the state of a bundle or starts a new one, File Install would detect that something had changed and could try to start a failed bundle again.

> File Install should be smarter about starting failed bundles
> ------------------------------------------------------------
>
>                 Key: FELIX-2702
>                 URL: https://issues.apache.org/jira/browse/FELIX-2702
>             Project: Felix
>          Issue Type: Improvement
>          Components: File Install
>    Affects Versions: fileinstall-3.0.2
>            Reporter: David Hay
>            Priority: Minor
>
> When the File Install bundle tries to start a bundle and there are errors (e.g. unresolved imports), it keeps trying to start that bundle even though nothing about the system has changed.  It seems like File Install could check if the contents of the felix.fileinstall.dir have changed since the last time it checked as well as installing a BundleListener to determine if it's worth trying to start a bundle that failed before.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FELIX-2702) File Install should be smarter about starting failed bundles

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932985#action_12932985 ] 

Guillaume Nodet commented on FELIX-2702:
----------------------------------------

FileInstall may not be the only deployment mechanism ...

> File Install should be smarter about starting failed bundles
> ------------------------------------------------------------
>
>                 Key: FELIX-2702
>                 URL: https://issues.apache.org/jira/browse/FELIX-2702
>             Project: Felix
>          Issue Type: Improvement
>          Components: File Install
>    Affects Versions: fileinstall-3.0.2
>            Reporter: David Hay
>            Priority: Minor
>
> When the File Install bundle tries to start a bundle and there are errors (e.g. unresolved imports), it keeps trying to start that bundle even though nothing about the system has changed.  It seems like File Install could check if the contents of the felix.fileinstall.dir have changed since the last time it checked as well as installing a BundleListener to determine if it's worth trying to start a bundle that failed before.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.