[JBoss JIRA] (RF-12700) LongRangeValidator client-side messages differs from server-side ones on MyFaces
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12700?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12700:
----------------------------
Issue Type: Bug (was: Component Upgrade)
> LongRangeValidator client-side messages differs from server-side ones on MyFaces
> --------------------------------------------------------------------------------
>
> Key: RF-12700
> URL: https://issues.jboss.org/browse/RF-12700
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators, tests - unit
> Affects Versions: 4.3.0.CR1
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Fix For: 4.3.0.CR1
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.richfaces.javascript.client.validator.LongRangeValidatorTest
> -------------------------------------------------------------------------------
> Tests run: 15, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 4.617 sec <<< FAILURE!
> testValidator[3](org.richfaces.javascript.client.validator.LongRangeValidatorTest) Time elapsed: 0.279 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<[testComponent: Validation Error: Value is less than allowable minimum of '2']> but was:<[: Validation Error: Specified attribute is not between the expected values of 2 and testComponent.]>
> at org.junit.Assert.assertEquals(Assert.java:123)
> at org.junit.Assert.assertEquals(Assert.java:145)
> at org.richfaces.javascript.client.validator.ValidatorTestBase.testValidator(ValidatorTestBase.java:70)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at org.jboss.test.qunit.Qunit$1.evaluate(Qunit.java:139)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> {code}
--
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
11 years, 11 months
[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12670:
----------------------------
Issue Type: Bug (was: Feature Request)
> JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> ---------------------------------------------------------------------------------------------------
>
> Key: RF-12670
> URL: https://issues.jboss.org/browse/RF-12670
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Dupont Dupont
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a
> {code}
> java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387)
> at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIForm.visitTree(UIForm.java:269)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90)
> at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142)
> at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171)
> at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> at
> {code}
> RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor.
> See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288...
--
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
11 years, 11 months
[JBoss JIRA] (RF-12693) Mojarra fails to encode form inputs correctly when they doesn't have name attribute
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12693?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12693:
----------------------------
Summary: Mojarra fails to encode form inputs correctly when they doesn't have name attribute (was: JSF fails to encode form inputs correctly when they doesn't have name attribute)
> Mojarra fails to encode form inputs correctly when they doesn't have name attribute
> -----------------------------------------------------------------------------------
>
> Key: RF-12693
> URL: https://issues.jboss.org/browse/RF-12693
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.0.M3
> Environment: JBoss 7.1.1 with the stock "jsf-impl-2.1.7-jbossorg-2.jar" or upgraded to "jsf-impl-2.1.15.jar"
> Reporter: Justin Rosenberg
> Assignee: Lukáš Fryč
> Fix For: 4.3.0.CR1
>
> Attachments: JSFButtonBug-1.0.0-SNAPSHOT.war, mojarraBug.zip
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> When using the Richfaces a4j:commandButton I get the following stack trace when using Internet Explorer 7. This problem does not occur in IE8+ or Chrome.
> {code}
> 15:19:57,630 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception: java.lang.NullPointerException
> at com.sun.faces.context.PartialViewContextImpl.createPartialResponseWriter(PartialViewContextImpl.java:441) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.context.PartialViewContextImpl.access$300(PartialViewContextImpl.java:71) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.context.PartialViewContextImpl$DelayedInitPartialResponseWriter.getWrapped(PartialViewContextImpl.java:582) [jsf-impl-2.1.15.jar:2.1.15]
> at javax.faces.context.PartialResponseWriter.startDocument(PartialResponseWriter.java:115) [jsf-api-2.1.15.jar:2.1]
> at com.sun.faces.context.AjaxExceptionHandlerImpl.handlePartialResponseError(AjaxExceptionHandlerImpl.java:199) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.context.AjaxExceptionHandlerImpl.handle(AjaxExceptionHandlerImpl.java:124) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.15.jar:2.1.15]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jsf-api-2.1.15.jar:2.1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_20]
> {code}
> I was surprised that this was only an IE7 issue, but I did find that PrimeFaces ran into a similar problem (http://code.google.com/p/primefaces/issues/detail?id=4361).
> Is there a workaround for this? Is this a Mojarra, RichFaces, or JBoss issue?
> I created http://java.net/jira/browse/JAVASERVERFACES-2666 in case this is a Mojarra problem, maybe we could help them resolve the issue.
--
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
11 years, 11 months
[JBoss JIRA] (RF-12691) extendedDataTable: Header facet render problem in RichFaces 4
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/RF-12691?page=com.atlassian.jira.plugin.s... ]
Jan Papousek closed RF-12691.
-----------------------------
Verified.
> extendedDataTable: Header facet render problem in RichFaces 4
> --------------------------------------------------------------
>
> Key: RF-12691
> URL: https://issues.jboss.org/browse/RF-12691
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final
> Reporter: Ilia Vassilev
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
> Attachments: screenshots.zip, testapp.zip
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> extendedDataTable header renders OK if entire table or panel that contains it are rendered. if I render just the header row using render="table@header" format, the header row re-renders, but its format is lost (refer to the attached screenshots). Checkbox in column 1 is the trigger for this issue.
> * Header contains 'select all' checkbox, each data row contains row-level checkbox.
> * Click on data row will rerender the header row and this is event that causes alignment to go off.
> * If I rerender the entire table and/or panel, this does not happen, but causes undesirable performance problems when clicking individual rows in succession due to delays from jsf 2 / richfaces 4 render cycles.
> It looks like the header-only render is trying to do a vertical center of header cell contents while the panel/table render is not, causing the cell contents to slide down vertically in the header cell.
> This problem occurs in every browser I tested: IE 9, Firefox 16, Firefox 17, and Chrome 23.0
--
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
11 years, 11 months
[JBoss JIRA] (RF-12693) JSF fails to encode form inputs correctly when they doesn't have name attribute
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12693?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12693:
----------------------------
Summary: JSF fails to encode form inputs correctly when they doesn't have name attribute (was: a4j:commandButton causes NullPointerException in PartialViewContextImpl for IE7 requests if a <button> is present)
> JSF fails to encode form inputs correctly when they doesn't have name attribute
> -------------------------------------------------------------------------------
>
> Key: RF-12693
> URL: https://issues.jboss.org/browse/RF-12693
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.0.M3
> Environment: JBoss 7.1.1 with the stock "jsf-impl-2.1.7-jbossorg-2.jar" or upgraded to "jsf-impl-2.1.15.jar"
> Reporter: Justin Rosenberg
> Assignee: Lukáš Fryč
> Fix For: 4.3.0.CR1
>
> Attachments: JSFButtonBug-1.0.0-SNAPSHOT.war, mojarraBug.zip
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> When using the Richfaces a4j:commandButton I get the following stack trace when using Internet Explorer 7. This problem does not occur in IE8+ or Chrome.
> {code}
> 15:19:57,630 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception: java.lang.NullPointerException
> at com.sun.faces.context.PartialViewContextImpl.createPartialResponseWriter(PartialViewContextImpl.java:441) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.context.PartialViewContextImpl.access$300(PartialViewContextImpl.java:71) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.context.PartialViewContextImpl$DelayedInitPartialResponseWriter.getWrapped(PartialViewContextImpl.java:582) [jsf-impl-2.1.15.jar:2.1.15]
> at javax.faces.context.PartialResponseWriter.startDocument(PartialResponseWriter.java:115) [jsf-api-2.1.15.jar:2.1]
> at com.sun.faces.context.AjaxExceptionHandlerImpl.handlePartialResponseError(AjaxExceptionHandlerImpl.java:199) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.context.AjaxExceptionHandlerImpl.handle(AjaxExceptionHandlerImpl.java:124) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) [jsf-impl-2.1.15.jar:2.1.15]
> at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.15.jar:2.1.15]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jsf-api-2.1.15.jar:2.1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_20]
> {code}
> I was surprised that this was only an IE7 issue, but I did find that PrimeFaces ran into a similar problem (http://code.google.com/p/primefaces/issues/detail?id=4361).
> Is there a workaround for this? Is this a Mojarra, RichFaces, or JBoss issue?
> I created http://java.net/jira/browse/JAVASERVERFACES-2666 in case this is a Mojarra problem, maybe we could help them resolve the issue.
--
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
11 years, 11 months
[JBoss JIRA] (RF-12691) extendedDataTable: Header facet render problem in RichFaces 4
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/RF-12691?page=com.atlassian.jira.plugin.s... ]
Jan Papousek updated RF-12691:
------------------------------
Labels: (was: needs-qe)
> extendedDataTable: Header facet render problem in RichFaces 4
> --------------------------------------------------------------
>
> Key: RF-12691
> URL: https://issues.jboss.org/browse/RF-12691
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final
> Reporter: Ilia Vassilev
> Assignee: Brian Leathem
> Fix For: 4.3.0.CR1
>
> Attachments: screenshots.zip, testapp.zip
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> extendedDataTable header renders OK if entire table or panel that contains it are rendered. if I render just the header row using render="table@header" format, the header row re-renders, but its format is lost (refer to the attached screenshots). Checkbox in column 1 is the trigger for this issue.
> * Header contains 'select all' checkbox, each data row contains row-level checkbox.
> * Click on data row will rerender the header row and this is event that causes alignment to go off.
> * If I rerender the entire table and/or panel, this does not happen, but causes undesirable performance problems when clicking individual rows in succession due to delays from jsf 2 / richfaces 4 render cycles.
> It looks like the header-only render is trying to do a vertical center of header cell contents while the panel/table render is not, causing the cell contents to slide down vertically in the header cell.
> This problem occurs in every browser I tested: IE 9, Firefox 16, Firefox 17, and Chrome 23.0
--
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
11 years, 11 months