StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11511954
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-16T20:23:22.667
FavoriteCount
0
LastActivityDate
2015-06-11T07:48:39.490
LastEditDate
2015-06-11T07:48:39.490
LastEditorUserId
157882
OwnerUserId
149872
ParentId
10618123
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Instead of injecting the Spring beans via EL in a <code>@ManagedProperty</code> annotation (executed on the ManagedBean initialization), obtain the beans evaluating the EL at runtime. With this approach, this is what the JSF beans should look like: <pre><code>@ManagedBean @ViewScoped public class SomeMB implements Serializable { private static final long serialVersionUID = 1L; private static SomeService someService() { return SpringJSFUtil.getBean("someService"); } // ... </code></pre> And the utility class SpringJSFUtil.java that gets the bean via EL: <pre><code>import javax.faces.context.FacesContext; public class SpringJSFUtil { public static <T> T getBean(String beanName) { if (beanName == null) { return null; } return getValue("#{" + beanName + "}"); } @SuppressWarnings("unchecked") private static <T> T getValue(String expression) { FacesContext context = FacesContext.getCurrentInstance(); return (T) context.getApplication().evaluateExpressionGet(context, expression, Object.class); } } </code></pre> This eliminates the Spring bean property (at the cost of doing a few more EL evaluations), thus avoiding all the serialization issues of having the property in first place. The same approach, using <a href="http://omnifaces.org" rel="nofollow">OmniFaces</a>: In my actual code, I use the <code>evaluateExpressionGet(String expression)</code> method of an <a href="http://showcase.omnifaces.org/utils/Faces" rel="nofollow">utility class</a> available from <a href="http://omnifaces.org" rel="nofollow">OmniFaces</a>. So, for those of you who use it too, this is what my code really look like: <pre><code>import static org.omnifaces.util.Faces.evaluateExpressionGet; @ManagedBean @ViewScoped public class SomeMB implements Serializable { private static final long serialVersionUID = 1L; private static SomeService someService() { return evaluateExpressionGet("#{someService}"); } // ... </code></pre> Notice that here the method gets the full EL ("#{expression}"), not just the Spring bean name (or you would get a ClassCastException).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to re-inject a transient @ManagedProperty at deserializing?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBalusC
UserOwnerUserId
1. USelias
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to re-inject a transient @ManagedProperty at deserializing?
 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
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.