January 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-8206) remove all session scoped bindings from richfaces-demo

by Ilya Shaikovsky (JIRA)

remove all session scoped bindings from richfaces-demo ------------------------------------------------------ Key: RF-8206 URL: https://jira.jboss.org/jira/browse/RF-8206 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: examples Affects Versions: 3.3.2.SR1 Reporter: Ilya Shaikovsky Assignee: Ilya Shaikovsky Fix For: 3.3.3.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (RF-8249) Calendar: Incorrect week numbering for first and last week of year

by Mareks Tumass (JIRA)

Calendar: Incorrect week numbering for first and last week of year ------------------------------------------------------------------ Key: RF-8249 URL: https://jira.jboss.org/jira/browse/RF-8249 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.2.GA Reporter: Mareks Tumass Attachments: weekNumbers.PNG Week numbering in calendar doesn't match: Calendar is opened for december, 2009. First two days of next year january belong to 53 week of 2009, however week starting from 3rd january is marked as 1st week of 2010 year, should be 2nd. When calendar is opened for january, 2010 then week starting from 3rd january is marked as 2nd week of 2010! Week numbering must match. minDaysInFirstWeek=1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
16
0 / 0

[JBoss JIRA] Created: (RF-8304) Scrollable datatable error rendering on ie8

by javier gallegos (JIRA)

Scrollable datatable error rendering on ie8 ------------------------------------------- Key: RF-8304 URL: https://jira.jboss.org/jira/browse/RF-8304 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: browser compatibility Affects Versions: 3.3.3.BETA1 Environment: ie8 8.0.6001.17802 Reporter: javier gallegos Priority: Critical the scrollabledatatable component is misaligned when it's rendered on ie8, the columns are misaligned with the headers of the table -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

5
11
0 / 0

[JBoss JIRA] Created: (RF-8277) ajax4jsf Filter should ignore HTTP 304 and other responses <200 or >299

by Mark Struberg (JIRA)

ajax4jsf Filter should ignore HTTP 304 and other responses <200 or >299 ----------------------------------------------------------------------- Key: RF-8277 URL: https://jira.jboss.org/jira/browse/RF-8277 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 3.3.3.BETA1 Reporter: Mark Struberg It seems the Filter currently tries to reformat the response in any case. But if you e.g. get a HTTP 304 response, this doesn't even have a content body (onyl headers) and wrinting to the response causes an Exception: {noformat} java.lang.IllegalStateException: NO CONTENT at org.mortbay.jetty.HttpGenerator.addContent(HttpGenerator.java:106) at org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:644) at org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:579) at java.io.ByteArrayOutputStream.writeTo(ByteArrayOutputStream.java:109) at org.mortbay.jetty.AbstractGenerator$OutputWriter.write(AbstractGenerator.java:901) at org.mortbay.jetty.AbstractGenerator$OutputWriter.write(AbstractGenerator.java:752) at java.io.PrintWriter.write(PrintWriter.java:412) at java.io.PrintWriter.write(PrintWriter.java:429) at org.ajax4jsf.io.parser.ParsingContext.sendBuffer(ParsingContext.java:118) at org.ajax4jsf.io.parser.ParsingContext.send(ParsingContext.java:131) at org.ajax4jsf.io.parser.FastHtmlParser.parse(FastHtmlParser.java:162) at org.ajax4jsf.io.parser.FastHtmlParser.parseHtml(FastHtmlParser.java:230) at org.ajax4jsf.webapp.FilterServletResponseWrapper.parseContent(FilterServletResponseWrapper.java:594) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:367) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) {noformat} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (RF-8168) Rich:modalPanel and Chrome

by Nicolas Gaudin (JIRA)

Rich:modalPanel and Chrome -------------------------- Key: RF-8168 URL: https://jira.jboss.org/jira/browse/RF-8168 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-panels-layout-themes Affects Versions: 3.3.2.SR1 Environment: Jdk 1.6_7 Glassfih v2.1 Facelets 1.1.14 BROWSER: CHROME Reporter: Nicolas Gaudin Hi, Facing a weird issue with chrome, as my modal Panels are put at the top of the window (centered horizontally). They should be at the middle. Did you face this issue also? Thanks Regards -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (RF-8316) Implement skinning support for datatables

by Andrey Markhel (JIRA)

Implement skinning support for datatables ----------------------------------------- Key: RF-8316 URL: https://jira.jboss.org/jira/browse/RF-8316 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: core Affects Versions: 4.0.0.ALPHA1 Reporter: Andrey Markhel Assignee: Andrey Markhel Fix For: 4.0.0.ALPHA2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-8289) Create CDK Integration Tests

by Alexander Smirnov (JIRA)

Create CDK Integration Tests ---------------------------- Key: RF-8289 URL: https://jira.jboss.org/jira/browse/RF-8289 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: CDK Reporter: Alexander Smirnov Fix For: 4.0.0.ALPHA2 To test CDK as whole solid system, create test progects that use CDK to generate JSF components from: 1) annotated classes 2) faces-config.xml 3) mixed configuration. These projects should be build during "integration-test" phase and have scripts to check what all desired classes have been generated and compiled without errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (RF-8283) AjaxViewRoot is giving misleading information when a component with id from areasToProcess is not found in components tree

by Piotr Witusowski (JIRA)

AjaxViewRoot is giving misleading information when a component with id from areasToProcess is not found in components tree -------------------------------------------------------------------------------------------------------------------------- Key: RF-8283 URL: https://jira.jboss.org/jira/browse/RF-8283 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.BETA1 Reporter: Piotr Witusowski Priority: Minor Around line 248 one can find: {code} Set<String> areasToProcess = ajaxContext.getAjaxAreasToProcess(); if(null != areasToProcess){ for (String areaId : areasToProcess) { boolean areaProcessed = invokeOnComponent(context, areaId, invokerCallback); if(!areaProcessed){ _log.warn("No component found to process for clientId "+ajaxSingleClientId); } } } {code} It gives misleading information that it is component with ajaxSingleClientId missing but actually it is areaId. Consider changing line 254 to: {code} _log.warn("No component found to process for clientId "+areaId); {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-8223) ExtendedDataTable duplicate Id exception

by Alex Kolonitsky (JIRA)

ExtendedDataTable duplicate Id exception ---------------------------------------- Key: RF-8223 URL: https://jira.jboss.org/jira/browse/RF-8223 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: JSF 2.0 Reporter: Alex Kolonitsky Assignee: Alex Kolonitsky For exapmle below <f:view> <h:form id="form"> <rich:extendedDataTable id="table"> <rich:column >Hello</rich:column> </rich:extendedDataTable> </h:form> </f:view> I have exception java.lang.IllegalStateException: duplicate Id for a component form:table:j_id3 org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:68) org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92) org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92) org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92) org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92) org.ajax4jsf.application.AjaxStateManager.getTreeStructureToSave(AjaxStateManager.java:194) org.ajax4jsf.application.AjaxStateManager.buildViewState(AjaxStateManager.java:520) org.ajax4jsf.application.AjaxStateManager.saveSerializedView(AjaxStateManager.java:473) com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:615) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (RF-8218) Conflicting version of commons-beanutils

by Lukas Fryc (JIRA)

Conflicting version of commons-beanutils ---------------------------------------- Key: RF-8218 URL: https://jira.jboss.org/jira/browse/RF-8218 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.BETA1 Reporter: Lukas Fryc Fix For: 3.3.3.CR1 There is conflicting library in richfaces-ui and richfaces-impl through the commons-digester dependency in 3.3.3.BETA1 (Dec 03 release) and also current 3.3.3-SNAPSHOT. (Attached screenshot) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

5
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2010