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
44 Developing Applications for J2EE Servers
Displaying the Borland Management Console in JBuilder
If you are working on a named context but have the root context in an already deployed
archive, the internal web browser in JBuilder will attempt to load once that archive is
loaded by the container, because the root context can potentially match any URL.
You’ll then probably get a “Document not found” error. To prevent this, remove
ROOT.war if you’re not using it or overwriting it.
Displaying the Borland Management Console in JBuilder
You can display the Borland Management Console in JBuilder. Choose View|Panes|
BES Console.
International issues
The Borland Enterprise Server AppServer Editions 6.0 and 5.2.1 do support Japanese
characters in the JNDI name.
Borland servers and JDataStore 7.0
The Borland Enterprise Servers 5.2.1 and 6.0 do not support JDataStore 7.0.1,
although JBuilder does. When you are running applications that access JDataStore
databases, be sure you are using the JDataStore 6.x or older file format and
JDataStore libraries that ship with the server. Databases created using JDataStore 7.0
cannot be used with Borland Enterprise Server 5.2.1 and 6.0.