[
https://issues.apache.org/jira/browse/AXIS2-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833695#comment-15833695
]
Hudson commented on AXIS2-2037:
-------------------------------
SUCCESS: Integrated in Jenkins build Axis2 #3656 (See
[https://builds.apache.org/job/Axis2/3656/])
AXIS2-2037: Using a non standard content type (application/json/badgerfish) is
already a questionable choice, but at least it should be spec compliant (which
is not the case because of the second slash). Use application/json+badgerfish
instead. (veithen: rev 1779844)
* (edit) axis2/modules/json/test-repository/json/axis2.xml
* (edit) axis2/modules/json/test/org/apache/axis2/json/JSONIntegrationTest.java
* (edit) axis2/modules/json/test/org/apache/axis2/json/JSONTestConstants.java
> Improvement in json support for Axis2
> -------------------------------------
>
> Key: AXIS2-2037
> URL: https://issues.apache.org/jira/browse/AXIS2-2037
> Project: Axis2
> Issue Type: Improvement
> Affects Versions: 1.2
> Reporter: Isuru Eranga Suriarachchi
> Assignee: Thilina Gunarathne
> Fix For: 1.2
>
> Attachments: latest_patch.txt, patch.txt, patch.txt
>
>
> There are 2 major json conventions available as Badgerfish and Mapped. So far
> Axis2 supported only Badgerfish. It is bit inconvenient for the javascript
> users to use Badgerfish formatted json strings. Mapped convention is a good
> solution for this matter. So in this patch I have implemented support for
> Mapped convention as well. Here I have used 2 different JSONBuilders and the
> default one is using Mapped convention.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
