Page History

...

In UNIX, Linux, or Mac OS X, the deploy tool can be executed as follows:

Wiki Markup{{\[user@host openejb-3.0]# ./bin/openejb start}}

Depending on your OpenEJB version, you may need to change execution bits to make the scripts executable. You can do this with the following command.

Wiki Markup{{\[user@host openejb-3.0]# chmod 755 bin/openejb}}

From here on out, it will be assumed that you know how to execute the right openejb script for your operating system and commands will appear in shorthand as show below.

...

Sets the openejb.configuration system variable to the file C:\openejb\conf\mytest.conf. When the server starts up and initializes OpenEJB, this configuration will be used to assemble the container system and load beans.

Example: --local-copy

The local-copy option controls whether Remote interface arguments and results are always copied.

openejb start --local-copy=true (default)

Remote interface business method arguments and results are always copied (via serialization), which is compliant with the EJB standard. Instructs the container system to marshal (ie, copy) all calls between beans are required by the EJB 1.1 specification.

openejb start --local-copy=false

Remote interface business method arguments and results are copied only when the client is in a different JVM. Otherwise, they are passed by reference - as if it were a Local interface. This is faster, of course, but non-compliant with the EJB standard.

Local interfaces are not affected; their arguments and results are passed by reference and never copied Instructs the container system to not marshal (copy) calls between beans. The container system as will pass parameters and return values without copying or marshalling as is required for EJB 2.0 Local interfaces.

CONFIG OVERRIDE EXAMPLES

...