This demo shows the use of JNDI Connector. It provides access to the JNDI namesapace accessible by SESJ. A common situation is that SESJ runs as a servlet within an application server and exposes its whole JNDI namespace, reflecting restrictions given in the connector's configration.
The demo includes EJBs and a regular J2EE client. To turn the communication between client and server into SOAP, you must first deploy SESJ and the EJBs into an application server and ensure that the EJBs are accessible to SESJ. For many of the most commonly used application servers, you can do this with the script 'WASP_HOME/demos/advanced/j2eeIntegration/deployWithEJBs.' The script creates an enterprise application containing SESJ and EJBs and modifies the environment of your SESJ installation so that the URLs of demos point to the deployed SESJ. Properties and classpaths are also set, so that JMS transport is able to find administered objects and demo clients are able to communicate with the deployed SESJ by SOAP messaging over JMS.
In addition to the files described in Files and Directories, this demo contains:
| File or directory | Description |
|---|---|
| src/demo/advanced/jndiOverSoap | EJBs and J2EE client sources |
This demo assumes that you have deployed SESJ and EJBs into an application server and EJBs can be found in the SESJ context. URLs in all env.bat scripts must be changed according to your deployment.
You can run the demo using "run.sh" or "run.bat" scripts. Running the script without arguments prints out a help message.
The following steps are for running the demo:
Compile client and EJBs classes ...
Windows: run.bat make_client Linux: ./run.sh make_client
Run the J2EE client (it calls EJBs accessible over SOAP messaging using JNDI connector)
Windows: run.bat run_client Linux: ./run.sh run_client
If you wish to follow the progress of the invocation with SoapSpy, perform the following:
Run server_java60/bin/soapspy.bat or soapspy.sh. This will bring up the SoapSpy GUI.
Start spying by selecting Start Spying from the Spy menu or by clicking the spy icon in the main pane.
Run the client using the run spy_client command instead of run_client.