Hibernate Community - Forums > JSR 380 Bean Validation feedback

JSR 380 Bean Validation feedback | Re: Automatic TCK coverage generated based on annotations

Hi Gunnar
Thanks a lot for your reply. I'll check out the links you provided, and ask any futher questions on BV mailing list.

Cheers
Phillip

JSR 380 Bean Validation feedback | BeanValidation 2.0 integration with JavaFX

How do I integrate Bean Validation with JavaFX?

I would like to make abidirectional bind between the entity field and the javaFx controllers. In this scenario how could I validate fields using Bean Validation?

Ex:

Code:

  
public class Category{
    @NotNull(message = "Name can't be null) 
    @Size(max = 255, min=3, message = "Size name must be between 255 and 3")
    private StringProperty name = new SimpleStringProperty();
    //... getters & setters
}

//some fx Controller...
public

...

JSR 380 Bean Validation feedback | Re: @ParameterScriptAssert on Bean Validation 1.1

Good, thank you!

JSR 380 Bean Validation feedback | Re: Bean Validation 2.0 CR3. Medellin JUG Results test

Hi Hilmer,

Thanks for providing feedback on all these issues, that's muchappreciated!

Quote:

Our doubt is why the last one (hilmer@gmail) pass the validation

We consider this in the RI as valid, as e.g. hilmer@localhost would be a valid address. IIUC, single-part domain names are valid (although uncommon). You can add a stricter validation via @Email#regexp().

Quote:

Our doubt is why did the validation take January First 2017 as a value of the present, this test was using Java Server Faces, but We made a second test

...

JSR 380 Bean Validation feedback | Re: Question about Bean Validation 1.1

I would recommend to use a dedicated POJO/DTO for each of the two services. If that's not viable, take a look at group conversion:

Code:

public void service1(@Valid @ConvertGroup(from=Default.class, to=Group1.class) MyDto dto) { ... }

public void service2(@Valid @ConvertGroup(from=Default.class, to=Group2.class) MyDto dto) { ... }

JSR 380 Bean Validation feedback | Re: Test Bean Validation Oracle WebLogic

Hi,

validation-api.jar is just the Bean Validation API. You need a compliant implementation to be able to use the features of Bean Validation 2.0.

At the moment, you are using the implementations provided by the app server which is probably compliant with Bean Validation 1.1 but does not support the new features of Bean Validation 2.0.

To make it work, you would need to override your app server BV implementation with the latest Hibernate Validator 6.0.0.Alpha2 which will be the RI of BV 2.0
...

JSR 380 Bean Validation feedback | Re: @NotNull and @UnwrapValidatedValue

With Hibernate Validator 6.0.0.Alpha2, you can do the following:

@NotNull(payload = Unwrapping.Skip)
private Optional foo;

JSR 380 Bean Validation feedback | Re: Bean validation 2.0 question

Which method on `Validator` are you invoking? I reckon it's validateValue() or validateProperty()? Note that cascaded validation isn't supported for these in the BV spec, although HV (the implementation) is trying to do it. If you file an issue in our JIRA tracker with a small but complete example, we can try and take a look.

Btw. BV 2.0 is in the works currently, HV 5.3.2 implements BV 1.1. We already have experimental support for collection element constraints as you are trying to use them in
...

JSR 380 Bean Validation feedback | Non-empty default groups

I want to make annotations that are already 'grouped' to increase readability (decrease visual noise). The name of the Constraint Annotation is already extremely clear for when the validation willoccur.

Specifically:

Code:

   @RequiredForCreateAttribute
   @UpdatableAttribute(false)
   public String getKey() {
      return key;
   }

is easier to use and read for me than this:

Code:

   @NotNull(groups = CreateValidation.class)
   @Null(groups = UpdateValidation.class)
   public String getKey() {
      return key;
   }

...

JSR 380 Bean Validation feedback | Re: An annotation to reference other object annotations...

Hi,

Could you open an issue at the BV spec tracker (https://hibernate.atlassian.net/browse/BVAL) so the feature can be discussed for inclusion in a future BV revision?

One way you could solve your problem already today would be to query the constraint metadata (see Validator#getConstraintsForClass()) of one model and use that to drive dynamic creation of equivalent constraints on the other model using the Hibernate Validator API for programmatic constraint declaration (see http://docs.jboss.org/hibernate/validator/5.2/reference/en-US/html_single/#section-programmatic-api).

Hth,

--GUnnar
...