[
https://issues.apache.org/jira/browse/BVAL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Stumm updated BVAL-13:
----------------------------
Fix Version/s: 0.1-incubating
> ConstraintViolationImpl must be Serialziable according to JSR303 spec
> ---------------------------------------------------------------------
>
> Key: BVAL-13
> URL: https://issues.apache.org/jira/browse/BVAL-13
> Project: BeanValidation
> Issue Type: Bug
> Affects Versions: 0.1-incubating
> Reporter: Roman Stumm
> Fix For: 0.1-incubating
>
>
> JSR 303 Spec., chapter 4.2. ConstraintViolation: "Bean Validation
> implementations should ensure that a ConstraintViolation implementation is
> Serializable provided that the root bean, the leaf bean, the invalid value
> and keys in the Path object are Serializable objects. If a user wishes to
> send ConstraintViolation remotely, it should make sure the object graph
> validated is itself Serializable."
> Problem ist: ConstraintViolationImpl currently is not serializable, because
> ConstraintValidation is not either (and AccessStrategy, Field, Method, all
> ConstraintValidators are also NOT serializable...)
> I think the solution could be to implement methods for
> serialization/deserialization or, even better, remove field type
> ConstraintValidation from class ConstraintViolationImpl, so that
> ConstraintViolationImpl can become serializable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
