StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18532433
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-08-30T12:00:58.323
FavoriteCount
0
LastActivityDate
2014-12-12T11:09:05.487
LastEditDate
2017-05-23T11:49:52.460
LastEditorUserId
-1
OwnerUserId
157882
ParentId
18528491
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
This is indeed not going to work. Enum properties are initialized only once, applicationwide, while i18n is essentially supposed to be resolved on a per-request basis. You need to redesign your enum as such that only the label keys are hold instead of the resolved localized values. <pre><code>TRUCK("tv.moc.truck", "TRUCK"), AIRFREIGHT("tv.moc.airfreight", "AIRFREIGHT"), TRAIN("tv.moc.train", "TRAIN"), SEAFREIGHT("tv.moc.seafreight", "SEAFREIGHT"), BARGE("tv.moc.barge", "BARGE"); </code></pre> And then provide the enum values as follows in an application scoped bean: <pre><code>@ManagedBean @ApplicationScoped public class Data { public Transportmittel[] getTransportmittels() { return Transportmittel.values(); } } </code></pre> And then reference it in <code><f:selectItems></code> as follows (look, no need for <code>SelectItem</code> boilerplate): <pre class="lang-html prettyprint-override"><code><f:selectItems value="#{data.transportmittels}" var="transportmittel" itemValue="#{transportmittel}" itemLabel="#{bundle[transportmittel.ausgabe]}" /> </code></pre> Or, if you happen to use JSF utility library <a href="http://omnifaces.org" rel="nofollow noreferrer">OmniFaces</a> already, as currently indicated in your user profile, then you could also bypass the whole application scoped <code>Data</code> bean and <a href="http://showcase.omnifaces.org/taghandlers/importConstants" rel="nofollow noreferrer">import</a> it straight in the EL scope as follows: <pre class="lang-html prettyprint-override"><code><o:importConstants type="com.example.Transportmittels" />  ... <f:selectItems value="#{Transportmittels}" var="transportmittel" itemValue="#{transportmittel}" itemLabel="#{bundle[transportmittel.ausgabe]}" /> </code></pre> <h3>See also:</h3> <ul> <li><a href="https://stackoverflow.com/questions/4375578/jsf-best-way-to-enum-internationalization-i18n/4377192#4377192">Localizing enum values in resource bundle</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POenuma label from message bundle
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USBalusC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POenuma label from message bundle
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COAs always, thank you very much, I really appreciate your help.
 singulars
 PostPostId
 PO
 UserUserId
 USleostiw
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.