Why does BaseX create empty System-properties
Hi all, I am wondering why BaseX is setting empty System-properties like http.proxyHost on startup? We are experiencing problems with Spring Social. It tries to create a proxy since http.proxyHost exists, but fails due to the empty value. Best Rune
Hello Rune, this system property is overwritten by the BaseX configuration and the default values is empty for proxyhost. See https://docs.basex.org/wiki/Options#PROXYHOST for some more information and how to change the option. Cheers, Dirk On 14/08/14 23:36, rune.engh@fatax.no wrote:
Hi all,
I am wondering why BaseX is setting empty System-properties like http.proxyHost on startup? We are experiencing problems with Spring Social. It tries to create a proxy since http.proxyHost exists, but fails due to the empty value.
Best Rune
-- Dirk Kirsten, BaseX GmbH, http://basex.org |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22
Hi Rune, true, it's probably more reasonable to only set the properties if they are non-empty. Could you please check out the latest snapshot [1]? Best, Christian [1] http://files.basex.org/releases/latest/ On Thu, Aug 14, 2014 at 11:36 PM, <rune.engh@fatax.no> wrote:
Hi all,
I am wondering why BaseX is setting empty System-properties like http.proxyHost on startup? We are experiencing problems with Spring Social. It tries to create a proxy since http.proxyHost exists, but fails due to the empty value.
Best Rune
participants (3)
-
Christian Grün -
Dirk Kirsten -
rune.engh@fatax.no