StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8218434
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-11-21T20:56:36.623
FavoriteCount
0
LastActivityDate
2011-11-21T21:03:38.300
LastEditDate
2011-11-21T21:03:38.300
LastEditorUserId
157882
OwnerUserId
157882
ParentId
8190207
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> Why is Realm setting required in Server.xml and not web.xml </blockquote> This is not true, you can define it in your webapp as well, but then only in a servletcontainer-specific configuration file, such as <code>/META-INF/context.xml</code> in case of Tomcat. It cannot be definied in <code>/WEB-INF/web.xml</code> because it's specific to the standard Servlet API, not the servletcontainer implementation. <hr> <blockquote> But wouldn't that apply to all web application deployed on that server since it would become a server level configuration ?. </blockquote> That's correct. This is not recommended if you have no control over the server or if you don't want to publish the realm through other webapps. <hr> <blockquote> On a site I even saw a developer mentioning about context.xml but again can't see a standard document that mention about using this XML file for setting JDBC realm </blockquote> You can specify it in webapp's <code>/META-INF/context.xml</code>. See also <a href="http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Defining_a_context" rel="nofollow">Tomcat's own documentation on the <code><Context></code> element</a>: <blockquote> <h2>Defining a context</h2> It is NOT recommended to place <code><Context></code> elements directly in the <code>server.xml</code> file. This is because it makes modifying the Context configuration more invasive since the main <code>conf/server.xml</code> file cannot be reloaded without restarting Tomcat. Individual Context elements may be explicitly defined: <ul> <li>In an individual file at <code>/META-INF/context.xml</code> inside the application files. Optionally (based on the Host's copyXML attribute) this may be copied to <code>$CATALINA_BASE/conf/[enginename]/[hostname]/</code> and renamed to application's base file name plus a ".xml" extension.</li> <li>In individual files (with a ".xml" extension) in the <code>$CATALINA_BASE/conf/[enginename]/[hostname]/</code> directory. The context path and version will be derived from the base name of the file (the file name less the .xml extension). This file will always take precedence over any context.xml file packaged in the web application's META-INF directory.</li> <li>Inside a <a href="http://tomcat.apache.org/tomcat-7.0-doc/config/host.html" rel="nofollow">Host</a> element in the main <code>conf/server.xml</code>.</li> </ul> </blockquote> (emphasis is not mine, it is already as such in Tomcat's documentation)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy is Realm setting required in Server.xml and not web.xml
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBalusC
UserOwnerUserId
1. USBalusC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy is Realm setting required in Server.xml and not web.xml
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks for the information. This really helps
 singulars
 PostPostId
 PO
 UserUserId
 USKunal Uppal
2. COYou're welcome.
 singulars
 PostPostId
 PO
 UserUserId
 USBalusC

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.