JBuilder is a tool for Java development developed by Borland, while JDeveloper is an IDE tool that Oracle provides you. The recent development process uses these two tools, now talk about itself in design and development. The two tools are different, and the functions provided by the two tools are a simple comparison, I hope to communicate with you.
I. UML design: Before developing, we first thought that using UML designed to develop projects to make yourself in your heart when you really encode. In this regard, JDeveloper has a natural advantage than JBuilder, because in JDeveloper contains tools for creating a UML diagram, we can easily perform UML design under a tool, and in it, the conversion from Figure to code is automatic Completed without our manual conversion, and all graphic and source code are in a project, which is also convenient for our grasp and management of the entire project.
During the development of JBuilder, we have to make UML design with other tools. We chose Borland's TOGETHER DESigner for JBuilder for JBuilder, however, this tool is somewhat uncoordinated with our project to a certain extent. The place. I don't say this tool is not as good as the UML design tool in JDeveloper. In contrast, I think it is large, especially for easy use, together Designer has a greater advantage over JDeveloper, on the one hand, TOGETHER DESIGNER 2005 is fully integrated For UML 2.0 support, we can create UML design in very aspects. (Unfortunately, I don't know how to understand the UML2.0, there is no guts, huh, huh), on the other hand, integrate some templates of some modes. What models? That is the most familiar "four-person help", so if we use design patterns in the design process, it can be easily called without your own design, which is also very convenient. But our design is a very small project, I think about it, but there is no place to use design patterns, but unfortunately.
In addition, I personally think that there is a long time, that is, on the processing of the parameters, in JDeveloper, all parameters need to be manually input, and can be displayed in the design diagram. In to TOGETHER Designer, we can detail the parameters of an operation as in the process of the program, but all parameters will not be displayed on the map, this feature I think everyone's opinion It is not the same. If you say good, then this design can avoid problems on the page display due to the description of the operation. If it is not good, that is what we can't understand when you look at the UML map.
In the process of design, it should be said that both is a flat hand.
Second, the development: I mainly refer to the actual coding work, in this regard, Oracle as a database of databases, of course, for us, providing us with a lot of convenience, but as everyone knows, Borland The development tools provided are simple and easy to use. During the actual development process, the code is automatically completed in the code. The Error Automatic Correction is also available in the process of the JDeveloper, which provides the convenience of JDeveloper. This is also the reason why we finally chose JBuilder when developing. For example: When we use a class we don't have referenced in your code, JDeveloper is just a simple to report, without providing us with a solution, and in jbuilder, we can easily press Alt Enter. To see the prompt, and choose to automatically modify our errors in the recommended improvement method. Or in Java development, we are deeply painful Catch Exception, some operations are not captured, but cannot pass during the compilation process, in JDeveloper, we can only add TRY ... CATCH, but in jbuilder, we can also Let it complete this feature.
In this regard, it should be said that JBuilder has gained a large extent.
The above is a simple comparison of the use of the two during the development process, which may be in some ways because I have not used some biased, I hope to discuss with everyone.
