svn commit: r805573 - in /websites/staging/openejb/trunk: ./ content/embedded-configuration.html

[bu...@apache.org]

Author: buildbot
Date: Tue Feb 21 01:25:13 2012
New Revision: 805573

Log:
Staging update by buildbot for openejb

Modified:
    websites/staging/openejb/trunk/   (props changed)
    websites/staging/openejb/trunk/content/embedded-configuration.html

Propchange: websites/staging/openejb/trunk/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 21 01:25:13 2012
@@ -1 +1 @@
-1291514
+1291544

Modified: websites/staging/openejb/trunk/content/embedded-configuration.html
==============================================================================
--- websites/staging/openejb/trunk/content/embedded-configuration.html (original)
+++ websites/staging/openejb/trunk/content/embedded-configuration.html Tue Feb 21 01:25:13 2012
@@ -140,7 +140,7 @@
 
 <h1>Defaults, Overrides and Order</h1>
 
-<p>When booting up OpenEJB for testing via the LocalInitialContextFactory
+<p>When booting up OpenEJB for testing via the <code>LocalInitialContextFactory</code>
 there is quite a bit of flexibility to how things are configured.</p>
 
 <p>OpenEJB will function fine with no configuration at all and will happily
@@ -162,8 +162,8 @@ worry about it)</li>
 environment.  You could do 100% of your configuration in your test case via
 InitialContext propertes, or you could do say 80% in a jndi.properties file
 or openejb.xml file and 20% in your test case via InitialContext
-properties.  You can put 100% of your configuration in a jndi.properties or
-openejb.xml file and override them via InitialContext properties.</p>
+properties.  You can put 100% of your configuration in a <code>jndi.properties</code> or
+<code>openejb.xml</code> file and override them via <code>InitialContext</code> properties.</p>
 
 <p>You can manage the properties how you wish and there is no need for
 redundant definitions if you do not want them.</p>
@@ -174,18 +174,15 @@ redundant definitions if you do not want
 
 <p>Everything you can configure via an openejb.xml (minus the <Deployment>
 element) can be configured/overridden via properties. See <a href="configuring-containers-in-tests.html">Configuring Containers in Tests</a>
- and [Configuring DataSources in Tests]
-.</p>
+ and <a href="configuring-datasources-in-tests.html">Configuring DataSources in Tests</a>.</p>
 
 <p>Everything in your logging.properties can be configured/overridden via
-properties.  See <a href="configuring-logging-in-tests.html">Configuring Logging in Tests</a>
-.</p>
+properties.  See <a href="configuring-logging-in-tests.html">Configuring Logging in Tests</a>.</p>
 
 <p>The properties of persistence units declared in a persistence.xml can be
-configured/overridden via properties.  See <a href="configuring-persistenceunits-in-tests.html">Configuring PersistenceUnits in Tests</a>
-.</p>
+configured/overridden via properties.  See <a href="configuring-persistenceunits-in-tests.html">Configuring PersistenceUnits in Tests</a>.</p>
 
-<p>OpenEJB has many flags that can also be set as properties.  See <a href="openejb-properties.html">OpenEJB Properties</a>
+<p>OpenEJB has many flags that can also be set as properties.  See <a href="properties-listing.html">OpenEJB Properties</a>
  for details on those.</p>
 
 <p><a name="EmbeddedConfiguration-ExampleofusingInitialContextproperties"></a></p>
@@ -195,12 +192,9 @@ configured/overridden via properties.  S
 <pre><code>Properties p = new Properties();
 
 // set the initial context factory
-p.put("java.naming.factory.initial ", "
-</code></pre>
-
-<p>org.apache.openejb.client.LocalInitialContextFactory");</p>
+p.put("java.naming.factory.initial ", "org.apache.openejb.client.LocalInitialContextFactory");
 
-<pre><code>// change some logging
+// change some logging
 p.put("log4j.category.OpenEJB.options ", " debug");
 p.put("log4j.category.OpenEJB.startup ", " debug");
 p.put("log4j.category.OpenEJB.startup.config ", " debug");
@@ -211,12 +205,9 @@ p.put("movieDatabase.JdbcDriver ", " org
 p.put("movieDatabase.JdbcUrl ", " jdbc:hsqldb:mem:moviedb");
 
 // override properties on your "movie-unit" persistence unit
-p.put("movie-unit.hibernate.dialect ", "
-</code></pre>
-
-<p>org.hibernate.dialect.HSQLDialect");</p>
+p.put("movie-unit.hibernate.dialect ", "org.hibernate.dialect.HSQLDialect");
 
-<pre><code>// set some openejb flags
+// set some openejb flags
 p.put("openejb.jndiname.format ", " {ejbName}/{interfaceClass}");
 p.put("openejb.descriptors.output ", " true");
 p.put("openejb.validation.output.level ", " verbose");
@@ -255,7 +246,7 @@ openejb.descriptors.output = true
 openejb.validation.output.level = verbose
 </code></pre>
 
-<p>Then OpenEJB can be booted via the InitialContext as normal.  Properties
+<p>Then OpenEJB can be booted via the <code>InitialContext</code> as normal.  Properties
 can still be used to override any of the above properties:</p>
 
 <pre><code>Properties p = new Properties();