Skip to main content

[jsr353-experts] Re: JSON_PROCESSING_SPEC-44:Replace JsonFeature/JsonConfiguration with Properties

  • From: Jörn Horstmann < >
  • To:
  • Subject: [jsr353-experts] Re: JSON_PROCESSING_SPEC-44:Replace JsonFeature/JsonConfiguration with Properties
  • Date: Fri, 11 Jan 2013 23:41:18 +0100

On 01/11/2013 08:55 PM, Jitendra Kotamraju wrote:
Brian Goetz strongly suggests this [1]. I don't really agree, but if
most of you think that's right way to do this, we can use Properties or
Map for configuration. We had some discussion about this on the mailing
lists as well.

[1] http://java.net/jira/browse/JSON_PROCESSING_SPEC-44

I agree with his point, a string based api like in JAXP with setFeature/setProperty methods on the factories would be better for extensability and compatibility.

A useful part of that api is that these methods can throw a SAXNotRecognizedException which the library user can then decide to ignore if the feature is not essential for operation. For example I could customize the pretty printing using features of a specific implementation, and just use the default format for other implementations.

Jörn



[jsr353-experts] JSON_PROCESSING_SPEC-44:Replace JsonFeature/JsonConfiguration with Properties

Jitendra Kotamraju 01/11/2013

[jsr353-experts] Re: JSON_PROCESSING_SPEC-44:Replace JsonFeature/JsonConfiguration with Properties

Jörn Horstmann 01/11/2013
 
 
Close
loading
Please Confirm
Close