gerhard

2011/9/27 Emmanuel Bernard <emmanuel@hibernate.org>

For your info, here is my ordered list

## Must have
- BVAL-241 Method level validation
- BVAL-238 Support for container injection in ConstraintValidator
- BVAL-226 Make clear whether the static or the runtime type should be considered when creating property paths in case of cascaded validations
- BVAL-221 The constraint violation builder cannot put constraint on a top level map key
- BVAL-210 Make sure JTA / Java EE plays well with Bean Validation + JPA when exceptions occurs (at least raise the concern upstairs ;) )
- BVAL-208 Support groups translation when cascading operations (hosted on @Valid or not)

## Should have
- BVAL-220 Offer stereotypes to skip validation on empty or null
- BVAL-240 Revisit cross-field validation
- BVAL-225 Propose ability to provide default resource bundles (for a constraint definition provider)
- BVAL-219 Consider interpolating the value in error messages
- BVAL-223 Add formatter syntax for interpolated messages
- BVAL-216 Work with the JAXB EG to have a nice Bean Validation integration
- BVAL-214 Ability to validate an object and a list of changes
- BVAL-199 Offer helper classes to build ConstraintViolationExceptions (and potentially raise them)
- BVAL-198 Simplify creation of ConstraintViolationExceptions
- BVAL-192 Add 'exclusive' boolean attribute to @DecimalMin/@DecimalMax constraints
- BVAL-230 Add support for validating CharSequence types instead of just Strings
- BVAL-217 Seperate the notion of message resolver vs message interpolator
- BVAL-249 Add unwrap method to ConstraintValidatorContext for provider extension

## Nice to have
- BVAL-235 Support parameterized payload attributes (additional string param on @Payload)
- BVAL-233 provide access to contextual info during message interpolation
- BVAL-229 Offer a programmatic API to declare constraints on a domain model
- BVAL-222 Add a ALL group to validate all groups instead of DEFAULT or the selected ones
- BVAL-215 Make composition more flexible (OR support)
- BVAL-213 Convert persistence storage exception into Bean Validation exceptions
- BVAL-202 Apply constraints on the elements of an iterator
- BVAL-191 Introduce a addEntityNode() method to the fluent node builder API
- BVAL-211 Consider making javax.validation.ValidatorContext a self-referential generic type
- BVAL-237 Expose validated bean via ConstraintValidatorContext

## Next revision
-

## Discuss with JPA's expert group
- BVAL-234 Ignore @NotNull on JPA's @GeneratedValue properties for pre-persist operations

On 26 sept. 2011, at 22:35, Gunnar Morling wrote:

> I created a filter to list all open BVAL issues without sub tasks:
>
> https://hibernate.onjira.com/secure/IssueNavigator.jspa?mode=hide&requestId=11462
>
> This should be a good starting point.
>
> --Gunnar
>
>
> 2011/9/26 Gunnar Morling <gunnar.morling@googlemail.com>:
>> I see you concerns about solely relying on votes.
>>
>> Marking the issues with the 4 categories also works for me. Once
>> everybody has given his categorization, we can use standard JIRA
>> priorities based on that to create a prioritized backlog.
>>
>> --Gunnar
>>
>>
>> 2011/9/26 Emmanuel Bernard <emmanuel@hibernate.org>:
>>> My problems with votes is that they are not weighted. I am not running the EG as a direct democracy. In general, I value someone's opinion proportional to his knowledge and involvement.
>>>
>>> For example, method level validation might not make sense to the commoner and thus be voted low but we see it as extremely important esp since it's used by other JSRs. Votes cannot really expose that.
>>>
>>> That being said, we can categorize issues in 4 circles:
>>> - must have
>>> - should have
>>> - nice to have
>>> - post 1.1
>>>
>>> and we can use the comment system to mark issues with these circles.
>>>
>>> On 25 sept. 2011, at 13:37, Gunnar Morling wrote:
>>>
>>>> I'm wondering what's the best way to achieve some initial
>>>> prioritization. Should we add comments to the JIRA issues? Another
>>>> idea would be to use JIRA's voting feature and start with working on
>>>> features with most votes. WDYT?
>>>>
>>>> --Gunnar
>>>>
>>>>
>>>> 2011/9/7 beanvalidation-dev List <beanvalidation-dev@lists.jboss.org>:
>>>>> Hi all,
>>>>>
>>>>> I have not seen your comment on the priority list.
>>>>>
>>>>> http://beanvalidation.org/roadmap/ (main)
>>>>> https://hibernate.onjira.com/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+BVAL+AND+status+%3D+Open (complete list of candidates)
>>>>>
>>>>> Can you put some thoughts to what has top priority for you and give your feedback?
>>>>>
>>>>> Emmanuel
>>>>>
>>>>> PS: I will be away from connected computers of most sort for 7 days ( for good reasons :o) ), but get the flow going without me.
>>>>> _______________________________________________
>>>>> beanvalidation-dev mailing list
>>>>> beanvalidation-dev@lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>>>>>
>>>> _______________________________________________
>>>> beanvalidation-dev mailing list
>>>> beanvalidation-dev@lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>>>
>>>
>>> _______________________________________________
>>> beanvalidation-dev mailing list
>>> beanvalidation-dev@lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>>>
>>
>
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev

_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev