StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5135729
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-02-27T20:30:04.167
FavoriteCount
0
LastActivityDate
2011-02-27T20:30:04.167
LastEditDate
LastEditorUserId
0
OwnerUserId
480431
ParentId
5105031
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The reason is probably that the request goes through the SeamFilter, as you supposed. I think it's not the SeamFilter itself that buffer the data stream from your servlet but the Ajax4Jsf filter that is invoked in the filter chain. If you have RichFaces in the classpath there is a seam component that registers the Ajax4jsf filter in the chain. Namely, the Seam component is <code>org.jboss.seam.web.ajax4jsfFilter</code>. If you don't need RichFaces try removing it from the classpath. If you need it, I suggest that you override <code>org.jboss.seam.web.ajax4jsfFilter</code> in order to skip the Ajax4Jsf filter for requests directed to your servlet. Another possible solution is converting your servlet in a filter as a Seam component (see @Filter annotation) and positioning it at the beginning of the chain with the around attribute. Something like: <pre><code>@Name("FormerServlet") @Scope(STATELESS) @BypassInterceptors @Filter(around = "org.jboss.seam.web.ajax4jsfFilterInstantiator") public class FormerServletFilter implements Filter { protected void init(FilterConfig filterConfig) throws Exception { } protected void doDestroy() { } /** * Performs the filtering for a request. */ protected void doFilter(final HttpServletRequest request, final HttpServletResponse response, final FilterChain chain) throws Exception { if (thisRequestShoudBeManagedByMyServlet(request) ) { // do here what you previously did in the servlet } else { // go ahead with the Seam lifecycle chain.doFilter(request, response); } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSeam and ServletOutputStream - flush is not immediately visible
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USStefano Travelli
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSeam and ServletOutputStream - flush is not immediately visible
 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
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COIt works! Thanks a lot!
 singulars
 PostPostId
 PO
 UserUserId
 USGuus

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.