* As UCB is only ever initialized with "Local"/"Office", remove this
configuration vector completely. The "create" ctor creates an instance
internally initialized with those "Local"/"Office" keys. Special (test) code
can still instantiate an uninitialized one via plain createInstance. And for
backwards compatilibity process startup still ensures to create an initialized
instance early, in case there is still code out there (in extensions) that
later calls plain createInstance and expects to get the already-initialized
(single) instance.
* XInitialization is an "implementation detail" of the UniversalContentBroker
service, do not expose in XUniversalContentBroker.
* ucbhelper/configurationkeys.hxx is no longer needed and is removed.
* ucbhelper/contentbroker.hxx is an empty wrapper and is removed; however, that
requires ucbhelper::Content constructors to take explicit XComponentContext
arguments now.
* The only remaining code in ucbhelper/source/client/contentbroker.cxx is
Android-only InitUCBHelper. Is that relevant still?
Change-Id: I3f7bddd0456bffbcd13590c66d9011915c760f28
Create a merged XNumberFormatter2 interface for this service to implement.
Which is backwards-compatible, but does not require creating a new service.
Change-Id: I57f35cde0a9dbbe91c1d2c3d068cb3a97c7245e3
dbtools were added in 01089138cc only to
create dependency and fix the build.
This creates circular dependency for libmerged, dbtools is not that
common library.
It's better to create real dependency in connectivity_inc package.
To avoid another circular dependency gb_YaccTarget_get_header_target
must not depend on external headers target.
Change-Id: I536376303de5330addd2dbf85bdfea8b9a23301c
With gb_Jar_add_jar and gb_Jar_add_system_jar adding to the manifest
classpath automatically it is no longer necessary to call
gb_Jar_set_jarclasspath manually except for the URE jars, which
are apparently not supposed to be added automatically.
Change-Id: I1e743e7ecb9cb5651e02005aa09e127bea1b0a29
The descriptions for fdo#53246 "Libo36 does not start, InvalidRegistryException
from program/services/postgresql-sdbc.rdb" make it look like the user had
installed the functionality that comes bundled in postgresql-sdbc.rdb also as an
extension installed per-user or shared.
<http://wiki.documentfoundation.org/PostgreSQL-SDBC> indicates that what is now
bundled due to c97d74b5f0 "fdo#45090: Changed
postgresql-sdbc from bundled oxt to proper optional part" indeed was once
available as a freestanding postgresql-sdbc-*.oxt that could have been installed
per-user or shared.
To prevent problems with such scenarios, rename the relevant implementation
names by adding a ".noext" suffix.
Change-Id: I43414a64461ba643f0ca0b2749450099cb6c8a4d
This avoids fetching data that will not be requested when the "cursor" is only moved and no data requested. That is typically what RowSetCache does when its own cursor is moved within its window.
This basically makes the whole {next,previous,absolute,...}_checked story obsolete, by basically always being as fast as the i_bFetchRow==false case, but in a safer way.
Change-Id: I89eaf277069736b3077bde8b45325929db290f2d
