jettison-json/jettison

Issues

• `optString` Method Does Not Return Default Value for Explicit Null

  #105 opened 2 months ago by PurnAnrup
  1

• A OOM problem was found in jettison

  #88 opened a year ago by Alex111998
  1

• Jettison Unit test fail for version 1.2

  #95 opened 4 months ago by vimalchandts
  1

• Jettison compatibility with JDK 17

  #92 opened 4 months ago by test-account1233
  1

• Possible NumberFormatException thrown from JSONTokener

  #96 opened 6 months ago by arthurscchan
  0

• Security scan tool (Black Duck Binary Analysis) detected CVE-2023-5072, is the latest version 1.5.4 really affected by this vulnerability?

  #86 opened a year ago by ChewuuHi
  2

• Security scan tool (Black Duck Binary Analysis) detected CVE-2022-45688, is the latest version 1.5.4 really affected by this vulnerability?

  #77 opened 2 years ago by ChewuuHi
  2

• Question on breaking change or incompatibility between version 1.2 and 1.5.4

  #85 opened a year ago by pcouas
  1

• Jettison serialize array object as like json object when array object contains only one element in it.

  #83 opened a year ago by aweseeker
  0

• Find a StackOverflowError in jettison

  #54 opened 2 years ago by BIngDiAn-s
  2

• optXXX() should return default value instead of throwing a RuntimeException

  #78 opened 2 years ago by h-cheon
  0

• NoClassDefFoundError Exception with jettison 1.5.3

  #71 opened 2 years ago by sharma070289
  0

• upgraded jettison 1.5.1 to 1.5.2 , throwing error were JSONObject used and force to handle try/catch or surround with JSONException

  #68 opened 2 years ago by prasa18
  1

• If the value inside a Collection is itself, using it with JSONArray causes a StackOverflowError which may lead to DoS

  #60 opened 2 years ago by nitay-jfrog
  1

• JSON formatter/builders don't support all the data types defined in the JSON spec

  #61 opened 2 years ago by s3valkov
  0

• If the value in map is the map's self, the new new JSONObject(map) cause StackOverflowError which may lead to dos

  #52 opened 2 years ago by BIngDiAn-s
  2

• New OSS-Fuzz Findings in Jettison

  #45 opened 2 years ago by henryrneh
  10

• Incorrect backslash escaping

  #58 opened 2 years ago by siarheibarsukou
  3

• Please revert the recursion depth default limit as the retardation it is.

  #56 opened 2 years ago by newbstarr
  1

• Incorrect recursion depth check in JSONTokener in 1.5.2 causes it to fail for inputs with low recursion depth

  #57 opened 2 years ago by jiritousek
  1

• BDSA-2022-3278 was detected by security scan tool

  #55 opened 2 years ago by zhudaxi
  1

• Question on backward compatibility of 1.5.1 release with 1.4.x and 1.3.7

  #50 opened 2 years ago by Sachpat
  0

• Integrating jettison into OSS-Fuzz

  #40 opened 2 years ago by vargen
  2

• Need more check for JSONArray init, bad string can cause infinite loop

  #36 opened 2 years ago by manecocomph
  1

• improve "A JSONObject text must begin with '{' at character 1 of" error message

  #46 opened 2 years ago by ralfhauser
  3

• Infinite loop in the parser finally leading to Stack Overflow

  #47 opened 2 years ago by kmnls
  1

• What is the outlook for the Jettison development/release model?

  #44 opened 3 years ago by ind1go
  1

• method JSONObject.write() bug in case of ignored elements

  #35 opened 3 years ago by deadlious
  3

• Unicode escaping

  #39 opened 4 years ago by hlavki
  0

• JSONObject not handling properly in-code defined arrays

  #34 opened 5 years ago by juanjmostazo
  0

• Jettison 1.3.x array handling breaks XStream

  #12 opened 5 years ago by sberyozkin
  1

• JSONObject#quote should escape U+2028 and U+2029 characters too

  #19 opened 5 years ago by pvojtechovsky
  0

• TypeConverter not running for strings of type Object

  #32 opened 5 years ago by kpentaris
  0

• indentFactor not honored

  #29 opened 5 years ago by tresf
  0

• @xmlns in JSON not showing up when converting to XML

  #27 opened 6 years ago by mwooten
  0

• doesn't preserve order

  #26 opened 6 years ago by ravi005e
  0

• The single element array issue is fixed in the latest version?

  #24 opened 7 years ago by shengang1978
  1

• Truning off forward slash escaping is not possible for JSON Arrays

  #17 opened 7 years ago by grunci
  2

• Align Jettison POM with OSSRH

  #16 opened 7 years ago by sberyozkin
  1

• Remove StAX dependency

  #20 opened 7 years ago by runeflobakk
  1

• Make jettison JDK 10+ compliant

  #21 opened 7 years ago by rsvoboda
  0

• new JSONArray("[") return StackOverFlowException

  #18 opened 8 years ago by JosselinChantrel
  0

• MappedNamespaceConvention.setAttributesAsElements() does not set attributes as elements

  #7 opened 9 years ago by sberyozkin
  0

• Turn off or on forward slash escaping on an already created JSONObject.

  #13 opened 9 years ago by grunci
  1

• MappedXMLStreamWriter does not auto-convert attributes to primitives

  #15 opened 9 years ago by sberyozkin
  0

• Jettison stream readers should return NamespaceContexts based on the info available in MappedNamespaceConvention

  #11 opened 10 years ago by sberyozkin
  1

• List problem in MappedXMLStreamWriter

  #10 opened 10 years ago by sberyozkin
  0

• getElementText() should set the current event to the END_ELEMENT in MappedXMLStreamReader.

  #9 opened 10 years ago by sberyozkin
  0

• SerializeAsArray feature does not work if a list contains a single element only if its XML representation has attributes

  #8 opened 10 years ago by sberyozkin
  1

• JSONObject do support octal

  #6 opened 10 years ago by sberyozkin
  0