Validation.properties ResourceBundle and modularity
by Ed Burns
Hello Experts,
I understand this may be off topic, but I am not sure how to best bring
this to your attention, so please excuse this email.
GlassFish uses JSR-303 for ensuring that its configuration information
is valid. In the course of this usage, we ran into an apparent
shortcoming in the JSR-303 spec regarding ClassLoaders and the
Validation.properties ResourceBundle. A succint writeup of the problem
is at [1] but in 140 characters or less, the problem is:
In a MessageInterpolatorImpl, I need a reference to the .class to
which the constraint is applied, *without using payload*.
In other words, can we make the default value of the payload attribute
be the .class to which the constraint is applied?
Thank you,
Ed
[1] http://wikis.sun.com/display/GlassFish/GlassFish+Bean+Validation+Error+Me...
--
| edward.burns(a)oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/
| 4 business days until JSF 2.2 Early Draft Review
| 8 business days until JavaOne 2011
12 years, 7 months
Method level validation
by Emmanuel Bernard
While we still decide what to do in which order, I'd like to start thinking about method level validation in parallel.
Probably the biggest feature for this new round ( http://beanvalidation.org/roadmap/ ) is method level validation.
## Goal
Offer the ability to:
- annotate method and constructor parameters and return values with Bean Validation constraints.
- provide validation methods to validate a method / constructor given a set of parameters
This set of methods will be used by framework controlling the method execution cycle (CDI, JAX-RS, aspect oriented frameworks etc).
https://hibernate.onjira.com/browse/BVAL-232
We need to explore this feature to clarify what we want to support, how we want to support it, how it integrates with Bean Validation 1.0.
## Usefulness
This method will be useful to various other specifications including CDI and JAX-RS. That's why I'd like to stabilize this feature as early as possible.
## Proposals
Hibernate Validator has an implementation of such feature and I am sure OVal, Apache Bean Validation and others have something similar. Let's start with describing what we have and start the discussion from here.
Gunnar, could to take the lead on the Hibernate Validator version? You know this area best.
Emmanuel
12 years, 7 months
Introductions
by Emmanuel Bernard
Let's introduce ourselves. Whether you are an expert group member or want to contribute, please introduce yourself.
Let's start with me.
I am data platform architect at JBoss by Red Hat and member of the Hibernate team.
I have spent a few years in the retail industry as developer and architect and moved in the ORM space. I have lead Hibernate JPA implementation and founded Hibernate Search, Hibernate Validator and Hibernate OGM.
I am a member of the JPA 2.1 expert group and the spec lead of Bean Validation. You can see me speak at various conferences and JUGs, including JavaOne, JBoss World and Devoxx. I am also founder and co-host of two podcasts: JBoss Community Asylum and Les Cast Codeurs Podcast (French).
Emmanuel Bernard
12 years, 7 months
Welcome, infrastructure and presentation
by Emmanuel Bernard
Hello everyone,
Welcome to this group and thanks for joining. I have been waiting for the summer vacations to end before soliciting you. But now is the time to start.
I have been working mainly on the infrastructure of the specification with to goal to streamline our work as much as possible. The goal for this infra is to:
- work the spec in the open
- make contributions as easy as possible
- have me do less work :)
Infrastructure
The spec has:
- a website http://beanvalidation.org
- source repositories https://github.com/beanvalidation (spec, API, TCK and the website itself)
- a mailing list (this one)
- a forum for more casual interactions (not sure it is useful)
- a issue tracker http://beanvalidation.org/issues
All publicly accessible.
The portal for everything Bean Validation is http://beanvalidation.org. People can find the latest news as well as information on how to contribute.
I encourage you to read the contribute section http://beanvalidation.org/contribute. This page (and associated pages) explains how to contribute to the specification document, the API, the TCK, the RI and even the beanvalidation.org website itself. Let me know if you think something needs to be refined and clarified.
Process
I have listed the main goals of this specification in http://beanvalidation.org/roadmap/ but the true source is the issue tracker http://beanvalidation.org/issues.
Our first objective is going to make sure that what we want to do is in JIRA and sort the work in decreasing priority.
Once this settled, I will call for one or two subjects at a given time on which we can brainstorm on this mailing list and or on the issue tracker before converging and writing a proposal (see http://beanvalidation.org/contribute/specification/). I don't have to be the one writing a proposal necessarily.
All of this is a base proposal for our work, we can change it. So feel free to speak up and contribute.
Let the fun start!
Emmanuel Bernard
JBoss by Red Hat
12 years, 7 months
