Re: [one-users] Java OCA: poor choiche of Exception class

2011-04-28 Thread Carlos Martín Sánchez
Hi there, The RuntimeException looks better to me. The only thing I'm not sure about is why you deleted the 'throws' declaration from Client.java. Doing that, a client application is not forced to catch the connection problem. I think it's better to force the coder to be aware of this kind of

Re: [one-users] Java OCA: poor choiche of Exception class

2011-04-11 Thread Carlos Martín Sánchez
Hi Gian Uberto, Thank you for your feedback. As you may know, we use mainly our Ruby bindings for external tools and extensions, so these comments about the Java API are very welcome. Please feel free to open a ticket in our development portal [1], along with any other comments, suggestions or

[one-users] Java OCA: poor choiche of Exception class

2011-04-04 Thread Gian Uberto Lauri
Hello, I just started to use OCA and immediately had the bad surprise to find an Exception thrown by Client class instantiation. Peeking in the code, I discovered that the Client class throws it when it does not find two mandatory resources, the $ONE_AUTH file and the SHA-1 algorithm. In my

Re: [one-users] Java OCA: poor choiche of Exception class

2011-04-04 Thread Gian Uberto Lauri
CC == Gian Uberto Lauri sa...@eng.it writes: CC Hello, I just started to use OCA and immediately had the bad CC surprise to find an Exception thrown by Client class CC instantiation. One thing I forgot in the previous message: I know people in Apache Software Foundation do such raw