OpenCSV Java - CsvToBeanFilter using annotated objects instead of a HeaderColumnNameTranslateMappingStrategy











up vote
0
down vote

favorite












I'm reading a CSV file and am using a HeaderColumnNameTranslateMappingStrategy to associate columns in my Object to those in the input data and it all works fine.



In addition, I've implemented a CsvToBeanFilter to filter out data before the objects are constructed to improve performance.



What I would like to do is move away from HeaderColumnNameTranslateMappingStrategy and move to annotated fields on my object.



The provided example for CsvToBeanFilter however, seem to be referring to the MappingStrategy to get the column outside of the object.



Any ideas how I can do this with annotated fields?



From the fact the supplied documentation doesn't compile, and references a deprecated method makes me think I might be out of luck.










share|improve this question


























    up vote
    0
    down vote

    favorite












    I'm reading a CSV file and am using a HeaderColumnNameTranslateMappingStrategy to associate columns in my Object to those in the input data and it all works fine.



    In addition, I've implemented a CsvToBeanFilter to filter out data before the objects are constructed to improve performance.



    What I would like to do is move away from HeaderColumnNameTranslateMappingStrategy and move to annotated fields on my object.



    The provided example for CsvToBeanFilter however, seem to be referring to the MappingStrategy to get the column outside of the object.



    Any ideas how I can do this with annotated fields?



    From the fact the supplied documentation doesn't compile, and references a deprecated method makes me think I might be out of luck.










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm reading a CSV file and am using a HeaderColumnNameTranslateMappingStrategy to associate columns in my Object to those in the input data and it all works fine.



      In addition, I've implemented a CsvToBeanFilter to filter out data before the objects are constructed to improve performance.



      What I would like to do is move away from HeaderColumnNameTranslateMappingStrategy and move to annotated fields on my object.



      The provided example for CsvToBeanFilter however, seem to be referring to the MappingStrategy to get the column outside of the object.



      Any ideas how I can do this with annotated fields?



      From the fact the supplied documentation doesn't compile, and references a deprecated method makes me think I might be out of luck.










      share|improve this question













      I'm reading a CSV file and am using a HeaderColumnNameTranslateMappingStrategy to associate columns in my Object to those in the input data and it all works fine.



      In addition, I've implemented a CsvToBeanFilter to filter out data before the objects are constructed to improve performance.



      What I would like to do is move away from HeaderColumnNameTranslateMappingStrategy and move to annotated fields on my object.



      The provided example for CsvToBeanFilter however, seem to be referring to the MappingStrategy to get the column outside of the object.



      Any ideas how I can do this with annotated fields?



      From the fact the supplied documentation doesn't compile, and references a deprecated method makes me think I might be out of luck.







      java opencsv






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 10 at 19:14









      Jakg

      19710




      19710
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted










          Cross-posting from the bug report I filed.




          Yeah, you've caught us at an inopertune moment. I became aware of that
          use for getColumnIndex() after I deprecated it, and the replacement
          for CsvToBeanFilter (BeanVerifier) is in master, but hasn't been
          released yet. Right now, just use the deprecated getColumnIndex() if
          you have to. It should be very easy to move from CsvToBeanFilter to
          BeanVerifier once 4.4 is released.



          I'll take care of the documentation error another time, but thanks
          very much for pointing it out. I believe in flawless documentation.







          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%2f53242524%2fopencsv-java-csvtobeanfilter-using-annotated-objects-instead-of-a-headercolumn%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



            accepted










            Cross-posting from the bug report I filed.




            Yeah, you've caught us at an inopertune moment. I became aware of that
            use for getColumnIndex() after I deprecated it, and the replacement
            for CsvToBeanFilter (BeanVerifier) is in master, but hasn't been
            released yet. Right now, just use the deprecated getColumnIndex() if
            you have to. It should be very easy to move from CsvToBeanFilter to
            BeanVerifier once 4.4 is released.



            I'll take care of the documentation error another time, but thanks
            very much for pointing it out. I believe in flawless documentation.







            share|improve this answer

























              up vote
              0
              down vote



              accepted










              Cross-posting from the bug report I filed.




              Yeah, you've caught us at an inopertune moment. I became aware of that
              use for getColumnIndex() after I deprecated it, and the replacement
              for CsvToBeanFilter (BeanVerifier) is in master, but hasn't been
              released yet. Right now, just use the deprecated getColumnIndex() if
              you have to. It should be very easy to move from CsvToBeanFilter to
              BeanVerifier once 4.4 is released.



              I'll take care of the documentation error another time, but thanks
              very much for pointing it out. I believe in flawless documentation.







              share|improve this answer























                up vote
                0
                down vote



                accepted







                up vote
                0
                down vote



                accepted






                Cross-posting from the bug report I filed.




                Yeah, you've caught us at an inopertune moment. I became aware of that
                use for getColumnIndex() after I deprecated it, and the replacement
                for CsvToBeanFilter (BeanVerifier) is in master, but hasn't been
                released yet. Right now, just use the deprecated getColumnIndex() if
                you have to. It should be very easy to move from CsvToBeanFilter to
                BeanVerifier once 4.4 is released.



                I'll take care of the documentation error another time, but thanks
                very much for pointing it out. I believe in flawless documentation.







                share|improve this answer












                Cross-posting from the bug report I filed.




                Yeah, you've caught us at an inopertune moment. I became aware of that
                use for getColumnIndex() after I deprecated it, and the replacement
                for CsvToBeanFilter (BeanVerifier) is in master, but hasn't been
                released yet. Right now, just use the deprecated getColumnIndex() if
                you have to. It should be very easy to move from CsvToBeanFilter to
                BeanVerifier once 4.4 is released.



                I'll take care of the documentation error another time, but thanks
                very much for pointing it out. I believe in flawless documentation.








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 10 at 20:13









                Jakg

                19710




                19710






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242524%2fopencsv-java-csvtobeanfilter-using-annotated-objects-instead-of-a-headercolumn%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

                    Xamarin.iOS Cant Deploy on Iphone

                    Glorious Revolution

                    Dulmage-Mendelsohn matrix decomposition in Python