On Tue, Dec 27, 2011 at 7:58 PM, Andreas Veithen
<andreas.veit...@gmail.com>wrote:

> On Sun, Dec 25, 2011 at 15:09, Shameera Rathnayaka
> <shameerai...@gmail.com> wrote:
> > 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?
>

According to the user perspective, if user has a xml representation of json
object then user can convert it to json with Badgerfish convetion and send
it to Axis2. But if user doesn't have such xml representation then he needs
to generate Badgerfish convention of Json object. If Axis2 support normal
json object then it would be easy to users to communicate without using
Badgerfish convention.

And there is no point of converting json to xml in middle as both are used
for same purpose. and also Json is
a light-weighted data exchangeable format so it would be great if axis2
supports fully Json too as it support xml.

JSON string is processed inside the JsonMessageReceiver. All dispatching
things happen url based. Therefore Axis2 engine can identify service ,
operation etc.. without processing incoming json string.



>
> Andreas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-dev-h...@axis.apache.org
>
>


-- 
Shameera Rathnayaka
Undergraduate
Department of Computer Science and Engineering
University of Moratuwa.
Sri Lanka.

Blog : http://shameerarathnayaka.blogspot.com/

Reply via email to