New cppu::defaultBootstrap_InitialComponentContext implementation

...that no longer uses XSimpleRegistry structures for the service data and thus
is potentially more performant.

* Registry-based functions from cppuhelper/bootstrap are deprecated now, client
  code should always use defaultBootstrap_InitialComponentContext.

* References to the obsolete UNO_WRITERDB have been removed.

* Some of the functions in cppuhelper/source that are used from multiple .cxx
  but had not been properly placed into .hxx have been cleaned up.

* css.lang.ServiceManager XSet insert/remove now support special
  sequence<NamedValue> to improve live deployment/removal of XML-based extension
  components data.

* 09524d410bbaad2a0b9b39811cb5cc16621b1396 "stoc: accelerate opening of multiple
  XML .rdb files in a directory" and its follow-up
  cb5c881a7f179391ee853f76e159254c97d776a3 "avoid using the new rdb reading
  logic for empty/non-existent directories" have been obsoleted by this change
  and have been reverted again.

1 files changed, 15 insertions, 0 deletions

diff --git a/udkapi/com/sun/star/lang/ServiceManager.idl b/udkapi/com/sun/star/lang/ServiceManager.idl
index f74ca9f22fec..cc11c0844614 100644
--- a/udkapi/com/sun/star/lang/ServiceManager.idl
+++ b/udkapi/com/sun/star/lang/ServiceManager.idl
@@ -75,6 +75,21 @@ module com {  module sun {  module star {  module lang {
     on the factory when going down (i.e. it is commonly disposed by the component context).</dd>
     </dl>
 
+    <p>Since LibreOffice 3.6, in addition to instances of
+    <type>XServiceInfo</type> et al, the
+    <type scope="com::sun::star::container">XSet</type> of at least the default
+    C++ service manager implementation now also supports sequences of
+    <type scope="com::sun::star::beans">NamedValue</type> in <code>insert</code>
+    and <code>remove</code>.  The sequence elements must each have a
+    <code>Name</code> of <code>uri</code> and a string <code>Value</code> that
+    is the URI of a service rdb.  It is legal for there to be no such
+    <code>uri</code> elements.  For <code>insert</code>, there can additionally
+    be an optional element with a <code>Name</code> of
+    <code>component-context</code> and a value that is a non-null reference of
+    type <type scope="com::sun::star::uno">XComponentContext</type> that shall
+    be used instead of this service manager's default component context when
+    loading the corresponding implementations.
+
     @see com::sun::star::uno::XComponentContext
 */
 published service ServiceManager