This reminds me of the difference between implementation.ejb and implementation.jee.
Regards, Steve Stephen Kinder STSM, SOA Foundation Architect WAS for z/OS Architecture IBM Poughkeepsie, New York USA (845) 435-4854 [email protected] ----- Forwarded by Stephen J Kinder/Poughkeepsie/IBM on 02/12/2009 09:11 AM ----- "Ramkumar Ramalingam (JIRA)" To <[email protected] [email protected] he.org> cc 02/12/2009 06:45 Subject AM [jira] Commented: (TUSCANY-2503) Spring implementation doesn't see spring beans Please respond to [email protected] e.org [ https://issues.apache.org/jira/browse/TUSCANY-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672954#action_12672954 ] Ramkumar Ramalingam commented on TUSCANY-2503: ---------------------------------------------- Hi Marek, I believe this is really a very interesting usecase. Lets talk about the possibilities here... Talking about implementation, I think examining the beans from the application context would not be possible as we don't want to create an application context before we understand which beans are tagged from sca services/references/properties. But I believe it should be possible to create a XMLBeanFactory factory with the given application-context.xml and use the beanFactory to locate the beans. Let me try this and let you know the details. > Spring implementation doesn't see spring beans > ---------------------------------------------- > > Key: TUSCANY-2503 > URL: https://issues.apache.org/jira/browse/TUSCANY-2503: > Project: Tuscany > Issue Type: Bug > Components: Java SCA Spring Implementation Extension > Affects Versions: Java-SCA-1.2.1 > Reporter: Marek Kaluzny > Assignee: Ramkumar Ramalingam > Priority: Critical > Fix For: Java-SCA-Next > > > Spring implementation looks only for beans declared in file specified with location parameter, and only with <bean> tags. > If we import some other context files with beans definitions or declare spring beans in other ways than <bean> tag (for example tags in different namespace or using annotations) such beans will be unavailable for Spring Implementation. > Now if we are using <sca:service> tag then target property can refer only to beans declared in the same applicationContext file and only with <bean> tag. > Spring implementation should examine whole ApplicationContext created by Spring to locate the bean rather than parsing xml files on his own. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
<<inline: pic31327.gif>>
<<inline: ecblank.gif>>
