PrimeFaces commandButton doesn't navigate or update
up vote
38
down vote
favorite
I'am using Primefaces to make my app a little bit more beautiful. I noticed that p:commandButton
and h:commandButton
don't work the same way.
The p:commandButton
calls the method and nothing else hapens. The h:commandButton
calls the method and returns a navigation.
I have got trouble with redirecting after pressing the login button when using p:commandButton
. How to deal with that?
I do have an update parameter:
<p:commandButton value="Login" action="#{login.login}" type="submit" update="msgs" />
jsf jsf-2 primefaces
add a comment |
up vote
38
down vote
favorite
I'am using Primefaces to make my app a little bit more beautiful. I noticed that p:commandButton
and h:commandButton
don't work the same way.
The p:commandButton
calls the method and nothing else hapens. The h:commandButton
calls the method and returns a navigation.
I have got trouble with redirecting after pressing the login button when using p:commandButton
. How to deal with that?
I do have an update parameter:
<p:commandButton value="Login" action="#{login.login}" type="submit" update="msgs" />
jsf jsf-2 primefaces
add a comment |
up vote
38
down vote
favorite
up vote
38
down vote
favorite
I'am using Primefaces to make my app a little bit more beautiful. I noticed that p:commandButton
and h:commandButton
don't work the same way.
The p:commandButton
calls the method and nothing else hapens. The h:commandButton
calls the method and returns a navigation.
I have got trouble with redirecting after pressing the login button when using p:commandButton
. How to deal with that?
I do have an update parameter:
<p:commandButton value="Login" action="#{login.login}" type="submit" update="msgs" />
jsf jsf-2 primefaces
I'am using Primefaces to make my app a little bit more beautiful. I noticed that p:commandButton
and h:commandButton
don't work the same way.
The p:commandButton
calls the method and nothing else hapens. The h:commandButton
calls the method and returns a navigation.
I have got trouble with redirecting after pressing the login button when using p:commandButton
. How to deal with that?
I do have an update parameter:
<p:commandButton value="Login" action="#{login.login}" type="submit" update="msgs" />
jsf jsf-2 primefaces
jsf jsf-2 primefaces
edited Jan 9 '11 at 13:39
BalusC
835k29430993184
835k29430993184
asked Jan 9 '11 at 12:56
Sven
3,0021960107
3,0021960107
add a comment |
add a comment |
6 Answers
6
active
oldest
votes
up vote
51
down vote
accepted
<p:commandButton>
needs one of the following to work correctly:
- the
update
attribute to list id's of components to re-render (for AJAX requests) - the attribute
ajax="false"
to make a normal, non-ajax submit.
If you have neither, the button does per default an AJAX request with no UI feedback.
Additionally, I've had problems with neither option working when the surrounding <h:form>
had an enctype
attribute.
I do have an update parameter. See updated question
– Sven
Jan 9 '11 at 13:23
1
You wantajax="false"
if you want to have a synchronous request with a navigation. As to theupdate
parameter, see my comment in one of your previous questions which you didn't respond to yet.
– BalusC
Jan 9 '11 at 13:39
Sry, just forgot about that -.-
– Sven
Jan 9 '11 at 13:56
As to theenctype="multipart/form-data"
issue, for that you need to ensure that you've configured the PrimeFacesFileUploadFilter
as per the instructions in their User Guide.
– BalusC
Jan 26 '11 at 19:42
@BalusC: Ah, and now I know where thatenctype
came from - the file upload turned out to be unnecessary, but the attribute stayed around to mess up things... Thanks!
– Michael Borgwardt
Jan 26 '11 at 21:11
add a comment |
up vote
31
down vote
I think what Cagatay ment was:
Does not navigate the page:
<p:commandButton action="home.xhtml" value="Go Home"/>
Works (redirects the page):
<p:commandButton action="home.xhtml?faces-redirect=true" value="Go Home"/>
Works (redirects the page)
<p:commandButton action="home?faces-redirect=true" value="Go Home"/>
if .xhtml is your default postfix defined in web.xml:
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
More info can be found in the primefaces forum, for example in this discussion about navigation
I hope that helped a bit...
Nice conclusion!
– Sven
May 5 '11 at 9:24
add a comment |
up vote
8
down vote
You must use redirect if you are doing navigation and request is done with ajax.
add a comment |
up vote
4
down vote
I am having a similar problem.
I am using primefaces and primefaces mobile and the navigation fails in Firefox when using
<p:commandButton>
with ajax="false" and action="find.xhtml?faces-redirect=true".
The only way I could make it work also in Firefox was by using <h:commandButton>
:
<h:commandButton value="#{msg.find}" process="find"
action="find.xhtml?faces-redirect=true" />
add a comment |
up vote
-1
down vote
none of the above solution worked for me.
You can still go for simple javascript
<p:commandButton onclick="window.location.href =home.xhtml"
style="height: 20px" type="button" title="title" icon="ui-icon-transferthick-e-w"/>
add a comment |
up vote
-1
down vote
<h:commandButton
styleClass="btn btn-primary-active upgrade" data-dismiss="modal"
value="Upgrade Account"
action="profile.do?faces-redirect=true&tab=plan"
oncomplete="$('#freeGiftModal').hide();" process="@this" partialSubmit="true" immediate="true"/>
I used the commandbutton to navigate to profile page, and its working fine for me.
Your answer isffectively not different from others and in a way it is worse. Besides it not beimg ap:commandButton
, which with the right attributes 'just works' it containsttributes that are not valid for anh:commandButton
, mor that one of the other answers
– Kukeltje
Nov 11 at 8:14
add a comment |
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
51
down vote
accepted
<p:commandButton>
needs one of the following to work correctly:
- the
update
attribute to list id's of components to re-render (for AJAX requests) - the attribute
ajax="false"
to make a normal, non-ajax submit.
If you have neither, the button does per default an AJAX request with no UI feedback.
Additionally, I've had problems with neither option working when the surrounding <h:form>
had an enctype
attribute.
I do have an update parameter. See updated question
– Sven
Jan 9 '11 at 13:23
1
You wantajax="false"
if you want to have a synchronous request with a navigation. As to theupdate
parameter, see my comment in one of your previous questions which you didn't respond to yet.
– BalusC
Jan 9 '11 at 13:39
Sry, just forgot about that -.-
– Sven
Jan 9 '11 at 13:56
As to theenctype="multipart/form-data"
issue, for that you need to ensure that you've configured the PrimeFacesFileUploadFilter
as per the instructions in their User Guide.
– BalusC
Jan 26 '11 at 19:42
@BalusC: Ah, and now I know where thatenctype
came from - the file upload turned out to be unnecessary, but the attribute stayed around to mess up things... Thanks!
– Michael Borgwardt
Jan 26 '11 at 21:11
add a comment |
up vote
51
down vote
accepted
<p:commandButton>
needs one of the following to work correctly:
- the
update
attribute to list id's of components to re-render (for AJAX requests) - the attribute
ajax="false"
to make a normal, non-ajax submit.
If you have neither, the button does per default an AJAX request with no UI feedback.
Additionally, I've had problems with neither option working when the surrounding <h:form>
had an enctype
attribute.
I do have an update parameter. See updated question
– Sven
Jan 9 '11 at 13:23
1
You wantajax="false"
if you want to have a synchronous request with a navigation. As to theupdate
parameter, see my comment in one of your previous questions which you didn't respond to yet.
– BalusC
Jan 9 '11 at 13:39
Sry, just forgot about that -.-
– Sven
Jan 9 '11 at 13:56
As to theenctype="multipart/form-data"
issue, for that you need to ensure that you've configured the PrimeFacesFileUploadFilter
as per the instructions in their User Guide.
– BalusC
Jan 26 '11 at 19:42
@BalusC: Ah, and now I know where thatenctype
came from - the file upload turned out to be unnecessary, but the attribute stayed around to mess up things... Thanks!
– Michael Borgwardt
Jan 26 '11 at 21:11
add a comment |
up vote
51
down vote
accepted
up vote
51
down vote
accepted
<p:commandButton>
needs one of the following to work correctly:
- the
update
attribute to list id's of components to re-render (for AJAX requests) - the attribute
ajax="false"
to make a normal, non-ajax submit.
If you have neither, the button does per default an AJAX request with no UI feedback.
Additionally, I've had problems with neither option working when the surrounding <h:form>
had an enctype
attribute.
<p:commandButton>
needs one of the following to work correctly:
- the
update
attribute to list id's of components to re-render (for AJAX requests) - the attribute
ajax="false"
to make a normal, non-ajax submit.
If you have neither, the button does per default an AJAX request with no UI feedback.
Additionally, I've had problems with neither option working when the surrounding <h:form>
had an enctype
attribute.
edited Jan 26 '11 at 15:52
answered Jan 9 '11 at 13:04
Michael Borgwardt
292k61423662
292k61423662
I do have an update parameter. See updated question
– Sven
Jan 9 '11 at 13:23
1
You wantajax="false"
if you want to have a synchronous request with a navigation. As to theupdate
parameter, see my comment in one of your previous questions which you didn't respond to yet.
– BalusC
Jan 9 '11 at 13:39
Sry, just forgot about that -.-
– Sven
Jan 9 '11 at 13:56
As to theenctype="multipart/form-data"
issue, for that you need to ensure that you've configured the PrimeFacesFileUploadFilter
as per the instructions in their User Guide.
– BalusC
Jan 26 '11 at 19:42
@BalusC: Ah, and now I know where thatenctype
came from - the file upload turned out to be unnecessary, but the attribute stayed around to mess up things... Thanks!
– Michael Borgwardt
Jan 26 '11 at 21:11
add a comment |
I do have an update parameter. See updated question
– Sven
Jan 9 '11 at 13:23
1
You wantajax="false"
if you want to have a synchronous request with a navigation. As to theupdate
parameter, see my comment in one of your previous questions which you didn't respond to yet.
– BalusC
Jan 9 '11 at 13:39
Sry, just forgot about that -.-
– Sven
Jan 9 '11 at 13:56
As to theenctype="multipart/form-data"
issue, for that you need to ensure that you've configured the PrimeFacesFileUploadFilter
as per the instructions in their User Guide.
– BalusC
Jan 26 '11 at 19:42
@BalusC: Ah, and now I know where thatenctype
came from - the file upload turned out to be unnecessary, but the attribute stayed around to mess up things... Thanks!
– Michael Borgwardt
Jan 26 '11 at 21:11
I do have an update parameter. See updated question
– Sven
Jan 9 '11 at 13:23
I do have an update parameter. See updated question
– Sven
Jan 9 '11 at 13:23
1
1
You want
ajax="false"
if you want to have a synchronous request with a navigation. As to the update
parameter, see my comment in one of your previous questions which you didn't respond to yet.– BalusC
Jan 9 '11 at 13:39
You want
ajax="false"
if you want to have a synchronous request with a navigation. As to the update
parameter, see my comment in one of your previous questions which you didn't respond to yet.– BalusC
Jan 9 '11 at 13:39
Sry, just forgot about that -.-
– Sven
Jan 9 '11 at 13:56
Sry, just forgot about that -.-
– Sven
Jan 9 '11 at 13:56
As to the
enctype="multipart/form-data"
issue, for that you need to ensure that you've configured the PrimeFaces FileUploadFilter
as per the instructions in their User Guide.– BalusC
Jan 26 '11 at 19:42
As to the
enctype="multipart/form-data"
issue, for that you need to ensure that you've configured the PrimeFaces FileUploadFilter
as per the instructions in their User Guide.– BalusC
Jan 26 '11 at 19:42
@BalusC: Ah, and now I know where that
enctype
came from - the file upload turned out to be unnecessary, but the attribute stayed around to mess up things... Thanks!– Michael Borgwardt
Jan 26 '11 at 21:11
@BalusC: Ah, and now I know where that
enctype
came from - the file upload turned out to be unnecessary, but the attribute stayed around to mess up things... Thanks!– Michael Borgwardt
Jan 26 '11 at 21:11
add a comment |
up vote
31
down vote
I think what Cagatay ment was:
Does not navigate the page:
<p:commandButton action="home.xhtml" value="Go Home"/>
Works (redirects the page):
<p:commandButton action="home.xhtml?faces-redirect=true" value="Go Home"/>
Works (redirects the page)
<p:commandButton action="home?faces-redirect=true" value="Go Home"/>
if .xhtml is your default postfix defined in web.xml:
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
More info can be found in the primefaces forum, for example in this discussion about navigation
I hope that helped a bit...
Nice conclusion!
– Sven
May 5 '11 at 9:24
add a comment |
up vote
31
down vote
I think what Cagatay ment was:
Does not navigate the page:
<p:commandButton action="home.xhtml" value="Go Home"/>
Works (redirects the page):
<p:commandButton action="home.xhtml?faces-redirect=true" value="Go Home"/>
Works (redirects the page)
<p:commandButton action="home?faces-redirect=true" value="Go Home"/>
if .xhtml is your default postfix defined in web.xml:
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
More info can be found in the primefaces forum, for example in this discussion about navigation
I hope that helped a bit...
Nice conclusion!
– Sven
May 5 '11 at 9:24
add a comment |
up vote
31
down vote
up vote
31
down vote
I think what Cagatay ment was:
Does not navigate the page:
<p:commandButton action="home.xhtml" value="Go Home"/>
Works (redirects the page):
<p:commandButton action="home.xhtml?faces-redirect=true" value="Go Home"/>
Works (redirects the page)
<p:commandButton action="home?faces-redirect=true" value="Go Home"/>
if .xhtml is your default postfix defined in web.xml:
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
More info can be found in the primefaces forum, for example in this discussion about navigation
I hope that helped a bit...
I think what Cagatay ment was:
Does not navigate the page:
<p:commandButton action="home.xhtml" value="Go Home"/>
Works (redirects the page):
<p:commandButton action="home.xhtml?faces-redirect=true" value="Go Home"/>
Works (redirects the page)
<p:commandButton action="home?faces-redirect=true" value="Go Home"/>
if .xhtml is your default postfix defined in web.xml:
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
More info can be found in the primefaces forum, for example in this discussion about navigation
I hope that helped a bit...
answered May 3 '11 at 10:11
alfonx
4,1973955
4,1973955
Nice conclusion!
– Sven
May 5 '11 at 9:24
add a comment |
Nice conclusion!
– Sven
May 5 '11 at 9:24
Nice conclusion!
– Sven
May 5 '11 at 9:24
Nice conclusion!
– Sven
May 5 '11 at 9:24
add a comment |
up vote
8
down vote
You must use redirect if you are doing navigation and request is done with ajax.
add a comment |
up vote
8
down vote
You must use redirect if you are doing navigation and request is done with ajax.
add a comment |
up vote
8
down vote
up vote
8
down vote
You must use redirect if you are doing navigation and request is done with ajax.
You must use redirect if you are doing navigation and request is done with ajax.
answered Jan 9 '11 at 17:48
Cagatay Civici
5,86112034
5,86112034
add a comment |
add a comment |
up vote
4
down vote
I am having a similar problem.
I am using primefaces and primefaces mobile and the navigation fails in Firefox when using
<p:commandButton>
with ajax="false" and action="find.xhtml?faces-redirect=true".
The only way I could make it work also in Firefox was by using <h:commandButton>
:
<h:commandButton value="#{msg.find}" process="find"
action="find.xhtml?faces-redirect=true" />
add a comment |
up vote
4
down vote
I am having a similar problem.
I am using primefaces and primefaces mobile and the navigation fails in Firefox when using
<p:commandButton>
with ajax="false" and action="find.xhtml?faces-redirect=true".
The only way I could make it work also in Firefox was by using <h:commandButton>
:
<h:commandButton value="#{msg.find}" process="find"
action="find.xhtml?faces-redirect=true" />
add a comment |
up vote
4
down vote
up vote
4
down vote
I am having a similar problem.
I am using primefaces and primefaces mobile and the navigation fails in Firefox when using
<p:commandButton>
with ajax="false" and action="find.xhtml?faces-redirect=true".
The only way I could make it work also in Firefox was by using <h:commandButton>
:
<h:commandButton value="#{msg.find}" process="find"
action="find.xhtml?faces-redirect=true" />
I am having a similar problem.
I am using primefaces and primefaces mobile and the navigation fails in Firefox when using
<p:commandButton>
with ajax="false" and action="find.xhtml?faces-redirect=true".
The only way I could make it work also in Firefox was by using <h:commandButton>
:
<h:commandButton value="#{msg.find}" process="find"
action="find.xhtml?faces-redirect=true" />
answered Jul 5 '12 at 13:54
zzirna
5427
5427
add a comment |
add a comment |
up vote
-1
down vote
none of the above solution worked for me.
You can still go for simple javascript
<p:commandButton onclick="window.location.href =home.xhtml"
style="height: 20px" type="button" title="title" icon="ui-icon-transferthick-e-w"/>
add a comment |
up vote
-1
down vote
none of the above solution worked for me.
You can still go for simple javascript
<p:commandButton onclick="window.location.href =home.xhtml"
style="height: 20px" type="button" title="title" icon="ui-icon-transferthick-e-w"/>
add a comment |
up vote
-1
down vote
up vote
-1
down vote
none of the above solution worked for me.
You can still go for simple javascript
<p:commandButton onclick="window.location.href =home.xhtml"
style="height: 20px" type="button" title="title" icon="ui-icon-transferthick-e-w"/>
none of the above solution worked for me.
You can still go for simple javascript
<p:commandButton onclick="window.location.href =home.xhtml"
style="height: 20px" type="button" title="title" icon="ui-icon-transferthick-e-w"/>
answered Apr 25 at 9:59
Toumi
8941415
8941415
add a comment |
add a comment |
up vote
-1
down vote
<h:commandButton
styleClass="btn btn-primary-active upgrade" data-dismiss="modal"
value="Upgrade Account"
action="profile.do?faces-redirect=true&tab=plan"
oncomplete="$('#freeGiftModal').hide();" process="@this" partialSubmit="true" immediate="true"/>
I used the commandbutton to navigate to profile page, and its working fine for me.
Your answer isffectively not different from others and in a way it is worse. Besides it not beimg ap:commandButton
, which with the right attributes 'just works' it containsttributes that are not valid for anh:commandButton
, mor that one of the other answers
– Kukeltje
Nov 11 at 8:14
add a comment |
up vote
-1
down vote
<h:commandButton
styleClass="btn btn-primary-active upgrade" data-dismiss="modal"
value="Upgrade Account"
action="profile.do?faces-redirect=true&tab=plan"
oncomplete="$('#freeGiftModal').hide();" process="@this" partialSubmit="true" immediate="true"/>
I used the commandbutton to navigate to profile page, and its working fine for me.
Your answer isffectively not different from others and in a way it is worse. Besides it not beimg ap:commandButton
, which with the right attributes 'just works' it containsttributes that are not valid for anh:commandButton
, mor that one of the other answers
– Kukeltje
Nov 11 at 8:14
add a comment |
up vote
-1
down vote
up vote
-1
down vote
<h:commandButton
styleClass="btn btn-primary-active upgrade" data-dismiss="modal"
value="Upgrade Account"
action="profile.do?faces-redirect=true&tab=plan"
oncomplete="$('#freeGiftModal').hide();" process="@this" partialSubmit="true" immediate="true"/>
I used the commandbutton to navigate to profile page, and its working fine for me.
<h:commandButton
styleClass="btn btn-primary-active upgrade" data-dismiss="modal"
value="Upgrade Account"
action="profile.do?faces-redirect=true&tab=plan"
oncomplete="$('#freeGiftModal').hide();" process="@this" partialSubmit="true" immediate="true"/>
I used the commandbutton to navigate to profile page, and its working fine for me.
answered Nov 11 at 7:43
shehraz490
11
11
Your answer isffectively not different from others and in a way it is worse. Besides it not beimg ap:commandButton
, which with the right attributes 'just works' it containsttributes that are not valid for anh:commandButton
, mor that one of the other answers
– Kukeltje
Nov 11 at 8:14
add a comment |
Your answer isffectively not different from others and in a way it is worse. Besides it not beimg ap:commandButton
, which with the right attributes 'just works' it containsttributes that are not valid for anh:commandButton
, mor that one of the other answers
– Kukeltje
Nov 11 at 8:14
Your answer isffectively not different from others and in a way it is worse. Besides it not beimg a
p:commandButton
, which with the right attributes 'just works' it containsttributes that are not valid for an h:commandButton
, mor that one of the other answers– Kukeltje
Nov 11 at 8:14
Your answer isffectively not different from others and in a way it is worse. Besides it not beimg a
p:commandButton
, which with the right attributes 'just works' it containsttributes that are not valid for an h:commandButton
, mor that one of the other answers– Kukeltje
Nov 11 at 8:14
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f4639205%2fprimefaces-commandbutton-doesnt-navigate-or-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown