All Examples All EJB Examples
WebLogic provides shell scripts and makefiles to build the example EJB classes, interfaces, and clients. This document describes how to build examples using both methods.
Each EJB example includes a client application ("Client") and sometimes a servlet ("Servlet"). All EJB client examples are included in the same Java package as the EJB classes. Classes that are intended only for the client are identified by the word "Client" in the classname. Servlets are identified by "Servlet" in the classname. Classes that are intended only for the server have the word "Bean" in the classname.
To build EJB examples using either build.cmd or build.sh:
$ cd c:\weblogic\examples\ejb\basic\containerManaged
Each script generates the final EJB .jar file in /weblogic/myserver. The EJB .jar file is named according to the example's location. For example:
The scripts also build the clients required for the example, placing the classes in the correct locations:
Note: If you build an example EJB with the supplied build scripts and deploy it, you cannot run the build script again and redeploy the bean from the same .jar without getting an error. Instead, edit the script to build the EJB to a new .jar file, and redeploy from the new file.
if not exist %JDK_HOME% set JDK_HOME=\java if not exist %WL_HOME% set WL_HOME=\weblogic set MYSERVER=%WL_HOME%\myserver set MYCLASSPATH=%JDK_HOME%\lib\classes.zip;%WL_HOME%\classes;%WL_HOME%\lib\weblogicaux.jar;%MYSERVER%\clientclassesJDK_HOME and WL_HOME are defined in the setEnv script, and they must exactly match your JDK and WebLogic Server installations. If they do not match your installation, edit the setEnv script using the instructions in Setting your development environment.
Note: If JDK_HOME and WL_HOME are not defined, the build script sets these variables to default directories. However, these defaults may not correctly match your installation.
mkdir build build\META-INF copy *.xml build\META-INF
In the next step, compiled EJB classes are also placed in the build directory, in subdirectories that match the classes' Java package structure.
build.cmd compiles the EJB classes and interfaces into the build directory:
javac -d build -classpath %MYCLASSPATH% Account.java AccountHome.java AccountPK.java ProcessingErrorException.java AccountBean.java
Next, the build script uses the jar utility to create a .jar file of the subdirectories staged in build:
cd build jar cv0f std_ejb_basic_beanManaged.jar META-INF examples cd ..
Once the .jar file has been created, the build script uses ejbc to generate EJB container classes. ejbc inserts the container classes into a new .jar file, which is created in the /weblogic/myserver directory:
java -classpath %MYCLASSPATH% -Dweblogic.home=%WEBLOGICHOME% weblogic.ejbc -compiler javac build\std_ejb_basic_beanManaged.jar %MYSERVER%\ejb_basic_beanManaged.jar
Finally, the script uses javac to compile the EJB example's client classes into the appropriate directories. In the beanManaged example, compiled clients are placed in the /myserver/clientclasses and /myserver/servletclasses directories:
javac -d %MYSERVER%\clientclasses -classpath %MYCLASSPATH% Account.java AccountHome.java AccountPK.java ProcessingErrorException.java Client.java javac -d %MYSERVER%\servletclasses -classpath %MYCLASSPATH% Servlet.java
JDK_HOME=/usr/lib/java WL_HOME=/weblogicAfter editing the file, execute the command:
$ make all
Copyright © 1997-2000 BEA Systems, Inc. All rights reserved.
Last updated 02/7/2000