[ https://issues.apache.org/jira/browse/COCOON-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517898 ]
Grzegorz Kossakowski commented on COCOON-2083: ---------------------------------------------- See this[1] comment describing how beans should be named to work properly in Avalon components. [1] https://issues.apache.org/jira/browse/COCOON-2106#action_12517896 > Allow database connections defined as Spring beans to be used in Avalon > components > ---------------------------------------------------------------------------------- > > Key: COCOON-2083 > URL: https://issues.apache.org/jira/browse/COCOON-2083 > Project: Cocoon > Issue Type: New Feature > Components: * Cocoon Core, Blocks: Databases > Affects Versions: 2.2-dev (Current SVN) > Reporter: Grzegorz Kossakowski > Assignee: Grzegorz Kossakowski > Fix For: 2.2-dev (Current SVN) > > > In thread http://thread.gmane.org/gmane.text.xml.cocoon.devel/73925 we have > came to conclusion that there is no way to access database connections > defined as Spring beans. Since we have a lot of Avalon-managed components in > Cocoon and Spring-based solutions are preferred now I think it's worth to > implement a bridge that will connect both worlds. > The idea is implement Avalon's selector (DataSourceSelector) that will gather > connections defined both in Avalon and Spring way and expose all of them. New > Spring-based selector will replace old one and the old one will be renamed to > stay still accessible for new selector. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.