theli

Show:

What's happening?

  • Comment: Character encoding problem

    Hi, due to the last commit to the GeoAddressStandardizer (see [1]) the "get.getResponseCharSet()" was transformed to a "get.getRequestCharSet()" and therefore the encoding of the response is done wrong for german umlauts now. Could you change this back to use the response-charset to generate the String? Thank you! Regards, Martin [1]...

    2008-12-12 11:23:54 UTC in Geo-Google - Free Address Standardizer

  • Comment: Manual refresh of monitoring values

    Thank you for your answer. The patch is quite simple. For my usecase this simple restructuring is sufficient but please feel free to modify the patch if necessary. Best regards, Martin.

    2008-11-25 17:14:53 UTC in JSysmon

  • Comment: Manual refresh of monitoring values

    File Added: jsysmon.patch.

    2008-11-25 17:12:43 UTC in JSysmon

  • Manual refresh of monitoring values

    For my project I need the monitoring values generated by jsysmon very infrequently so the delay could be set to a higher value than the default. But there are some usecases where I need the values just now (e.g. if the user presses a button for refresh). Would you accept a patch providing a possibility to manually trigger re-reading of cpu- and memory-values? Regards, Martin.

    2008-11-01 08:43:41 UTC in JSysmon

  • DNSJavaNameService for both Jre1.5 and Jre1.6

    Hi, the DNSJavaNameService currently only supports Jre1.6. In the attached file there is patch that supports both, Jre1.5 and Jre1.6. Regards, Martin.

    2008-03-30 12:50:53 UTC in dnsjava

  • Multithreading Path

    As discussed in [1], it would be nice if Geo-google would support persistent connections and connection-pools. I've attached a patch for this. See: GeoGoogleMultiThreadingPatch.txt Regards, Martin [1] http://sourceforge.net/forum/forum.php?thread_id=1931939&forum_id=710555.

    2008-03-10 11:06:57 UTC in Geo-Google - Free Address Standardizer

  • Character encoding problem

    The response body is not read properly because |> IOUtils.toString(get.getResponseBodyAsStream()); is uses which uses the default character encoding of the platform. Therefore e.g. german umlauts were not read properly. The fuction call should be changed to: |> IOUtils.toString(get.getResponseBodyAsStream(),get.getResponseCharSet()); See: GeoGoogleCharsetPatch.txt Regards...

    2008-02-13 14:55:08 UTC in Geo-Google - Free Address Standardizer

  • jSoapServer

    thelian committed patchset 84 of module jSoapServer to the jSoapServer CVS repository, changing 3 files.

    2007-08-30 14:59:14 UTC in jSoapServer

  • jSoapServer

    thelian committed patchset 83 of module jSoapServer to the jSoapServer CVS repository, changing 14 files.

    2007-08-30 14:52:41 UTC in jSoapServer

  • jSoapServer

    thelian committed patchset 82 of module jSoapServer to the jSoapServer CVS repository, changing 1 files.

    2007-08-30 13:00:52 UTC in jSoapServer

About Me


Send me a message