I have done exactally that today, to develop a SOAP x REST benchmark. I talk about it at
RESTlet slower than Axis2.
Jackson + RESTlet + RESTlet built-in HTTP client had really really bad results, both in stability and performance, compared to Axis2 and its built-in XML marshaller and HTTP client. Basically, Axis2 has all we need and can make dozens of thousands of sequential calls with ease and have 3-5 milisecs overhead on each, while Jackson + RESTlet + RESTlet built-in HTTP client timeout hangs after a couple hundred calls and have 4-6 milisecs overhead on each. With stability issues and worse performance, it's hard to advocate for REST, and with a few milisecs of overhead, Axis2 is very lightweigth for the features and flexibility it provides.
To do what you want, using Axis2, RESTlet and a unique Eclipse project, basically:
1) Create Axis2 WebService as normal, using Eclipse for automating it
2) Manually create RESTlet ServerResource, as Eclipse has no automation features (RESTlet seems to have an Eclipse plugin, but I was unable to install it and didn't need at all)
3) When routing URLs in RESTlet Resource, be careful to not use Axis2 paths
4) Together with Axis2 and RESTlet you can also develop traditional
Servlets, just when creating them in Eclipse be careful to not conflict their paths with Axis2 and RESTlet ones
5) In WEB-INF/web.xml you'll need to bind RESTlet routes manually, tomorrow I can post an example of it, it's not hard
6) Export war file normally from Eclipse project, it will have (1), (2) and (4) all together
7) Deploy war file in
Tomcat and
test all URL paths you have created, testing their parameters and responses
8) Run many tests with thousands of calls in your RESTlet client, I had A LOT of issues in it!!
..
