Could you detail what "cumbersome" and "not good" mean in your case and what issues are you experiencing?
Gson is a core dependency in jclouds and currently there is not an easy way to change that. Many components assume Gson, and I'm not sure adding Jackson just for a single provider would be a good idea (even if the dep resides only in the provider). We should try to have one common way to serialize/deserialize (this gains importance when having to maintain all providers and deal with the particularities of each one). Serialization should be as easy as building the java domain objects matching the json model. Are you having trouble with that? I can help with this either in this thread or in the IRC if you prefer (you'll find me as nacx). HTH! Ignasi El 24/11/2013 07:57, "Timur Sungur" <[email protected]> escribió: > Hi, > > I have a short question. Can I add Jackson dependency for json processing? > > Using Gson is more cumbersome and results are not that good with > respect to Jackson. > > I'm using it to serialize and de-serialize domain specific objects. > > Regards, > > Timur > > > On Fri, Oct 25, 2013 at 4:11 PM, Everett Toews > <[email protected]> wrote: > > I don't know if this was from the same person but the same question came > up on StackOverflow [1]. I answered it there and most of it was cribbed > from Ignasi comments [3]. Thanks again, Ignasi! > > > > I invite you all to edit my answer on SO and when were happy with it, > I'll copy it into the wiki and maybe we can get this question answered once > and for all. ;) > > > > Thanks, > > Everet > > > > [1] > http://stackoverflow.com/questions/19571901/information-about-jclouds/19592104#19592104 > > > > > > On Oct 23, 2013, at 5:06 AM, Andrew Phillips wrote: > > > >> Hi Timur > >> > >>> Could you please tell me how do you accept contributions and what still > >>> needs to be done so that this contribution can also reside with > existing > >>> providers? > >> > >> Thanks for contributing! The basic details can be found on the > "Contributing to jclouds" page [1]; one important thing to note for new > providers is that the pull request should be opened against the > jclouds-labs repository [2]. > >> > >> For some very useful style and implementation tips, see Ignasi's recent > comment to a different "new provider" pull request [3]. Thanks again, > Ignasi! > >> > >> Regards > >> > >> ap > >> > >> [1] > http://jclouds.incubator.apache.org/documentation/devguides/contributing-to-jclouds/ > >> [2] https://github.com/jclouds/jclouds-labs > >> [3] https://github.com/jclouds/jclouds/pull/188#issuecomment-26856785 > > >
