spring-projects / spring-projects/spring-hateoas
JSR 303 annotations validation in web tier
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 476
- PR merge metrics
- No merged PRs in 30d
Description
Hi, this is in relation to the issue described in this stackoverflow question - http://stackoverflow.com/questions/36649331/spring-boot-starter-data-rest-notnull-constraint-not-working.
The gist is that the JSR303 annotation don't appear to getting enforced for resources exposed via @RepositoryRestResource. I could see that it does work for JPA based implementations where the check happens prior to data being inserted or updated but for Mongo and other non-JPA stores it would likely ignore the annotations. I wanted to see what the right approach could be here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the missing JSR 303 validation for resources exposed through @RepositoryRestResource, comparing the behavior described for JPA-based implementations with Mongo and other non-JPA stores. Read the related Stack Overflow question and determine what web-tier validation behavior should be considered done across these resource types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mongodb, spring
- Domain
- api, backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100