Selection of JSP development tools

After the JSP Engine is built, you can start to use the development tools for JSP programming. Currently, popular JSP development tools include IBM VisualAge, JBuilder, NetBeans, JRun, Urledit, dreamweaver, editplus, etc. Here we will mainly introduce some basic information about the three tools, IBM VisualAge, JBuilder, and Jrun. You can refer to their respective features and select development tools based on their own development environment.

IBM VisualAge for Java

IBM's Web development products can be described as a giant of the same kind: they are large in size and have a large number of features. They are used by the entire development team, while the design goal is to get everything you can see from the perspective!

The IBM WebSphere softwAre platfoRm (a full set of integrated e-commerce solutions, including Visual Age for Java 1.2) is a key part of the e-commerce application architecture, this architecture is a unified end-to-end architecture developed by IBM on the same programming model. As a public programming model, the EJB specification is widely supported by the industry. It is also an integrated component model of the e-commerce application architecture. VisualAge for Java is the first Java IDE that provides the wizard function. It can generate a large number of EJB infrastructure code, thus simplifying the EJB development process. In addition, the creation wizard of the dialog and object beans, the beans ing of beans to existing relational data storage, and the advanced test environment greatly reduce the time required to create, test, and deploy ejbs.

The VisualAge for Java continuity tool allows developers to map ejbs to existing relational database structures. With support for dialogs and object beans (CMP), developers can generate ejbs from existing database tables or generate database structures from existing ejbs. VisualAge for Java can also map object models to data models, so that database administrators and Java developers can join each other. In addition, VisualAge for Java 3.5 also supports IBM DB2 S/390 and Sybase, as well as IBM DB2 general database and Oracle.

If the IBM WebSphere test environment (WTE) is run on the host in VisualAge for Java, developers can pre-test the EJB and servlet before deploying them to the remote server. Since developers can start and stop servers and applications, and can arbitrarily change applications in VisualAge for Java IDE, developers do not have to remotely deploy and test code, thus saving a lot of time.

Generating a test client allows developers to test their server-side ejbs without having to write a user interface or a mandatory interface provided by the graphic maker. In addition, when the user interface is complete, it can also be used as a test tool to determine whether the problem exists in the client part of the application or the server part.

VisualAge for Java also simplifies the process of adding ejbs to existing applications. By generating AccessBeans, VisualAge for Java hides the remote and local interfaces of EJB and integrates them into the JavaBeans programming model. This provides a simplified JavaBeans interface to EJB, simplifies programming interfaces between enterprise beans and servlets or JSP, and is widely recognized by all Java developers. In addition, AccessBeans introduces the advanced local cache function for EJB attributes, which reduces the number of remote calls and provides quick access to ejbs.

Now, the WebSphere Studio Advanced Edition and Its VisualAge for Java Professional Edition Software released by IBM to build the Web site have been fully switched to Java-centric, java developers may feel a lot better about the full set of WebSphere tools. Studio provides the following tools: Web site management, quick JDBC page development wizard, HTML editor, and HTML syntax check. This is indeed a good HTML site page editing environment. Studio and VisualAge are highly integrated, and the menu provides the option to quickly move code between the two software packages. This allows the Web page designers using Studio and Java programmers using VisualAge to exchange files and work together.

Studio provides a complete front-end development environment for building a Java Server Page. Many wizard programs can help you implement specific development tasks in a faster and more error-prone manner. For example, the SQL wizard allows us to browse tables and execute a variety of SQL tasks (such as adding connections, limiting queries with constraints, and viewing queries before storing results) in the Oracle 8i database used for testing. results ).

The new tags added by IBM make it easier for JSP to access data. For example, the <tsx: repeat> tag is used to traverse all rows in the query without adding Java code to process the database. These labels indicate that IBM is gradually adopting a tag-centric Data Access solution (as in ColdFusion ).

When editing the page, we have several tools available in front of us, including a graphic interface WYSIWYG page editor, an outline view that displays the page hierarchy, and an HTML source code editing view. However, we found that there were some integration problems between these editing tools, compared with Dreamweaver or ColdFusion.

Studio provides code complementing features, but is disappointing ?? This feature can only be used for VoiceXML files and cannot be used for HTML or JSP files. However, its support for Web technologies such as VoiceXML and WML is still in the leading position in the market.

Both Studio and VisualAge include the assumerver Page debugger. Because the assumerver Page runs in pre-compilation mode before execution, the Page debugging method provided by IBM for its pre-compilation form is worth noting, this method does not actually run the Java source code form on the server. With the Visual Age Java Server Page debugger, we can view the HTML display in the output window during Page debugging. However, after compiling the JavaServer Page, the compiler output only lists the error results and does not automatically mark the source code with errors.

VisualAge for Java supports team development. The built-in code library can automatically modify the program code based on our changes, so that we can easily compare the current code with earlier versions. Maxcompute Studio does not support source code version management. It only includes a built-in file lock system. When editing project files, you can prevent others from making incorrect changes to these files. The software also supports third-party source code control systems such as Microsoft Visual SourceSafe. Maxcompute Studio provides complete And customizable support for multi-server and multi-stage project deployment. After the application is developed, applications on the test server and product server are deployed quickly.

WebSphere Studio Advanced Edition 3.5 and VisualAge for Java Enterprise Edition 3.5 are both excellent development environments available to the development team. They provide built-in support for multiple developers in a single project. However, the interfaces and editing defects of these two sets of products make IBM products the best developer kit.