[jira] [Comment Edited] (CAMEL-14359) camel-bean - Let cache be default enabled

["Claus Ibsen (Jira)" <ji...@apache.org>]

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

Claus Ibsen edited comment on CAMEL-14359 at 1/7/20 12:43 PM:
--------------------------------------------------------------

We could also introduce a scope option to have
- singleton
- request (scoped per exchange)
- prototype (whatever scope from delegate registry such as spring / blueprint / cdi)


was (Author: davsclaus):
We could also introduce a scope option to have
- singleton
- request (scoped per exchange)
- delegate (whatever scope from delegate registry such as spring / blueprint / cdi)

> camel-bean - Let cache be default enabled
> -----------------------------------------
>
>                 Key: CAMEL-14359
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14359
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.1.0
>
>
> See CAMEL-14357
> We should let cache=true by default enabled. This then avoids re-creating new beans when you refer to a bean by its class name, and also avoids looking up the bean from the registry each time, and so on.
> In other words it acts as a singleton scoped bean.
> If people want to create a new bean per use, then they can set cache=false.
> And we could update the documentation to indicate cache acts as a singleton scope. Or we could add singleton=true|false as the option and deprecate cache if its a better name.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)