You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Freeman Fang (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/17 12:50:30 UTC
[jira] [Resolved] (KARAF-1114) osgi shell blueprint bundle
shouldn't use lazy default-activation
[ https://issues.apache.org/jira/browse/KARAF-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved KARAF-1114.
---------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
2.2.5
commit fix
http://svn.apache.org/viewvc?rev=1215467&view=rev for trunk
http://svn.apache.org/viewvc?rev=1215461&view=rev for 2.2.x branch
> osgi shell blueprint bundle shouldn't use lazy default-activation
> -----------------------------------------------------------------
>
> Key: KARAF-1114
> URL: https://issues.apache.org/jira/browse/KARAF-1114
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Affects Versions: 2.2.4
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 2.2.5, 3.0.0
>
>
> otherwise org.apache.karaf.shell.osgi.SpringStateListenerFactory won't get initialized until
> we use osgi shell, this can cause bundle Spring status miss, as SpringApplicationListener can't receive spring-dm event when spring bundle refreshed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira