Databases
StackOverflow2013
Postsdbo
POMultiple beans validation inside containing bean with different group interfaces
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMultiple beans validation inside containing bean with different group interfaces
    primarykey
    data
    text
    <p>I have problem with validation a very specific beans. Let me give you some code first:</p> <pre><code>@Entity @Table(name = "customers", schema = "public", uniqueConstraints = @UniqueConstraint(columnNames = {"cus_email" })) public class Customers extends ModelObject implements java.io.Serializable { private static final long serialVersionUID = -3197505684643025341L; private long cusId; private String cusEmail; private String cusPassword; private Addresses shippingAddress; private Addresses invoiceAddress; @Id @Column(name = "cus_id", unique = true, nullable = false) @SequenceGenerator(name = "cus_seq", sequenceName = "customers_cus_id_seq", allocationSize = 1) @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "cus_seq") @NotNull public long getCusId() { return cusId; } public void setCusId(long cusId) { this.cusId = cusId; } @NotEmpty @Size(min=5, max=255) @Email @Column(name = "cus_email", unique = true, nullable = false, length = 255) public String getCusEmail() { return cusEmail; } public void setCusEmail(String cusEmail) { this.cusEmail = cusEmail; } @NotNull @Column(name = "cus_password", nullable = false) public String getCusPassword() { return cusPassword; } public void setCusPassword(String cusPassword) { this.cusPassword = cusPassword; } @NotNull @OneToOne(fetch = FetchType.LAZY) @JoinColumn(name = "cus_shipping_adr_id", nullable = false) @Cascade(value = CascadeType.ALL) @Valid public Addresses getShippingAddress() { return shippingAddress; } public void setShippingAddress(Addresses cusShippingAddress) { this.shippingAddress = cusShippingAddress; } @OneToOne(fetch = FetchType.LAZY) @JoinColumn(name = "cus_invoice_adr_id", nullable = true) @Cascade(value = CascadeType.ALL) @Valid public Addresses getInvoiceAddress() { return invoiceAddress; } public void setInvoiceAddress(Addresses cusInvoiceAddress) { this.invoiceAddress = cusInvoiceAddress; } } </code></pre> <p>As you can see, I have here two address fields - one for shipping address, the other for invoice address.<br/> The validation for each type of address should be different, as e.g. I don't need VAT number in shipping address, but I may want that in invoice.<br/><br/> I used groups to perform different validation on invoice address and shipping address which works OK if I do manual validation of address field.<br/></p> <p>But now I'd like to validate whole Customer object with addresses (if available).<br/> I tried to do that with code below:<br/></p> <pre><code> private void validateCustomerData() throws CustomerValidationException { ValidatorFactory factory = Validation.buildDefaultValidatorFactory(); Validator validator = factory.getValidator(); Set&lt;ConstraintViolation&lt;Customers&gt;&gt; constraintViolations; constraintViolations = validator.validate(customer, Default.class, InvoiceAddressCheck.class, ShippingAddressCheck.class); if (!constraintViolations.isEmpty()) { throw new CustomerValidationException(3, Message.CustomerDataException, constraintViolations); } } </code></pre> <p><br/> Of course this doesn't work as it supposed, since both validations are run on both instances of address objects inside customer object, so I get errors in shipping address from InvoiceAddressCheck interface and errors in invoice address from ShippingAddressCheck.<br/> <br/></p> <p>Here is shortened declaration of Addresses bean:<br/><br/></p> <pre><code>@Entity @Table(name = "addresses", schema = "public") @TypeDef(name = "genderConverter", typeClass = GenderConverter.class) public class Addresses extends ModelObject implements Serializable{ private static final long serialVersionUID = -1123044739678014182L; private long adrId; private String street; private String houseNo; private String zipCode; private String state; private String countryCode; private String vatNo; private Customers customersShipping; private Customers customersInvoice; public Addresses() {} public Addresses(long adrId) { super(); this.adrId = adrId; } @Id @Column(name = "adr_id", unique = true, nullable = false) @SequenceGenerator(name = "adr_seq", sequenceName = "adr_id_seq", allocationSize = 1) @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "adr_seq") @NotNull public long getAdrId() { return adrId; } public void setAdrId(long adrId) { this.adrId = adrId; } @NotNull @Column(name = "adr_street", nullable = false) public String getStreet() { return street; } public void setStreet(String street) { this.street = street; } @NotEmpty(groups = ShippingAddressCheck.class) @Column(name = "adr_house_no") public String getHouseNo() { return houseNo; } @NotEmpty(groups = ShippingAddressCheck.class) @Column(name = "adr_zip_code") public String getZipCode() { return zipCode; } public void setZipCode(String zipCode) { this.zipCode = zipCode; } @Column(name = "adr_vat_no") @NotEmpty(groups = InvoiceAddressCheck.class) public String getVatNo() { return vatNo; } public void setVatNo(String vatNo) { this.vatNo = vatNo; } @OneToOne(fetch = FetchType.LAZY, mappedBy = "shippingAddress") public Customers getCustomersShipping() { return customersShipping; } public void setCustomersShipping(Customers customersShipping) { this.customersShipping = customersShipping; } @OneToOne(fetch = FetchType.LAZY, mappedBy = "invoiceAddress") public Customers getCustomersInvoice() { return customersInvoice; } public void setCustomersInvoice(Customers customersInvoice) { this.customersInvoice = customersInvoice; } } </code></pre> <p><br/> Is there any way to run the validation, so that invoiceAddress is validated with InvoiceAddressCheck group and shippingAddress validated with ShippingAddressCheck group, but run during validation of Customer object?<br/> I know that I can do it manually for each subobject, but that is not the point in here.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDamian Walczak
    1. USDamian Walczak
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMultiple beans validation inside containing bean with different group interfaces
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMultiple beans validation inside containing bean with different group interfaces
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMultiple beans validation inside containing bean with different group interfaces
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload