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
90 Developing Applications for J2EE Servers
Deploying exploded web modules
Both the Server Deployment dialog box and the Deployment page of the Project|
Project Properties dialog box have these two options:
■
Include System Modules When Listing Deployments
■
Include Disabled Modules When Listing Deployments
These options allow you to fine tune what you see when you list deployments using
either the List Deployments action in the Server Deployment dialog box or when you
right-click a module and choose Deploy Options|List Deployments. Listed deployments
appear in a tree in the message pane. A system module is one that extends the server
and provides a service your modules can use. A disabled module is one you mark as
Disabled by right-clicking the module and choosing Deploy Options|Disable. When a
module is disabled, it is simply renamed to <module>.disabled. To enable a module
again, right-click the module and choose Deploy Options|Enable.
Deploying exploded web modules
To deploy exploded modules, follow these steps:
1 Create a web module in a directory with the name <modulename>.<fileext>, such as
Module1.war, for example.
2 Ensure that the directory that contains the web module is at least one level below
the project directory. So, for example, if your project is created in a directory named
Project1, you might create your module in a directory named Project1/deploy/
<modulename>.<fileext>.
3 Edit the jboss-service.xml file in your JBoss configuration directory (<CONFIG_NAME>/
conf
). Add the parent directory of your module directory (such as Project1/deploy) to
the URL attribute element under the mbean named
jboss.deployment:type=DeploymentScanner,flavor=URL. For example, deploy/,file://
C:/Project1/deploy/
. Be that you add to the existing URL attribute (deploy/).
4 Start the server.
Remote debugging
Within JBuilder, follow these steps:
1 In the project from which you want to launch the remote debug session, click Run|
Configurations. If you have not yet created a server type run configuration, click
New and select type Server. If you have already created a server type run
configuration, select it and choose Edit.
2 Select Debug|Remote in the tree.
3 Check the Enable Remote Debugging option.
4 Enter the host name (the name of the machine on which the server is running.)
5 Specify the correct port number for the remote server.
6 Click OK.
7 Click the down arrow next to the Debug Project icon ( ) on the JBuilder toolbar
and select the debug run configuration you just created or edited. You will now be
able to set breakpoints in Java code, such as in EJBs, servlets, and so on.