Oracle launched the latest JDeveloper10g, and the wind turns on the wind is full of fire, and there are many advertising messages on this. It is flat that 10g is already greatly improved. He tries to complete the program development work through visual editing methods. I hope that JDeveloper can work highly like Microsoft's Studio. However, after a period of trial, it has finally understood that JDeveloper and mature commercial Java Ide are gap. Here I only talk about immature places. Let's see the official touch, I will come:
When you look at Oracle's Demo, I feel very good, for a data sheet, from the establishment of Entity Object (entity object), viewobject, struts action, JSP to the final run, basically no write code, is downtown , Data increase, modification, and deletion are automatically automatically completed. Very easy, of course, this is the most ideal, simplest situation. Then this advantage is actually a shortcoming. High efficiency sacrifices flexibility, the viewObject and the performance layer are too close, and when we do it directly in the actionform, you can operate freely to the Actionform, but now you want If you want to operate at ViewObject, because he has the rule of the database, in the way of the JDeveloper, ViewObject takes too much work, although viewObject is directly exchanged with the page, it is convenient to do data exchange (the addition of automatic management data, Modify, delete), but in complex conditions (multi-table constraints, foreign keys), some complex operations cannot be implemented unless it is a very simple item, otherwise he is a chicken rib.
Disadvantages 1: I hope to save everyone's time less write repeat code, and the results can only meet simple needs.
We all know that any one of the projects is not easy to rest in one or two people, so it is definitely a group of works, then this involves a version management, cooperative work. At this part I finally realized the power of Oracle, and I won't give you tossing. Let's talk about Oracle's project file structure, .jpr is the primary file of the project, then there will be various .xml files in the SRC, and some .cpx files, these files are the type of item directory subscription , PATH. In other words, there are very many common documents in the same project, which is a nightmare for the team's parallel development. In the project, an additional file will be recorded in the public files described above. If everyone's project is merged, there will be n confeicts, solve the problem, the project can't open. I got Metalink, and I got it on Oracle Forum, I know that everyone is painful and thinks of various ways to solve this problem. Finally, there is no way, only exclusive mode is best, do not merge. When only one person is done, others will rest.
Disadvantages: Do a personal development tool to do it.
A large number of XML profiles store a lot of information, want to maintain only through graphical tools, but also not let you modify. I am afraid that you change it, so I only turn off the JDeveloper, use EditPlus to the outside to modify the change. Then open the JDeveloper again.
Disadvantages: Consider entry a newcomer, but you should provide an Edit XML function for your skilled.
