StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4204355
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-11-17T12:30:26.180
FavoriteCount
0
LastActivityDate
2010-11-17T12:30:26.180
LastEditDate
LastEditorUserId
0
OwnerUserId
139595
ParentId
4186093
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I'm assuing your <code>abf.xsd</code> starts with <pre><code><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.boschafb.com" targetNamespace="http://www.boschafb.com" elementFormDefault="qualified"> </code></pre> With <code>elementFormDefault</code> set to <code>qualified</code>, all element declarations, even nested ones, belong to the specified target namespace. Note that this applies only to elements, a referenced type does not affect the namespace of the element referencing it. A solution would be to define an element instead of a type in 'kts.xsd' and referencing this element in your first schema: <pre><code><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.boschkts.com" targetNamespace="http://www.boschkts.com" elementFormDefault="qualified"> <xs:element name="RESULTS"> <xs:complexType> <xs:sequence> <xs:element name="SUMMARY" type="SUMMARY" minOccurs="0" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.boschafb.com" targetNamespace="http://www.boschafb.com" elementFormDefault="qualified" xmlns:kts="http://www.boschkts.com"> <xs:import namespace="http://www.boschkts.com" schemaLocation="kts.xsd"/> <xs:element name="vehicle"> <xs:complexType> <xs:sequence> <xs:element ref="vType"/> <xs:element ref="kts:RESULT"/> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJAXB generating wrong Namespace
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJörn Horstmann
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COI don't know if this solved the OP's problem, but it worked for me - I had a child element from an imported schema that was taking the parent namespace when it should have retained the imported namespace. Changing from `<element type='childNS:whateverType' />` to `<element ref='childNS:whateverElement' />` worked for me. Thanks!
 singulars
 PostPostId
 PO
 UserUserId
 USthom_nic

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.