[Geronimo Wiki] Update of "Deployment" by TobyCabot

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Geronimo Wiki" for change notification.

The following page has been changed by TobyCabot:
http://wiki.apache.org/geronimo/Deployment

The comment on the change is:
minor fixup on 2nd-level headings

------------------------------------------------------------------------------
  
  = Deployment =
  
-   == Deployment From Maven ==
+ == Deployment From Maven ==
  
    The preferred deployment method for a project built with maven is to use the geronimo maven deployment plugin to install an application specific copy of geronimo and deploy one or more modules to it.  More extensive instructions are on the [wiki:Running Running] page.
  
    Generally, a geronimo deployment plan is advisable.  A simple default plan can be generated for all module types except resource adapters.  The plan can either be included in the module next to the spec-required deployment descriptor or external to the module and located by an additional parameter to the deploy command.  Again, this is discussed in more detail on the [wiki:Running Running] page.  Additional aspects of each deployment plan are discussed below.
  
-   == Deployment From the Command Line ==
+ == Deployment From the Command Line ==
  
    The Geronimo deployment tool is packaged in the executable jar `bin/deployer.jar`.  The deployer uses a XML deployment plan to figure out what to do and this xml file determined by the module type. Ultimately this will be produced by a JSR-88 tool but for now an XML aware text editor is the best choice.
  
@@ -58, +58 @@

  
    '''Login:''' The username and password used to deploy to a running server are set in {{{var/security/users.properties}}}, and the user should be a member of the admin group in {{{var/security/groups.properties}}}.  If you don't specify a username and password on the command line, you will be prompted if they turn out to be necessary.
  
-   == Deployment from Ant ==
+ == Deployment from Ant ==
  
    Here's an example fragment from an Ant `build.xml` file:
     {{{
@@ -69, +69 @@

    </target>
  }}}
  
-   == General Configuration ==
+ == General Configuration ==
  
    The schema of Geronimo plans is located in the ''schema/geronimo-config.xsd'' file (in the repo it's in ''modules/deployment/src/schema/geronimo-config.xsd''). The very minimal and working plan looks as follows:
  
@@ -103, +103 @@

  
  = J2EE Application (.ear file) =
  
-   == Configuration ==
+ == Configuration ==
  
    If you're using the M2 snapshot or an older version you must add a `geronimo-application.xml` file to your .ear file.  If you're using recent (post September 2004) CVS versions of Geronimo then this is optional.  Here's an example:
  
@@ -115, +115 @@

  }}}
  
  
-   == Deployment ==
+ == Deployment ==
  
    To deploy your application execute the following command from the Geronimo home directory:
      {{{
@@ -129, +129 @@

  
  = Web Application =
  
-   == Configuration ==
+ == Configuration ==
  
    To deploy a web application in Geronimo, you '''must''' add a `WEB-INF/geronimo-jetty.xml` file to your war file (this restriction will be removed in a future release '''NOTE: It seems that M3 has removed this requirement.''').  An example geronimo-jetty.xml file follows:
      {{{
@@ -154, +154 @@

  
      If true, Geronimo will load classes from the web application before the Geronimo server environment.  If  false, Geronimo will use normal Java class loading rules and check the Geronimo server before loading class from the web application.  False is the preferred setting
  
-   == Deployment ==
+ == Deployment ==
  
    To deploy your web application execute the following command from the Geronimo home directory:
      {{{
@@ -180, +180 @@

  
  = EJB Application =
  
-   == Configuration ==
+ == Configuration ==
  
    To deploy an EJB application in Geronimo, you '''must''' add a `META-INF/openejb-jar.xml` file to your ejb-jar file (this restriction will be removed in a future release).  An example openejb-jar.xml file follows:
      {{{
@@ -202, +202 @@

  
    Change the configId attribute to the configuration identifier you would like to use for your application.  The configId should follow with the domain name of your organization.  
  
-   == Deployment ==
+ == Deployment ==
  
    To deploy your EJB application execute the following command from the Geronimo home directory:
      {{{
@@ -218, +218 @@

  
  = Resource Adapter =
  
-   == Configuration ==
+ == Configuration ==
  
    To deploy a Resource adapter into Geronimo, you '''must''' add a `META-INF/geronimo-ra.xml` file to your rar file (this restriction will be removed in a future release).  An example JCA 1.0 geronimo-ra.xml file follows:
      {{{
@@ -277, +277 @@

  
    Change the configId attribute to the configuration identifier you would like to use for your application.  The configId should follow with the domain name of your organization.  
  
-   == Deployment ==
+ == Deployment ==
  
    To deploy your resource adapter execute the following command from the Geronimo home directory:
      {{{
@@ -294, +294 @@

  
  = Services =
  
-   == Configuration ==
+ == Configuration ==
  
    Geronimo can deploy generalized GBean services in addition to the standard J2EE deployment types.   An example service-plan.xml file follows:
      {{{
@@ -313, +313 @@

  
    Change the configId attribute to the configuration identifier you would like to use for your application.  The configId should follow with the domain name of your organization.  
  
-   == Deployment ==
+ == Deployment ==
  
    To deploy your service execute the following command from the Geronimo home directory:
      {{{