[richfaces-issues] [JBoss JIRA] (RF-13203) a4j:queue should have status attribute

[Brian Leathem (JIRA)]

     [ https://issues.jboss.org/browse/RF-13203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13203:
-------------------------------

    Fix Version/s: 5-Tracking
                       (was: 4.3.5)


Re-scheduling for implementation in RF 5.  We will consider back-porting this to our stable branch once the feature itself has stabilized.
                
> a4j:queue should have status attribute
> --------------------------------------
>
>                 Key: RF-13203
>                 URL: https://issues.jboss.org/browse/RF-13203
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 4.3.2
>            Reporter: Jonáš Trantina
>              Labels: gss, queue
>             Fix For: 5-Tracking
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> a4j:queue should have status attribute, so it can connect to a4j:status. Consider the following example:
> {noformat}
>     <a4j:queue name="quick" requestDelay="200" />
>     <a4j:queue name="slow" requestDelay="1000" />
>     <a4j:status name="quickStatus" startText="Started!" stopText="Stopped"/>
>     <br/>
>     <a4j:statusname="slowStatus" startText="Started!" stopText="Stopped" />
>    
>     <h:form>
>         <a4j:commandButton action="#{test.dummy}" value="Quick">
>             <a4j:attachQueue name="quick"/>
>         </a4j:commandButton>
>     </h:form>
>     <br/>
>     <h:form>
>         <a4j:commandButton action="#{test.dummy}" value="Slow">
>             <a4j:attachQueue name="slow"/>
>         </a4j:commandButton>
>     </h:form>
> {noformat}
> By using the status attr. of a4j:queue, it would be possible to connect "slow" queue to "slowStatus" and thus every component that would be connected to the queue, would also be connected to the status.
> Note in this example it would be simpler to set status attr. on the components themselves, but imagine there are more components connected to the queue.
> I was also informed, that this functionality was present in RF 3.3.
> Workarounds:
> - set status attr on every component instead of on the queue- in larger applications this is not doable.
> - use a4j:status JS API and a4j:queues' onsubmit and oncomplete methods- onsubmit and oncomplete a4j:queue are not implemented, so not working now

--
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