How to provide implementation of annotations reading alongside the annotation











up vote
0
down vote

favorite












Let's say have I have an annotation that's to be used like this:



public void foo (@IntParam int quantity, @FooParam Foo bar) {
...
}


I would like to call this method, access the params from an object and pass it like this:



public void invokeFoo (Method fooMethod, Map<String, String> context) throws ... {
List<Object> params = Arrays.stream(fooMethod.getAnnotations()).map(annos -> {
if (annos[0] instanceof IntParam) {
return context.get( ... ); // <-
} else if (annos[0] instanceof FooParam) {
return new Foo(context); // <-
}
}).collect(Collectors.toList());
fooMethod.invoke(params.toArray());
}


The problem with this implentation is that I need to edit 2 different files if I want to add new types of params, which I would like to avoid for several reasons.Is there a way to write those lines in the same annotation file ?. The only way would be using a static/default method on the interface but either way this would type poorly.



Any other way ?










share|improve this question


























    up vote
    0
    down vote

    favorite












    Let's say have I have an annotation that's to be used like this:



    public void foo (@IntParam int quantity, @FooParam Foo bar) {
    ...
    }


    I would like to call this method, access the params from an object and pass it like this:



    public void invokeFoo (Method fooMethod, Map<String, String> context) throws ... {
    List<Object> params = Arrays.stream(fooMethod.getAnnotations()).map(annos -> {
    if (annos[0] instanceof IntParam) {
    return context.get( ... ); // <-
    } else if (annos[0] instanceof FooParam) {
    return new Foo(context); // <-
    }
    }).collect(Collectors.toList());
    fooMethod.invoke(params.toArray());
    }


    The problem with this implentation is that I need to edit 2 different files if I want to add new types of params, which I would like to avoid for several reasons.Is there a way to write those lines in the same annotation file ?. The only way would be using a static/default method on the interface but either way this would type poorly.



    Any other way ?










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Let's say have I have an annotation that's to be used like this:



      public void foo (@IntParam int quantity, @FooParam Foo bar) {
      ...
      }


      I would like to call this method, access the params from an object and pass it like this:



      public void invokeFoo (Method fooMethod, Map<String, String> context) throws ... {
      List<Object> params = Arrays.stream(fooMethod.getAnnotations()).map(annos -> {
      if (annos[0] instanceof IntParam) {
      return context.get( ... ); // <-
      } else if (annos[0] instanceof FooParam) {
      return new Foo(context); // <-
      }
      }).collect(Collectors.toList());
      fooMethod.invoke(params.toArray());
      }


      The problem with this implentation is that I need to edit 2 different files if I want to add new types of params, which I would like to avoid for several reasons.Is there a way to write those lines in the same annotation file ?. The only way would be using a static/default method on the interface but either way this would type poorly.



      Any other way ?










      share|improve this question













      Let's say have I have an annotation that's to be used like this:



      public void foo (@IntParam int quantity, @FooParam Foo bar) {
      ...
      }


      I would like to call this method, access the params from an object and pass it like this:



      public void invokeFoo (Method fooMethod, Map<String, String> context) throws ... {
      List<Object> params = Arrays.stream(fooMethod.getAnnotations()).map(annos -> {
      if (annos[0] instanceof IntParam) {
      return context.get( ... ); // <-
      } else if (annos[0] instanceof FooParam) {
      return new Foo(context); // <-
      }
      }).collect(Collectors.toList());
      fooMethod.invoke(params.toArray());
      }


      The problem with this implentation is that I need to edit 2 different files if I want to add new types of params, which I would like to avoid for several reasons.Is there a way to write those lines in the same annotation file ?. The only way would be using a static/default method on the interface but either way this would type poorly.



      Any other way ?







      java annotations






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 10 at 18:41









      Vinz243

      3,55653062




      3,55653062





























          active

          oldest

          votes











          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%2f53242228%2fhow-to-provide-implementation-of-annotations-reading-alongside-the-annotation%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242228%2fhow-to-provide-implementation-of-annotations-reading-alongside-the-annotation%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