[
https://issues.apache.org/jira/browse/COCOON-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518179
]
Grzegorz Kossakowski commented on COCOON-2106:
----------------------------------------------
If registration of wrapper is implemented that bridge won't be needed anymore
and should be removed. I also think that further discussion about wrappers
should continue in COCOON-2083 because it's an issue covering the task of
datasources bridging. Unfortunately, I'll not have enough free time to
implement registration in upcoming days so I'll unassign myself from both
issues. However, I'll be happy to help any volunteer.
When it comes to Avalon sources not correctly looked up in Avalon components I
have no idea why it doesn't work. I guess that the answer is in
SpringToAvalonDataSourceBridge becuse it replaces original Avalon's
DataSourceComponentSelector so even Avalon sources are handled by this
component.
Kazo, if you wanted to dig into this particular issue I think it's not worth
the effort because as I said earlier whole bridge should be replaced by
wrappers registration.
> DatabaseReader and SQLTransformer cannot obtain datasource
> ----------------------------------------------------------
>
> Key: COCOON-2106
> URL: https://issues.apache.org/jira/browse/COCOON-2106
> Project: Cocoon
> Issue Type: Bug
> Components: Blocks: Databases
> Affects Versions: 2.2-dev (Current SVN)
> Reporter: Kazó Csaba
> Assignee: Grzegorz Kossakowski
> Attachments: dbreader.diff, sqltrans.diff
>
>
> The DatabaseReader and SQLTransformer components fail to obtain the
> configured data source and throw a ServiceException like "Component with
> 'org.apache.avalon.excalibur.datasource.DataSourceComponent/personnel' is not
> defined in this service manager. (Key='AvalonServiceManager')". The failing
> function call in both cases is:
> this.manager.lookup(DataSourceComponent.ROLE + '/' + datasourceName)
> The result is the same regardless of whether the data source is defined as an
> Avalon component or a Spring bean.
> Changing the code to use ServiceSelector as in the "Creating a Reader"
> document [1] and the modular database actions solves the problem for both
> cases. The attached patch applies this modification to DatabaseReader.java.
> [1] http://cocoon.zones.apache.org/daisy/cdocs/g1/g1/g2/g1/g2/681.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
