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
Chapter 5: Using JBuilder with Borland servers 43
Web module workarounds
Remote debugging in JBuilder
Once either edition of the Borland Enterprise Server AppServer and the partition have
been started, follow these steps from within JBuilder:
1 In the project from which you want to launch the remote debug session, choose
Run|Configurations. If you have not yet created a Server type run configuration,
click New. In the New Runtime Configuration dialog box, set the Type to Server. If
you have already created a Server run configuration, select it and choose Edit.
2 Select the Debug|Remote node.
3 Check the Enable Remote Debugging option.
4 Select the Attach option.
5 Enter the name of the machine on which the server is running in the Host Name
field.
6 Make sure the Transport Type is set to dt_socket and the Address is set to 3999.
The dialog box will look similar to this:
7 Click OK to close the dialog box.
8 Set a breakpoint in the process you want to debug.
9 Deploy that process to the running partition.
10 Click the down arrow next to the Debug Project button on the toolbar and select the
Server configuration you just created or edited. The debugger launches, attaches to
the partition running remotely, and stops at the breakpoint.
Web module workarounds
The default application server install includes ROOT.war, which contains the default
context. If you deploy an EAR that contains a default context, you must delete
ROOT.war
(or rename its extension) so that it does not load and cause a conflict. If deploying
WARs (with the container classloader policy), the resulting WAR is automatically
copied to the partition as
ROOT.war, in which case there is no conflict. Please note that it
is the
<context-root>!ROOT!</context-root> element in the web-borland.xml file that
designates the context as root, not the file name.