[
https://issues.jboss.org/browse/RF-11162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Bryan updated RF-11162:
---------------------------
Attachment: TestCommandButton.xhtml
TestCommandButtonAction.java
In our project, we used the Seam support in JBoss Tools to generate a Seam
project. The xhtml file would be part of the WebContent in the web module, and
the action class would be part of the EJB module.
> dynamically-enabled commandButton doesn't work (need a:htmlCommandButton?)
> --------------------------------------------------------------------------
>
> Key: RF-11162
> URL: https://issues.jboss.org/browse/RF-11162
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.3.1
> Environment: Seam 2.2.0.GA, Richfaces 3.3.1, and JBoss 5.1.0
> Reporter: Tom Bryan
> Attachments: TestCommandButton.xhtml, TestCommandButtonAction.java
>
>
> When an h:commandButton is initially rendered as disabled and then
> dynamically-enabled during an a:commandButton, it does not seem to submit the
> page. Changing the h:commandButton to a h:commandLink gives the same
> results, but changing it to an a:htmlCommandLink does work. I'm not sure
> whether h:commandButton is supposed to work in this case or whether there
> should just be an a:htmlCommandButton.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
