StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19713902
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-31T18:20:50.907
FavoriteCount
0
LastActivityDate
2013-10-31T19:18:26.920
LastEditDate
2013-10-31T19:18:26.920
LastEditorUserId
1883511
OwnerUserId
1883511
ParentId
19695644
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
After checking the source code the problem is related to outcome: the com.sun.faces.flow.FlowHandlerImpl.getFlow method need Id to be not null: <pre><code>public Flow getFlow(FacesContext context, String definingDocumentId, String id) { Util.notNull("context", context); Util.notNull("definingDocumentId", definingDocumentId); Util.notNull("id", id); </code></pre> The com.sun.faces.application.NavigationHandlerImpl: <pre><code>result.isFlowEntryFromExplicitRule = null != fh.getFlow(ctx, toFlowDocumentId, outcome); </code></pre> So the outcome is null and exception is rised. In my case I don't have outcome. If is needed from-outcome then in some place has to be ejecuted an action. To accomplish that the login.xhtml page need a f:viewAction. Implementing all this now my the requested use case is working well. If from-action is declared then the from-outcome is optional and vice versa. If the same logic of redirection is required when user go to root folder (domain/appname/) the only thing that has to be done is to add welcome-file to web.xml. <pre><code><welcome-file>login.jsf</welcome-file> </code></pre> Finally this is the navigation rule declaration <pre><code><navigation-rule> <from-view-id>/login.xhtml</from-view-id> <navigation-case>  <from-outcome>logged</from-outcome> <if>#{identity.loggedIn}</if> <to-view-id>/home.xhtml</to-view-id> <redirect /> </navigation-case> </navigation-rule> </code></pre> And this has to be added to login.xhtml <pre><code><f:metadata> <f:viewParam name="x" value="#{bean.x}"/> <f:viewAction action="#{bean.loggedInNavigationRuleAction}" phase="APPLY_REQUEST_VALUES"/> </f:metadata> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJSF 2 Navigation Rule redirect to home page if user is logged
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTvori
UserOwnerUserId
1. USTvori
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POJSF 2 Navigation Rule redirect to home page if user is logged
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.