You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2009/02/19 13:05:59 UTC

[jira] Commented: (SMX4KNL-202) Startup of a pending to deploy Spring config file fails when all required bundles got installed

    [ https://issues.apache.org/activemq/browse/SMX4KNL-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49781#action_49781 ] 

Guillaume Nodet commented on SMX4KNL-202:
-----------------------------------------

If the transformed bundle installation fails, I'm not sure we can do much about it.
However, if the bundle has been successfully installed but failed to resolve, the file monitor should reschedule the start to be executed later when new bundles have been installed, so that the bundle can be resolved correctly.
If the bundle is resolved but fails to start, we might want to reschedule the start later, but I'm not sure about that.

In your example, at which stage is the problem ? If you add some Require-Bundle and if the resolution is rescheduled, it may solve the problem.

> Startup of a pending to deploy Spring config file fails when all required bundles got installed
> -----------------------------------------------------------------------------------------------
>
>                 Key: SMX4KNL-202
>                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-202
>             Project: ServiceMix Kernel
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Lars Heinemann
>             Fix For: 1.2.0
>
>
> I have a spring xml config file I want to deploy into smx4.
> This config has several required bundles defined in the manifest tag.
> On startup of smx it recognizes that the required bundles are not yet available and suspends the deployment.
> If I install the required bundles now, the spring file fails very fast because of some missing namespace element.
> My idea is that the spring file is processed before all needed bundles are fully deployed and therefor it fails then.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.