[ 
https://issues.apache.org/jira/browse/KARAF-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460327#comment-13460327
 ] 

Christian Schneider commented on KARAF-1487:
--------------------------------------------

I think this is not a bug. The ServletActivator should react on the HttpServlet 
coming up and then register its servlet. You can probably produce a similar 
problem with the above jar by installing it correctly and then uninstall and 
reinstall the war feature. The servlet will then disappear and not come back 
again. If you track the HttpService the above use case would work.
                
> Bundles in deploy are deployed before startup process had been  finished
> ------------------------------------------------------------------------
>
>                 Key: KARAF-1487
>                 URL: https://issues.apache.org/jira/browse/KARAF-1487
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 2.2.7
>            Reporter: Andreas Pieber
>             Fix For: 2.2.10, 2.3.1, 3.0.0
>
>         Attachments: 
> tinybundles_e7d0a17a16a7451b4eac69f524c961f4d9b1d9df.bin.jar
>
>
> I'm not sure, but I assume that this also affects the master. This needs to 
> be evaluated after a fix had been crafted.
> To reproduce the issue download and unpack karaf-2.2.7; then add the attached 
> jar to the deploy folder (which is basically [1] packed with tinybundles). 
> Now, BEFORE starting karaf, edit etc/org.apache.karaf.features.cfg and add 
> "war" to the bootFeatures. Now start Karaf. you see that the deploy folder 
> bundle had been deployed BEFORE the war feature had been started. Therefore 
> the bundle is missing some packages and is not refreshed as the new feature 
> is available. When you refresh the bundle now manually it works.
> [1] 
> https://github.com/openengsb/labs-paxexam-karaf/tree/master/regression/src/test/java/org/openengsb/labs/paxexam/karaf/regression/supports

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to