I was just reading about it.
The only requirement I see is not to break the API contract on management.
Most of the JSON we have is for management responses, where we return
objects as JSON Arrays or JSON Objects.
Apparently using JSONP would change the responses we have on management?
Changing this to JSON-P would apparently mean we have to add a
function name to the return?
i.e... say... getConnectionsAsJSON currently returns this on the MBean Console:
apparently it would start to return something with a function name:
that is: getConnectionsAsJSON([......])
Which would be an incompatible change for a point release.
If we can use the library you mentioned but keeping the same output
through management without breaking a contract like this, it would be
How do you see it?
On Tue, Jun 14, 2016 at 5:30 PM, John D. Ament wrote:
Would you be interested in an impl based on the JSON-P spec? If so maybe
Johnzon would be a solution here.
On Tue, Jun 14, 2016 at 5:21 PM Clebert Suconic wrote:
Accordingly to apache legal, we can use JSON on our codebase, however
other projects may be unable to redistribute your code if you use this
license because of the:
"The Software shall be used for Good, not Evil."
So, Fedora guys are asking us to replace this on Artemis.
I looked at HBase and they have been through the same path apparently,
where they replaced it byhttps://code.google.com/archive/p/json-simple/
More fun reading at: https://issues.apache.org/jira/browse/ARTEMIS-565
Any volunteer to make the change? :)