spring-projects / spring-projects/spring-ws
Modernize configuration strategies
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 346
- Forks
- 323
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 7
Description
Looking at https://github.com/spring-projects/spring-ws/issues/242 we've introduced a number of default strategies for beans. They now look a little bit out of place. We could move them to spring.factories but I'd rather remove them entirely.
Looking at our option, we have @EnableWs and ws:annotation-drive that could be used as a source for the additional beans. Moving them to code might reveal package tangle so this'll have to be investigated.
Contributor guide
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 reading issue 242 and locating the default bean strategies discussed here. Compare the existing spring.factories approach with @EnableWs and ws:annotation-drive, then investigate whether moving configuration into code creates a package tangle; done means the default strategies are removed or the selected configuration path is clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100