Multiple beans with the same implementation in Spring boot
I have a situation where I'm using one possible implementation for a particular bean, and it looks like this:
@Configuration
public class MyConfig
@Autowired
private ApplicationContext context;
@Bean
public SomeInterface someInterface()
if (this.context.getEnvironment().getProperty("implementation") != null)
return new ImplementationOne();
else
return new ImplementationTwo();
This worked great so far, until a new requirement came in, to use an additional interface which for the moment only ImplementationTwo
provides implementation, and it wouldn't make sense to use it with ImplementationOne
:
@Bean
public SomeOtherInterface someOtherInterface()
return new ImplementationTwo();
I guess this would work, but I'm wondering if this really make sense because in one scenario I could have both beans basically instantiating the same object. Does that make sense ? Is there maybe a better way to achieve the same thing?
java spring-boot javabeans
add a comment |
I have a situation where I'm using one possible implementation for a particular bean, and it looks like this:
@Configuration
public class MyConfig
@Autowired
private ApplicationContext context;
@Bean
public SomeInterface someInterface()
if (this.context.getEnvironment().getProperty("implementation") != null)
return new ImplementationOne();
else
return new ImplementationTwo();
This worked great so far, until a new requirement came in, to use an additional interface which for the moment only ImplementationTwo
provides implementation, and it wouldn't make sense to use it with ImplementationOne
:
@Bean
public SomeOtherInterface someOtherInterface()
return new ImplementationTwo();
I guess this would work, but I'm wondering if this really make sense because in one scenario I could have both beans basically instantiating the same object. Does that make sense ? Is there maybe a better way to achieve the same thing?
java spring-boot javabeans
Depending on how it's used, ImplementationOne could also implement these new methods, but throwUnsuportedOperationException
if they're being called: docs.oracle.com/javase/6/docs/api/java/lang/…. That works if your internal logic knows not to call these methods when the bean isImpl1
. Otherwise, it means you'll need logic to distinguish between the 2, you might as well make them separate beans at that point ?
– alexbt
Nov 14 '18 at 3:01
add a comment |
I have a situation where I'm using one possible implementation for a particular bean, and it looks like this:
@Configuration
public class MyConfig
@Autowired
private ApplicationContext context;
@Bean
public SomeInterface someInterface()
if (this.context.getEnvironment().getProperty("implementation") != null)
return new ImplementationOne();
else
return new ImplementationTwo();
This worked great so far, until a new requirement came in, to use an additional interface which for the moment only ImplementationTwo
provides implementation, and it wouldn't make sense to use it with ImplementationOne
:
@Bean
public SomeOtherInterface someOtherInterface()
return new ImplementationTwo();
I guess this would work, but I'm wondering if this really make sense because in one scenario I could have both beans basically instantiating the same object. Does that make sense ? Is there maybe a better way to achieve the same thing?
java spring-boot javabeans
I have a situation where I'm using one possible implementation for a particular bean, and it looks like this:
@Configuration
public class MyConfig
@Autowired
private ApplicationContext context;
@Bean
public SomeInterface someInterface()
if (this.context.getEnvironment().getProperty("implementation") != null)
return new ImplementationOne();
else
return new ImplementationTwo();
This worked great so far, until a new requirement came in, to use an additional interface which for the moment only ImplementationTwo
provides implementation, and it wouldn't make sense to use it with ImplementationOne
:
@Bean
public SomeOtherInterface someOtherInterface()
return new ImplementationTwo();
I guess this would work, but I'm wondering if this really make sense because in one scenario I could have both beans basically instantiating the same object. Does that make sense ? Is there maybe a better way to achieve the same thing?
java spring-boot javabeans
java spring-boot javabeans
asked Nov 14 '18 at 2:17
ZedZed
1,99952755
1,99952755
Depending on how it's used, ImplementationOne could also implement these new methods, but throwUnsuportedOperationException
if they're being called: docs.oracle.com/javase/6/docs/api/java/lang/…. That works if your internal logic knows not to call these methods when the bean isImpl1
. Otherwise, it means you'll need logic to distinguish between the 2, you might as well make them separate beans at that point ?
– alexbt
Nov 14 '18 at 3:01
add a comment |
Depending on how it's used, ImplementationOne could also implement these new methods, but throwUnsuportedOperationException
if they're being called: docs.oracle.com/javase/6/docs/api/java/lang/…. That works if your internal logic knows not to call these methods when the bean isImpl1
. Otherwise, it means you'll need logic to distinguish between the 2, you might as well make them separate beans at that point ?
– alexbt
Nov 14 '18 at 3:01
Depending on how it's used, ImplementationOne could also implement these new methods, but throw
UnsuportedOperationException
if they're being called: docs.oracle.com/javase/6/docs/api/java/lang/…. That works if your internal logic knows not to call these methods when the bean is Impl1
. Otherwise, it means you'll need logic to distinguish between the 2, you might as well make them separate beans at that point ?– alexbt
Nov 14 '18 at 3:01
Depending on how it's used, ImplementationOne could also implement these new methods, but throw
UnsuportedOperationException
if they're being called: docs.oracle.com/javase/6/docs/api/java/lang/…. That works if your internal logic knows not to call these methods when the bean is Impl1
. Otherwise, it means you'll need logic to distinguish between the 2, you might as well make them separate beans at that point ?– alexbt
Nov 14 '18 at 3:01
add a comment |
1 Answer
1
active
oldest
votes
I believe, if you have multiple implementations of a single interface, then you should go about specific bean names as below.
Here implementation1 will be the primary bean created and injected where ever we have the Interface1 dependency.
@Primary
@Bean
public Interface1 implementation1()
return new Implementation2();
@Bean
public Interface1 implementation2()
return new Implementation2();
If we need implementation2 injected we need @Resource annotation as below.
@Resource(name="implementation2")
Interface1 implementation2;
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53292253%2fmultiple-beans-with-the-same-implementation-in-spring-boot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I believe, if you have multiple implementations of a single interface, then you should go about specific bean names as below.
Here implementation1 will be the primary bean created and injected where ever we have the Interface1 dependency.
@Primary
@Bean
public Interface1 implementation1()
return new Implementation2();
@Bean
public Interface1 implementation2()
return new Implementation2();
If we need implementation2 injected we need @Resource annotation as below.
@Resource(name="implementation2")
Interface1 implementation2;
add a comment |
I believe, if you have multiple implementations of a single interface, then you should go about specific bean names as below.
Here implementation1 will be the primary bean created and injected where ever we have the Interface1 dependency.
@Primary
@Bean
public Interface1 implementation1()
return new Implementation2();
@Bean
public Interface1 implementation2()
return new Implementation2();
If we need implementation2 injected we need @Resource annotation as below.
@Resource(name="implementation2")
Interface1 implementation2;
add a comment |
I believe, if you have multiple implementations of a single interface, then you should go about specific bean names as below.
Here implementation1 will be the primary bean created and injected where ever we have the Interface1 dependency.
@Primary
@Bean
public Interface1 implementation1()
return new Implementation2();
@Bean
public Interface1 implementation2()
return new Implementation2();
If we need implementation2 injected we need @Resource annotation as below.
@Resource(name="implementation2")
Interface1 implementation2;
I believe, if you have multiple implementations of a single interface, then you should go about specific bean names as below.
Here implementation1 will be the primary bean created and injected where ever we have the Interface1 dependency.
@Primary
@Bean
public Interface1 implementation1()
return new Implementation2();
@Bean
public Interface1 implementation2()
return new Implementation2();
If we need implementation2 injected we need @Resource annotation as below.
@Resource(name="implementation2")
Interface1 implementation2;
answered Nov 14 '18 at 4:52
janardhan sharmajanardhan sharma
2537
2537
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53292253%2fmultiple-beans-with-the-same-implementation-in-spring-boot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Depending on how it's used, ImplementationOne could also implement these new methods, but throw
UnsuportedOperationException
if they're being called: docs.oracle.com/javase/6/docs/api/java/lang/…. That works if your internal logic knows not to call these methods when the bean isImpl1
. Otherwise, it means you'll need logic to distinguish between the 2, you might as well make them separate beans at that point ?– alexbt
Nov 14 '18 at 3:01