Not a problem. My example was picking up org.apache.bval.jsr303.* (in OpenEJB)
instead of the hibernate validator. When I fixed the classpath the problem went
away. It doesn't fully explain the symptoms I described, but for now I'm happy.
On 16/05/2013, at 1:04 AM, Geoff Callender wrote:
> Nor
Igor Drobiazko wrote
>
> Tapestry provides its own MessageInterpolator which is the wrapper around
> the default one. Tapestry's interpolator is using ThreadLocale#getLocale()
> in MessageInterpolator#interpolate without Locale parameter. Check this
> out.
>
> https://svn.apache.org/repos/asf/ta
Tapestry provides its own MessageInterpolator which is the wrapper around
the default one. Tapestry's interpolator is using ThreadLocale#getLocale()
in MessageInterpolator#interpolate without Locale parameter. Check this out.
https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk/tapestry-beanv
You are missing the tapestry-beanvalidator in your gradle build file
/Serge
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Bean-Validation-tp6726904p6729278.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
-
yep, JSR 303 since 5.2 and JSR 330 since 5.3
On Fri, Aug 26, 2011 at 5:05 PM, Werner Keil wrote:
> Great to hear, the JSR is fully supported.
>
> Is Tapestry 5.2 or 5.3 also compatible with JSR 330 instead of declaring
> its
> own @Inject?
>
> --
>
> Werner Keil | UOMo Lead | Eclipse.org
>
> T
Yes from 5.3 you can use javax.inject.Inject
http://blog.tapestry5.de/index.php/2011/08/22/tapestry-5-3-preview/
On Fri, Aug 26, 2011 at 8:35 PM, Werner Keil wrote:
> Great to hear, the JSR is fully supported.
>
> Is Tapestry 5.2 or 5.3 also compatible with JSR 330 instead of declaring its
> o
Great to hear, the JSR is fully supported.
Is Tapestry 5.2 or 5.3 also compatible with JSR 330 instead of declaring its
own @Inject?
--
Werner Keil | UOMo Lead | Eclipse.org
Twitter @wernerkeil | Skype: werner.keil | www.eclipse.org/uomo |
#EclipseUOMo
* JavaOne: October 2-6 2011, San Franc
tapestry-beanvalidator depends only on JSR 303 specification. You need to
drop an implementation of the specification (like Hibernate Validator) on
the classpath. It is not provided by Tapestry.
Regarding contribution to BeanValidatorSource: you don't need to contribute
anything in order to bootst
