StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POJSF2 EL not displayed in components IDs
primarykey
Id
9374151
data
AcceptedAnswerId
9394583
AnswerCount
4
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-21T08:12:34.097
FavoriteCount
0
LastActivityDate
2012-02-22T12:19:24.407
LastEditDate
2012-02-21T09:11:06.757
LastEditorUserId
1080129
OwnerUserId
1080129
ParentId
0
PostTypeId
1
Score
4
ViewCount
976
LastEditorDisplayName
text
Body
I have the following piece of code: <pre><code><ui:repeat var = "ctr" value = "#{bean.counterList}"> <h:outputLabel for = "message#{ctr}" value = "#{appMessage['No #{ctr} :" /> <h:inputText id="message#{ctr}" value="#{bean.messageList}" /> </ui:repeat> </code></pre> The <code>counterList</code> is an <code>List<String></code>. If the list contains <code>1, 2, 3</code> on the view thee should be 3 input fields with the ids : <code>message1, message2, message3</code>. The EL has no effect in the id attribute and all the components receive just message as an ID. On the other hand, in the label's value, the EL works great. I can imagine that this may be the desired behaviour but is there a workaround? UPDATE: I removed the <code>id</code> attribute and the <code>ui:repeat</code> is in charge of naming the id's now. From the source code I can see that the ID's generated are unique but now this warning is thrown: <pre><code>INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed. sourceId=fm-story:j_idt103:0:j_idt54[severity=(ERROR 2), summary=(Conversion Error setting value '' for 'null Converter'.), detail=(Conversion Error setting value '' for 'null Converter'.)] sourceId=fm-story:j_idt103:1:j_idt54[severity=(ERROR 2), summary=(Conversion Error setting value '' for 'null Converter'.), detail=(Conversion Error setting value '' for 'null Converter'.)] </code></pre>
Tags
<java><jsf>
Title
JSF2 EL not displayed in components IDs
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USIonut
UserOwnerUserId
1. USIonut
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
3. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POJSF2 EL not displayed in components IDs
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POJSF2 EL not displayed in components IDs
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POJSF2 EL not displayed in components IDs
 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.