camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7452) beanRef is caching instances - unwanted behavior
Date Mon, 01 Sep 2014 12:57:21 GMT

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

Claus Ibsen commented on CAMEL-7452:
------------------------------------

Yeah I think we should

- cache by default (which is the behavior we have now)
- setting cache=false, should create a new instance on-demand, eg like a prototype scoped
bean.

> beanRef is caching instances - unwanted behavior
> ------------------------------------------------
>
>                 Key: CAMEL-7452
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7452
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.13.0
>            Reporter: Christoph Giera
>            Assignee: Claus Ibsen
>             Fix For: 2.14.0
>
>
> After upgrading from 2.11.0 to 2.13.0 the behavior of beanRef has changed(unwanted behavior).
Beans only get instanted once, even if the cache option is explicitly set to "false".  
> see http://camel.465427.n5.nabble.com/beanRef-is-caching-instances-in-camel-2-13-0-unwanted-behavior-td5751335.html



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

Mime
View raw message