[
http://opensource.atlassian.com/projects/hibernate/browse/HV-402?page=com...
]
Gunnar Morling commented on HV-402:
-----------------------------------
Right, there is no problem if ValueMessageInterpolator is not explicitely configured.
But there is a problem, if you do want to work with ValueMessageInterpolator but only want
to use the toString() approach (and not the scripting one) for the interpolation of the
validated value. This is because this class can't be loaded by the JVM when running on
JDK 5 (and not having a JSR 223 implementation on the classpath) due to the imports from
javax.script.*
So if I'm not mistaken one always needs a JSR 223 implementation to use
ValueMessageInterpolator although not actually using scripting interpolation.
We had a similar issue (HV-302), where JAXB was always required, also if no XML
configuration was used. This was solved by only loading those classes importing from
javax.xml.bind.* if actually required.
To confirm, one would need to configure ValueMessageInterpolator and test a toString()
interpolation, which currently is expected to fail on JDK 5.
Make sure that Validator still works on JDK 5 due to
ValueMessageInterpolator
-----------------------------------------------------------------------------
Key: HV-402
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-402
Project: Hibernate Validator
Issue Type: Bug
Components: documentation, engine
Affects Versions: 4.1.0.Final
Reporter: Hardy Ferentschik
Assignee: Hardy Ferentschik
Fix For: 4.2.0.Beta1
{{ValueMessageInterpolator}} requires the JSR 223 scripting API. We have to make sure
that this does not cause any problems on a Java 5 runtime. However, since you have to
explicitly configure this interpolator. We have to confirm that though.
We probably need a note in the documentation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira