cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Kossakowski (JIRA)" <j...@apache.org>
Subject [jira] Closed: (COCOON-2083) Allow database connections defined as Spring beans to be used in Avalon components
Date Wed, 19 Sep 2007 22:32:14 GMT

     [ https://issues.apache.org/jira/browse/COCOON-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Grzegorz Kossakowski closed COCOON-2083.
----------------------------------------

    Resolution: Fixed

Implemented solution that has been described in this comment: https://issues.apache.org/jira/browse/COCOON-2106#action_12528410

Since Csaba Kazó confirmed it works I'm closing this issue. The only part left is to provide
tiny document explaining how to migrate Avalon configuration of database connection to Spring
ones. I'll create such within few days.

> 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.


Mime
View raw message