what will happen if I override a bean definition in java config?











up vote
0
down vote

favorite












When developing with Spring Data Mongodb, I want to do some customization in my MongoDB configuraion.
General, I will extends the AbstractMongoConfiguration, and implement the abstract methods. currently, the AbstractMongoConfiguration class has the following:



@Configuration
public abstract AbstractConfiguration extends MongoConfigurationSupport {
public abstract MongoClient mongoClient();

@Bean
public MongoTemplate mongoTemplate() throws Exception {
return new MongoTemplate(mongoDbFactor(), mappingMongoConverter());

....
}


When extending this class, I want to customize the bean MongoTemplate, So I want to override the mongoTemplate method, does this work?



@Configuration
public MongoConfiguration extends AbstractConfiguration {
public MongoClient mongoClient(){
....
}

@Override
@Bean
public MongoTemplate mongoTemplate() throws Exception {
MongoTemplate template = super.mongoTemplate();
template.setWriteResultChecking(WriteResultChecking.EXCEPTION);
}

....
}









share|improve this question


























    up vote
    0
    down vote

    favorite












    When developing with Spring Data Mongodb, I want to do some customization in my MongoDB configuraion.
    General, I will extends the AbstractMongoConfiguration, and implement the abstract methods. currently, the AbstractMongoConfiguration class has the following:



    @Configuration
    public abstract AbstractConfiguration extends MongoConfigurationSupport {
    public abstract MongoClient mongoClient();

    @Bean
    public MongoTemplate mongoTemplate() throws Exception {
    return new MongoTemplate(mongoDbFactor(), mappingMongoConverter());

    ....
    }


    When extending this class, I want to customize the bean MongoTemplate, So I want to override the mongoTemplate method, does this work?



    @Configuration
    public MongoConfiguration extends AbstractConfiguration {
    public MongoClient mongoClient(){
    ....
    }

    @Override
    @Bean
    public MongoTemplate mongoTemplate() throws Exception {
    MongoTemplate template = super.mongoTemplate();
    template.setWriteResultChecking(WriteResultChecking.EXCEPTION);
    }

    ....
    }









    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      When developing with Spring Data Mongodb, I want to do some customization in my MongoDB configuraion.
      General, I will extends the AbstractMongoConfiguration, and implement the abstract methods. currently, the AbstractMongoConfiguration class has the following:



      @Configuration
      public abstract AbstractConfiguration extends MongoConfigurationSupport {
      public abstract MongoClient mongoClient();

      @Bean
      public MongoTemplate mongoTemplate() throws Exception {
      return new MongoTemplate(mongoDbFactor(), mappingMongoConverter());

      ....
      }


      When extending this class, I want to customize the bean MongoTemplate, So I want to override the mongoTemplate method, does this work?



      @Configuration
      public MongoConfiguration extends AbstractConfiguration {
      public MongoClient mongoClient(){
      ....
      }

      @Override
      @Bean
      public MongoTemplate mongoTemplate() throws Exception {
      MongoTemplate template = super.mongoTemplate();
      template.setWriteResultChecking(WriteResultChecking.EXCEPTION);
      }

      ....
      }









      share|improve this question













      When developing with Spring Data Mongodb, I want to do some customization in my MongoDB configuraion.
      General, I will extends the AbstractMongoConfiguration, and implement the abstract methods. currently, the AbstractMongoConfiguration class has the following:



      @Configuration
      public abstract AbstractConfiguration extends MongoConfigurationSupport {
      public abstract MongoClient mongoClient();

      @Bean
      public MongoTemplate mongoTemplate() throws Exception {
      return new MongoTemplate(mongoDbFactor(), mappingMongoConverter());

      ....
      }


      When extending this class, I want to customize the bean MongoTemplate, So I want to override the mongoTemplate method, does this work?



      @Configuration
      public MongoConfiguration extends AbstractConfiguration {
      public MongoClient mongoClient(){
      ....
      }

      @Override
      @Bean
      public MongoTemplate mongoTemplate() throws Exception {
      MongoTemplate template = super.mongoTemplate();
      template.setWriteResultChecking(WriteResultChecking.EXCEPTION);
      }

      ....
      }






      java spring mongodb configuration override






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 11 at 4:09









      Roy

      1




      1
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          The fact that you're using @Override in this case is not directly related to the concept of overriding a Spring Bean. Spring tracks beans by name, and it's possible to replace a bean with another one with the same name--this isn't used very often, but it's sometimes necessary to get around sticky situations. @Override is specifically a Java-inheritance bit.



          In your case, your setup should work as you expect because when Spring instantiates your bean, it'll call MongoConfiguration#mongoTemplate(). If the definitions were in different classes, then they would both be producing beans named mongoTemplate, and the last one evaluated would win (there are tricks to controlling this explicitly, either using @Order or injecting the other configuration, but it's not ideal).



          Note that in this specific case, you might prefer to use Spring Boot auto-configuration, in which case you wouldn't override the Java method. Instead, you could inject the MongoTemplate and just call the setter method on it, either by writing an ApplicationRunner or listening for ContextRefreshedEvent.






          share|improve this answer





















            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',
            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
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53245766%2fwhat-will-happen-if-i-override-a-bean-definition-in-java-config%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








            up vote
            0
            down vote













            The fact that you're using @Override in this case is not directly related to the concept of overriding a Spring Bean. Spring tracks beans by name, and it's possible to replace a bean with another one with the same name--this isn't used very often, but it's sometimes necessary to get around sticky situations. @Override is specifically a Java-inheritance bit.



            In your case, your setup should work as you expect because when Spring instantiates your bean, it'll call MongoConfiguration#mongoTemplate(). If the definitions were in different classes, then they would both be producing beans named mongoTemplate, and the last one evaluated would win (there are tricks to controlling this explicitly, either using @Order or injecting the other configuration, but it's not ideal).



            Note that in this specific case, you might prefer to use Spring Boot auto-configuration, in which case you wouldn't override the Java method. Instead, you could inject the MongoTemplate and just call the setter method on it, either by writing an ApplicationRunner or listening for ContextRefreshedEvent.






            share|improve this answer

























              up vote
              0
              down vote













              The fact that you're using @Override in this case is not directly related to the concept of overriding a Spring Bean. Spring tracks beans by name, and it's possible to replace a bean with another one with the same name--this isn't used very often, but it's sometimes necessary to get around sticky situations. @Override is specifically a Java-inheritance bit.



              In your case, your setup should work as you expect because when Spring instantiates your bean, it'll call MongoConfiguration#mongoTemplate(). If the definitions were in different classes, then they would both be producing beans named mongoTemplate, and the last one evaluated would win (there are tricks to controlling this explicitly, either using @Order or injecting the other configuration, but it's not ideal).



              Note that in this specific case, you might prefer to use Spring Boot auto-configuration, in which case you wouldn't override the Java method. Instead, you could inject the MongoTemplate and just call the setter method on it, either by writing an ApplicationRunner or listening for ContextRefreshedEvent.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                The fact that you're using @Override in this case is not directly related to the concept of overriding a Spring Bean. Spring tracks beans by name, and it's possible to replace a bean with another one with the same name--this isn't used very often, but it's sometimes necessary to get around sticky situations. @Override is specifically a Java-inheritance bit.



                In your case, your setup should work as you expect because when Spring instantiates your bean, it'll call MongoConfiguration#mongoTemplate(). If the definitions were in different classes, then they would both be producing beans named mongoTemplate, and the last one evaluated would win (there are tricks to controlling this explicitly, either using @Order or injecting the other configuration, but it's not ideal).



                Note that in this specific case, you might prefer to use Spring Boot auto-configuration, in which case you wouldn't override the Java method. Instead, you could inject the MongoTemplate and just call the setter method on it, either by writing an ApplicationRunner or listening for ContextRefreshedEvent.






                share|improve this answer












                The fact that you're using @Override in this case is not directly related to the concept of overriding a Spring Bean. Spring tracks beans by name, and it's possible to replace a bean with another one with the same name--this isn't used very often, but it's sometimes necessary to get around sticky situations. @Override is specifically a Java-inheritance bit.



                In your case, your setup should work as you expect because when Spring instantiates your bean, it'll call MongoConfiguration#mongoTemplate(). If the definitions were in different classes, then they would both be producing beans named mongoTemplate, and the last one evaluated would win (there are tricks to controlling this explicitly, either using @Order or injecting the other configuration, but it's not ideal).



                Note that in this specific case, you might prefer to use Spring Boot auto-configuration, in which case you wouldn't override the Java method. Instead, you could inject the MongoTemplate and just call the setter method on it, either by writing an ApplicationRunner or listening for ContextRefreshedEvent.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 11 at 4:29









                chrylis

                49.9k1678115




                49.9k1678115






























                    draft saved

                    draft discarded




















































                    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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


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




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53245766%2fwhat-will-happen-if-i-override-a-bean-definition-in-java-config%23new-answer', 'question_page');
                    }
                    );

                    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







                    Popular posts from this blog

                    鏡平學校

                    ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

                    Why https connections are so slow when debugging (stepping over) in Java?