You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2016/02/05 16:32:39 UTC

[jira] [Commented] (KARAF-4284) Blueprint Services are not creating a service instance per consuming bundle for prototype-scoped beans

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

Jean-Baptiste Onofré commented on KARAF-4284:
---------------------------------------------

I think this issue is not directly a Karaf issue, but more an Aries Blueprint issue. Let me reproduce and I will create the Jira at Aries.

> Blueprint Services are not creating a service instance per consuming bundle for prototype-scoped beans
> ------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-4284
>                 URL: https://issues.apache.org/jira/browse/KARAF-4284
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.4.3, 3.0.5, 4.0.4
>         Environment: Oracle Java 1.7.0_79
> Camel 2.16.1
>            Reporter: Quinn Stevenson
>
> According to the book "Enterprise OSGi In Action" (section 6.3.3), when a prototype-scoped bean is exposed as a service using Blueprint, a new instance of the service should get created for each consuming bundle.
> Services exposed in this manner in Karaf are not behaving this way - a single service instance is created and
> all consuming bundles use it.  It appears the prototype scope is being ignored since the obseved behaviour is 
> what is expected for singleton-scoped beans exposed as services.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)