JSF defects: insufficient IDE support

With a suitable component set, it is easy to establish a good "ecological environment. When enough users are used, a good "ecological environment" begins to be established. For JSF, such an "ecological environment" has been partially created. In addition to component suppliers, there are also many tools for developing JSF. For example, JbossTools or Exadel Studio is more suitable), BEA WorkshopWorkshop and NitroX M7 products) jdeveloper, MyEclipse, NetBeans of Oracle, JSF tools of IBM, and IDEA support for JSF.

That's about the JSF development tools. Some may say that developing JSF relies heavily on these development tools. In fact, this is not fair. For beginners, these IDE tools will help them learn JSF more easily. Many developers often advise beginners of Java, and the ideal Java IDE is notepad) and command line cmd), so some may infer from this, JSF's best IDE should also be a simple editor such as Notepad, while JSF's professional development tools will make Beginners "lazy", so that their understanding of JSF is superficial. This often makes JSF beginners confused.

Does that mean giving up using the jsf ide tool? Of course not. Because we cannot consider a tool as defective or a framework as defective because it provides easier development processes.

The jsf ide does not absorb a large number of JSF users. This shows that the "ecological environment" of JSF is insufficient to guide JSF beginners. The "ecological environment" represents the capabilities and power of JSF. However, it does not show its core ideas to beginners, nor does it clearly explain what beginners need to know first, at the same time, it does not allow beginners to understand the advantages that the JSF framework can provide but other frameworks cannot provide.

The real problem is that JSF cannot directly provide users with more advantageous components based on such basic components unless users re-develop better components based on JSF. However, before discovering the potential of JSF, it is difficult for users to develop better component sets. At the same time, relevant documents may not help.

Component developers can stop repetitive development. Each person has a tab panel, menu component, spinner, and drag-and-drop mechanism. These are mature. We are welcome to better update the implementation method, but the implementation method "I Can" is not conducive to the spread of technology. What JSF needs is a component set developed based on the interface model. It will be the standard implementation of the interface. The document on this component set must be clear and easy for beginners to learn.

JSF is growing fast. All the books mentioned above are excellent resources about JSF. Especially for the Seam project and Quick Start books on JSF. The advantage of JSF is that it is a standard, but standards alone are not enough. Because it cannot be the standard of what people expect, it will be replaced by other standards one day. As far as the author is concerned, JSF is not qualified for this standard. Of course, every developer will make his own final decision.

In any case, JSF is always a very promising component framework. Of course, it is not the only component framework. The topic of this article is not to compare various component frameworks. However, to put it bluntly, JSF is a part of J2EE and its components are still being expanded and improved. Since it is the Implementation Standard of J2EE 5.0, its potential is still huge. It will be like JSP, you can only care about it with indifference, but JSF is still moving toward it, whether you like it or not.

JSF is equal to other frameworks. It is a standard, which means that users and implementers have a platform to follow. If JSF follows a common specification, you can imagine the running mechanism of JSF. If not, you can ignore it.

JSF problems can be solved and are being solved. Some component sets have emerged. Facelets replaces JSP, making webpage templating easier and bringing faster and more concise performance. The establishment of the JSF2.0 Expert Group will bring a simple Java EE model to JSF. At the same time, relevant documents will be updated and revised, and new books will be published not only to focus on the Seam project developed by Jboss using JSF ). While complaining about JSF, as a developer, I am also trying to find a solution to the problem. The following are some of my preliminary views:

1. Use facelets to replace JSP.

2. Try to use the ADF or Seam instead of RI or myfaces.

3. Use Spring to enhance the scalability of JSF.

4. Don't complain about JSF. After all, it is just a standard specification, not a specific implementation framework.

1. JSF2.0 has implemented all features through final voting JSF
2. Three Advantages of JSF Web development
3. New-generation Java Web development framework JSF interview recording
4. Let's take a closer look at whether JSF can save the WEB arena.
5. Comparison of functions between JSF and Struts