web server - Borland Technical Publications

Embedding VisiClient Container functionality into an existing application
To run the J2EE client using the appclient:
1 Set the PATH to appclient.exe and JDK.
2 Edit the appclient.config to change JAVA_HOME, and lib PATH.
3 Run the J2EE client from /client.
Embedding VisiClient Container functionality into an existing
application
As an alternative to deploying and running a client application in the VisiClient
container, it is possible to use a programmatic approach to embed the client container's
functionality into an existing application. In this case, the client application can be
started in a common Java fashion by running a class implementing the main() method.
To embed the VisiClient container functionality into your application, you need to call
the following method:
public static void com.borland.appclient.Container.init
(java.io.InputStream deploymentDescriptorSun,
java.io.InputStream deploymentDescriptorBorland)
throws IllegalArgumentException;
This method will create and populate the “java:comp/env” naming context based on the
information provided in the pair of Sun and Borland deployment descriptors. The
deploymentDescriptorSun and deploymentDescriptorBorland parameters must represent
text XML data corresponding to the deployment descriptors. An
IllegalArgumntException exception is thrown if the data provided is not recognized as a
valid deployment descriptor.
Note
Sample code
This example shows usage of this method:
public static void main (String[] args) {
. . .
// load deployment descriptor files
java.io.FileInputStream ddSun = new
java.io.FileInputStream("META-INF/application-client.xml");
java.io.FileInputStream ddBorland = new
java.io.FileInputStream("META-INF/application-client-borland.xml");
// initialize client container
com.borland.appclient.Container.init(ddSun, ddBorland);
// lookup ejb in JNDI using an ejb-ref
javax.naming.Context context = new javax.naming.InitialContext();
Object ref = context.lookup ("java:comp/env/ejb/hello");
. . .
}
Only application client descriptors can be loaded using this method. This means that all
ejb-refs must be resolved or located by specifying the jndi-name in the Borland
descriptor. This cannot be done using the ejb-link in the Sun descriptor since using ejblink
requires complete knowledge of the whole application including application and
EJB JAR deployment descriptors.
Chapter 12: The VisiClient Container 103