|
From: Adrian C. <adr...@in...> - 2006-09-27 14:05:03
|
Yes, this is the expected behaviour. AspectJ honours Java semantics, and the Java rules for annotations are that they are never inherited from an interface (so from the perspective of Java and AspectJ, the class that you instantiate does *not* have the @Configurable annotation, even if it implements an interface that does). Regards, Adrian. Nicolas De Loof wrote: > I have a business objet that implements an interface marked as > "@Configurable". > AspectJ weaving enhances my business object as expected, but the > AnnotationBeanWiringInfoResolver doesn't extracts BeanWiringInfo as my > object class isn't itself annotated. > > Is this the expected behavious ? > Couldn't the AnnotationBeanWiringInfoResolver search in the classe > hierarchy for @Configurable ? (Maybe as an optional behaviour) > > Nico. > > > > This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > -- Adrian adr...@in... |