[JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms
by Holger Walter (JIRA)
[ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.s... ]
Holger Walter updated RF-13408:
-------------------------------
Description:
When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener)
Is it possible to reduce this timeout, or make it configurable via properties
was:
When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js ,
> ExtendedDataTable, ajax loading delay of 1000ms
> -----------------------------------------------
>
> Key: RF-13408
> URL: https://issues.jboss.org/browse/RF-13408
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Holger Walter
>
> When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
> I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener)
> Is it possible to reduce this timeout, or make it configurable via properties
--
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, 4 months
[JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms
by Holger Walter (JIRA)
[ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.s... ]
Holger Walter updated RF-13408:
-------------------------------
Description:
When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js ,
was:
When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js
> ExtendedDataTable, ajax loading delay of 1000ms
> -----------------------------------------------
>
> Key: RF-13408
> URL: https://issues.jboss.org/browse/RF-13408
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Holger Walter
>
> When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
> I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js ,
--
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, 4 months
[JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms
by Holger Walter (JIRA)
[ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.s... ]
Holger Walter updated RF-13408:
-------------------------------
Affects Version/s: 4.3.4
> ExtendedDataTable, ajax loading delay of 1000ms
> -----------------------------------------------
>
> Key: RF-13408
> URL: https://issues.jboss.org/browse/RF-13408
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Holger Walter
>
> When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
> I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js
--
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, 4 months
[JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms
by Holger Walter (JIRA)
[ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.s... ]
Holger Walter updated RF-13408:
-------------------------------
Description:
When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js
> ExtendedDataTable, ajax loading delay of 1000ms
> -----------------------------------------------
>
> Key: RF-13408
> URL: https://issues.jboss.org/browse/RF-13408
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Holger Walter
>
> When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
> I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js
--
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, 4 months
[JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13400:
----------------------------------
There is only {{r:pickList}} on the page.
IMHO it is not caused by any other component, because as it is said in description the shrinking works on desktop browser when it changes its size. Is my assumption right ?
> PickList from Metamer is not responsive on real mobile device
> -------------------------------------------------------------
>
> Key: RF-13400
> URL: https://issues.jboss.org/browse/RF-13400
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Juraj Húska
> Priority: Critical
>
> PickList in the _Metamer_ demo is not responsive at all on real mobile device.
> When changing the size of the desktop browser screen it works correctly.
> Note that RichWidgets are responsive correctly on mobile devices.
--
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, 4 months
[JBoss JIRA] (RF-4308) rich:pickList: keep sort order of source list after add/remove operations
by Val Blant (JIRA)
[ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.sy... ]
Val Blant edited comment on RF-4308 at 12/3/13 6:44 PM:
--------------------------------------------------------
I have an easy fix for this problem that seems to work pretty well. Just include this _orderedPickListFix.js_ in your app, and the pickLists should start behaving.
{code:javascript|title=orderedPickListFix.js|borderStyle=solid}
/**
* This is an extension to the RichFaces PickList that preserves the original order of items in the source list
*
* @author Val Blant
*/
if ( typeof window.RichFaces.ui.List != 'undefined' && !window.PickListExtension ) {
window.PickListExtension = {};
if ( typeof window.RichFaces.ui.PickList != 'undefined' ) {
/**
* Overriding original constructor found in "org.richfaces/pickList.js" resource
*/
window.RichFaces.ui.PickList = function(oldPickListConstructor) {
return function(id, options) {
// Instantiate the original PickList
//
var pickList = new oldPickListConstructor(id, options);
// Assign item indecies to each item in the source list to preserve original order
//
pickList.sourceList.items.each(function( index ) {
this.itemIndex = index;
});
return pickList;
};
}(window.RichFaces.ui.PickList);
}
/**
* Original code taken from "org.richfaces/list.js" resource
*/
(function($, rf, list) {
/**
* Insert items into a pick list according to their original order stored in 'itemIndex' attribute
*/
list.prototype.addItems = function(items) {
var parentContainer = this.scrollContainer;
items.each(function() {
if ( parentContainer.children().length <= this.itemIndex ) {
parentContainer.append(this);
}
else {
itemAtOurIndex = parentContainer.children()[this.itemIndex];
jQuery(this).insertBefore( itemAtOurIndex );
}
});
this.__updateItemsList();
rf.Event.fire(this, "additems", items);
};
}(jQuery, window.RichFaces, window.RichFaces.ui.List));
}
{code}
was (Author: vace117):
I have an easy fix for this problem that seems to work pretty well. Just include this _orderedPickListFix.js_ in your app, and the pickLists should start behaving.
{code:javascript|title=orderedPickListFix.js|borderStyle=solid}
/**
* This is an extension to the RichFaces PickList that preserves the original order of items in the source list
*
* @author Val Blant
*/
if ( typeof window.RichFaces.ui.List != 'undefined' && !window.PickListExtension ) {
window.PickListExtension = {};
if ( typeof window.RichFaces.ui.PickList != 'undefined' ) {
/**
* Overriding original constructor found in "org.richfaces/pickList.js" resource
*/
window.RichFaces.ui.PickList = function(oldPickListConstructor) {
return function(id, options) {
// Instantiate the original PickList
//
var pickList = new oldPickListConstructor(id, options);
// Assign item indecies to each item in the source list to preserve original order
//
pickList.sourceList.items.each(function( index ) {
this.itemIndex = index;
});
return pickList;
};
}(window.RichFaces.ui.PickList);
}
/**
* Original code taken from "org.richfaces/list.js" resource
*/
(function($, rf, list) {
/**
* Insert items into a pick list according to their original order stored in 'itemIndex' attribute
*/
list.prototype.addItems = function(items) {
var parentContainer = this.scrollContainer;
items.each(function() {
if ( parentContainer.children().length < this.itemIndex ) {
parentContainer.append(this);
}
else {
itemAtOurIndex = parentContainer.children()[this.itemIndex];
jQuery(this).insertBefore( itemAtOurIndex );
}
});
this.__updateItemsList();
rf.Event.fire(this, "additems", items);
};
}(jQuery, window.RichFaces, window.RichFaces.ui.List));
}
{code}
> rich:pickList: keep sort order of source list after add/remove operations
> -------------------------------------------------------------------------
>
> Key: RF-4308
> URL: https://issues.jboss.org/browse/RF-4308
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 3.2.2, 4.3.4, 5.0.0.Alpha1
> Reporter: Martin Höller
> Labels: low_hanging_fruit, order, picklist, sort
> Fix For: 5-Tracking
>
>
> When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user.
> My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting.
--
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, 4 months
[JBoss JIRA] (RF-12062) a4j:outputMedia does not reRender in Firefox 11
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12062?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12062:
-------------------------------
Description:
a4j:outputMedia does not reRender in Firefox 11. The following error appears:
{quote}
ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BPM-Process].[default]] Servlet.service() for servlet default threw exception: javax.faces.FacesException: Error decode resource data
at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:627) [:3.3.3.Final]
at org.ajax4jsf.resource.ResourceBuilderImpl.getResourceDataForKey(ResourceBuilderImpl.java:371) [:3.3.3.Final]
at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:156) [:3.3.3.Final]
at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) [:3.3.3.Final]
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) [:3.3.3.Final]
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [:2.2.2.Final]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final]
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.2.Final]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [:2.2.2.Final]
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final]
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.1.0.Final]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final]
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final]
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final]
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final]
at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final]
at java.lang.Thread.run(Unknown Source) [:1.6.0_31]
Caused by: java.util.zip.DataFormatException: invalid bit length repeat
at java.util.zip.Inflater.inflateBytes(Native Method) [:1.6.0_31]
at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31]
at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31]
at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:621) [:3.3.3.Final]
... 30 more
{quote}
The picture is not visible. But if you refresh the site with f5, there is no error and all works great.
was:
a4j:outputMedia does not reRender in Firefox 11. The following error appears:
ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BPM-Process].[default]] Servlet.service() for servlet default threw exception: javax.faces.FacesException: Error decode resource data
at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:627) [:3.3.3.Final]
at org.ajax4jsf.resource.ResourceBuilderImpl.getResourceDataForKey(ResourceBuilderImpl.java:371) [:3.3.3.Final]
at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:156) [:3.3.3.Final]
at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) [:3.3.3.Final]
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) [:3.3.3.Final]
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [:2.2.2.Final]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final]
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.2.Final]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [:2.2.2.Final]
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final]
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.1.0.Final]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final]
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final]
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final]
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final]
at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final]
at java.lang.Thread.run(Unknown Source) [:1.6.0_31]
Caused by: java.util.zip.DataFormatException: invalid bit length repeat
at java.util.zip.Inflater.inflateBytes(Native Method) [:1.6.0_31]
at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31]
at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31]
at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:621) [:3.3.3.Final]
... 30 more
The picture is not visible. But if you refresh the site with f5, there is no error and all works great.
> a4j:outputMedia does not reRender in Firefox 11
> ------------------------------------------------
>
> Key: RF-12062
> URL: https://issues.jboss.org/browse/RF-12062
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 3.3.3.Final
> Environment: JBoss AS 6
> Reporter: Toni Neubert
> Labels: a4j, outputmedia, richfaces
> Fix For: 3.Future
>
> Attachments: richfaces-impl-3.3.3.Final.jar, WebXml.patch
>
>
> a4j:outputMedia does not reRender in Firefox 11. The following error appears:
> {quote}
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BPM-Process].[default]] Servlet.service() for servlet default threw exception: javax.faces.FacesException: Error decode resource data
> at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:627) [:3.3.3.Final]
> at org.ajax4jsf.resource.ResourceBuilderImpl.getResourceDataForKey(ResourceBuilderImpl.java:371) [:3.3.3.Final]
> at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:156) [:3.3.3.Final]
> at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) [:3.3.3.Final]
> at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) [:3.3.3.Final]
> at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [:2.2.2.Final]
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final]
> at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.2.Final]
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final]
> at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [:2.2.2.Final]
> at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.2.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final]
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.1.0.Final]
> at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final]
> at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final]
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final]
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final]
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final]
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final]
> at java.lang.Thread.run(Unknown Source) [:1.6.0_31]
> Caused by: java.util.zip.DataFormatException: invalid bit length repeat
> at java.util.zip.Inflater.inflateBytes(Native Method) [:1.6.0_31]
> at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31]
> at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31]
> at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:621) [:3.3.3.Final]
> ... 30 more
> {quote}
> The picture is not visible. But if you refresh the site with f5, there is no error and all works great.
--
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, 4 months