That's correct. I would like to implement a generic service, for example a
database connection handler and instantiate preconfigured instances of it
without programming. Using my previous pseudocode example:

component.xml of bundle 1:

<reference interface="com.acme.IDatabase" bind="setDB" unbind="unsetDB"
policy="dynamic" cardinality="1..1" >
   <property name="databaseurl" value="jdbc:mysql://database1..."/>
</reference>

component.xml of bundle 2:

<reference interface="com.acme.IDatabase" bind="setDB" unbind="unsetDB"
policy="dynamic" cardinality="1..1" >
   <property name="databaseurl" value="jdbc:mssql://database2..."/>
</reference>

But now I understand from Richard's response that this is not possible.



Richard S. Hall wrote:
> 
> 
> On 6/2/10 12:22, Felix Meschberger wrote:
>> Hi,
>>
>> On 02.06.2010 13:58, Norbert Somlai wrote:
>>    
>>> Hi,
>>>
>>> I know how to use FileInstall or the Web Console to reconfigure a
>>> component.
>>> What I could not find is a way to declaratively configure a component
>>> instance in component.xml, so I could keep the reference and the
>>> configuration at the same place. Something like
>>>
>>> <reference interface="com.acme.IInterface" bind="setInterface"
>>> unbind="unsetInterface" policy="dynamic" cardinality="1..1">
>>>
>>>     <property name="param1" value="value1"/>
>>>     ...
>>> </reference>
>>>
>>> and the ComponentContext on activation would contain this property so
>>> the
>>> new instance could initialize itself with it.
>>>
>>> Is there a way to achieve something like this with DS or DS+CM?
>>>      
>> I think there is a misconception here:
>>
>> The reference element is used to declare that the component uses a
>> service from the service registry. The attributes define further
>> requirements, e.g. the target property can be used to select the actual
>> services.
>>
>> The property element is used to configure the component itself.
>>
>> The configuration of the referenced service, which I assume is what you
>> are referring to, is not the task of the component. That service must
>> care for its configuration itself.
>>    
> 
> I understood it that he wanted to be injected with configured instances, 
> like if you used the specified properties to create a configured 
> instance from a component factory and then injected his component with 
> those specifically configured instances.
> 
> -> richard
> 
>> Regards
>> Felix
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>    
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Is-configuring-service-properties-the-Spring-DM-way-possible-with-Declarative-Services-tp28753396p28757815.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to