StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9087074
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2012-01-31T21:16:22.583
FavoriteCount
0
LastActivityDate
2017-09-07T19:01:41.753
LastEditDate
2017-09-07T19:01:41.753
LastEditorUserId
8239277
OwnerUserId
392730
ParentId
4873429
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
<p>JAXB always adds all namespaces that are known by the JAXBContext to the root element of the XML document for performance reasons. See this comment by Kohsuke on <a href="https://github.com/javaee/jaxb-v2/issues/103#issuecomment-296633602" rel="nofollow noreferrer">JAXB-103</a> for more information.</p> <p>The only way I found to deal with this, is to traverse the document myself after it has been created with JAXB and remove all unused namespaces using the following helper class:</p> <pre><code>public class RemoveUnusedNamespaces { private static final String XML_NAMESPACE_SCHEMA_INSTANCE = "http://www.w3.org/2001/XMLSchema-instance"; private static final String XML_NAMESPACE_NAMESPACE = "http://www.w3.org/2000/xmlns/"; private interface ElementVisitor { void visit(Element element); } public void process(Document document) { final Set<String> namespaces = new HashSet<String>(); Element element = document.getDocumentElement(); traverse(element, new ElementVisitor() { public void visit(Element element) { String namespace = element.getNamespaceURI(); if (namespace == null) namespace = ""; namespaces.add(namespace); NamedNodeMap attributes = element.getAttributes(); for (int i = 0; i < attributes.getLength(); i++) { Node node = attributes.item(i); if (XML_NAMESPACE_NAMESPACE.equals(node.getNamespaceURI())) continue; String prefix; if (XML_NAMESPACE_SCHEMA_INSTANCE.equals(node.getNamespaceURI())) { if ("type".equals(node.getLocalName())) { String value = node.getNodeValue(); if (value.contains(":")) prefix = value.substring(0, value.indexOf(":")); else prefix = null; } else { continue; } } else { prefix = node.getPrefix(); } namespace = element.lookupNamespaceURI(prefix); if (namespace == null) namespace = ""; namespaces.add(namespace); } } }); traverse(element, new ElementVisitor() { public void visit(Element element) { Set<String> removeLocalNames = new HashSet<String>(); NamedNodeMap attributes = element.getAttributes(); for (int i = 0; i < attributes.getLength(); i++) { Node node = attributes.item(i); if (!XML_NAMESPACE_NAMESPACE.equals(node.getNamespaceURI())) continue; if (namespaces.contains(node.getNodeValue())) continue; removeLocalNames.add(node.getLocalName()); } for (String localName : removeLocalNames) element.removeAttributeNS(XML_NAMESPACE_NAMESPACE, localName); } }); } private final void traverse(Element element, ElementVisitor visitor) { visitor.visit(element); NodeList children = element.getChildNodes(); for (int i = 0; i < children.getLength(); i++) { Node node = children.item(i); if (node.getNodeType() != Node.ELEMENT_NODE) continue; traverse((Element) node, visitor); } } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POControlling namespace prefixes in JAXB
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USReboot
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. 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.