[JBoss JIRA] (RF-13656) Table collapse after tab change
by André Faber (JIRA)
André Faber created RF-13656:
--------------------------------
Summary: 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
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)
9 years, 10 months
[JBoss JIRA] (RF-13655) Popup Panel autosize does not work when its content is dynamically updated
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13655?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13655:
------------------------------------
Note that in 4.3.6 the auto-resizing was done by browser - i.e. there is no code being executed - and it doesn't resize the panel shadow so we can't simply go back to that. In 4.3.7 we opted for assigning a fixed width so it doesn't change if the content changes (though it works fine for RF-13616).
> Popup Panel autosize does not work when its content is dynamically updated
> --------------------------------------------------------------------------
>
> Key: RF-13655
> URL: https://issues.jboss.org/browse/RF-13655
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.7
> Reporter: Juraj Húska
> Labels: regression
>
> When Popup Panel has dynamically rendered content, e.g. {{rich:dataTable}} with dynamically added rows, then its auto-size functionality cease to work.
> Please see the steps to reproduce. It is a regression against 4.3.6.Final.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 10 months
[JBoss JIRA] (RF-13655) Popup Panel autosize does not work when its content is dynamically updated
by Juraj Húska (JIRA)
Juraj Húska created RF-13655:
--------------------------------
Summary: Popup Panel autosize does not work when its content is dynamically updated
Key: RF-13655
URL: https://issues.jboss.org/browse/RF-13655
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-output
Affects Versions: 4.3.7
Reporter: Juraj Húska
When Popup Panel has dynamically rendered content, e.g. {{rich:dataTable}} with dynamically added rows, then its auto-size functionality cease to work.
Please see the steps to reproduce. It is a regression against 4.3.6.Final.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 10 months
[JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored
by Tony Cramer (JIRA)
[ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.s... ]
Tony Cramer commented on RF-13648:
----------------------------------
Simple demo project attached.
> 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
> Labels: waiting_on_user
> 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)
9 years, 10 months
[JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored
by Tony Cramer (JIRA)
[ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.s... ]
Tony Cramer updated RF-13648:
-----------------------------
Description:
{{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
was:
{{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 included (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
> 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
> Labels: waiting_on_user
> 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)
9 years, 10 months
[JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored
by Tony Cramer (JIRA)
[ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.s... ]
Tony Cramer updated RF-13648:
-----------------------------
Description:
{{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 included (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
was:
{{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
> 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
> Labels: waiting_on_user
> 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 included (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)
9 years, 10 months