Java™ Application Development on Linux - Dator

22.2 EJBs: You Don’t Know Beans?501unmarshaled, they don’t have to be serializable. For some applications, this isthe only way that they can use beans.Finally, keep in mind that the choice of local versus remote interfaces isnot necessarily an either-or choice. For our session bean we have defined bothkinds of interfaces. Then the deployment can determine which one will be used.22.2.6 Compiling Your BeansIn order to compile these bean-related Java classes, you need to have a J2EEJAR in your classpath. If you’ve installed JBoss into /usr/local/jboss, youcould add the JAR to your classpath this way:export CLASSPATH="/usr/local/jboss/client"\"/jboss-j2ee.jar:.:${CLASSPATH}"If you have the Sun J2EE reference implementation installed on yoursystem (in /usr/local), then you could use:export CLASSPATH="/usr/local/SUNWappserver"\"/lib/j2ee.jar:.:${CLASSPATH}"If you have Geronimo installed on your system (with an environmentvariable GHOME to hold its location), then you would use: 1export CLASSPATH="${GHOME}/repository/geronimo-spec/jars"\"/geronimo-spec-j2ee-1.0-M1.jar:.:${CLASSPATH}"In any case, the point is to have in your classpath the JAR file whichcontains the javax/ejb/ classes, such as EJBObject.class. If you haven’tinstalled one of these containers on your machine, then download a copy ofthe JAR from the machine where that container is installed. Put your copysomewhere in your classpath, as in the examples above.1. Our JAR is named geronimo-spec-j2ee-1.0-M1.jar but yours will likely have a differentname by the time the J2EE-certified version of Geronimo is available. It may likely justhave the trailing -M1 dropped from the name; check in the geronimo-spec/jars directory.Another option is to use any of the J2EE JARs, for example, from the Sun reference implementation.That’s the advantage of standards. Any of them should work for this compilation step.The resulting compiled code should be deployable to any server. “Compile once, runanywhere,” right?