June 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12950) Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12950?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12950: ------------------------------- Fix Version/s: 4.5.0.Beta1 (was: 4.5.0.Alpha3) > Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests > ------------------------------------------------------------------------------------------------------ > > Key: RF-12950 > URL: https://issues.jboss.org/browse/RF-12950 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Smoke tests should verify that basic showcase functionality works as expected. > Full showcase test suite can be moved into RF5 repository then. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13654) Port photoalbum changes from 4.3.x

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13654?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13654: ------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > Port photoalbum changes from 4.3.x > ---------------------------------- > > Key: RF-13654 > URL: https://issues.jboss.org/browse/RF-13654 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha4 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha4 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-13648: ---------------------------------- You can workaround the problem in your example project for example by altering the setter method for the {{swift}} bean property, like: {code} public void setSwiftCode(String swiftCode) { if(swiftCode == null || swiftCode.isEmpty()) { this.swiftCode = null; } else { this.swiftCode = swiftCode; } } {code} > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj Húska > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.s... ] Juraj Húska edited comment on RF-13648 at 6/3/14 8:31 AM: ---------------------------------------------------------- You can workaround the problem in your example project for example by altering the setter method for the {{swift}} bean property, like: {code} public void setSwiftCode(String swiftCode) { if(swiftCode == null || swiftCode.isEmpty()) { this.swiftCode = null; } else { this.swiftCode = swiftCode; } } {code} was (Author: jhuska): You can workaround the problem in your example project for example by altering the setter method for the {{swift}} bean property, like: {code} public void setSwiftCode(String swiftCode) { if(swiftCode == null || swiftCode.isEmpty()) { this.swiftCode = null; } else { this.swiftCode = swiftCode; } } {code} > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj Húska > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.s... ] Juraj Húska resolved RF-13648. ------------------------------ Resolution: Rejected > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj Húska > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-13648: ---------------------------------- Thank you [~tony.cramer] for the reproducer. However, I need to repeat my previous conclusion. The behavior is expected, and it is defined in EL specification. It worked prior Tomcat 8.0.8 because there was a [bug|https://issues.apache.org/bugzilla/show_bug.cgi?id=56522#c1] in jasper, which is now fixed and meets the EL spec. There is an [issue|https://java.net/jira/browse/EL_SPEC-18] filed for EL spec though, which should address your problem. This is not a RichFaces bug. > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj Húska > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-13648: ----------------------------- Labels: (was: waiting_on_user) > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj Húska > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13656) Table collapse after tab change

by André Faber (JIRA)

[ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.s... ] André Faber updated RF-13656: ----------------------------- Attachment: screenshot-2.jpg After changing the tab, the table is "collapsed" (also if I switch back, the other table is shown the same way) > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Reporter: André Faber > Labels: 4.3.7, colapse, rich:extenedDataTable, rich:tabPanel, richfaces > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13656) Table collapse after tab change

by André Faber (JIRA)

[ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.s... ] André Faber updated RF-13656: ----------------------------- Attachment: screenshot-1.jpg At the begin all looks good > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Reporter: André Faber > Labels: 4.3.7, colapse, rich:extenedDataTable, rich:tabPanel, richfaces > Attachments: screenshot-1.jpg > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13656) Table collapse after tab change

by André Faber (JIRA)

[ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.s... ] André Faber reopened RF-13656: ------------------------------ > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Reporter: André Faber > Labels: 4.3.7, colapse, rich:extenedDataTable, rich:tabPanel, richfaces > Attachments: screenshot-1.jpg > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues June 2014