felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Koehler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-938) FileInstall starts a stopped bundles even if it is stopped transiently by user
Date Fri, 20 Feb 2009 11:25:01 GMT

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

Kristian Koehler commented on FELIX-938:


by the way, there is a property to define auto start behaviour for new installed bundles via
fileinstall (svn trunk, not sure if it available in felix 1.4.1):


Default value is true


> FileInstall starts a stopped bundles even if it is stopped transiently by user
> ------------------------------------------------------------------------------
>                 Key: FELIX-938
>                 URL: https://issues.apache.org/jira/browse/FELIX-938
>             Project: Felix
>          Issue Type: Bug
>          Components: File Install
>         Environment: generic
>            Reporter: Sahoo
> Configure File Install to watch a directory. Add some bundles there. File Install will
install and start them. Now, using Felix shell or some other utility, stop one of these bundles,
wait for File Install to loop again. You shall notice that File Install will start the bundle
again. I think this behavior is not desirable. if user has explicitly stopped a bundle, why
should File Install start it immediately? In act, there is no way to stop a bundle other than
removing it from watched directory. Removing a bundle from watched dir may not always be practical
because of file system permission issues. So, I think File Install should not automatically
restart a stopped bundle, at least not in the same framework instance.

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

View raw message