On Thu, Dec 29, 2011 at 15:55, Amila Suriarachchi
> On Tue, Dec 27, 2011 at 7:58 PM, Andreas Veithen <firstname.lastname@example.org
>> On Sun, Dec 25, 2011 at 15:09, Shameera Rathnayaka
>> > 2. store json string without doing any process untill it reaches
>> > JsonMessageReceiver. JsonMessageReceiver is a new Message Receiver which
>> > use
>> > gson to convert json to java objects, call relevant operation and get
>> > result.
>> What this means in practice is that you will have a message builder, a
>> message receiver and a message formatter that interact with each
>> other, but that have no meaningful interaction with any other
>> component of the Axis2 framework (the fundamental reason being that
>> google-gson defines a mapping between JSON and Java objects, but
>> eliminates XML from the picture). The question is then why would a
>> user go through all the pain of setting up Axis2 for this?
> if you look into a point where users only need to expose a POJO with json
> then they don't have to use Axis2.
> But if the user want to expose the same POJO service both soap and json
> formats this provides a value in terms of performance for latter case. In
> this case JSON message receiver can be written extending RPC message
> receiver and call the normal RPC processing if the received message is not a
> json one.