[
https://issues.jboss.org/browse/RF-12700?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12700:
---------------------------------
{{FacesValidatorServiceImpl}} used hard-coded values for {{LongRangeValidator}} min/max
limits which determined what message key to use.
I have replaced it with inferring limits from default LongRangeValidator state.
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: Component Upgrade
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