WS-PAPI client communication (SOAP)

Question

I'm writing a web service (it's Global Activity) in ALBPM and I have a little question about SOAP encapsulation. When other app calls my web service, I do something inside my web service, and the result of web service is some xml created by me, for simplicity assume it looks like this:
<output>
<arg1>aaa</arg1>
<arg2>bbb</arg2>
</output>
But what should I do, when I have to use SOAP? Should I manually add soap envelope&body parts and everything needed to my output xml? Or my output xml will be automatically wrapped to SOAP message by WS-PAPI before sending to client, and I don't have to care about SOAP? Because I read in documentation of WS-PAPI:
The client application connected to PAPI Web Service, uses SOAP (Simple Object Access
Protocol) over HTTP to invoke any of the functions listed in the WSDL. PAPI Web Service relies on
PAPI to obtain the information the client requests. Then it translates this information into
XML and uses SOAP to send it back to the client.
PAPI Web Service implementation is based on the following:
+ JAX-WS 2.0 web service+
+ WS-I 1.1 compliant+
+ Document/literal wrapped style WSDL SOAP binding+
Anybody with concrete experiences? Thanx for answering

Answer 1

I have exactly the same problem.
how you solved this issue?