• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Jersey JSON notation conflicts

 
Ranch Hand
Posts: 201
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi


I am developing a RESTful client for a RESTful webservice and the data exchange format specified by the service is JSON. I am using Jersey 1.2 API for interacting with the service. This might seem a dumb question but I have a doubt and need your suggestions on this -

There are four different types of JSON notations namely MAPPED (default for Jersey), NATURAL, JETTISON_MAPPED and BADGERFISH. I am unsure on which type of notation the web service is going to send the response in because I have not yet received detailed specifications on the service.

My question is, if use the default notation, i.e. MAPPED one and the service returns the response in, say, JETTISON_MAPPED, is it going to create problems ? Similarly, if I send JSON request in MAPPED notation form while the service used JETTISON_MAPPED, will it cause processing errors at the service end ?

Please clarify.
 
Girish Vasmatkar
Ranch Hand
Posts: 201
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Bump
 
reply
    Bookmark Topic Watch Topic
  • New Topic