The choice of JSP development tool

JS JSP engine can be set up after the use of development tools for JSP programming, now popular JSP development tools are mainly IBM Visualage,jbuilder,netbeans,jrun,urledit,dreamweaver, EditPlus and so on, here we mainly introduce IBM Visualage,jbuilder, jrun three kinds of tools of some basic conditions, you can refer to their respective characteristics, combined with their own development environment for development tools to choose.

IBM VisualAge for Java

IBM's Web development products are the same kind of giants: large size, many functions, the use of the object is the entire development team, and the design goal is to fix the vision can see everything!

The IBM WebSphere software platform (a full suite of integrated e-business solutions, including VisualAge for Java version 1.2) is a critical part of the E-business application architecture, a unified End-to-end architecture developed by IBM on the same programming model. As a common programming model, the EJB specification has been widely supported in the industry, and it is also the integrated component model of the application architecture of e-commerce. VisualAge for Java is the first Java IDE that provides the wizard functionality to generate a large amount of EJB infrastructure code that simplifies the EJB development process. In addition, the creation of dialogs and entity beans wizards, mapping beans to existing relational data stores, and advanced test environments greatly reduce the time it takes to create, test, and deploy EJBS.

The VisualAge for Java Persistence Tool enables developers to map EJBS to existing relational database structures. With support for dialogs and entity beans (CMP), developers can generate EJBS from existing database tables or build database structures from existing EJBS. VisualAge for Java also provides the means to map object models to data models, linking database administrators to Java developers. In addition, VisualAge for Java version 3.5 also supports IBM DB2 s/390 and Sybase, as well as support for IBM DB2 Common Database and Oracle.

If the IBM WebSphere Test Environment (WTE) is run in the VisualAge for Java host, developers can also test the EJB and servlet before deploying them to a remote server. Because developers can start and stop servers and applications and can arbitrarily change applications in the VisualAge for Java IDE, developers save a lot of time by not having to deploy and test code remotely.

Generating a test client enables developers to test their server-side EJBS without having to write a user interface or wait for a mandatory interface from the graphics producer. In addition, when the user interface is complete, it can be used as a test tool to determine whether the problem exists in the client or server part of the application.

VisualAge for Java also simplifies the process of adding EJBS to existing applications. Hides the remote and local interfaces of the EJB and merges it into the JavaBeans programming model by generating accessbeans,visualage for Java. This provides a simplified JavaBeans interface to the EJB, simplifying the programming interface between the enterprise beans and the servlet or JSP, and is universally accepted by all Java developers. In addition, Accessbeans introduces the Advanced EJB property Local caching function, reduces the number of remote calls and provides fast access to the EJB.

Now, IBM has turned the WebSphere Studio Advanced Edition and its contained visualage for Java Professional Edition software to build a Web site into a Java-centric, Java developers may feel a lot better about WebSphere's full set of tools. The tools provided by Studio include: Web site management, rapid development of the JDBC Page Wizard, HTML Editor, and HTML grammar checking. This is really 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 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 Java Server page. Many wizards can help users achieve specific development tasks in a faster, more error-prone manner. For example, the SQL Wizard allows us to browse the tables in the Oracle 8i database for testing, perform a variety of SQL tasks (such as increasing connections, restricting queries with constraints, and viewing query results before storing the results, and so on).

IBM's newly added tags make it easier for JSP to access data, such as <tsx:repeat> tags, which are responsible for traversing the rows of the query without increasing the Java code that processes the database. These tags indicate that IBM is gradually adopting a label-centric data access solution (as in the case of the ColdFusion approach).

When we edit the page, we have several tools to choose from, including a graphical interface WYSIWYG page Editor, an outline view that shows the page hierarchy, and an HTML source edit view. But we found some problems with the integration of these editing tools, compared to Dreamweaver or ColdFusion doing better.

Studio provides code-addition features, but it's disappointing?? This attribute can only be used for voicexml files, not for HTML or JSP files. However, its support for Web technologies such as VoiceXML and WML is still in the market-leading position.

Both studio and visualage include the JavaServer page debugger. Because the JavaServer page is run precompiled before execution, the way IBM provides page debugging for its precompiled form is noteworthy, and does not actually run Java source code forms on the server. With the VisualAge Java Server Page Debugger, we can view the HTML display from the Output window when the page is debugged. However, after compiling the JavaServer page, the compiler's output lists only the error results and does not automatically mark the source code where the error occurred.

VisualAge for Java Support Team development, the built-in code base can automatically modify the program code according to the changes we make, so that we can easily compare the current code with the previous version. Studio itself does not provide support for source version management, it simply contains a built-in file locking system that prevents others from incorrectly modifying these files when we edit the project file. The software also supports Third-party source code control systems such as Microsoft Visual SourceSafe. Because studio provides complete, configurable support for multiple-server and multi-stage project deployments, applications are deployed quickly on both the test server and the product server after the application has been developed.

WebSphere Studio Advanced Edition 3.5 and VisualAge for Java Enterprise Edition 3.5 are an excellent development environment for development teams, They provide built-in support for multiple developers under a single project. But the interface and editing flaws of the two sets of products make IBM's product the best development package failed.

　　

　　

　　
Jbuiler

JBuilder software is targeted at code developers rather than senior designers, so JBuilder contains a number of wizards and other quick development tools for the middle tier. JBuilder performance is stable, easy to use, especially for the creation of Java components. In addition, the software also provides a number of JSP features.

JBuilder itself supports Cross-platform software development through built-in Java and Swing (Java GUI program framework) technologies: It can run on Windows, Linux, and Solaris operating systems, and the operating interface and tools are exactly the same. This so-called "All-java" strategy means that the software does not run JBuilder memory too much. 128MB is the minimum system requirement, we recommend to equip 256MB memory for better performance.

Like earlier versions, the JBuilder 4 IDE was designed to be more efficient and functional. You can easily view Java, HTML, and JSP files in the same development environment, build a new sun-launched JDK 1.3 hotspot virtual machine (this new virtual machine optimizes Java code). JBuilder has a very good response interface. After a variety of compelling features, we particularly like the handy Automatic supplemental feature (Auto-completion Wizardry), which not only supports instant help but also supports the automatic filling of parameters for typing Java code.

　　

　　
The JBuilder Enterprise Edition provides support for enterprise Java-bean component development. In JBuilder, it is easier to create a configuration (deploy) Enterprise JavaBean. A series of wizards are provided to create, process, and configure the process of Enterprise JavaBean. Integrate the configuration Description editor of IAS into the JBuilder development environment (However, the IAS4.1 is not built into Jbuilder4 and requires additional download). JBuilder also supports Bea's WebLogic Server 5.1.

A new feature of Jbuider4 is the EJB Group feature. Each EJB group represents a configurable jar file. EJB group allows you to migrate existing EJBS between EJB group. There can be multiple EJB Group in a project project.
Entity Bean Modeler can create an entity Entity bean that maps to an existing table. You can generate all the necessary Java code and update the configuration description in Ejbgroup.
In JBuilder, you can:
1. Create session bean and entity bean with EJB Wizard
2, use entity Bean Modeler to map the entity bean to an existing table.
3. Create an EJB group through the EJB Group Wizard. In this way, you can put multiple enterprise JavaBean in an application.
4, you can transfer a enterprise JavaBean from one EJB group to another EJB group
5, an application can have more than one EJB Group.
6, with make and rebuild can automatically create a configurable jar file.
7, you can view the contents of the jar in the node viewer.
8, the Test Client Wizard can be in the local container or EJB1.1 compatible with the application Server testing Enterprise JavaBean.
9, when running or mode EJB will automatically configure the EJB. JBuilder supports EJB 1.1, and the software is ready to support EJB 2.0 with a flexible XML solution. Currently, users can automatically generate EJB Java classes based on back-end database tables. JBuilder also simplifies the automatic deployment of EJBS. It also supports CORBA, which helps users comprehensively manage IDL (the interface Definition Language Interface Definition language required to distribute applications) and control remote objects.

JBuilder's local development relies on the mild Java database contained in the software, which is called Jdatastore. The software contains Jdatastore Explorer and JDBC Explorer that allow users to manage jdatastore and any data sources that comply with JDBC standards. The Database Tools feature is enhanced and easier to use.
Jdatastore: Faster, more flexible. There is a significant improvement in the performance of the underlying connection pool. JBUILDER4 support for JTA enables Jdatastore connections to participate in distributed transactions with a standard XA interface.
Jdatastore Explorer can create and manipulate table with a graphical interface. You can create indexes for tables. Jdatastore now supports cross joins, inner joins, outer joins, left and right connections.
In a current release, you specify a connected domain by using the "natural" or "using" keyword. Jdatastore now also supports the SQL-92 connection sequence, which supports hierarchical subqueries.

JBuilder processing is also handy for transactions built on the middle-tier EJB. Although it's easy to create a default JSP with JBuilder, you can do it with a basic HTML form instead of a tool in WebSphere Studio. JSP itself is a very new technology for JBuilder, you can use simple JavaBean technology to manage JavaServer Page.

The JBuilder 4 enterprise contains more than 300 components, most of which belong to the JavaBean and swing controls, which are useful for building client applets and running stand-alone Java applications. In addition, the software includes 16 special controls named Internetbeans. However, these controls are dedicated to both the JSP and the servlet. These components encapsulate the controls that are used in Web forms, including the advanced features of simple buttons and tables.

These objects separate HTML from the Jsp/servlet code in the background, so that Web designers can modify HTML individually without requiring Java programmers to modify the underlying code. This solution is attractive to us, and with it there is plenty of scope for future expansion. In fact, similar components can also allow users to generate WML code for wireless devices, you only need to change the template to WML, these Internetbeans will dynamically populate the data for WAP devices. In a real-world application environment, we can use HTML tools that we like to do HTML editing work. JBuilder supports the development of Web applications, adds support for XML, and provides better servlet and JSP support. With Internetbeans Express and some components, you can seamlessly transform data between Java and HTML. JBuilder built-in Tomcat3.1, you can dynamically debug the servlet and JSP programs.　　Each Servlet has an alias (Servlet-name) and init () initialization function parameters that are capable of leaving shtml for independent execution. JBuilder provides enhanced JSP support, and it is easy to debug the JSP source code directly. provides support for XML. The ability to write XML files quickly and easily. The high brightness display of XML keywords is easily familiar to the structure of the entire XML file. By Internetbeans Express control, the content of Web pages can be generated dynamically.

JBuilder also launched the CVS versioning feature for team development, which has been used by our programmers to build test applications. With CVS, the development team can easily track the whole process of project development.
Engineering Documents (*.JPR and *.JPX) can be divided into two parts, private and shared. Windows, watch, breakpoints are saved in private, while libraries and compilation options are saved in the publicly shared part.

Version tracking and control: JBUILDER4 provides support for changes for each release. To view the version information for a file, click the Histroy tab at the bottom, which has a history of record changes for each file. JBuilder automatically maintains a backup of the file. You can set the number of backups. Histroy pages Use these backups to manage history's record of changes. You can access the previous version of the file. You can also see what changes have been made between two versions. Jbuilder4 's Enterprise Edition also provides CVS (Concurrent versions system concurrent version systems)

JBuilder's beautiful IDE environment is a good showcase for inprise and Borland developers, and JBuilder will continue to gain the favor of Java programmers. The software, which is equipped with a good reputation for help programs and server-side EJB tools, is a fairly mature and excellent Java development environment at the overall level. But Jbuilder4 also has its drawbacks:

1. There is a conflict with the Chinese system. At least there is a conflict with Win2000 's Chinese system, its menu always triggers the Chinese input bar.
2. Speed is not fast enough. High configuration is still required.
3. The hardware environment required to develop EJB requirements is too high because of the need to application Server and the requirement to be mounted on the same machine
4. There is a lack of useful tools in Webgain studio, such as Structurebuilder. Lack of efficient integration with tools such as Rose
5. Support Tools, such as version control tools are relatively few

　　
Jrun

The Allaire Company's JRun is a Java engine with the widest applicability for developing and implementing server-side Java applications written by Java Servlets (JSP) and JavaServer pages. JRun is the first commercial product to fully support the JSP 1.0 specification, with more than 80,000 developers worldwide using JRun to add server-side Java functionality to their existing Web servers. The Web server includes Microsoft Iis,netscape Enterprise Server,apache, and so on.
JRun is an advanced engine for developing implementation of server-side Java. If you want to add server-side Java functionality to your Web application, then JRun will be the right choice for you.
You can use JRun to run Java servlets-there are 2 ways to run Java Servlets, extend your Web server, or use a built-in JRun Web server. By using Servlets as an extensible, fully defined Java part model throughout the environment, you can easily, quickly develop, implement complex applications, and be more economical to maintain.
JRun currently has 3 versions, it is the first commercial product to support Java Server Pages (JSP) Specification 1.0. JSP is a powerful server-side technology that is a set of rapid application development systems for creating complex web applications.
JRun allows you to start developing and testing Java applications. It accepts up to 5 concurrent connections and:
Include all Java Servlet APIs
Support JavaServer Pages (JSP)
Support for all major Web servers and computer platforms
JRun Pro can withstand heavy traffic loads in a production environment to help you implement applications, services, or Web sites (including intranets). JRun Pro supports unlimited concurrent connections to run multiple Java virtual machines, including multiple concurrent Java virtual machines (JVMS).
Provides a remote management applet and a remotely distributed management applet. The JRun Pro Unlimited includes all JRun Pro features, which can run an unlimited number of concurrent JVMs, in addition to the Times.

Allaire JRun is a versatile engine for developing and implementing Java applications developed using JavaServer Pages (JSP) and Java Servlets. With Java technology, you can add server-side Java functionality on top of an existing Web server, and the Web servers supported by JRun include Microsoft IIS and Personal Web server-based. Netscape's Enterprise or Fasttrack,apache, O´reilly's website and StarNine Company's WebSTAR.

JRun relies on its built-in JRun Web server to run independently. With server-side Java, users can develop complex business application systems. Most importantly, it is a great alternative to CGI (Common Gateway Interface) or Perl scripts due to Servlets's platform independence and simpler development, faster implementation, and more economical maintenance costs.
Main function:
JRun 2.3 can fully implement the latest Java Servlet APIs. At the same time, JRun can take advantage of many of the advanced features in the Java WEB server. Some important functions of JRun2.3 are listed as follows:
? Full support for Java Servlet API version2.1
? Full support JavaServer Pages (JSP) 1.0 Draft spec
? Dynamic Taglets
? Provide ready-made templates
? Page edits
? Dynamic-servlet overload? Servlet-initialization Property
? Servlet Series and filtration
? Multiple hosts (virtual host) support? <servlet> Tag Support
? Task tracking
? Setup Wizard
? Complex swing-based management applications
? 100% Pure Java and complete cross-platform
? Can run on any Java Virtual Machine? Runs up to 5 Java Virtual machine (JRun Pro)? can run on unlimited number of Java Virtual machine (JRun Pro Unlimited)
? Remote administration (JRun Pro)
Technical advantages
The Java Servlets is a standalone Cross-platform server-side program written as part of the Java Servlet Api--java platform. The Java Servlets has the power of "write once, run everywhere," with network delivery security and a good scalability for server-side applications. Servlets can replace the traditional server-side applications and extenders written by perl,c/c++ or other languages. Using the servlet as an extensible, well-defined cross-platform environment, users can easily develop, quickly implement server-side complex applications, and save on maintenance costs. (You can deploy servlets on a cheap Windows NT machine)

In the existing mature server technology, such as Web server combined with Servlets, when writing complex applications, you can avoid the specific server configuration platform limitations and complexity. With Servlets, developers no longer have to worry about how the server works internally. The internal classes of the Servlets API controls form data, Server header,cookies, and everything.

The biggest difference between existing server-side applications and Servlets is performance. Running a separate jvm,servlet on the server is loaded as soon as it is called. It will not be loaded again until the servlets changes. A modified servlet can be loaded automatically without restarting the server or application. Because the servlet resides in memory forever, it loads very quickly. Static or persistent information can be shared across multiple active servlet, and allows information to be shared among multiple users. Servelet are also modular, they can be individually completed a specific task, but also can be combined to work together. Servlets can talk to each other.

JRun supported Web Server? Microsoft´s Internet Information Server (IIS) and Personal Web server (PWS)? Netscape´s Enterprise and FastTrack Servers
? Apache? O´reilly´s WebSite Pro
? Starnine´s WebSTAR
? Novell Netware 5 (Novonyx)