[JBoss JIRA] (RF-13203) a4j:queue should have status attribute
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13203?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13203:
-------------------------------
Original Estimate: 2 days
Remaining Estimate: 2 days
> 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: 4.3.5
>
> 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
10 years, 11 months
[JBoss JIRA] (RF-13257) PhotoAlbum: uploading and deleting images
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13257?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek updated RF-13257:
-----------------------------
Description:
What doesn't work:
* uploading file to album (image isn't saved to DB)
* deleting uploaded file (cannot delete not existing file, but the image is present in album even after relog)
was:
PhotoAlbum 4.3.x known bugs:
* uploading file to album (image isn't saved to DB)
* deleting uploaded file (cannot delete not existing file, but the image is present in album even after relog)
> PhotoAlbum: uploading and deleting images
> -----------------------------------------
>
> Key: RF-13257
> URL: https://issues.jboss.org/browse/RF-13257
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Jiří Štefek
> Assignee: Jiří Štefek
> Fix For: 4.3.5
>
>
> What doesn't work:
> * uploading file to album (image isn't saved to DB)
> * deleting uploaded file (cannot delete not existing file, but the image is present in album even after relog)
--
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
10 years, 11 months