Age | Commit message (Collapse) | Author |
|
Modules sal, salhelper, cppu, cppuhelper, codemaker (selectively) and odk
have kept them, in order not to break external API (the automatic using declaration
is LO-internal).
Change-Id: I588fc9e0c45b914f824f91c0376980621d730f09
|
|
Change-Id: I9c510a0edb2a04d1378d488cc724e8f9982b5ba3
|
|
First of all, NEON_VERSION is undefined, and second, it's actually
a text string, so this is all broken.
Change-Id: Iba841c78e9034bf9ef74eb4f31c9893608180b77
|
|
It won't work, ne_debug_init() will be called always (in non-release builds).
This reverts commit b6f6c3a2ed19cc34cce5d19c32c921227165bdd0.
|
|
Instead of #if OSL_DEBUG_LEVEL>0.
Change-Id: I2329de4deff4687fb1249c47f2e24eaf6ea6a248
|
|
Part of fix for the WebDAV https server authentication problem noticed when
fixing bnc#805901.
Change-Id: Ic54c59bdadaf34cdba32949400d5da69712017f3
|
|
Change-Id: I4acb7ab1aeba31bfeedd4dfbcd76d6bf517b8944
|
|
Change-Id: I08d540bdbe32ba9df994528bac97ac76e587795a
|
|
See <http://lists.manyfish.co.uk/pipermail/neon/2013-February/001533.html> "Re:
About ne_set_read_timeout" for why ne_close_connection is not a solution here
(and currently would not work anyway, for the thread calling abort would block
on the aGlobalNeonMutex introduced with 510da29131e56ba0e1783e505e7131e6f7e0d6b4
"forced to make certain neon api calls thread-safe due to cups" until the
blocking thread was done with its neon call) and "a new, dedicated, thread-safe
ne_session_* API call will be needed to allow aborting of a running request."
So enable DAVResourceAccess::abort again and instead disable the underlying
NeonSession::abort. i#106766 "Crash when cancelling extension update" does not
give any good rationale why DAVResourceAccess::abort had to be disabled, so it
might well have been because the underlying NeonSession::abort was bogus to
begin with.
Change-Id: If8293b93a960907726208bb2f93c375d83357ed3
|
|
Change-Id: I369da2262d42fbc7cc3cfeeef4920606522237cd
|
|
Also create an NSSInitializer service IDL and split it's interfaces
out from SEInitializer.
It looks like this was the intention all along, but someone
took a shortcut.
Change-Id: I53ac1cb5d38b78b6718fe22c9666eae1f194a3b7
|
|
...in favor of existing new-style configuration::theDefaultProvider singleton.
Theoretically, ConfigurationProvider instances can be created with specific
Locale and EnableAsync arguments, but this is hardly used in practice, and thus
effectively all uses of the ConfigurationProvider service use the
theDefaultProvider instance, anyway.
theDefaultProvider is restricted to the XMultiServiceFactory interface, while
ConfigurationProvider also makes available XComponent. However, dispose must
not be called manually on theDefaultProvider singleton anyway, and calls to
add-/removeEventListener are so few (and in dubious code that should better be
cleaned up) that requiring an explicit queryInterface does not really hurt
there.
This commit originated as a patch by Noel Grandin to "Adapt
configuration::ConfigurationProvider UNO service to new style [by creating] a
merged XConfigurationProvider interface for this service to implement." It was
then modified by Stephan Bergmann by deprecating ConfigurationProvider instead
of adding XConfigurationProvider and by replacing calls to
ConfigurationProvider::create with calls to theDefaultProvider::get.
Change-Id: I9c16700afe0faff1ef6f20338a66bd7a9af990bd
|
|
Change-Id: Ia8bcd2efd8137922024fb2ed2f2e4197f4ee25e1
|
|
|