[
https://issues.apache.org/jira/browse/OPENJPA-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-1177:
----------------------------------
Component/s: validation
Description:
We need to upgrade from CR2 level of the API
(geronimo-validation_1.0_spec-1.0-EA2-SNAPSHOT) to the ust released CR3 level
(geronimo-validation_1.0_spec-1.0-EA3-SNAPSHOT).
Moving from the Validation 1.0.CR2 to 1.0.CR3 levels are going to cause us some
churn:
- The 4 descriptor class were moved into a javax.validation.metadata package.
- A new javax.validation.Path was introduced for iterable nodes, which replaces
some String usage in ConstraintViolation and TraversableResolver.
Note: Either the agimatec-validation code will need to be updated or we'll have
to switch to using the RI for testing.
Fix Version/s: 2.0.0
> Upgrade to Bean Validation JSR-303 1.0 CR3 Spec API
> ---------------------------------------------------
>
> Key: OPENJPA-1177
> URL: https://issues.apache.org/jira/browse/OPENJPA-1177
> Project: OpenJPA
> Issue Type: Sub-task
> Components: validation
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.0
>
>
> We need to upgrade from CR2 level of the API
> (geronimo-validation_1.0_spec-1.0-EA2-SNAPSHOT) to the ust released CR3
> level (geronimo-validation_1.0_spec-1.0-EA3-SNAPSHOT).
> Moving from the Validation 1.0.CR2 to 1.0.CR3 levels are going to cause us
> some churn:
> - The 4 descriptor class were moved into a javax.validation.metadata package.
> - A new javax.validation.Path was introduced for iterable nodes, which
> replaces some String usage in ConstraintViolation and TraversableResolver.
> Note: Either the agimatec-validation code will need to be updated or we'll
> have to switch to using the RI for testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
