Bug#581487: java.lang.IllegalStateException: Failed to locate resource: XmlRpcClient.properties

2011-09-26 Thread Torsten Werner
Hi,

thank you for your bug report! I am sorry for my late reply. May you
come up with some patch to fix the issue? Or something similar, maybe
more detailed instructions? Any example property file?

Thanks!
Torsten

On Thu, May 13, 2010 at 8:20 AM, R B rjbbu...@gmail.com wrote:
 Package: libxmlrpc3-client-java
 Version: 3.1.3-2
 Severity: important
 Tags: squeeze upstream


 The version of libxmlrpc3-client-java which went into testing in April
 contains a change to allow the library version to be included in the
 client's user agent string, instead of hard-coding a more generic user agent
 string in the XmlRpcHttpTransport.java file.

 This change was implemented by adding an XmlRpcClient.properties file to the
 org/apache/xmlrpc/client directory which contains a property named
 user.agent
 whose value is the user agent string to use. The XmlRpcHttpTransport class
 was
 modified to look for this property file in that location and use the
 user.agent property contained therein as its USER_AGENT string.

 Presumably, the tool used to create the xmlrpc-client.jar file is supposed
 to
 first create or update the XmlRpcClient.properties file with the current
 version that is being built and include it in the jar, but the
 XmlRpcClient.properties file is missing in this release (and possibly from
 the
 upstream release, too), which results in a not-too-informative exception
 message.
 It is not possible to get a working client until an
 WEB-INF/classes/org/apache/xmlrpc/client/XmlRpcClient.properties file
 containing a user.agent property is added to the jar.

 It may not be a bad idea to add a fallback mechanism in the
 XmlRpcHttpTransport class in the event the XmlRpcClient.properties file is
 inadvertently forgotten in the future which will use a default hard coded
 user
 agent string if the attempt to load from the properties file fails for any
 reason, and maybe log some kind of warning.


 -- System Information:
 Debian Release: squeeze/sid
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'testing'), (500, 'stable')
 Architecture: amd64 (x86_64)

 Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/bash

 Versions of packages libxmlrpc3-client-java depends on:
 ii  libcommons-httpclient-java    3.1-9      A Java(TM) library for creating
 HT
 ii  libxmlrpc3-common-java        3.1.3-2    XML-RPC implementation in Java

 libxmlrpc3-client-java recommends no packages.

 libxmlrpc3-client-java suggests no packages.

 -- no debconf information




 __
 This is the maintainer address of Debian's Java team
 http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers.
 Please use
 debian-j...@lists.debian.org for discussions and questions.




__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for discussions and questions.


Bug#581487: java.lang.IllegalStateException: Failed to locate resource: XmlRpcClient.properties

2010-05-13 Thread R B

Package: libxmlrpc3-client-java
Version: 3.1.3-2
Severity: important
Tags: squeeze upstream


The version of libxmlrpc3-client-java which went into testing in April
contains a change to allow the library version to be included in the
client's user agent string, instead of hard-coding a more generic user agent
string in the XmlRpcHttpTransport.java file.

This change was implemented by adding an XmlRpcClient.properties file to the
org/apache/xmlrpc/client directory which contains a property named 
user.agent
whose value is the user agent string to use. The XmlRpcHttpTransport 
class was

modified to look for this property file in that location and use the
user.agent property contained therein as its USER_AGENT string.

Presumably, the tool used to create the xmlrpc-client.jar file is 
supposed to

first create or update the XmlRpcClient.properties file with the current
version that is being built and include it in the jar, but the
XmlRpcClient.properties file is missing in this release (and possibly 
from the
upstream release, too), which results in a not-too-informative exception 
message.

It is not possible to get a working client until an
WEB-INF/classes/org/apache/xmlrpc/client/XmlRpcClient.properties file
containing a user.agent property is added to the jar.

It may not be a bad idea to add a fallback mechanism in the
XmlRpcHttpTransport class in the event the XmlRpcClient.properties file is
inadvertently forgotten in the future which will use a default hard 
coded user

agent string if the attempt to load from the properties file fails for any
reason, and maybe log some kind of warning.


-- System Information:
Debian Release: squeeze/sid
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libxmlrpc3-client-java depends on:
ii  libcommons-httpclient-java3.1-9  A Java(TM) library for 
creating HT

ii  libxmlrpc3-common-java3.1.3-2XML-RPC implementation in Java

libxmlrpc3-client-java recommends no packages.

libxmlrpc3-client-java suggests no packages.

-- no debconf information




__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please 
use
debian-j...@lists.debian.org for discussions and questions.