Hi Alex, Am Mittwoch, den 18.06.2008, 10:04 -0500 schrieb Aleksandr Kravets: > Hi, > > Just wanted to make sure I understand the reason behind not persisting > Configuration when before its first update. > > Felix said: > "So in light of this situation, I turn to thinking, that Configuration > objects from createFactoryConfiguration must not be persisted. > Because, if such an object is created and then abandoned without ever > updating > it, it will not be accessible anymore: because the actual generated > PID of the Configuration might be unknown and the Configuration will > not be returned by listConfiguration." > > Is this the reason why specification mandates for not persisting a > Configuration upon its initial creation?
Actually, the spec mandates that Managed Service Configuration objects be immediately persisted (Section 104.7.1: The getConfiguration method must atomically create and persistently store an object if it does not yet exist). But: The spec does _not_ mandate any persistent storage for newly created Managed Service Factory Configuration objects (see section 104.7.2). This is what confused me. And what you cite above is my explanation, why Managed Service Factory Configuration should probably better not be stored before being updated. Regards Felix _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
