There are two ways that xml string can be converted into JSON string, Badgerfish and Mapped . Current Axis2 with JSON module completely supports Badgerfish convention while partialy supports Mapped convention as Mapped formatted JSON with namespaces are not supported in Axis2. Therefore if the client side java-script code needs to talk with java service which is deployed in Axis2, it should be sent as Badgerfish convention. It is cumbersome to generate Badgerfish convention of JSON string again and again to call services if there is no xml representation string in client side.
If java script client can send JSON object to relevant java service in Axis2, defining service and operation in request url, without doing any modifications to JSON objects, then it would be very helpful for Java-Script users at client side.
According to the thread in the mailing list, which discussed $subject we have two approaches. i have summarized those two approaches as below.
1. Store json inputstream in message context at the message builder while putting dummy SOAPEnvelop to the message context, and using google-gson process it inside the message receiver
2. Preserve the requirement that a message must have a well defined SOAP infoset and use a trivial representation similar (or identical) to what we use for plain text. This has the advantage that it is more in line with the rest of the Axis2 architecture,
another option is to write an xmlstream reader/writer implementation to parse the json stream. And provide that xml stream implementation to Axiom.