StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10929150
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-06-07T09:29:15.647
FavoriteCount
0
LastActivityDate
2012-06-07T09:29:15.647
LastEditDate
LastEditorUserId
0
OwnerUserId
750040
ParentId
10928362
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
May be this is oversimplification, A web server is basically a HTTP server serving contents over http protocol. So a web server is simply about serving the contents over http protocol. A typical example would be <a href="http://httpd.apache.org/" rel="nofollow">Apache web server</a>. This is simply a file server. Now the question is where does the web server gets the contents from ? Possible sources are <ol> <li>Static contents (the contents like images/css etc) which are not generated on request but statically served. </li> <li>Dynamic contents: Simply put, the contents to be served are generated upon the user request. </li> </ol> For the static contents, the web server does not need anything as it simply reads the file and serves it. For dynamic contents, the web server might need help of additional components which will generate the contents to be served. Here the Application Server comes into picture. Now these additional components referred earlier, might interact with database or some other system etc. In a web environment where your website is exposed to huge number of users (intended/unintended), you need typical services like transaction/security/concurrency etc. so that the user get expected responses and do not see inconsistencies in the behavior of the application. An application server has inbuilt abilities to manage transaction/security/concurrency/resource management. generally these are referred as Managed services and environment offered by them is called Managed Environment where these basic services are managed by the application server and programmer does not have be bother for them. Application Server needs web servers or we can say Web servers use Application server's services to generate dynamic contents. For example, JBoss uses Tomcat as inbuilt web server. Whereas web logic has its own web server. Tomcat again can be called as application server (in principle) as it also offers managed environment for servlets (it manages concurrency and instance pool of servlets/JSPs ). Coming your your example of Spring: An Application server will come inbuilt with transaction/security etc whether you need it or not. The Spring offers a very nice way handling this. Spring has all these things BUT you use what you need. Not just these, but just a Java Web Sever like Tomcat is sufficient to build a full fledged services that needs an application server. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat are the specific uses of Java Application Server that cannot be done with web servers?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSantosh
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. CO(+1) for your last 3 paragraphs...
 singulars
 PostPostId
 PO
 UserUserId
 USmukund

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.