Create SOAP Layer for Legacy Java System

I have a legacy system that uses Java RMI calls to Remote Interfaces implemented by Stateless Session Beans. There are 14 interfaces with around 34 value classes used by the interfaces. I want a "plug-in" SOAP layer that can be plugged in with minimal effort. To achieve this, the developer must create a SOAP service project that can be used in Eclipse and deployed in JBoss. The developer must also create the client side wrappers. All coding must be done in Java and use Java's standards such as JAX-WS, JEE, etc. It's important that the client side uses the exact interfaces I provide. The SOAP service must also delegate it's calls to classes implementing the exact interfaces I provide. To prove the wrapping, the developer must create client side test classes, that call the client side wrappers. The client side test classes MUST use the provided interfaces and value classes to prove that the soap wrappers are a drop in replacement. On the server side the SOAP service must call test classes created by the developer. The Test classes must implement the provided interfaces. This proves that the SOAP class can translate to the provided interface and that the data sent from the client was transported and translated correctly. The client and server test classes must create complete dummy data that tests all the attributes sent. The test classes must also test that the data was sent and translated completely. The project is deemed complete if all the tests pass. I understand that sometimes an existing interface with all it's value classes cannot be exactly implemented in SOAP and that the SOAP structure must look somewhat different. That's why I want a Delegate layer on the client side. The delegate layer will translate between my interfaces, and the SOAP interfaces. The SOAP service on the server side will translate between my interfaces and the SOAP interfaces on the server side. To test this translation and transport process, the client and server test classes may only make use of the provided interfaces. This will prove that the delegate layers does the job of translation and sending via SOAP correctly. See the attachment for a complete requirements doc and the eclipse project that includes the interfaces and value classes that must be wrapped. I expect as output: 1. A client side project (the one provided can be used and filled up) with the client side wrappers and delegates. 2. A server side JEE project that makes use of JAX-WS and can be deployed in something like JBoss. Developers must make use of annotations rather than config files where possible. Code must be commented. The test, delegate and service classes must be separated so that one of each is created for each interface. I don't want all the wrappers and delegates in one huge class. Please tell me how many individual methods you expect to wrap (the count of the methods in all the interfaces). This will convince me that you understand the scope of work. Bids without this information, will be automatically rejected. I will only communicate through the Freelancer site until the project is awarded. Once the project is awarded and commences, we can communicate through instant message if needed.