-
Notifications
You must be signed in to change notification settings - Fork 70
cobigen usecases
In addition to the selection of CobiGen applications introduced before, this chapter provides a more detailed overview about the currently implemented and maintained general use cases. These can be used by any project following a supported reference architecture as e.g. the ink:https://github.com/oasp/[OASP] or Register Factory.
With our templates for OASP, you can generate a whole CRUD application from a single Entity class. You save the effort for creating, DAOs, Transfer Objects, simple CRUD use cases with REST services and even the client application can be generated.
For the server, the required files for all architectural layers (Data access, logic, and service layer) can be created based on your Entity class. After the generation, you have CRUD functionality for the entity from bottom to top which can be accessed via a RESTful web service. Details are provided in the Devon wiki.
Generating a builder pattern for POJOs to easily create test data in your tests.
Person person = new PersonBuilder()
.firstname("Heinz")
.lastname("Erhardt")
.birthyear(1909)
.personDescription(
new PersonDescriptionBuilder().eyecolor("brown")
.skin("white").chin("small")
.nose("flat,wide").createNew())
.addChild(
new PersonBuilder()[...].createNew()).createNew();
Generates a CRUD application with persistence entites as inputs. This includes DAOs, TOs, use cases, as well as a CRUD JSF user interface if needed.
Analogous to Testdata Builder for OASP4J
Disclaimer
If you discover any documentation bugs or would like to request new content, please raise them as an issue or create a pull request. Contributions to this wiki are done through the main repo under the folder documentation.
License
This documentation is licensed under the Creative Commons License (Attribution-NoDerivatives 4.0 International
)