[
https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48464#action_48464
]
Guillaume Nodet commented on SMX4KNL-153:
-----------------------------------------
Not sure what you mean by a "separate" instance of the kernel: there is a
single osgi framework running and the shell is inside this osgi framework, else
we would not be able to easily access the osgi layer.
I'd rather investigate the second way, i.e. using security, but this would mean
associating each bundle with certain priviledges. While securing commands
should be easily doable, I'm not sure if this is possible to secure bundles
with different permissions. Another way would be to check the start-level of
the bundle: user bundles should be installed at level >= 50, and core bundles
installed at level < 50. We would rely on this information to know if the
bundle being modified is a core bundle or a user bundle and require different
roles.
Of course, it would first require to have a role based security framework,
which we don't really have yet (at least for commands).
> Stoping one of the "core" bundles of the servicemix engine block the server
> ---------------------------------------------------------------------------
>
> Key: SMX4KNL-153
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-153
> Project: ServiceMix Kernel
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Charles Moulliard
> Fix For: 1.0.1
>
>
> Hi,
> I have discovered a strange behavior of the application. It is possible to
> stop one of the "core" bundle of ServiceMix Kernel. In consequence, the
> server is blocked and the java process must be killed !
> ex : servicemix osgi > stop 14 (correspond to Spring OSGI extender)
> KR,
> Charles Moulliard
> SOA Architect
> Xpectis
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
