Re: Oops with DigitalOcean and jclouds 1.9.1

Well, although it is gson the one that deserializes, it is using a strategy class provided by jclouds to lookup the constructor or factory method to invoke: https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/json/internal/NamingStrategies.java#L183 The domain objects in

Re: Oops with DigitalOcean and jclouds 1.9.1

On Tue, Oct 27, 2015 at 6:19 PM, Ignasi Barrera wrote: > In order to get a better understanding of what is going on, I'll push a > branch with verbose logging at that point. Would you be able to build that > and use it in your build, to see more context when the failure happens?

Re: Oops with DigitalOcean and jclouds 1.9.1

I've just opened: https://github.com/jclouds/jclouds/pull/873 It would be great if you could build the PR branch and use that version in your builds. Let's see if the more detailed exceptions bring some light and help us understand what is going on. On 27 October 2015 at 20:30, Giovanni Toraldo

Re: Oops with DigitalOcean and jclouds 1.9.1

Yes, it looks good. Can you try a build with Java 7? It is the official version supported to build jclouds, although we have some builds configured to use Java 8, but not in jclouds-labs. Just to isolate the issue, as in the past we found that the JVM influenced. Also you should revoke your

Re: Oops with DigitalOcean and jclouds 1.9.1

For the record, I'm using jclouds 1.9.1 and digitalocean, and running the app on a: Java version: 1.8.0_45, vendor: Oracle Corporation And have no issues. Could you also try that version of the JVM? On 26 October 2015 at 14:58, Ignasi Barrera wrote: > Yes, it looks good. > >

Re: Oops with DigitalOcean and jclouds 1.9.1

Hi Ignasi, thanks for the fast response. I've added dependencies and mvn/java version to the previous gist, I should be able to provide wire logs tomorrow. Thanks! Il giorno ven 23 ott 2015, 12:47 Ignasi Barrera ha scritto: > Hi Giovanni, > > We already saw that issue in

Re: Oops with DigitalOcean and jclouds 1.9.1

Hi Giovanni, We already saw that issue in earlier versions [1] but it turned to be an issue with the domain classes having more than one constructor. Looking at your stacktrace I can see the issue is raised here [2], when jclouds tries to deserialize the list of regions and determine which json