November 2016 - beanvalidation-dev

by Otávio Gonçalves de Santana

I sent to adopt JSR email list and share it on social media. https://twitter.com/otaviojava/status/776549007799701504 On 15 Sep 2016 12:00, "Otávio Gonçalves de Santana" < otaviopolianasantana(a)gmail.com> wrote: > Nice form!! > I'm sharing it in adopt JSR program email list. > > On 15 Sep 2016 03:46, "Gunnar Morling" <gunnar(a)hibernate.org> wrote: > >> Hi, >> >> I've created a survey using Google Forms on our blog (staging atm.): >> http://staging.beanvalidation.org/news/2016/09/15/ >> which-constraints-to-add/ >> >> Feedback welcome. Unless I hear back otherwise, I'll push it to the >> production site tomorrow and then let's announce it on Twitter to get some >> answers. I'd leave it open for two weeks (allowing people to reply after J1 >> which is next week), which should be plenty of time. >> >> One question I have is should we allow anonymous voting or require >> logging in via Google. The latter prevents double votes, but it raises the >> level for participation and don't think people feel motivated to vote >> several times on this topic really. >> >> Andy thoughts? >> >> Thanks, >> >> --Gunnar >> >> >> 2016-09-14 12:02 GMT+02:00 Marco Molteni <moltenma(a)gmail.com>: >> >>> I agree about @Length. It was listed only because of the frequency. I'd >>> limit the addition to @NotBlank and @NotEmpty. >>> >>> On Wed, Sep 14, 2016 at 11:52 AM, Gunnar Morling <gunnar(a)hibernate.org> >>> wrote: >>> >>>> Btw. I don't see a strong reason for @Length, as we have @Size in the >>>> spec for it already. >>>> >>>> I think it's commonly used in older applications which migrated from HV >>>> 3.x (proprietary API) to HV 4.x (BV RI) and kept using the legacy >>>> constraint instead of using the spec'-ed @Size. >>>> >>>> 2016-09-14 11:48 GMT+02:00 Gunnar Morling <gunnar(a)hibernate.org>: >>>> >>>>> Hi, >>>>> >>>>> I like the idea of collecting some more feedback from the community. >>>>> >>>>> A blog post may be an option, though I reckon feedback will be sparse >>>>> based on previous experiences. I'd rather do a survey as it's more >>>>> actionable for people. Either on Twitter (though that seems a bit limited) >>>>> or using Google Forms [1], which is my preference. >>>>> >>>>> I'll prepare something and share it with you soon. If the survey looks >>>>> good, we can promote it on Twitter and during the Hackergarten at J1 (of >>>>> course talking to people in person there will be a great chance to learn >>>>> about their wishes, too). >>>>> >>>>> It'd be nice if we got some insight from that. >>>>> >>>>> Cheers, >>>>> >>>>> --Gunnar >>>>> >>>>> [1] https://docs.google.com/forms/ >>>>> >>>>> >>>>> 2016-09-09 11:34 GMT+02:00 Marco Molteni <moltenma(a)gmail.com>: >>>>> >>>>>> Hi all, >>>>>> >>>>>> which is the best / common way to get a representative feedback >>>>>> according to your experience? >>>>>> Thanks! >>>>>> >>>>>> On Thu, Sep 8, 2016 at 7:44 AM, Christian Kaltepoth < >>>>>> christian(a)kaltepoth.de> wrote: >>>>>> >>>>>>> I also think that adding the most popular 3rd party constraints >>>>>>> directly to the spec is a good thing. Especially @NotBlank and @NotEmpty. >>>>>>> >>>>>>> However, I also agree that it would be nice to gather more feedback >>>>>>> from the community to learn which constraints people would like to see in >>>>>>> the spec. >>>>>>> >>>>>>> 2016-09-06 20:50 GMT+02:00 Michael Nascimento <misterm(a)gmail.com>: >>>>>>> >>>>>>>> +1 to including them. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Michael >>>>>>>> >>>>>>>> On Mon, Aug 22, 2016 at 2:37 PM, Marco Molteni <moltenma(a)gmail.com> >>>>>>>> wrote: >>>>>>>> > Hi all, >>>>>>>> > >>>>>>>> > It would be possible to add some built-in constraints to the V >>>>>>>> 2.0? >>>>>>>> > >>>>>>>> > @NotBlank, @NotEmpty, @Length are used very often in projects, >>>>>>>> they are >>>>>>>> > already present in Hibernate Validator and their implementation >>>>>>>> is well >>>>>>>> > defined. >>>>>>>> > >>>>>>>> > What do you think? >>>>>>>> > >>>>>>>> > Here a list of the most used constraint for GitHub's projects >>>>>>>> (the numbers >>>>>>>> > change at every request but you get the idea. HV = Hibernate >>>>>>>> Validator, BV = >>>>>>>> > Bean Validation): >>>>>>>> > >>>>>>>> > 189'143 - BV - NotNull >>>>>>>> > 56'902 - BV - Size >>>>>>>> > 39'551 - HV - NotEmpty <- >>>>>>>> > 20'687 - HV - NotBlank <- >>>>>>>> > 17'735 - BV - Pattern >>>>>>>> > 16'763 - HV - Email >>>>>>>> > 16'033 - BV - Min >>>>>>>> > 12'769 - HV - Length <- >>>>>>>> > 7'806 - BV - Digits >>>>>>>> > 4'982 - BV - Max >>>>>>>> > 4'971 - BV - Past >>>>>>>> > 3'598 - BV - DecimalMin >>>>>>>> > 2'753 - BV - AssertTrue >>>>>>>> > 2'379 - BV - DecimalMax >>>>>>>> > 2'308 - BV - Future >>>>>>>> > 1'999 - HV - Range >>>>>>>> > 1'497 - HV - URL >>>>>>>> > < 1'000 other constraints >>>>>>>> > >>>>>>>> > Thanks >>>>>>>> > >>>>>>>> > Cheers >>>>>>>> > >>>>>>>> > Marco >>>>>>>> > >>>>>>>> > >>>>>>>> > _______________________________________________ >>>>>>>> > beanvalidation-dev mailing list >>>>>>>> > beanvalidation-dev(a)lists.jboss.org >>>>>>>> > https://lists.jboss.org/mailman/listinfo/beanvalidation-dev >>>>>>>> _______________________________________________ >>>>>>>> beanvalidation-dev mailing list >>>>>>>> beanvalidation-dev(a)lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Christian Kaltepoth >>>>>>> Blog: http://blog.kaltepoth.de/ >>>>>>> Twitter: http://twitter.com/chkal >>>>>>> GitHub: https://github.com/chkal >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> beanvalidation-dev mailing list >>>>>>> beanvalidation-dev(a)lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> beanvalidation-dev mailing list >>>>>> beanvalidation-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev >>>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> beanvalidation-dev mailing list >>>> beanvalidation-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev >>>> >>> >>> >>> _______________________________________________ >>> beanvalidation-dev mailing list >>> beanvalidation-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev >>> >> >> >> _______________________________________________ >> beanvalidation-dev mailing list >> beanvalidation-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev >> >

7 years, 1 month

6
12
0 / 0

Support for constraints on container values (e.g. Collection<@Email String>)

by Emmanuel Bernard

Hi all, I and a few others have been working on a proposal to support things like Collection<@Email String> and Optional<@Email String>. This is more complicated that it seems at first glance. Instead of doing an ad-hoc support for the various collection types, Optional and the JavaFX Properties, we quickly decided to define the notion of container and the ability to declare constraints on contained elements to validate them. This lead to two main proposals that you can read at http://beanvalidation.org/proposals/BVAL-508/ This is a relatively long read, you can start by ignoring "alternative" options for your first pass. We are very interested in feedback at this stage as we have been pushing these proposal very far already and they would need to become part of the spec as next step. Let me know of what you think, questions, remarks etc. In particular, I'm interested in what you think of the following. The capability to define custom containers. The extractor approach vs its alternative. The concepts of @ConstraintsAppliesTo(COMTAINED) used for JavaFX and for subclasses of containers. @Valid, in particular the legacy and new forms and how to handle the transition. And finally, but a big one, what do you think of proposal 1 vs proposal 2. The latter being more generic but with more open questions (and a less elaborated at this stage). Emmanuel

7 years, 5 months

8
38
0 / 0

Glossary

by Emmanuel Bernard

If like me, you can’t remember how these class Foo<F> and other List<@Email String> and other generics soup ingredients are named, there is a glossary of how we use these terms in Bean Validation http://beanvalidation.org/glossary/

7 years, 5 months

1
0
0 / 0

The GitHub Team

by Hendrik Ebbers

Hi all, currently all JBV repos are part of https://github.com/beanvalidation which is really great. 3 people are part of this team at GitHub and I asked myself if I can become member of the team, too. In addition I think that we need a logo for the JSR :) We could use this at Github, Twitter & beanvalidation.org <http://beanvalidation.org/>. I know an illustrator that did a lot of Java-related images for me. If you know the JavaOne voting machines: He created all the duke animations (http://www.guigarage.com/2016/01/the-javaone-voting-machine/). I would love to ask him for a logo for the JRS. Currently I’m thinking about a Duke that stamps beans. What do you think? Cheers, Hendrik

7 years, 5 months

3
8
0 / 0

Proposal for supporting new Java 8 date/time types

by Gunnar Morling

Hi, I've pushed another proposal to the website [1], it's about adding @Past/@Future support for the date/time types added in Java 8 (java.time.* package, added by JSR 310). The proposal essentially standardizes the proprietary support we had in HV, plus some additions. Please let me know what you think, especially on the questions towards the end. Either put comments inline on the source on GitHub [2] or let's have a discussion here. I haven't been using JSR 310 extensively myself, so any feedback by those who have is more than welcome. Thanks, --Gunnar [1] http://beanvalidation.org/proposals/BVAL-496/ [2] https://github.com/beanvalidation/beanvalidation.org/blob/production/prop...

7 years, 5 months

9
31
0 / 0

BVAL-214 Sample

by Hendrik Ebbers

Hi all, I created a small JavaFX as a playground for proposal BVAL-214. I already added a dummy implementation for my idea (see http://beanvalidation.org/proposals/BVAL-214/#proposition-2). You can find the sources here: https://github.com/guigarage/BeanValidationForUI <https://github.com/guigarage/BeanValidationForUI> I added a dummy implementation for the validation API and the sample can simply be started by the com.guigarage.validation.Demo class I will add some doc later to describe my ideas. Cheers, Hendrik

7 years, 5 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

beanvalidation-dev November 2016