[
https://issues.jboss.org/browse/RF-12907?page=com.atlassian.jira.plugin.s...
]
Jean ANDRE commented on RF-12907:
---------------------------------
We found another "wrong" behavior with the @all value. To reproduce it:
Inside the file listItem.xhtml change the code related to the cancel button. The cancel
button in the result list, returns back to the search screen. When you have returned back,
enter a value for the field "Item quantity" and press the "New List"
button from the search screen. The action does nothing. We need to press twice to get the
expected behavior.
We really appreciate to tell us if we doing something wrong and what or if it is a general
bug related to the values "@form", "@all".... Could you please give us
some explanation. Thx.
{code:title=listItem.xhtml - This code works}
<!-- -->
<!-- CANCEL -->
<!-- -->
<h:commandButton id="doCancelCmd"
value="#{msg['common.command.cancel']}"
action="#{listItemController.doCancel}" />
{code}
{code: title=listItem.xhtml - This code does not work}
<!-- -->
<!-- CANCEL -->
<!-- -->
<a4j:commandButton id="doCancelCmd"
value="#{msg['common.command.cancel']}"
render="@all"
action="#{listItemController.doCancel}" />
{code}
render="@form" problem with a4jCommand Button
---------------------------------------------
Key: RF-12907
URL:
https://issues.jboss.org/browse/RF-12907
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.2.3.Final, 4.3.1
Environment: JSF Mojarra 2.1.21 or 2.1.20 - Glassfish or WAS 8.0.0.x Servlet 3.0
or 2.5
Reporter: Jean ANDRE
Priority: Blocker
Labels: waiting_on_user
Attachments: Nested-Spring-3.2.2.zip, NestedEar-CDI.zip
Please see the report at:
http://java.net/jira/browse/JAVASERVERFACES-2016
It seems that that there is a problem with a4j button and the value of @form/render
attribute.
The symptom we got is after refreshing the panel for building a list. Click on link form
the result lisk does not trigger the action.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira