Server User Manual
Table Of Contents
- Developing Applications for J2EE™ Servers
- Contents
- Ch 1: Introduction
- Ch 2: Programming for the Java 2 Platform, Enterprise Edition
- Ch 3: Creating applications with J2EE technologies
- Ch 4: Configuring the target server settings
- Ch 5: Using JBuilder with Borland servers
- Configuring Borland servers in JBuilder
- Making the ORB available to JBuilder
- Configurations, partitions, partition services, and J2EE APIs
- Starting the configuration or server
- Remote deploying
- Remote debugging
- Web module workarounds
- Displaying the Borland Management Console in JBuilder
- International issues
- Borland servers and JDataStore 7.0
- Ch 6: Using JBuilder’s CORBA tools
- Ch 7: Using JBuilder with BEA WebLogic servers
- Ch 8: Using JBuilder with IBM WebSphere servers
- Ch 9: Using JBuilder with JBoss servers
- Ch 10: Using JBuilder with Tomcat
- Ch 11: Editing J2EE deployment descriptors
- Ch 12: Integrating with Enterprise Information Systems
- Ch 13: Building J2EE modules
- J2EE modules
- Setting module build properties
- Adding custom file types
- Sample build scenarios
- EJB JAR without any bean classes
- EJB JAR with custom files
- EJB JAR without EJB designer XML descriptors
- WAR with custom descriptor(s) in the WEB-INF directory
- WAR without any classes
- WAR with custom class filters
- WAR with custom file types
- EAR with custom files
- RAR with classes and dependencies
- Application client module with classes and dependencies
- Improving module build performance
- Index
![](/manual/borland-software/jbuilder-2005/server-user-manual/images/img-8.png)
6 Developing Applications for J2EE Servers
Why are J2EE applications desirable?
was “served up” by a server. This approach initially promised improved scalability and
functionality.
Through hard experience, however, the development community learned that building
and maintaining a flexible distributed system is very difficult using the client-server
model. For example, the business logic of the application was in the client application.
Every time that logic needed modification, the revised application had to be installed on
every client machine in the enterprise. Maintenance became a nightmare. These
applications also had to manage transactions, be concerned with security, and process
the data efficiently, all the while presenting an attractive, easy-to-understand interface
to its users. Few developers have talents in all these areas. While a client-server
architecture might be adequate for some environments, most of today’s global
companies demand considerably more than the client-server model can deliver.
Once the limitations of the client-server approach became apparent, the development
community began seeking a better way. The result is the multi-tier model.
In the multi-tier model, the logic involved in presenting the user interface of the
application to the user lives on the middle tier. The business logic is now on the middle
tier also. When changes are needed, they can be updated in one place instead of on
each client machine.