StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18344156
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-20T20:11:52.227
FavoriteCount
0
LastActivityDate
2013-08-20T20:11:52.227
LastEditDate
LastEditorUserId
0
OwnerUserId
1238957
ParentId
5324051
PostTypeId
2
Score
16
ViewCount
0
LastEditorDisplayName
text
Body
<a href="http://www.coderanch.com/t/501314/Web-Services/java/Simple-Unwrapped-Wrapped-SOAP-messages" rel="noreferrer">This discussion</a> at Java Ranch Forum cleared it for me. Specifically this example made by Jason Irwin: BARE client generated interface (using wsimport): <pre><code>@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE) public interface IMathServer { @WebMethod @WebResult(name = "addNumsResponse") public AddNumsResponse addNums(@WebParam(name = "addNums") AddNums parameters); } </code></pre> WRAPPED client generated interface (using wsimport): <pre><code>@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.WRAPPED) public interface IMathServer { @WebMethod @WebResult(name = "addNumsResponse") public int addNums(@WebParam(name = "num1") int num1, @WebParam(name = "num2") int num2); } </code></pre> This both pieces of code generate the same message: <pre><code><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Body> <ns2:addNums xmlns:ns2="http://SoapStyles/"> <num1>1</num1> <num2>2</num2> </ns2:addNums> </S:Body> </S:Envelope> </code></pre> As said by R Srini in the same discussion what is wrapped are the parameters, not the code. The only difference generating the clients is the way you are going to create the params in the client, but they both are going to generate the same message (wrapped or unwrapped) depending on the service WSDL. With BARE you will have only a top element (parameter) with "sub-parameters" inside. This one BARE will be sent directly (without "wrapping" it). While with WRAPPED you will have all this "sub-parameters" in the first level, and the client automatically wrap them in another top element. Quoting Jason Irwin: <blockquote> Only one parameter was passed ("addNums") and it was "Bare" in the body. In the second, the parameters were "bare" in the code, but "wrapped" at run-time by JAX-WS. </blockquote> Hope this helps!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWebServices : bare vs wrapped?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USChristian Vielma
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.