[ http://jira.andromda.org/browse/SPRING-123?page=comments#action_12179 ] Jens Vagts commented on SPRING-123: -----------------------------------
No, I don't want to "use a tagged value to add a reference to a service"! I only want to prevent the cartridge to generate code for the "foreign" service. Analogous the @andromda.spring.service.config.only tagged value but without generation of the "bean" definition in the application context. Only the "bean ref" elements for other services for each dependency drawn to this "foreign" service should be generated (like the config.only). > Use/define "foreign" services > ----------------------------- > > Key: SPRING-123 > URL: http://jira.andromda.org/browse/SPRING-123 > Project: Spring Cartridge > Type: Improvement > Versions: 3.1RC1 > Reporter: Jens Vagts > Assignee: Chad Brandon > > The nice thing about spring is the combination/instanciation of other objects > through "bean ref". In addition of the tagged value > @andromda.spring.service.config.only in SPRING-112 it would be nice to have a > "foreign" service reference by only defining the "bean ref" code but not the > bean declaration as of the @andromda.spring.service.config.only > implementation. The bean could than be defined in a separate application > context. > E.g. with a new tagged value "@andromda.spring.service.config.foreign"? ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl
