Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Received-SPF: pass (athena.apache.org: domain of amra@us.ibm.com designates
 32.97.182.145 as permitted sender)
In-Reply-To: <ed64f35e0805112350s14bf5bf5ke1fb7391873d304b@mail.gmail.com>
To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
MIME-Version: 1.0
Subject: Axis2/C doc/lit wrapper vs. non-wrapper style 
Message-ID: 
 <OF76A40D6A.5DFB0848-ON8625744C.0007C0B5-8625744C.0008A9FC@us.ibm.com>
From: Nadir Amra <amra@us.ibm.com>
Date: Fri, 16 May 2008 20:33:34 -0500
Content-Type: text/plain; charset="US-ASCII"

How does axis2/C handle document/literal wrapped vs. unwrapped?  Does it 
support it?  What is the default?  When I generate client stubs it seems 
it is always the case that  the following is generated:

adb_phoneStatusResponse_t* 
            axis2_stub_op_IPTelephonyService_phoneStatusRequest( 
axis2_stub_t *stub, 
                                                                 const 
axutil_env_t *env,
 adb_phoneStatusRequest_t* _phoneStatusRequest);

Even if I specify -uw

So I am curious about the following:

(1) When is wrapped vs. unwrapped used?

(2) Is there actually a difference in SOAP request between the two?  From 
my readings it seems that this is more of a programming interface aspect 
than anything else - that is, whether the child elements of the wrapper 
element are listed as parameters or whether a structure is used. 

Thanks in advance.

Nadir Amra


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org