How to structure your Code when implementing REST APIs with Spring MVC #77

Open

Open

How to structure your Code when implementing REST APIs with Spring MVC#77

Assignees

What's the best package structure?
One Controller per Use Case?
One Resource per Use Case?

Metadata

Assignees

thombergs

Labels

No labels

No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests