Proposal for method validation on beanvalidation.org
by Gunnar Morling
Hi all,
I've pushed now a first version of the proposal for method validation
(BV-241) to beanvalidation.org [1].
The proposal is still missing some parts (e.g. the XML configuration),
but I hope it touches all major issues related to method validation.
Throughout the document I've used the "DISCUSSION" marker for sections
which still need further consideration or a decision between several
possible options.
I'd be very happy on any feedback related to these issues in
particular but of course also to the complete proposal in general.
Don't hesitate to speak up in case you think anything is incomplete,
is missing or something doesn't make sense to you; after all this is
very much work in progress. Feel free to add remarks in place within
the document or start a dedicated discussion on the mailing list.
--Gunnar
[1] http://beanvalidation.org/proposals/BVAL-241/
11 years, 3 months
JavaEE Platform Annotation rules.
by Edward Burns
Hello Experts,
The discussion in this list about annotation inheritance and method
level validation reminded me of this collection of rules to that effect,
so, here they are.
I want to bring to your attention this document from JavaEE platform
architect Bill Shannon about annotations.
From: Bill Shannon
B> I've written up a set of "meta-rules" for annotations, that is,
B> rules for how annotations should be defined to work. These rules
B> collect together information that is in some of our specs while
B> also providing some of the design principles we had in mind when
B> we first started using annotations.
B> Of course, there's also a bunch of exceptions and special cases
B> that I've tried to document.
B> http://java.net/projects/javaee-spec/pages/AnnotationRules
B> Your feedback is encouraged, either privately or on the list.
B> Feel free to forward this message to other experts and expert groups.
Ed
--
| edward.burns(a)oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/
11 years, 3 months
BVAL-263 ValidatorFactory.close()
by Emmanuel Bernard
To support dependency injection, we need a close event at the ValidatorFactory level to properly release managed beans. I can imagine other resources could benefit from this close operation as well.
I'm working toward adding it to the spec but I am wondering whether or not we need a companion isClosed() method to the ValidatorFactory. Do you see situations where you would need this information (as container developer, framework developer or mere user of Bean Validation)?
Emmanuel
11 years, 3 months
