This content has been marked as final.
Show 3 replies
-
1. Re: BeanAnnotationAdapter/AnnotationPlugin
jaikiran Aug 12, 2009 2:07 PM (in response to kabirkhan)Similar discussion here http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153499.
-
2. Re: BeanAnnotationAdapter/AnnotationPlugin
alesj Aug 13, 2009 6:31 AM (in response to kabirkhan)"kabir.khan@jboss.com" wrote:
Would it not make more sense to do something like this instead, which would only hit the MDR.getAnnotation() when there actually are any annotations?
If that works, sure. -
3. Re: BeanAnnotationAdapter/AnnotationPlugin
kabirkhan Nov 27, 2009 11:53 AM (in response to kabirkhan)https://jira.jboss.org/jira/browse/JBKERNEL-64
On Monday, I'll try to get rid of this from AbstractAnnotationPlugin.apply/cleanAnnotation()public final void applyAnnotation(T info, MetaData retrieval, MetaDataVisitor visitor) throws Throwable { boolean trace = log.isTraceEnabled(); if (isCleanupOnly() == false) { Class<C> annotationClass = getAnnotation(); C annotation = retrieval.getAnnotation(annotationClass); if (annotation == null) { if (trace) log.trace("No annotation: " + annotationClass.getName()); return; } if (isMetaDataAlreadyPresent(info, annotation, visitor.getControllerContext())) ...
by changing it topublic final void applyAnnotation(T info, C annotation, MetaData retrieval, MetaDataVisitor visitor) throws Throwable { boolean trace = log.isTraceEnabled(); if (isMetaDataAlreadyPresent(info, annotation, visitor.getControllerContext())) ...
Since this is now driven by the existing annotations the check is pointless