[JBoss JIRA] (RF-13449) rich:fileuload progress not displaying
by Javier Gonzales (JIRA)
[ https://issues.jboss.org/browse/RF-13449?page=com.atlassian.jira.plugin.s... ]
Javier Gonzales updated RF-13449:
---------------------------------
Description:
On my local environment with IE 9 the progress bar works fine. Once the application is deployed in higher environments then the progress bar does not display at all. I've also noticed this same issue in the showcases with the same browser IE9 (I've tried other browsers and also experiencing the same problem, IE10/11, Chrome 31.0, etc). After some debugging I've noticed that when the application makes the following request, the response is always 0.
http://showcase.richfaces.org/rfRes/fileUploadProgress.jsf?ln=org.richfac....
was:
On my local environment with IE 9 the progress bar works fine. Once the application is deployed in higher environments then the progress bar does not display at all. I've also noticed this same issue in the showcases with the same browser IE9 (I've tried other browsers and also experiencing the same problem, IE10, Chrome 31.0, etc). After some debugging I've noticed that when the application makes the following request, the response is always 0.
http://showcase.richfaces.org/rfRes/fileUploadProgress.jsf?ln=org.richfac....
> rich:fileuload progress not displaying
> --------------------------------------
>
> Key: RF-13449
> URL: https://issues.jboss.org/browse/RF-13449
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Javier Gonzales
>
> On my local environment with IE 9 the progress bar works fine. Once the application is deployed in higher environments then the progress bar does not display at all. I've also noticed this same issue in the showcases with the same browser IE9 (I've tried other browsers and also experiencing the same problem, IE10/11, Chrome 31.0, etc). After some debugging I've noticed that when the application makes the following request, the response is always 0.
> http://showcase.richfaces.org/rfRes/fileUploadProgress.jsf?ln=org.richfac....
--
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-13452) UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor
by Lutz Ulrich (JIRA)
Lutz Ulrich created RF-13452:
--------------------------------
Summary: UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor
Key: RF-13452
URL: https://issues.jboss.org/browse/RF-13452
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: compatibility
Affects Versions: 4.3.4
Environment: Mojarra 2.1.?? - 2.1.26
Reporter: Lutz Ulrich
Whenever a component which is based on {{org.richfaces.component.UIDataAdaptor}} is added dynamically, NPE occurs in the next RESTORE_VIEW Phase when using Mojarra 2.1.x.
My first guess was, that this would be an error in Mojarra (issue 2152, see https://java.net/jira/browse/JAVASERVERFACES-2152?page=com.atlassian.jira... ),
which occurs whenever a sub-class of {{UIComponent}} registers itself as {{javax.faces.event.SystemEventListener}} for
{{javax.faces.event.PostAddToViewEvent}} in ist constructor, just like {{UIDataAdaptor}} does.
Now, Manfred Riem of Mojarra argues (in the very issue named above), that registering for PostAddToView in the constructor is a design flaw in itself.
Note that the error occurs with every UIComponent which is added dynamically and which registers itself as PostAddToView listener in its constructor. For the Mojarra issue, I provided a simple component which extends the standard JSF HtmlOutputText and registers itself in its constructor, too. Baam - same error. So maybe more components of RichFaces are affected - not just those based on {{UIDataAdaptor}}.
For completion, here is a stack trace:
{quote}
Schwerwiegend: java.lang.NullPointerException
at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2526)
at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106)
at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2163)
at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2111)
at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:289)
at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:247)
at javax.faces.component.UIComponentBase.publishAfterViewEvents(UIComponentBase.java:2203)
at javax.faces.component.UIComponentBase.doPostAddProcessing(UIComponentBase.java:1885)
at javax.faces.component.UIComponentBase.setParent(UIComponentBase.java:405)
at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2637)
at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2609)
at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicAdd(FaceletPartialStateManagementStrategy.java:421)
at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicActions(FaceletPartialStateManagementStrategy.java:247)
at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreView(FaceletPartialStateManagementStrategy.java:570)
at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:138)
at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123)
at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:653)
at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:142)
at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301)
at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301)
at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:192)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
{quote}
--
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-13451) Persian Datepicker/Calendar
by Seyed Mohammad Hosein Jamali (JIRA)
Seyed Mohammad Hosein Jamali created RF-13451:
-------------------------------------------------
Summary: Persian Datepicker/Calendar
Key: RF-13451
URL: https://issues.jboss.org/browse/RF-13451
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component
Affects Versions: 5.0.0.Alpha1
Reporter: Seyed Mohammad Hosein Jamali
Provides Persian Datepicker/Calendar for RichFaces 5
--
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-13450) page attribute on dataScroller doesn't work with a request scope
by Luca Stancapiano (JIRA)
[ https://issues.jboss.org/browse/RF-13450?page=com.atlassian.jira.plugin.s... ]
Luca Stancapiano updated RF-13450:
----------------------------------
Attachment: scrollablesample.zip
> page attribute on dataScroller doesn't work with a request scope
> ----------------------------------------------------------------
>
> Key: RF-13450
> URL: https://issues.jboss.org/browse/RF-13450
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-ScrollableDataTable
> Affects Versions: 4.3.4
> Environment: java 6 on jboss as 7.1
> Reporter: Luca Stancapiano
> Labels: datatable, scrollable
> Attachments: scrollablesample.zip, scrollablesample.zip
>
>
> Here the dataTable with a dataScroller:
> {code}
> <rich:dataScroller for="table" maxPages="5"
> page="#{currentPage.page}" />
> <rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
> id="table" rows="10">
> <rich:column>
> <f:facet name="header">
> <h:outputText value="Vendor " />
> </f:facet>
> <h:outputText value="#{car.vendor}" />
> </rich:column>
> ...
> </rich:dataTable>
> {code}
> Here the definition of the currentPage bean:
> {code}
> <managed-bean>
> <managed-bean-name>currentPage</managed-bean-name>
> <managed-bean-class>prova.CurrentPage</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> {code}
> Here the currentPage bean:
> {code}
> package prova;
> public class CurrentPage {
>
> private int page = 1;
> public int getPage() {
> return page;
> }
> public void setPage(int page) {
> this.page = page;
> }
> }
> {code}
> the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok
--
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-13450) page attribute on dataScroller doesn't work with a request scope
by Luca Stancapiano (JIRA)
[ https://issues.jboss.org/browse/RF-13450?page=com.atlassian.jira.plugin.s... ]
Luca Stancapiano updated RF-13450:
----------------------------------
Description:
Here the dataTable with a dataScroller:
{code}
<rich:dataScroller for="table" maxPages="5"
page="#{currentPage.page}" />
<rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
id="table" rows="10">
<rich:column>
<f:facet name="header">
<h:outputText value="Vendor " />
</f:facet>
<h:outputText value="#{car.vendor}" />
</rich:column>
...
</rich:dataTable>
{code}
Here the definition of the currentPage bean:
{code}
<managed-bean>
<managed-bean-name>currentPage</managed-bean-name>
<managed-bean-class>prova.CurrentPage</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
{code}
Here the currentPage bean:
{code}
package prova;
public class CurrentPage {
private int page = 1;
public int getPage() {
return page;
}
public void setPage(int page) {
this.page = page;
}
}
{code}
the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok
was:
Here the dataTable with a dataScroller:
{code}
<rich:dataScroller for="table" maxPages="5"
page="#{currentPage.page}" />
<rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
id="table" rows="10">
<rich:column>
<f:facet name="header">
<h:outputText value="Vendor " />
</f:facet>
<h:outputText value="#{car.vendor}" />
</rich:column>
...
</rich:dataTable>
{code}
Here the definition of the currentPage bean:
{code}
<managed-bean>
<managed-bean-name>currentPage</managed-bean-name>
<managed-bean-class>prova.CurrentPage</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
{code}
Here the currentPage bean:
{code}
package prova;
import javax.enterprise.context.RequestScoped;
import javax.inject.Named;
@Named
@RequestScoped
public class CurrentPage {
private int page = 1;
public int getPage() {
return page;
}
public void setPage(int page) {
this.page = page;
}
}
{code}
the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok
> page attribute on dataScroller doesn't work with a request scope
> ----------------------------------------------------------------
>
> Key: RF-13450
> URL: https://issues.jboss.org/browse/RF-13450
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-ScrollableDataTable
> Affects Versions: 4.3.4
> Environment: java 6 on jboss as 7.1
> Reporter: Luca Stancapiano
> Labels: datatable, scrollable
> Attachments: scrollablesample.zip
>
>
> Here the dataTable with a dataScroller:
> {code}
> <rich:dataScroller for="table" maxPages="5"
> page="#{currentPage.page}" />
> <rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
> id="table" rows="10">
> <rich:column>
> <f:facet name="header">
> <h:outputText value="Vendor " />
> </f:facet>
> <h:outputText value="#{car.vendor}" />
> </rich:column>
> ...
> </rich:dataTable>
> {code}
> Here the definition of the currentPage bean:
> {code}
> <managed-bean>
> <managed-bean-name>currentPage</managed-bean-name>
> <managed-bean-class>prova.CurrentPage</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> {code}
> Here the currentPage bean:
> {code}
> package prova;
> public class CurrentPage {
>
> private int page = 1;
> public int getPage() {
> return page;
> }
> public void setPage(int page) {
> this.page = page;
> }
> }
> {code}
> the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok
--
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-13450) page attribute on dataScroller doesn't work with a request scope
by Luca Stancapiano (JIRA)
[ https://issues.jboss.org/browse/RF-13450?page=com.atlassian.jira.plugin.s... ]
Luca Stancapiano updated RF-13450:
----------------------------------
Description:
Here the dataTable with a dataScroller:
{code}
<rich:dataScroller for="table" maxPages="5"
page="#{currentPage.page}" />
<rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
id="table" rows="10">
<rich:column>
<f:facet name="header">
<h:outputText value="Vendor " />
</f:facet>
<h:outputText value="#{car.vendor}" />
</rich:column>
...
</rich:dataTable>
{code}
Here the definition of the currentPage bean:
<managed-bean>
<managed-bean-name>currentPage</managed-bean-name>
<managed-bean-class>prova.CurrentPage</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
Here the currentPage bean:
package prova;
import javax.enterprise.context.RequestScoped;
import javax.inject.Named;
@Named
@RequestScoped
public class CurrentPage {
private int page = 1;
public int getPage() {
return page;
}
public void setPage(int page) {
this.page = page;
}
}
the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok
was:
Here the dataTable with a dataScroller:
<rich:dataScroller for="table" maxPages="5"
page="#{currentPage.page}" />
<rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
id="table" rows="10">
<rich:column>
<f:facet name="header">
<h:outputText value="Vendor " />
</f:facet>
<h:outputText value="#{car.vendor}" />
</rich:column>
...
</rich:dataTable>
Here the definition of the currentPage bean:
<managed-bean>
<managed-bean-name>currentPage</managed-bean-name>
<managed-bean-class>prova.CurrentPage</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
Here the currentPage bean:
package prova;
import javax.enterprise.context.RequestScoped;
import javax.inject.Named;
@Named
@RequestScoped
public class CurrentPage {
private int page = 1;
public int getPage() {
return page;
}
public void setPage(int page) {
this.page = page;
}
}
the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok
> page attribute on dataScroller doesn't work with a request scope
> ----------------------------------------------------------------
>
> Key: RF-13450
> URL: https://issues.jboss.org/browse/RF-13450
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-ScrollableDataTable
> Affects Versions: 4.3.4
> Environment: java 6 on jboss as 7.1
> Reporter: Luca Stancapiano
> Labels: datatable, scrollable
> Attachments: scrollablesample.zip
>
>
> Here the dataTable with a dataScroller:
> {code}
> <rich:dataScroller for="table" maxPages="5"
> page="#{currentPage.page}" />
> <rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
> id="table" rows="10">
> <rich:column>
> <f:facet name="header">
> <h:outputText value="Vendor " />
> </f:facet>
> <h:outputText value="#{car.vendor}" />
> </rich:column>
> ...
> </rich:dataTable>
> {code}
> Here the definition of the currentPage bean:
> <managed-bean>
> <managed-bean-name>currentPage</managed-bean-name>
> <managed-bean-class>prova.CurrentPage</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> Here the currentPage bean:
> package prova;
> import javax.enterprise.context.RequestScoped;
> import javax.inject.Named;
> @Named
> @RequestScoped
> public class CurrentPage {
>
> private int page = 1;
> public int getPage() {
> return page;
> }
> public void setPage(int page) {
> this.page = page;
> }
> }
> the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok
--
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-13450) page attribute on dataScroller doesn't work with a request scope
by Luca Stancapiano (JIRA)
[ https://issues.jboss.org/browse/RF-13450?page=com.atlassian.jira.plugin.s... ]
Luca Stancapiano updated RF-13450:
----------------------------------
Description:
Here the dataTable with a dataScroller:
{code}
<rich:dataScroller for="table" maxPages="5"
page="#{currentPage.page}" />
<rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
id="table" rows="10">
<rich:column>
<f:facet name="header">
<h:outputText value="Vendor " />
</f:facet>
<h:outputText value="#{car.vendor}" />
</rich:column>
...
</rich:dataTable>
{code}
Here the definition of the currentPage bean:
{code}
<managed-bean>
<managed-bean-name>currentPage</managed-bean-name>
<managed-bean-class>prova.CurrentPage</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
{code}
Here the currentPage bean:
{code}
package prova;
import javax.enterprise.context.RequestScoped;
import javax.inject.Named;
@Named
@RequestScoped
public class CurrentPage {
private int page = 1;
public int getPage() {
return page;
}
public void setPage(int page) {
this.page = page;
}
}
{code}
the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok
was:
Here the dataTable with a dataScroller:
{code}
<rich:dataScroller for="table" maxPages="5"
page="#{currentPage.page}" />
<rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
id="table" rows="10">
<rich:column>
<f:facet name="header">
<h:outputText value="Vendor " />
</f:facet>
<h:outputText value="#{car.vendor}" />
</rich:column>
...
</rich:dataTable>
{code}
Here the definition of the currentPage bean:
<managed-bean>
<managed-bean-name>currentPage</managed-bean-name>
<managed-bean-class>prova.CurrentPage</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
Here the currentPage bean:
package prova;
import javax.enterprise.context.RequestScoped;
import javax.inject.Named;
@Named
@RequestScoped
public class CurrentPage {
private int page = 1;
public int getPage() {
return page;
}
public void setPage(int page) {
this.page = page;
}
}
the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok
> page attribute on dataScroller doesn't work with a request scope
> ----------------------------------------------------------------
>
> Key: RF-13450
> URL: https://issues.jboss.org/browse/RF-13450
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-ScrollableDataTable
> Affects Versions: 4.3.4
> Environment: java 6 on jboss as 7.1
> Reporter: Luca Stancapiano
> Labels: datatable, scrollable
> Attachments: scrollablesample.zip
>
>
> Here the dataTable with a dataScroller:
> {code}
> <rich:dataScroller for="table" maxPages="5"
> page="#{currentPage.page}" />
> <rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
> id="table" rows="10">
> <rich:column>
> <f:facet name="header">
> <h:outputText value="Vendor " />
> </f:facet>
> <h:outputText value="#{car.vendor}" />
> </rich:column>
> ...
> </rich:dataTable>
> {code}
> Here the definition of the currentPage bean:
> {code}
> <managed-bean>
> <managed-bean-name>currentPage</managed-bean-name>
> <managed-bean-class>prova.CurrentPage</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> {code}
> Here the currentPage bean:
> {code}
> package prova;
> import javax.enterprise.context.RequestScoped;
> import javax.inject.Named;
> @Named
> @RequestScoped
> public class CurrentPage {
>
> private int page = 1;
> public int getPage() {
> return page;
> }
> public void setPage(int page) {
> this.page = page;
> }
> }
> {code}
> the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok
--
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-13450) page attribute on dataScroller doesn't work with a request scope
by Luca Stancapiano (JIRA)
Luca Stancapiano created RF-13450:
-------------------------------------
Summary: page attribute on dataScroller doesn't work with a request scope
Key: RF-13450
URL: https://issues.jboss.org/browse/RF-13450
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-ScrollableDataTable
Affects Versions: 4.3.4
Environment: java 6 on jboss as 7.1
Reporter: Luca Stancapiano
Attachments: scrollablesample.zip
Here the dataTable with a dataScroller:
<rich:dataScroller for="table" maxPages="5"
page="#{currentPage.page}" />
<rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
id="table" rows="10">
<rich:column>
<f:facet name="header">
<h:outputText value="Vendor " />
</f:facet>
<h:outputText value="#{car.vendor}" />
</rich:column>
...
</rich:dataTable>
Here the definition of the currentPage bean:
<managed-bean>
<managed-bean-name>currentPage</managed-bean-name>
<managed-bean-class>prova.CurrentPage</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
Here the currentPage bean:
package prova;
import javax.enterprise.context.RequestScoped;
import javax.inject.Named;
@Named
@RequestScoped
public class CurrentPage {
private int page = 1;
public int getPage() {
return page;
}
public void setPage(int page) {
this.page = page;
}
}
the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok
--
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