StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3617901
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-09-01T12:20:08.140
FavoriteCount
0
LastActivityDate
2010-09-01T12:20:08.140
LastEditDate
LastEditorUserId
0
OwnerUserId
358776
ParentId
3470565
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I eventually decided to use the 'xmlbeans' data binding format for the Outputted Generated Java classes representing the WSDL operations. It seems that the Axis2 data binding (ADB) does not handle WSDL with multiple Complex Types ( which are, when translated to Java code, return Java Objects) especially if they are configured with XMLSchema attributes <code>maxOccurs='unbounded'</code> . When the output is generated when using ADB it seems that a separate Object_x ( where x is an integer ranging from 1..n) is created for every Complex Type called Object which would require different properties depending on the Operation requirements as defined in the WSDL document. The Object_x would be placed in the same package as the other objects generated by wsdl2java. The sent SOAP request then contains a <code>type=Object_x</code> XSD Attribute accompanying the translation of the Object to the SOAP request as shown in the initial question. When the output is generated when using xmlbeans, a package.Object class is generated by wsdl2java where the package is the name of the Operation while the Object is the Complex type and it seems that xmlbeans disregards the <code>maxOccurs='unbounded'</code> attribute and the sent SOAP request does not have any type paramters placed in it. Well this was how I solved this problem. I have sent in a bug report to the Axis2 development team but I will keep following it up to see if there are any resolutions in future versions. Thanks to all who tried.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWSDL-Axis2 CodeGen Problem
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USKris Ogirri
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. This table or related slice is empty.
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.