On Mon, Apr 6, 2015 at 2:44 PM, Raymond Auge <raymond.a...@liferay.com> wrote:
> > > On Mon, Apr 6, 2015 at 2:33 PM, BJ Hargrave <hargr...@us.ibm.com> wrote: > >> > From: Raymond Auge <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. >> > FYI, This can't be supported by metatype, which puts it out of reach as a work around. - Ray > > >> > So to be clear, you mean something like: >> >> > my.primary.key.property.XYZ=value-ignored >> >> > and then: >> >> > (&(service.factoryPid=whatever.the.pid.is >> )(my.primary.key.property.XYZ=*)) >> >> Yes. >> >> > ... 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? >> > > ... because you'd be able to spec how that's handled? > > Meanwhile you can never localize a key which you never know ahead of time! > > - Ray > > >> >> > >> > - Ray >> > >> >> -- >> >> *BJ Hargrave* >> Senior Technical Staff Member, IBM >> OSGi Fellow and CTO of the *OSGi Alliance* <http://www.osgi.org/> >> *hargr...@us.ibm.com* <hargr...@us.ibm.com> >> >> office: +1 386 848 1781 >> mobile: +1 386 848 3788 >> >> >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> > > > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> > (@Liferay) > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> > (@OSGiAlliance) > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
