[
https://jira.jboss.org/browse/RF-7492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Belaevski updated RF-7492:
-------------------------------
Fix Version/s: 4.0.0.Milestone2
(was: 4.0.0.Milestone1)
> a4j:queue support for standard form submits as well as AJAX request
> -------------------------------------------------------------------
>
> Key: RF-7492
> URL: https://jira.jboss.org/browse/RF-7492
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-misc
> Affects Versions: 3.3.1
> Reporter: Jay Balunas
> Assignee: Pavel Yaschenko
> Fix For: 4.0.0.Milestone2
>
>
> a4j:queue does not currently support forwarding standard form requests
> through an a4j:queue. This means that input items that are ajax enabled may
> be processed through a queue, but if the user clicks submit on the form that
> request that fire before items in the queue.
> A user reported a work around. Use a4j:commandButton and then rerender the
> most of the page - not optimal.
> We need to create an FAQ for the work around and investigate the standard
> form support.
> Brainstorming: This behavior may not be possible on a global or page coped
> queue. A form scoped a4j:queue could behave like a4j:support and inject the
> needed behavior into the form tag.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
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
