All along, J2ee development process (in Struts + Hibernate + Spring as an example) are as follows:
Happen if the demand changes, or found a database design error, then all the steps have to come back again, very tedious job.
State diagram is as follows:
Because Netbeans also provides a good UML features, Netbeans at the same time the JPA is also very good, and why not to combine UML and JPA use?
Because of the use of JPA annotations are managed POJO, while UML synchronous code will automatically skip the comments, so as long as the adoption of UML and then generate POJO JPA annotations for the add, you can very easily generate a database.
According to this thinking, to improve the development process as follows:
This has the following advantages
1. Design Database
2. Generate database
3. From the project to establish database connection
4. Put the database reverse engineering to generate POJO
5. Finally in order to carry out development work
Happen if the demand changes, or found a database design error, then all the steps have to come back again, very tedious job.
State diagram is as follows:
Because Netbeans also provides a good UML features, Netbeans at the same time the JPA is also very good, and why not to combine UML and JPA use?
Because of the use of JPA annotations are managed POJO, while UML synchronous code will automatically skip the comments, so as long as the adoption of UML and then generate POJO JPA annotations for the add, you can very easily generate a database.
According to this thinking, to improve the development process as follows:
This has the following advantages
1. Enhance the work efficiency
2. Implementation of the field-driven development (Domain Drivern Design)
3. Because of the use of the JPA, the implementation can easily cross-database migration
4. To save the design time database
5. After the end of the project at hand will be a group of the field of sound-driven UML diagram, which can be easily generated design documents.