[
https://issues.apache.org/jira/browse/FELIX-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-875:
------------------------------------
Description:
Currently the web console does not support updating the system bundle. A simple
enhancement in the InstallAction class handling bundle update supports this
update.
Background: When a bundle file is submitted for installaiton (or update) in the
respective form on the bundle page, the web console analyses the bundle file to
find a matching bundle to update by the symbolic name. If no matching bundle is
found, the bundle is installed as a new bundle.
This mechanism could also be used to update the system bundle. But the symbolic
name of the system bundle is special, since the "system.bundle" strings is not
the required name but just an alias. To sitll support the system bundle, the
InstallAction checker for the bundle to update should treat the string
"system.bundle" (the defined alias for the symbolic name) as indications to
update the system bundle.
Generally, this may just restart the framework and not actually update the
system bundle. But there may be cases, where this already helps.In addition it
might prevent potential problems, if some administrator tries to install a
bundle, which happens to have the respective symbolic name.
was:
Currently the web console does not support updating the system bundle. A simple
enhancement in the InstallAction class handling bundle update supports this
update.
Background: When a bundle file is submitted for installaiton (or update) in the
respective form on the bundle page, the web console analyses the bundle file to
find a matching bundle to update by the symbolic name. If no matching bundle is
found, the bundle is installed as a new bundle.
This mechanism could also be used to update the system bundle. But the symbolic
name of the system bundle is special, since the "system.bundle" strings is not
the required name but just an alias. To sitll support the system bundle, the
InstallAction checker for the bundle to update should treat the strings
"system.bundle" (the defined alias for the symbolic name) and "System Bundle"
(the defined location for the system bundle) as indications to update the
system bundle.
Generally, this may just restart the framework and not actually update the
system bundle. But there may be cases, where this already helps.In addition it
might prevent potential problems, if some administrator tries to install a
bundle, which happens to have the respective symbolic name.
> Support updating the system bundle
> ----------------------------------
>
> Key: FELIX-875
> URL: https://issues.apache.org/jira/browse/FELIX-875
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: webconsole-1.2.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: webconsole-1.2.4
>
>
> Currently the web console does not support updating the system bundle. A
> simple enhancement in the InstallAction class handling bundle update supports
> this update.
> Background: When a bundle file is submitted for installaiton (or update) in
> the respective form on the bundle page, the web console analyses the bundle
> file to find a matching bundle to update by the symbolic name. If no matching
> bundle is found, the bundle is installed as a new bundle.
> This mechanism could also be used to update the system bundle. But the
> symbolic name of the system bundle is special, since the "system.bundle"
> strings is not the required name but just an alias. To sitll support the
> system bundle, the InstallAction checker for the bundle to update should
> treat the string "system.bundle" (the defined alias for the symbolic name) as
> indications to update the system bundle.
> Generally, this may just restart the framework and not actually update the
> system bundle. But there may be cases, where this already helps.In addition
> it might prevent potential problems, if some administrator tries to install a
> bundle, which happens to have the respective symbolic name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
