You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2009/07/15 22:43:14 UTC
[jira] Created: (OPENJPA-1177) Upgrade to Bean Validation JSR-303
1.0 CR3 Spec API
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
Reporter: Donald Woods
Assignee: Donald Woods
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-1177) Upgrade to Bean Validation JSR-303
1.0 CR3 Spec API
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732052#action_12732052 ]
Donald Woods commented on OPENJPA-1177:
---------------------------------------
Other API changes:
- Constraints and @Valid - now supports constructor and parameter targets
- ConstraintValidatorContext - several new Interfaces and method chnages
- ConstraintViolation - getPropertyPAth() now returns a Path instead of a String
- ConstraintViolationException - getConstraintViolations() now returns Set<ConstraintViolation<?>> instead of Set<ConstraintViolation>
- MessageInterpolator - static removed from internal Context interface
- ValidationProvider - now extends Configuration and createSpecializedConfiguration() method has changed
- TraversableResolver - method params have changed
- Validation -
- ValidationProviderResolver - getValidationProviders() now returns List<ValidationProvider<?>> instead of List<ValidationProvider>
- Validator - new unwrap() method
- ValidatorFactory - new unwrap() method
> 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.
[jira] Work started: (OPENJPA-1177) Upgrade to Bean Validation
JSR-303 1.0 CR3 Spec API
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on OPENJPA-1177 started by Donald Woods.
> 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.
[jira] Updated: (OPENJPA-1177) Upgrade to Bean Validation JSR-303
1.0 CR3 Spec API
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (OPENJPA-1177) Upgrade to Bean Validation JSR-303
1.0 CR3 Spec API
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods resolved OPENJPA-1177.
-----------------------------------
Resolution: Fixed
> 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.
[jira] Updated: (OPENJPA-1177) Upgrade to Bean Validation JSR-303
1.0 CR3 Spec API
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-1177:
----------------------------------
Affects Version/s: 2.0.0-M2
Fix Version/s: (was: 2.0.0)
2.0.0-M3
> 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
> Affects Versions: 2.0.0-M2
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.0-M3
>
>
> 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.