[JBoss JIRA] (RF-12555) On Scroll Ajax Content Loading
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12555?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12555:
-------------------------------
Component/s: component-panels-layout-themes
> On Scroll Ajax Content Loading
> ------------------------------
>
> Key: RF-12555
> URL: https://issues.jboss.org/browse/RF-12555
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes, mobile
> Reporter: nathan dennis
> Priority: Minor
> Labels: scrollable
> Fix For: 5-Tracking
>
>
> It would be nice to have on scroll content loading so that as the user reaches the bottom of the page more content can be loaded from the db. Currently most sites are using jQuery to do this, however, in an effort to make the foot print as small as possible for the mobile environment it would be nice to have a richfaces solution. an example (that i'm in no way affiliated with) http://www.webresourcesdepot.com/dnspinger/
--
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
12 years, 2 months
[JBoss JIRA] (RF-12555) On Scroll Ajax Content Loading
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12555?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12555:
-------------------------------
Component/s: component-ScrollableDataTable
> On Scroll Ajax Content Loading
> ------------------------------
>
> Key: RF-12555
> URL: https://issues.jboss.org/browse/RF-12555
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes, component-ScrollableDataTable, mobile
> Reporter: nathan dennis
> Priority: Minor
> Labels: scrollable
> Fix For: 5-Tracking
>
>
> It would be nice to have on scroll content loading so that as the user reaches the bottom of the page more content can be loaded from the db. Currently most sites are using jQuery to do this, however, in an effort to make the foot print as small as possible for the mobile environment it would be nice to have a richfaces solution. an example (that i'm in no way affiliated with) http://www.webresourcesdepot.com/dnspinger/
--
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
12 years, 2 months
[JBoss JIRA] (RF-12553) a4j:status doesn't work if there's a h:commandLink in the page
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12553?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12553:
----------------------------------
Assignee: Pavol Pitonak
QE, please verify this issue
> a4j:status doesn't work if there's a h:commandLink in the page
> --------------------------------------------------------------
>
> Key: RF-12553
> URL: https://issues.jboss.org/browse/RF-12553
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.1.0.Final
> Reporter: Guillaume Lancelin
> Assignee: Pavol Pitonak
>
> Hi all,
> The a4j:status tag seems not to work when a h:commandLink tag is in the same page.
> I made a little example to test it.
> The bean :
> {code:java}
> package fr.mycompany.test;
> import javax.enterprise.inject.Model;
> import javax.inject.Inject;
> import org.jboss.logging.Logger;
> @Model
> public class Test {
> @Inject
> private Logger logger;
> public String launch() {
> for (int i = 0; i < 20000; i++) {
> logger.debug(i);
> }
> return null;
> }
> }
> {code}
> The page :
> {code:xml}
> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html" xmlns:a4j="http://richfaces.org/a4j"
> xmlns:rich="http://richfaces.org/rich"
> xmlns:s="http://jboss.org/seam/faces" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets">
> <h:head />
> <h:body>
> <a4j:status id="status" onstart="#{rich:component('processingPopup')}.show()" onstop="#{rich:component('processingPopup')}.hide()" startText="en cours" stopText="fini" />
> <rich:popupPanel id="processingPopup" modal="true" styleClass="popupSouscription" autosized="true" show="false">
> Traitement en cours ...
> </rich:popupPanel>
> <h:form id="leForm">
> <a4j:commandLink value="a4j commandLink" action="#{test.launch}" id="a4jLink" /><br/>
> <h:commandLink value="h commandLink" action="#{test.launch}" id="hLink" />
> </h:form>
> <a4j:log id="logs" style="width: 1400px; height: 600px; overflow: scroll;" />
> </h:body>
> </html>
> {code}
> When I click on the a4j:commandLink the a4j:status doesn't work and the following log appears :
> {code}
> info [18:25:14.390]: Received 'begin' event from <a id=leForm:a4jLink ...>
> info [18:25:15.251]: Received 'beforedomupdate' event from <a id=leForm:a4jLink ...>
> debug[18:25:15.252]: Server returned responseText: <?xml version='1.0' encoding='UTF-8'?> <partial-response><changes><update id="javax.faces.ViewState"><![CDATA[5271447831659883319:-888481348828354087]]></update></changes></partial-response>
> info [18:25:15.253]: Listing content of response changes element:
> Element update for id=javax.faces.ViewState
> <update id="javax.faces.ViewState"><![CDATA[5271447831659883319:-888481348828354087]]></update>
> info [18:25:15.255]: Received 'success' event from <a id=leForm:a4jLink ...>
> info [18:25:15.256]: Received 'complete' event from <a id=leForm:a4jLink ...>
> {code}
> If I remove the line <h:commandLink value="h commandLink" action="#{test.launch}" id="hLink" /> and then click on the a4j:commandLink the a4j:status works and the following log appears :
> {code}
> debug[18:28:17.277]: New request added to queue. Queue requestGroupingId changed to leForm:a4jLink
> debug[18:28:17.277]: Queue will wait 0ms before submit
> debug[18:28:17.278]: richfaces.queue: will submit request NOW
> info [18:28:17.282]: Received 'begin' event from <a id=leForm:a4jLink ...>
> info [18:28:17.905]: Received 'beforedomupdate' event from <a id=leForm:a4jLink ...>
> debug[18:28:17.906]: Server returned responseText: <?xml version='1.0' encoding='UTF-8'?> <partial-response><changes><update id="javax.faces.ViewState"><![CDATA[-4055820746262438471:-5740665287677042238]]></update></changes></partial-response>
> info [18:28:17.908]: Listing content of response changes element:
> Element update for id=javax.faces.ViewState
> <update id="javax.faces.ViewState"><![CDATA[-4055820746262438471:-5740665287677042238]]></update>
> debug[18:28:17.909]: richfaces.queue: ajax submit successfull
> debug[18:28:17.910]: richfaces.queue: Nothing to submit
> info [18:28:17.913]: Received 'success' event from <a id=leForm:a4jLink ...>
> info [18:28:17.914]: Received 'complete' event from <a id=leForm:a4jLink ...>
> {code}
> I'm using Java 1.6.0_29, JBoss 6.1, mojarra 2.0.3_b5, RF 4.1.0-Final (but someone told me [here|http://community.jboss.org/thread/175872?tstart=0] that the problem appeared with the milestone 3), Seam 3.0.0-Final.
--
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
12 years, 2 months
[JBoss JIRA] (RF-12552) rich:calendar: @minDaysInFirstWeek is not working
by Jiří Štefek (JIRA)
Jiří Štefek created RF-12552:
--------------------------------
Summary: rich:calendar: @minDaysInFirstWeek is not working
Key: RF-12552
URL: https://issues.jboss.org/browse/RF-12552
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.3.0.M1
Environment: RichFaces 4.3.0-SNAPSHOT
Metamer 4.3.0-SNAPSHOT
Apache Tomcat 7.0.30 / JBoss AS 7.1
OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux
Firefox 16.0 @ Linux x86_64
Reporter: Jiří Štefek
This attribute should influence, that each first week of each year should contain at least a minimum of days.
--
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
12 years, 2 months