[JBoss JIRA] Created: (RF-6729) Patch for Jira issue RF-6633.
by Kevin Lester (JIRA)
Patch for Jira issue RF-6633.
-----------------------------
Key: RF-6729
URL: https://jira.jboss.org/jira/browse/RF-6729
Project: RichFaces
Issue Type: Patch
Reporter: Kevin Lester
Attachments: patch-09-04-07.diff
This is a patch for issue RF-6622 - pickList: allow to configure buttons.
The following attributes were added to the PickList component to allow users to conditionally render the controls:
- copyVisible
- copyAllVisible
- removeVisible
- removeAllVisible
These attributes may clash with the "moveControlsVisible" and the "fastMoveControlsVisible" attributes, so these are implemented such that the controls will only be shown if all the related 'visible' attributes are true. Hence if the "moveControlsVisible" attribute is false but the "copyVisible" attribute is true, the copy control will NOT be displayed.
NOTE: These attributes will need to be added to the PickList documentation.
This patch has the following changes:
picklist.xml - updated to support the new atrributes
PickListControlsHelper.java - updated to take the new attributes into account for the rendering of the controls
UIPickList.java - updated to support the new attributes
pickList-sample app - Updated to enable testing of the new attributes.
Patch created via : svn diff > file.diff
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (RF-5788) Queue: ignoreDupResponse functionality change
by Ilya Shaikovsky (JIRA)
Queue: ignoreDupResponse functionality change
---------------------------------------------
Key: RF-5788
URL: https://jira.jboss.org/jira/browse/RF-5788
Project: RichFaces
Issue Type: Task
Affects Versions: 3.3.0
Reporter: Ilya Shaikovsky
Assignee: Nick Belaevski
Current state:
1) queue has ignoreDupResponces defined as true
2) request сomes to queue and fired after its delay
3) new similar request comes to queue
4) previous one client side processing aborted - new one sent.
RESULT parallel requests occur.
To Be Changed:
4) new request should wait till previous response returned(but the response should not be processed) and then to be sent.
RESULT just client-side response processing should be ignored but queue should works as for normal requests (without ignoreResponse). New request waits till previous actually finished.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months