axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Rheinheimer <>
Subject Re: looking for sample code (simultaneous SOAP, REST and JSON)
Date Tue, 29 Sep 2009 19:25:08 GMT
It sounds like a pure REST implementation is better suited for your needs
than Axis2 with a REST layer on top.  Is that right?  Do you know for sure
that you need some of the underlying Axis2 or webservices technologies?  If
you can give up WSDL and SOAP, why not give a good JAX-RS implementation a
try?  (... and you can still support SOAP with a JAX-RS implementation.  I
suppose it depends how much effort you want to put into it.  Like you said,
it may be quite a bit of work to get REST and JSON working on top of Axis2
along with WSDL tweaks.  With JAX-RS implementations, specifically Apache
Wink, you get REST and JSON "out-of-the-box")

See Apache Wink:

It's still in incubator, but it's getting enough attention that I think it
will be out pretty soon.

On Tue, Sep 29, 2009 at 1:49 PM, John Klassa <> wrote:

> I'm looking for sample code (a complete, working system, even) that
> exemplifies how to support SOAP, REST and JSON inputs and outputs with the
> same underlying business logic...  And at that, I'm looking for "real" REST,
> like the kind described here:
> Seems like Axis2 is set up to do SOAP out of the box, and then also do
> something REST-like without too much trouble.  "Real" REST requires
> WSDL-tweaking that seems unnatural (to me)...  And, JSON seems to require
> even more effort.
> (I base all of this on a couple day's worth of reading everything I can
> find on the subject.  Apologies if this characterization is woefully
> inaccurate.)
> What I'm trying to get a handle on is how realistic it is to attempt to
> write the core logic just once (the part that reads data from a database,
> and writes it back out, for example), and then leverage it to provide SOAP,
> REST and JSON interfaces simultaneously.  And if it's realistic, how hard is
> it -- and how hard is it to maintain, as features/services are added?
> The key, for me, is interoperability -- most of my clients won't be using
> Axis2 on the client side, nor even Java (most likely).  A great many will
> use Javascript (ala AJAX), or perl, or other technologies.  I want to make
> the resulting service offerings as useful and flexible as possible, to
> accommodate as many of my users as possible.  I'm hopeful that Axis2 can
> help.
> Pointers appreciated.
> Thanks!

View raw message