You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Andrei Shakirin (Commented) (JIRA)" <ji...@apache.org> on 2012/03/02 14:41:58 UTC

[jira] [Commented] (KARAF-1189) Feature installation: synchronization between copiing configuration files and installing/starting bundles

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

Andrei Shakirin commented on KARAF-1189:
----------------------------------------

Hmm ... baiscally OK from technical point of view, but for me is still a problem as for Spring DM user.

Imagine following use case: I implement a simple CXF service using Spring DM and define endpoint via compendium properties:

 <spring:beans 
	xmlns="http://www.springframework.org/schema/beans"
	xmlns:spring="http://www.springframework.org/schema/beans"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:osgi="http://www.springframework.org/schema/osgi"
	xmlns:jaxws="http://cxf.apache.org/jaxws"
	xmlns:context="http://www.springframework.org/schema/context"	 
	xmlns:osgix="http://www.springframework.org/schema/osgi-compendium"
...
	<context:property-placeholder properties-ref="test-configuration" />
	<osgix:cm-properties id="test-configuration" persistent-id="test.authorization"/>

	<jaxws:endpoint id="AuthorizationProvider"
		xmlns:serviceNamespace="http://services.sopera.org/Authorization"
		serviceName="serviceNamespace:Authorization" endpointName="serviceNamespace:AuthorizationProvider"
		implementor="#authorizationProviderImpl" address="${authorization.endpoint}">
	</jaxws:endpoint>

</spring:beans>

Than I define my endpoint in configuration and deploy bundle with a service and configuration file as a feature.
What I see after deployment: service is failed, because of missing configuration. However configuration file is copiied and present in the Karaf/etc.
Very confusing ...

Sure, workarounds can be using OSGi ManagedService directly or blueprint, but how to resolve Spring DM case?

Andrei.

                
> Feature installation: synchronization between copiing configuration files and installing/starting bundles
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-1189
>                 URL: https://issues.apache.org/jira/browse/KARAF-1189
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-core
>            Reporter: Andrei Shakirin
>            Assignee: Jean-Baptiste Onofré
>              Labels: configuration, features,
>
> Hi,
> Actually there is no synchronization between installation/starting bundles and copiing configuration files.
> It causes sometimes that bundles with OSGi services are already started, but appropriate configuration is not yet accepted by ConfigurationAdmin. Result is failed services by first installation. After restart problem is resolved.
> Question: is it basically possible to wait untile configuration files are accepted by ConfigurationAdmin and only after it start bundles from the feature?
> Regards,
> Andrei.

--
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