[
https://issues.apache.org/jira/browse/FELIX-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675355#action_12675355
]
Sahoo commented on FELIX-937:
-----------------------------
Peter,
I like to keep all the bundles including fileinstall in one directory. I am
sure many people do so. Since I configure the framework to autostart
fileinstall bundle, I get an exception in every loop of the fileinstall when it
tried to install itself again. So, I thought it would be a good idea to
identify a problematic bundle and not try to install it again and again. Of
course, we can configure fileinstall to try "N" times before giving up and the
default can be infinite to make it behave like the old one. Is this what you
want?
Sahoo
> FileInstall can't handle autostart bundles that are part of watched directory
> -----------------------------------------------------------------------------
>
> Key: FELIX-937
> URL: https://issues.apache.org/jira/browse/FELIX-937
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Environment: generic
> Reporter: Sahoo
>
> Let's say you configure File Install to watch directory /tmp/modules and
> there is a bundle called /modules/foo.jar which is specified as an autostart
> bundle. In Felix's config.properties, autostart bundles are specified using
> URLs (file:///modules/foo.jar in this case) which is internally used as the
> location of the bundle as well. On the other hand, File Install uses
> "absolute path" (/modules/foo.jar in this case) as the location. As a result,
> when File Install tries to install the same bundle, it gets the following
> error:
> INFO: failed to install/start bundle: : org.osgi.framework.BundleException:
> Could not create bundle object.
> This is caused by org.osgi.framework.BundleException: Bundle symbolic name
> and version are not unique.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
