[
https://issues.apache.org/jira/browse/FELIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675361#action_12675361
]
Sahoo commented on FELIX-938:
-----------------------------
Peter,
How do you expect user to stop a bundle that's part of watchedDir temporarily?
As I said, removing it from watchedDir is not always an option in a secured
environment.
What I need is a management agent that installs & optionally starts bundles
from one or more directories and subsequently watch those directories for
changes. If a user stops a bundle in the running system, the system should not
automatically start it. So, I thought fileinstall would do the job.
Kristian,
Yes, I know about felix.fileinstall.bundles.new.start. I was the one who
supplied the patch to introduce that property.
Sahoo
> 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.
