StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14856071
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-13T14:43:28.367
FavoriteCount
0
LastActivityDate
2013-02-14T01:32:12.467
LastEditDate
2013-02-14T01:32:12.467
LastEditorUserId
1736425
OwnerUserId
1736425
ParentId
4987922
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I know it's been a while, but thought to share this alternate solution for the benefit of others. For composites, create a backing component with a getter, then iterate over the faces messages and call remove() after collecting each message. This will get you around the "messages queued" warning without the h:messages hack. xhtml: <pre><code><composite:interface displayName="Messages Component" shortDescription="Messages Component" componentType="com.company.dept.commons.ui.messages.Messages"> <composite:attribute name="styleClass" default="" type="java.lang.String" shortDescription="CSS style class for the component" /> </composite:interface> <composite:implementation> <div id="messagesComponent" class="#{cc.attrs.styleClass}"> <ui:repeat value="#{cc.messageList}" var="message"> #{message.severity} - #{message.detail} </ui:repeat> </div> </composite:implementation> </code></pre> Backing component: <pre><code>@FacesComponent("com.company.dept.commons.ui.messages.Messages") public class Messages extends UINamingContainer { private List<FacesMessage> messages; public List<FacesMessage> getMessageList() { //preserve messages in case getter is called multiple times if (messages == null) { messages = new ArrayList<FacesMessage>(); } Iterator<FacesMessage> messageItr = getFacesContext().getMessages(); while(messageItr.hasNext()) { FacesMessage message = messageItr.next(); messages.add(message); messageItr.remove(); } return messages; } } </code></pre> Note the componentType in the xhtml is set to the FacesComponent value in the code. Also, the reference to cc.messageList will trigger the call to getMessageList(). Hope this helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJSF 2.0 custom messages
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAli Cheaito
UserOwnerUserId
1. USAli Cheaito
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. 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.