StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9132509
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-03T17:06:48.427
FavoriteCount
0
LastActivityDate
2012-02-03T17:06:48.427
LastEditDate
LastEditorUserId
0
OwnerUserId
834135
ParentId
7307348
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I think you may be having a similar problem as I did. But, I'm not totally sure, so this is just a guess at an answer. I found that a binding file that did some class customization fixed my issue with elements and complexTypes that had matching names across multiple schemas that were referenced in a singular wsdl file just like you have in your example above. In XSD=1 you have <pre><code><xs:complexType="getId"> and <xs:element name="getId" ...> </code></pre> And, in XSD=2 you have <pre><code><xs:element name="getId" ...> </code></pre> So, to fix this I used something like this in my binding file... <pre><code><jxb:bindings version="2.0" xmlns:jxb="http://java.sun.com/xml/ns/jaxb" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <jxb:bindings schemaLocation="http://192.168.178.105:7001/BWebService/AWebService?xsd=1" node="//xs:element[@name='getId']"> <jxb:class name="getIdElement"></jxb:class> </jxb:bindings> </jxb:bindings> </code></pre> This solved my issue of having the same name for a complexType and an element. Since you have the same name for multiple elements in two xsd files with different namespaces, I'm not even sure if this will help that problem. There's a lot more info about possible collision problems and their solutions here... <a href="http://goo.gl/vlQe3" rel="nofollow">http://goo.gl/vlQe3</a> Good Luck, TW
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJava EE Web services: Naming conflict
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStwindham
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.