Hey all,
I've just tried upgrading to the latest ConfigAdmin and found that the
persistence manager stuff has a breaking change.
Reading the code I see the following comment indicating that things should
work as previously:
/**
* The name of the framework context property defining the persistence
* manager to be used. If not specified, the old behaviour is used
* and all available pms are used
*
* @see #start(BundleContext)
*/
private static final String CM_CONFIG_PM = "felix.cm.pm";
However, that's not true. If I don't specify a _name_ service property for
my custom persistence manager AND configure this framework property with
that name, NO tracker is ever created, let alone started, which means NO
external persistence managers are ever tracked.
As it seems we've moved quite far along with this implementation I'd at
least request that the documentation and this comment be updated to
indicate that custom persistence managers are ONLY configurable through the
above framework property.
I'm very sorry that I didn't catch this in review :(
Sincerely,
--
*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)
