Vadim Gritsenko wrote:
So, to answer Harald's question, he should use Serviceable instead of Composable, and may be file a bug against avalon excalibur component manager (Carsten? any info on this?)
Afaik, this is not considered a bug :) Cocoon is based on the ECM which is a ComponentManager. But you can use Serviceable and in that case still the ComponentManager is used which requires the Component interface.
It's the excalibur datasource that's in question here, not his code. He's not getting a proxy returned on his component but on the Datasource he's gotten out of the DataSourceSelector. IIRC Component/Serviceable is not the only time you'll get a proxy out of excalibur-xxxx. Does anyone know about the JDK 1.3/1.4 thing it does?
Geoff
