Hi

Am 06.04.2015 um 20:33 schrieb BJ Hargrave 
<hargr...@us.ibm.com<mailto:hargr...@us.ibm.com>>:

> From: Raymond Auge <raymond.a...@liferay.com<mailto:raymond.a...@liferay.com>>

> On 04/06/2015 03:30 PM, BJ Hargrave wrote:
> Seem like you just need a convention where you put the human
> readable/pretty name in a key of the configuration and then you can find
> it with listConfigurations if you need to.
>
> So to be clear, you mean something like:

> my.primary.key.property.XYZ=value-ignored

> and then:

> (&(service.factoryPid=whatever.the.pid.is<http://whatever.the.pid.is>)(my.primary.key.property.XYZ=*))

Yes.

Hmm, why the „foreign key“ value as the property name ?

Wouldn’t it rather be the value of a conventional name, e.g.

    my.primary.key.property=XYZ

and thus

    
(&(service.factoryPid=whatever.the.pid.is<http://whatever.the.pid.is>)(my.primary.key.property=XYZ))

AFAICT both Felix FileInstall and Sling OSGi Install do this already and 
invented their own „alias“ property key.

Maybe the ask is to come up with a common convention such that user agents such 
as the Web Console can easily and specifically deal with it like they currently 
deal with the factoryPid and the pid ?

Whether that needs to go to the specification is another question ...

Regards
Felix



> ... that might work as a temporary solution :(

> However it means you could never localize that key in the UI!

I don't understand? How would this be any different if you were allowed to set 
the value of the pid for a factory configuration?

>
> - Ray
>

--

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance<http://www.osgi.org/>
hargr...@us.ibm.com<mailto:hargr...@us.ibm.com>

office: +1 386 848 1781
mobile: +1 386 848 3788


_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org>
https://mail.osgi.org/mailman/listinfo/osgi-dev

_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to