OpenEJB at SourceForge     OpenEJB at Exolab     
 

Main
   Welcome!
   Download
   Mailing Lists
   The Team
Users
   Quickstart
   Support
   Request Feature
Servers
   Local Server
   Remote Server
Adapters
   Tomcat
Integrators
   Why OpenEJB
   Overview
   Design
   Specification
   Presentation
Developers
   Release Plan
   Source Code
   SourceForge
  



OpenEJB QuickStart Guide


1Abstract
2Join the mailing list
3Get the source
4Building OpenEJB
5Run the test suite
6Deploy your ejb-jar

Abstract

This document is a slightly verbose quickstart, if you are not interested in all the chat and simply want the bare minimum, we offer a Commands-Only Guide for Windows Users and a Commands-Only Guide for Linux/Unix/Mac OS X Users

Join the mailing list

The OpenEJB User list is where the general OpenEJB community goes to ask questions, make suggestions, chat with other users, and keep a finger on the pulse of the project.

Please feel free to ask as many questions as you need while becoming familiar with the project. We believe the perspective of those who are new the project is very valuable and we rely on your feedback to make the project easier to use and understand for everyone. If you have any suggestions on ways we can help those that are new to the project get up to speed more quickly, we are more than willing to listen.

Subscribe/View Archive

Get the source

Getting involved in any Open Source project requires the source. The standard tool for managing source code in open source projects is CVS. If you are not familiar with CVS, take a moment to read our CVS FAQ.

If you have cvs already installed and are ready to go, the following commands are all you need to get the source. The first command logs you into the system, when it prompts you for the CVS password, simply hit the Enter key.

cvs -d:pserver:anonymous@cvs.openejb.sf.net:/cvsroot/openejb login

cvs -z3 -d:pserver:anonymous@cvs.openejb.sf.net:/cvsroot/openejb co openejb

NOTE: The 'cvs ....' commands above should be on one line and executed as one command.

If you are a new user to cvs, the above steps may seem overly simplistic to you. For a more detailed explanation of the login/checkout process, click here.

Building OpenEJB

After doing the checkout, there should be a new directory named 'openejb', change to that directory and execute the following command:

Windows:
[prompt] cd openejb [prompt] openejb build

Unix/Linux/Mac OS X:
[prompt] cd openejb [prompt] chmod 755 openejb.sh bin/* [prompt] ./openejb.sh build

Run the test suite

Now that you have built OpenEJB and other needed jars, it's a good to run the test suite and verify that everything is setup. Execute the following commands:

Windows:
[prompt] openejb test

Unix/Linux/Mac OS X:
[prompt] ./openejb.sh test

Deploy your ejb-jar

OpenEJB comes with a command-line tool to help guide you through deploying your jars in OpenEJB. The options are as follows:

Windows:
[prompt] deploy config-file jar-file

Unix/Linux/Mac OS X:
[prompt] ./openejb.sh deploy config-file jar-file

config-file is the location of the configuration file used to start OpenEJB.

jar-file is the location of the EJB jar file containing the beans you would like to deploy.

Windows Example:
[prompt] openejb deploy conf\default.openejb.conf dist\beans\undeployedBeans.jar

Unix/Linux/Mac OS X Example:
[prompt] ./openejb.sh deploy conf/default.openejb.conf dist/beans/undeployedBeans.jar

NOTE: The text above should be on one line and executed as one command.

The above examples actually work! Go ahead and try them out, you must execute them in the same directory you build the source in. Note, the undeployedBeans.jar was built when you ran the build script earlier.

 
 
   
 SourceForge Logo 
   
 


Java, EJB, JDBC, JNDI, JTA, Sun, Sun Microsystems are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. XML, XML Schema, XSLT and related standards are trademarks or registered trademarks of MIT, INRIA, Keio or others, and a product of the World Wide Web Consortium. All other product names mentioned herein are trademarks of their respective owners.