Databases
StackOverflow2013
Postsdbo
POPassing annotation properties to meta-annotations
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPassing annotation properties to meta-annotations
    primarykey
    data
    text
    <p>Say I have an annotation with a property:</p> <pre><code>@Named(name = "Steve") private Person person </code></pre> <p>and I want to create a compound annotation with several meta-annotations, including the one that takes a property</p> <pre><code>@Named @AnotherAnnotation @YetAnotherAnnotation public @interface CompoundAnnotation { ... } </code></pre> <p>Is there a way that I can pass properties to the compound annotation to one of the meta annotations?</p> <p>Eg, something like this:</p> <pre><code>@CompoundAnnotation(name = "Bob") private Person person; </code></pre> <p>that is equivalent to, but much more convenient than</p> <pre><code>@Named(name = "Bob") @AnotherAnnotation @YetAnotherAnnotation private Person person; </code></pre> <p>Thanks!</p> <p>PS apologies for my poor choice of an example annotation - I didn't have the javax.inject.@Named annotation in mind, just some arbitrary annotation that has properties.</p> <hr> <p>Thank you everyone for your answers/comments.</p> <p>It definitely seems to be the case that this is not possible. However, it just happens that there is a simple work-around for my case-in-point, which I will share in case it helps anyone:</p> <p>I am working with Spring and want to create my own Annotations that have @Component as a meta-annotation, thus being autodetected by component scanning. However, I also wanted to be able to set the BeanName property (corresponding to the value property in @Component) so I could have custom bean names.</p> <p>Well it turns out that the thoughtful guys at Spring made it possible to do just that - the AnnotationBeanNameGenerator will take the 'value' property of whatever annotation it is passed and use that as the bean name (and of course, by default, it will only get passed annotations that are @Component or have @Component as a meta-annotation). In retrospect this should have been obvious to me from the start - this is how existing annotations with @Component as a meta-annotation, such as @Service and @Registry, can provide bean names.</p> <p>Hope that is useful to someone. I still think it's a shame that this is not possible more generally though!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTom McIntyre
    1. USTom McIntyre
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPassing annotation properties to meta-annotations
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPassing annotation properties to meta-annotations
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPassing annotation properties to meta-annotations
      1. USsmendola
      1. VTFavorite
    1. COI don't see how, unless you're adding annotations via byte-code manipulation at load time. (Or a custom annotation processor, I suppose.) Curious to see what all is possible w/o tricks, though.
      singulars
      1. POPassing annotation properties to meta-annotations
      1. USDave Newton
    2. COJust thinking aloud here, will this not be a workaround if you had a base class annotated with AnotherAnnotation and YAA, and then Person class extended that? Look at Reflections too, maybe you'll get some ideas: http://code.google.com/p/reflections/
      singulars
      1. POPassing annotation properties to meta-annotations
      1. USmaksimov
    3. CORelated to http://stackoverflow.com/questions/1624084/why-is-not-possible-to-extend-annotations-in-java
      singulars
      1. POPassing annotation properties to meta-annotations
      1. USGray
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload