You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by bu...@apache.org on 2011/07/11 01:55:38 UTC
svn commit: r792504 - /websites/staging/openejb/trunk/content/
Author: buildbot
Date: Sun Jul 10 23:55:37 2011
New Revision: 792504
Log:
Staging update by buildbot
Modified:
websites/staging/openejb/trunk/content/application-discovery-via-the-classpath.html
websites/staging/openejb/trunk/content/configuration.html
websites/staging/openejb/trunk/content/configuring-javamail.html
websites/staging/openejb/trunk/content/configuring-persistenceunits-in-tests.html
websites/staging/openejb/trunk/content/containers.html
websites/staging/openejb/trunk/content/datasource-password-encryption.html
websites/staging/openejb/trunk/content/deployments.html
websites/staging/openejb/trunk/content/details-on-openejb-jar.html
websites/staging/openejb/trunk/content/dynamic-datasource.html
websites/staging/openejb/trunk/content/embedded-and-remotable.html
websites/staging/openejb/trunk/content/failover.html
websites/staging/openejb/trunk/content/faq.html
websites/staging/openejb/trunk/content/getting-started.html
websites/staging/openejb/trunk/content/hibernate.html
websites/staging/openejb/trunk/content/jms-resources-and-mdb-container.html
websites/staging/openejb/trunk/content/jpa-concepts.html
websites/staging/openejb/trunk/content/management-and-voting.html
websites/staging/openejb/trunk/content/openejb-3.0.html
websites/staging/openejb/trunk/content/openejb-3.1.1.html
websites/staging/openejb/trunk/content/openejb-3.1.html
websites/staging/openejb/trunk/content/openejb-release-process.html
websites/staging/openejb/trunk/content/openjpa.html
websites/staging/openejb/trunk/content/persistence-unit-ref.html
websites/staging/openejb/trunk/content/spring-and-openejb-3.0.html
websites/staging/openejb/trunk/content/tips-and-suggestions.html
websites/staging/openejb/trunk/content/tomcat-installation.html
websites/staging/openejb/trunk/content/webadmin.html
Modified: websites/staging/openejb/trunk/content/application-discovery-via-the-classpath.html
==============================================================================
--- websites/staging/openejb/trunk/content/application-discovery-via-the-classpath.html (original)
+++ websites/staging/openejb/trunk/content/application-discovery-via-the-classpath.html Sun Jul 10 23:55:37 2011
@@ -179,9 +179,9 @@ This is the recommended approach for peo
need for you to specify any path information which tends to complicate
builds.</p>
-<pre><code>h1. Including/Excluding paths (advanced)
+<h1>Including/Excluding paths (advanced)</h1>
-If you do not like the idea of having the ejb-jar.xml in your app or an
+<pre><code>If you do not like the idea of having the ejb-jar.xml in your app or an
</code></pre>
<p>openejb.xml, we can search the classpath for annotated beans (@Stateless,
@@ -249,9 +249,9 @@ like to use these settings to also filte
descriptors, set the <em>openejb.deployments.classpath.filter.descriptors</em>
property to <em>true</em>. The default is <em>false</em>.</p>
-<pre><code>h1. Troubleshooting
+<h1>Troubleshooting</h1>
-If you're having trouble determining if the META-INF/ejb-jar.xml file for
+<pre><code>If you're having trouble determining if the META-INF/ejb-jar.xml file for
</code></pre>
<p>your ejb module is in the classpath, a little debug code like this in your
Modified: websites/staging/openejb/trunk/content/configuration.html
==============================================================================
--- websites/staging/openejb/trunk/content/configuration.html (original)
+++ websites/staging/openejb/trunk/content/configuration.html Sun Jul 10 23:55:37 2011
@@ -207,9 +207,9 @@ OpenEJB saves deployment descriptors - e
<Deployments dir="beans/" />
</openejb></p>
-<pre><code>h1. Basic Layout
+<h1>Basic Layout</h1>
-Basically, openejb.base is the source for 100% of all configuration
+<pre><code>Basically, openejb.base is the source for 100% of all configuration
</code></pre>
<p>information and third party config files (log4j, castor, instantdb,
@@ -272,9 +272,9 @@ own and are also loaded from the openeb.
<p>to the classpath.</p>
-<pre><code>h2. Summary
+<h2>Summary</h2>
-A summary of the above in a different notation:
+<pre><code>A summary of the above in a different notation:
{noformat}
openejb.home = user.dir (can be set explicitly)
@@ -288,9 +288,9 @@ deployments = paths listed in openejb.c
Classpath includes openejb.home/lib and openejb.home/dist
{noformat}</p>
-<pre><code>h2. Example layout
+<h2>Example layout</h2>
-In this one the openejb.home and openejb.base are set, everything else is
+<pre><code>In this one the openejb.home and openejb.base are set, everything else is
</code></pre>
<p>defaulted. The openejb.conf file as been updated to point to the ejb jars
@@ -308,11 +308,11 @@ by name (abc-ejbs.jar and xyz-ejbs.jar).
/home/jsmith/foo_app/xyz-ejbs.jar (Deployment entry in openejb.conf)
/home/jsmith/foo_app/logs/
{noformat}
+</code></pre>
+<h2>Another Example layout</h2>
-h2. Another Example layout
-
-In this example openejb.home and openejb.base are setup as well as the
+<pre><code>In this example openejb.home and openejb.base are setup as well as the
</code></pre>
<p>explicit paths for the openejb and log4j configuration files.</p>
Modified: websites/staging/openejb/trunk/content/configuring-javamail.html
==============================================================================
--- websites/staging/openejb/trunk/content/configuring-javamail.html (original)
+++ websites/staging/openejb/trunk/content/configuring-javamail.html Sun Jul 10 23:55:37 2011
@@ -187,9 +187,9 @@ which may cause issues if the provider d
before attempting to use them.
{note}</p>
-<pre><code>h1. Overriding
+<h1>Overriding</h1>
-If you wanted to do a System property or InitialContext property override
+<pre><code>If you wanted to do a System property or InitialContext property override
</code></pre>
<p>of the above example mail session, you could do so like this:</p>
Modified: websites/staging/openejb/trunk/content/configuring-persistenceunits-in-tests.html
==============================================================================
--- websites/staging/openejb/trunk/content/configuring-persistenceunits-in-tests.html (original)
+++ websites/staging/openejb/trunk/content/configuring-persistenceunits-in-tests.html Sun Jul 10 23:55:37 2011
@@ -235,8 +235,7 @@ provider (in this case Hibernate). With
understand or modify these properties. Details on that one exception
below.</p>
-<pre><code>h3. No need to specify a "transaction lookup" property
-</code></pre>
+<h3>No need to specify a "transaction lookup" property</h3>
<p>All vendors have such a property for getting a reference to the container's
TransactionManager and nothing works if this is not set correctly to the
@@ -248,9 +247,9 @@ take the liberty of setting it for you.<
<p>will set for you:</p>
-<pre><code>h4. Provider org.hibernate.ejb.HibernatePersistence
+<h4>Provider org.hibernate.ejb.HibernatePersistence</h4>
-When using this provider, the *hibernate.transaction.manager_lookup_class*
+<pre><code>When using this provider, the *hibernate.transaction.manager_lookup_class*
</code></pre>
<p>will be automatically set by OpenEJB to
@@ -259,10 +258,11 @@ is already set in the persistence unit i
with the standard "org.hibernate.transaction." prefix. </p>
<pre><code>Custom lookup implementations will never be overwritten.
+</code></pre>
-h4. Provider oracle.toplink.essentials.PersistenceProvider
+<h4>Provider oracle.toplink.essentials.PersistenceProvider</h4>
-Or _oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider_.
+<pre><code>Or _oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider_.
When using this provider, the *toplink.target-server* will be automatically
</code></pre>
@@ -273,10 +273,11 @@ overwritten if it starts with the standa
prefix. </p>
<pre><code>Custom transaction controller implementations will never be overwritten.
+</code></pre>
-h4. Provider org.eclipse.persistence.jpa.PersistenceProvider
+<h4>Provider org.eclipse.persistence.jpa.PersistenceProvider</h4>
-Or _org.eclipse.persistence.jpa.osgi.PersistenceProvider_.
+<pre><code>Or _org.eclipse.persistence.jpa.osgi.PersistenceProvider_.
When using this provider, the *eclipselink.target-server* will be
</code></pre>
@@ -287,10 +288,11 @@ is already set in the persistence unit i
with the standard "org.eclipse.persistence.transaction." prefix. </p>
<pre><code>Custom transaction controller implementations will never be overwritten.
+</code></pre>
-h4. Provider org.apache.openjpa.persistence.PersistenceProviderImpl
+<h4>Provider org.apache.openjpa.persistence.PersistenceProviderImpl</h4>
-OpenJPA is capable of discovering the correct method for locating the
+<pre><code>OpenJPA is capable of discovering the correct method for locating the
</code></pre>
<p>TransactionManager without the need for users to specify the specific
Modified: websites/staging/openejb/trunk/content/containers.html
==============================================================================
--- websites/staging/openejb/trunk/content/containers.html (original)
+++ websites/staging/openejb/trunk/content/containers.html Sun Jul 10 23:55:37 2011
@@ -213,9 +213,9 @@ $ system
<p>called "Default CMP Container".</p>
-<pre><code>h1. Naming your Container
+<h1>Naming your Container</h1>
-You can call the container anything you want, just change the value of the
+<pre><code>You can call the container anything you want, just change the value of the
</code></pre>
<p>id attribute. Here is a container called "My PostgreSQL Contianer"</p>
@@ -273,9 +273,9 @@ or -help for more information.</p>
do not redeploy the myCMPBean.jar to point to the new container id, you
will have big problems!</p>
-<pre><code>h1. Container types
+<h1>Container types</h1>
-You can declare as many containers as you want. The available container
+<pre><code>You can declare as many containers as you want. The available container
</code></pre>
<p>types are:
Modified: websites/staging/openejb/trunk/content/datasource-password-encryption.html
==============================================================================
--- websites/staging/openejb/trunk/content/datasource-password-encryption.html (original)
+++ websites/staging/openejb/trunk/content/datasource-password-encryption.html Sun Jul 10 23:55:37 2011
@@ -210,28 +210,31 @@ You can plug your own algorithm to exten
do such, you just need to implement the </p>
<pre><code>{tip}
+</code></pre>
+
+<h2>Command line tool</h2>
-h2. Command line tool
-Apache OpenEJB also provides a command line tool allowing password cipher
+<pre><code>Apache OpenEJB also provides a command line tool allowing password cipher
</code></pre>
<p>algorithm. Actually, it's useful to get the ciphered value of a plain text
value using a given algorithm.</p>
-<pre><code>h3. NAME
+<h3>NAME</h3>
-openejb cipher - OpenEJB Cypher Tool
+<pre><code>openejb cipher - OpenEJB Cypher Tool
+</code></pre>
-h3. SYNOPSIS
+<h3>SYNOPSIS</h3>
-openejb cipher [#options]
+<pre><code>openejb cipher [#options]
</code></pre>
<p><value></p>
-<pre><code>h3. DESCRIPTION
+<h3>DESCRIPTION</h3>
-The OpenEJB Cipher tool is an OPTIONAL tool that allows you to use
+<pre><code>The OpenEJB Cipher tool is an OPTIONAL tool that allows you to use
</code></pre>
<p>{{PasswordCipher}} algorithm to encode/decode values.</p>
@@ -280,10 +283,11 @@ In UNIX, Linux, or Mac OS X, the cipher
shorthand as show below.</p>
<pre><code>{{openejb cipher --help}}
+</code></pre>
-h3. OPTIONS
+<h3>OPTIONS</h3>
-|-h, --_help_ |Lists these options and exit.|
+<pre><code>|-h, --_help_ |Lists these options and exit.|
|-c, --_cipher_ |Specifies the password cipher implementation to use
</code></pre>
@@ -291,9 +295,9 @@ h3. OPTIONS
|-d, --<em>decrypt</em> |Switches command line tool to decrypt.|
|-e, --<em>encrypt</em> |Switches command line tool to encrypt (default).|</p>
-<pre><code>h3. EXAMPLES
+<h3>EXAMPLES</h3>
-Encrypt a plain password using the default algorithm.
+<pre><code>Encrypt a plain password using the default algorithm.
{{openejb cipher Passw0rd}}
Output
Modified: websites/staging/openejb/trunk/content/deployments.html
==============================================================================
--- websites/staging/openejb/trunk/content/deployments.html (original)
+++ websites/staging/openejb/trunk/content/deployments.html Sun Jul 10 23:55:37 2011
@@ -179,9 +179,9 @@ So, for example, of the value of openejb
OpenEJB would look for the jar 'c:\timeapp\timeTrack.jar'. See the [OPENEJB:Configuration]
guide for more details.</p>
-<pre><code>h2. A directory of jars
+<h2>A directory of jars</h2>
-To point to a directory that contains several jar files that OpenEJB should
+<pre><code>To point to a directory that contains several jar files that OpenEJB should
</code></pre>
<p>load, simply declare a 'Deployments' element with a 'dir' attribute
@@ -248,9 +248,9 @@ to 'C:\myapp\acmeEjbs' as shown below.</
OpenEJB will treat the directory as an unpacked ejb jar. Otherwise OpenEJB
will look for ejb jar files to load as detailed in the above section.</p>
-<pre><code>h1. Log file
+<h1>Log file</h1>
-When trying to figure out if your ejbs were loaded, the openejb.log file is
+<pre><code>When trying to figure out if your ejbs were loaded, the openejb.log file is
</code></pre>
<p>an incredible asset.</p>
Modified: websites/staging/openejb/trunk/content/details-on-openejb-jar.html
==============================================================================
--- websites/staging/openejb/trunk/content/details-on-openejb-jar.html (original)
+++ websites/staging/openejb/trunk/content/details-on-openejb-jar.html Sun Jul 10 23:55:37 2011
@@ -216,9 +216,9 @@ client's JNDI namespace. The <em>contain
your openejb.conf file that you would like the bean to run in. There MUST
be one <em>ejb-deployment</em> element for each EJB in your jar.</p>
-<pre><code>h1. What if my bean uses a JDBC datasource?
+<h1>What if my bean uses a JDBC datasource?</h1>
-Then you simply add a <resource-link> element to your <ejb-deployment>
+<pre><code>Then you simply add a <resource-link> element to your <ejb-deployment>
</code></pre>
<p>element like this</p>
Modified: websites/staging/openejb/trunk/content/dynamic-datasource.html
==============================================================================
--- websites/staging/openejb/trunk/content/dynamic-datasource.html (original)
+++ websites/staging/openejb/trunk/content/dynamic-datasource.html Sun Jul 10 23:55:37 2011
@@ -361,9 +361,9 @@ META-INF/<package>. For example META-INF
</ServiceProvider>
</ServiceJar>{code}</p>
-<pre><code>h2. openejb.xml
+<h2>openejb.xml</h2>
-In the openejb.xml file, you have to declare your dynamic database and in
+<pre><code>In the openejb.xml file, you have to declare your dynamic database and in
</code></pre>
<p>our example it needs the proxied datasources too:</p>
Modified: websites/staging/openejb/trunk/content/embedded-and-remotable.html
==============================================================================
--- websites/staging/openejb/trunk/content/embedded-and-remotable.html (original)
+++ websites/staging/openejb/trunk/content/embedded-and-remotable.html Sun Jul 10 23:55:37 2011
@@ -258,13 +258,15 @@ to the embedded container system over th
<p>{snippet:id=setup|url=openejb3/examples/telephone-stateful/src/test/java/org/superbiz/telephone/TelephoneTest.java|lang=java}</p>
-<p>h2. LocalInitialContextFactory: making in-vm calls to a remote business
-interface</p>
+<h2>LocalInitialContextFactory: making in-vm calls to a remote business</h2>
+
+<p>interface</p>
<p>{snippet:id=localcontext|url=openejb3/examples/telephone-stateful/src/test/java/org/superbiz/telephone/TelephoneTest.java|lang=java}</p>
-<p>h2. RemoteInitialContextFactory: making networked calls to a remote
-business interface</p>
+<h2>RemoteInitialContextFactory: making networked calls to a remote</h2>
+
+<p>business interface</p>
<p>This is the part you would want to do in apps that are running a different
VM than the one in which the ejb container is embedded. These "client" VMs
Modified: websites/staging/openejb/trunk/content/failover.html
==============================================================================
--- websites/staging/openejb/trunk/content/failover.html (original)
+++ websites/staging/openejb/trunk/content/failover.html Sun Jul 10 23:55:37 2011
@@ -302,9 +302,9 @@ there are no other servers to talk to.</
connect directly to that server, at which point that server will share the
full list of its peers.</p>
-<pre><code>h2. Multicast Servers with TCP Clients
+<h2>Multicast Servers with TCP Clients</h2>
-Note that clients do not need to use multicast to communicate with servers.
+<pre><code>Note that clients do not need to use multicast to communicate with servers.
</code></pre>
<p>Servers can use multicast to discover each other, but clients are still
@@ -394,11 +394,11 @@ p.put(Context.PROVIDER_URL,
"failover:ejbd://192.168.1.20:4201,ejbd://192.168.1.30:4201");
InitialContext remoteContext = new InitialContext(p);</p>
-<pre><code>h2. Considerations
+<h2>Considerations</h2>
-h3. Network size
+<h3>Network size</h3>
-The general disadvantage of this topology is the number of connections
+<pre><code>The general disadvantage of this topology is the number of connections
</code></pre>
<p>required. The number of connections for the network of servers is equal to
@@ -415,9 +415,9 @@ only needs "n - 1" connections.</p>
From a pure threading perspective, the option is extremely efficient with
just one thread to listen and broadcast to many peers. </p>
-<pre><code>h3. Double connect
+<h3>Double connect</h3>
-It is possible in this process that two servers learn of each other at the
+<pre><code>It is possible in this process that two servers learn of each other at the
</code></pre>
<p>same time and each attempts to connect to the other simultaneously,
@@ -427,9 +427,9 @@ connections will be dropped and one will
condition rarely happens and can be avoided almost entirely by fanning out
server startup by as little as 100 milliseconds.</p>
-<pre><code>h1. Multipoint Configuration Recommendations
+<h1>Multipoint Configuration Recommendations</h1>
-As mentioned above the {{initialServers}} is only used for bootstrapping
+<pre><code>As mentioned above the {{initialServers}} is only used for bootstrapping
</code></pre>
<p>the multipoint network. Once running, all servers will dynamically
@@ -451,9 +451,9 @@ dynamically.</p>
<p>must already be running when the server starts or the server might never
become introduced and connected to all the other servers in the network.</p>
-<pre><code>h2. Failed scenario (background)
+<h2>Failed scenario (background)</h2>
-As an example of a failed scenario, imagine there are three servers;
+<pre><code>As an example of a failed scenario, imagine there are three servers;
</code></pre>
<p>server1, server2, server3. They are setup only to point to the server in
@@ -514,9 +514,9 @@ listing nothing at all, then all servers
regardless of startup order; assuming all three servers did eventually
start.</p>
-<pre><code>h2. Bootstrapping Three Servers or Less
+<h2>Bootstrapping Three Servers or Less</h2>
-In a three sever scenario, we recommend simply having all three servers
+<pre><code>In a three sever scenario, we recommend simply having all three servers
</code></pre>
<p>list all three servers. </p>
@@ -534,8 +534,9 @@ There's no harm to a server listing itse
<p>maintain and it will work even if you decide not to start one of the three
servers.</p>
-<pre><code>h2. Bootstrapping Four Servers or More
-{span:style=float: right;}
+<h2>Bootstrapping Four Servers or More</h2>
+
+<pre><code>{span:style=float: right;}
{gliffy:name=MultipointFour|space=OPENEJBx30|page=Failover|align=right|border=false|size=L|version=3}
{span}
@@ -586,10 +587,11 @@ server in the network as all servers wil
convenience.</p>
<pre><code>{div:style=clear:both;}{div}
+</code></pre>
-h2. Command line overrides
+<h2>Command line overrides</h2>
-Always remember that any property in a conf/<server-service>.properties
+<pre><code>Always remember that any property in a conf/<server-service>.properties
</code></pre>
<p>file can be overridden on the command line or via system properties. So it
Modified: websites/staging/openejb/trunk/content/faq.html
==============================================================================
--- websites/staging/openejb/trunk/content/faq.html (original)
+++ websites/staging/openejb/trunk/content/faq.html Sun Jul 10 23:55:37 2011
@@ -200,8 +200,9 @@ database like Derby, so it is usable in
application is run via Maven, Ant, Intellij, Eclipse, NetBeans, JUnit,
TestNG, etc.</p>
-<p>h3. Can I start and stop OpenEJB from an IDE? If yes, which IDE is
-supported by OpenEJB?</p>
+<h3>Can I start and stop OpenEJB from an IDE? If yes, which IDE is</h3>
+
+<p>supported by OpenEJB?</p>
<p>The short answer is yes. The basic approach for all embedding scenarios is
to 1) add OpenEJB to your classpath, and 2) construct your InitialContext
@@ -212,8 +213,9 @@ http://openejb.apache.org/embedding-open
embed openejb in your application and IDE. See <a href="openejbx30:application-discovery-via-the-classpath.html">Application discovery via the classpath</a>
for various ways to have your applications discovered. </p>
-<p>h3. During embedded testing, how can I externalize all my DataSource
-configuration? </p>
+<h3>During embedded testing, how can I externalize all my DataSource</h3>
+
+<p>configuration? </p>
<p>Create an openejb.xml file in any directory that gets added to your test
classpath. For maven, something that winds up directly under
Modified: websites/staging/openejb/trunk/content/getting-started.html
==============================================================================
--- websites/staging/openejb/trunk/content/getting-started.html (original)
+++ websites/staging/openejb/trunk/content/getting-started.html Sun Jul 10 23:55:37 2011
@@ -152,8 +152,9 @@
<P>
<!-- $BODY -->
<DIV id="PageContent">
- <p>h2. The following instructions are written using Eclipse 3.2. We will
-refer to the install location of OpenEJB as OPENEJB_HOME</p>
+ <h2> The following instructions are written using Eclipse 3.2. We will</h2>
+
+<p>refer to the install location of OpenEJB as OPENEJB_HOME</p>
<p>Here are some basic steps you need to perform to get started with OpenEJB
1. Download and install OpenEJB
Modified: websites/staging/openejb/trunk/content/hibernate.html
==============================================================================
--- websites/staging/openejb/trunk/content/hibernate.html (original)
+++ websites/staging/openejb/trunk/content/hibernate.html Sun Jul 10 23:55:37 2011
@@ -199,9 +199,9 @@ always be used and never replaced by Ope
<p>to add it.</p>
-<pre><code>h1. Not using OpenEJB in production?
+<h1>Not using OpenEJB in production?</h1>
-If you're using OpenEJB 3.0 which does not support the dynamic switching of
+<pre><code>If you're using OpenEJB 3.0 which does not support the dynamic switching of
</code></pre>
<p>the <em>hibernate.transaction.manager</em>lookup_class_ this is one way to achieve
Modified: websites/staging/openejb/trunk/content/jms-resources-and-mdb-container.html
==============================================================================
--- websites/staging/openejb/trunk/content/jms-resources-and-mdb-container.html (original)
+++ websites/staging/openejb/trunk/content/jms-resources-and-mdb-container.html Sun Jul 10 23:55:37 2011
@@ -227,9 +227,9 @@ context.lookup("openejb:Resource/FooQueu
javax.jms.Topic topic = (Topic)
context.lookup("openejb:Resource/BarTopic");</p>
-<pre><code>h1. Internal ActiveMQ Broker
+<h1>Internal ActiveMQ Broker</h1>
-_TODO_
+<pre><code>_TODO_
</code></pre>
</DIV>
Modified: websites/staging/openejb/trunk/content/jpa-concepts.html
==============================================================================
--- websites/staging/openejb/trunk/content/jpa-concepts.html (original)
+++ websites/staging/openejb/trunk/content/jpa-concepts.html Sun Jul 10 23:55:37 2011
@@ -329,9 +329,9 @@ entityTransaction.commit();
<p>}</p>
-<pre><code>h1. Valid TRANSACTION Unit usage
+<h1>Valid TRANSACTION Unit usage</h1>
-EJBs can use TRANSACTION persistence units through the EntityManager as
+<pre><code>EJBs can use TRANSACTION persistence units through the EntityManager as
</code></pre>
<p>follows:</p>
Modified: websites/staging/openejb/trunk/content/management-and-voting.html
==============================================================================
--- websites/staging/openejb/trunk/content/management-and-voting.html (original)
+++ websites/staging/openejb/trunk/content/management-and-voting.html Sun Jul 10 23:55:37 2011
@@ -227,8 +227,9 @@ community are significant to the project
cause for pause and discussion. We frequently encourage and welcome votes
from anyone in the community regardless of status.</p>
-<p>h2. Q. Voting on people: Is it hard to vote -1 in public / Can someone get
-their feelings hurt ?</p>
+<h2>Q. Voting on people: Is it hard to vote -1 in public / Can someone get</h2>
+
+<p>their feelings hurt ?</p>
<p>Yes and yes. Voting in public requires greater care and sensitivity on
behalf of everyone; the vote proposer, the voters, and the votee. Prior to
Modified: websites/staging/openejb/trunk/content/openejb-3.0.html
==============================================================================
--- websites/staging/openejb/trunk/content/openejb-3.0.html (original)
+++ websites/staging/openejb/trunk/content/openejb-3.0.html Sun Jul 10 23:55:37 2011
@@ -547,9 +547,9 @@ WARN ... Movies: Ignoring @TransactionA
org.superbiz.injection.jpa.Movies method addMovie.
Annotation only usable on the bean class.</p>
-<pre><code>h2. JNDI Name Formatting
+<h2>JNDI Name Formatting</h2>
-A complication when using EJB is that plain client applications are at the
+<pre><code>A complication when using EJB is that plain client applications are at the
</code></pre>
<p>mercy of vendor's chosen methodology for how JNDI names should be
@@ -559,8 +559,9 @@ Supply us with a formatting string, such
"ejb/{ejbName}/{interfaceClass.simpleName}", to get a JNDI layout that
best matches your needs.</p>
-<pre><code>h1. Changelog
-{swizzlejira}
+<h1>Changelog</h1>
+
+<pre><code>{swizzlejira}
#set ( $jira =
</code></pre>
@@ -568,23 +569,23 @@ best matches your needs.</p>
)
#set( $issues = $jira.issues )</p>
-<pre><code>h3. New Features:
+<h3>New Features:</h3>
-{swizzlejiraissues:issues=$as.param($issues.equals("type", "New
+<pre><code>{swizzlejiraissues:issues=$as.param($issues.equals("type", "New
</code></pre>
<p>Feature").descending("id"))|columns=key;summary}</p>
-<pre><code>h3. Improvements:
+<h3>Improvements:</h3>
-{swizzlejiraissues:issues=$as.param($issues.equals("type",
+<pre><code>{swizzlejiraissues:issues=$as.param($issues.equals("type",
</code></pre>
<p>"Improvement"))|columns=key;summary}</p>
-<pre><code>h3. Tasks & Sub-Tasks:
+<h3>Tasks & Sub-Tasks:</h3>
-{swizzlejiraissues:issues=$as.param($issues.matches("type",
+<pre><code>{swizzlejiraissues:issues=$as.param($issues.matches("type",
</code></pre>
<p>"Task|Sub-task").sort("summary"))|columns=key;summary}</p>
Modified: websites/staging/openejb/trunk/content/openejb-3.1.1.html
==============================================================================
--- websites/staging/openejb/trunk/content/openejb-3.1.1.html (original)
+++ websites/staging/openejb/trunk/content/openejb-3.1.1.html Sun Jul 10 23:55:37 2011
@@ -664,9 +664,9 @@ WARN ... Movies: Ignoring @TransactionA
org.superbiz.injection.jpa.Movies method addMovie.
Annotation only usable on the bean class.</p>
-<pre><code>h2. JNDI Name Formatting
+<h2>JNDI Name Formatting</h2>
-A complication when using EJB is that plain client applications are at the
+<pre><code>A complication when using EJB is that plain client applications are at the
</code></pre>
<p>mercy of vendor's chosen methodology for how JNDI names should be
@@ -676,8 +676,9 @@ Supply us with a formatting string, such
"ejb/{ejbName}/{interfaceClass.simpleName}", to get a JNDI layout that
best matches your needs.</p>
-<pre><code>h1. Changelog
-{swizzlejira}
+<h1>Changelog</h1>
+
+<pre><code>{swizzlejira}
#set ( $jira =
</code></pre>
@@ -685,23 +686,23 @@ best matches your needs.</p>
)
#set( $issues = $jira.issues )</p>
-<pre><code>h3. New Features:
+<h3>New Features:</h3>
-{swizzlejiraissues:issues=$as.param($issues.equals("type", "New
+<pre><code>{swizzlejiraissues:issues=$as.param($issues.equals("type", "New
</code></pre>
<p>Feature").descending("id"))|columns=key;summary}</p>
-<pre><code>h3. Improvements:
+<h3>Improvements:</h3>
-{swizzlejiraissues:issues=$as.param($issues.equals("type",
+<pre><code>{swizzlejiraissues:issues=$as.param($issues.equals("type",
</code></pre>
<p>"Improvement"))|columns=key;summary}</p>
-<pre><code>h3. Tasks & Sub-Tasks:
+<h3>Tasks & Sub-Tasks:</h3>
-{swizzlejiraissues:issues=$as.param($issues.matches("type",
+<pre><code>{swizzlejiraissues:issues=$as.param($issues.matches("type",
</code></pre>
<p>"Task|Sub-task").sort("summary"))|columns=key;summary}</p>
Modified: websites/staging/openejb/trunk/content/openejb-3.1.html
==============================================================================
--- websites/staging/openejb/trunk/content/openejb-3.1.html (original)
+++ websites/staging/openejb/trunk/content/openejb-3.1.html Sun Jul 10 23:55:37 2011
@@ -667,9 +667,9 @@ WARN ... Movies: Ignoring @TransactionA
org.superbiz.injection.jpa.Movies method addMovie.
Annotation only usable on the bean class.</p>
-<pre><code>h2. JNDI Name Formatting
+<h2>JNDI Name Formatting</h2>
-A complication when using EJB is that plain client applications are at the
+<pre><code>A complication when using EJB is that plain client applications are at the
</code></pre>
<p>mercy of vendor's chosen methodology for how JNDI names should be
@@ -679,8 +679,9 @@ Supply us with a formatting string, such
"ejb/{ejbName}/{interfaceClass.simpleName}", to get a JNDI layout that
best matches your needs.</p>
-<pre><code>h1. Changelog
-{swizzlejira}
+<h1>Changelog</h1>
+
+<pre><code>{swizzlejira}
#set ( $jira =
</code></pre>
@@ -688,23 +689,23 @@ best matches your needs.</p>
)
#set( $issues = $jira.issues )</p>
-<pre><code>h3. New Features:
+<h3>New Features:</h3>
-{swizzlejiraissues:issues=$as.param($issues.equals("type", "New
+<pre><code>{swizzlejiraissues:issues=$as.param($issues.equals("type", "New
</code></pre>
<p>Feature").descending("id"))|columns=key;summary}</p>
-<pre><code>h3. Improvements:
+<h3>Improvements:</h3>
-{swizzlejiraissues:issues=$as.param($issues.equals("type",
+<pre><code>{swizzlejiraissues:issues=$as.param($issues.equals("type",
</code></pre>
<p>"Improvement"))|columns=key;summary}</p>
-<pre><code>h3. Tasks & Sub-Tasks:
+<h3>Tasks & Sub-Tasks:</h3>
-{swizzlejiraissues:issues=$as.param($issues.matches("type",
+<pre><code>{swizzlejiraissues:issues=$as.param($issues.matches("type",
</code></pre>
<p>"Task|Sub-task").sort("summary"))|columns=key;summary}</p>
Modified: websites/staging/openejb/trunk/content/openejb-release-process.html
==============================================================================
--- websites/staging/openejb/trunk/content/openejb-release-process.html (original)
+++ websites/staging/openejb/trunk/content/openejb-release-process.html Sun Jul 10 23:55:37 2011
@@ -177,9 +177,9 @@ svn copy -m "OpenEJB 3.0-beta-1 branch"
https://svn.apache.org/repos/asf/openejb/trunk/openejb3 \
https://svn.apache.org/repos/asf/openejb/branches/3.0-beta-1</p>
-<pre><code>h1. Merging things from trunk to the branch
+<h1>Merging things from trunk to the branch</h1>
-While fixing issues in the branch and trunk in parallel it may happen that
+<pre><code>While fixing issues in the branch and trunk in parallel it may happen that
</code></pre>
<p>some changes in trunk have not been applied to the branch. Provided you're
@@ -431,9 +431,9 @@ href="http://openejb.apache.org/">http:/
<P>
<P></P></BODY></HTML></p>
-<pre><code>h1. Publishing
+<h1>Publishing</h1>
-When all voting is done
+<pre><code>When all voting is done
{code:none}
mvn stage:copy -Dsource="http://people.apache.org/~dblevins/stage/repo/" \
Modified: websites/staging/openejb/trunk/content/openjpa.html
==============================================================================
--- websites/staging/openejb/trunk/content/openjpa.html (original)
+++ websites/staging/openejb/trunk/content/openjpa.html Sun Jul 10 23:55:37 2011
@@ -200,11 +200,11 @@ p.put("movieDatabaseUnmanaged.JdbcDriver
p.put("movieDatabaseUnmanaged.JdbcUrl", "jdbc:hsqldb:mem:moviedb");
p.put("movieDatabaseUnmanaged.JtaManaged", "false");</p>
-<pre><code>h1. Common exceptions
+<h1>Common exceptions</h1>
-h2. Table not found in statement
+<h2>Table not found in statement</h2>
-Or as derby will report it "Table 'abc.xyz' doesn't exist"
+<pre><code>Or as derby will report it "Table 'abc.xyz' doesn't exist"
Someone has to create the database structure for your persistent objects.
</code></pre>
Modified: websites/staging/openejb/trunk/content/persistence-unit-ref.html
==============================================================================
--- websites/staging/openejb/trunk/content/persistence-unit-ref.html (original)
+++ websites/staging/openejb/trunk/content/persistence-unit-ref.html Sun Jul 10 23:55:37 2011
@@ -215,11 +215,11 @@ following xml.</p>
</injection-target>
</persistence-unit-ref></p>
-<pre><code>h1. Lookup only
+<h1>Lookup only</h1>
-h2. Via annotation
+<h2>Via annotation</h2>
-{code:title=Usable by EJB, Interceptor, Servlet, Filter, or Listener}
+<pre><code>{code:title=Usable by EJB, Interceptor, Servlet, Filter, or Listener}
package org.superbiz;
import javax.persistence.PersistenceUnit;
Modified: websites/staging/openejb/trunk/content/spring-and-openejb-3.0.html
==============================================================================
--- websites/staging/openejb/trunk/content/spring-and-openejb-3.0.html (original)
+++ websites/staging/openejb/trunk/content/spring-and-openejb-3.0.html Sun Jul 10 23:55:37 2011
@@ -230,9 +230,9 @@ datasources, topics, queues, containers
. You can then expose any of these things to other Spring components with
custom factory beans.</p>
-<pre><code>h1. Injecting OpenEJB-created resources into Spring components
+<h1>Injecting OpenEJB-created resources into Spring components</h1>
-If you want to have any of the Topics, Queues, DataSources, EntityManagers
+<pre><code>If you want to have any of the Topics, Queues, DataSources, EntityManagers
</code></pre>
<p>or more that OpenEJB creates injected into components that Spring creates,
Modified: websites/staging/openejb/trunk/content/tips-and-suggestions.html
==============================================================================
--- websites/staging/openejb/trunk/content/tips-and-suggestions.html (original)
+++ websites/staging/openejb/trunk/content/tips-and-suggestions.html Sun Jul 10 23:55:37 2011
@@ -344,8 +344,9 @@ David</p>
<p></three></p>
-<p>h3. scp, ssh, and rsync examples for working with files and directories on
-people.apache.org</p>
+<h3>scp, ssh, and rsync examples for working with files and directories on</h3>
+
+<p>people.apache.org</p>
<p><em>Contributed by</em>: David Blevins</p>
Modified: websites/staging/openejb/trunk/content/tomcat-installation.html
==============================================================================
--- websites/staging/openejb/trunk/content/tomcat-installation.html (original)
+++ websites/staging/openejb/trunk/content/tomcat-installation.html Sun Jul 10 23:55:37 2011
@@ -238,8 +238,9 @@ LICENSE RELEASE-NOTES bin/
<p>{deck}</p>
-<p>h1. [OPENEJB:Windows](openejb:windows.html)
- Set JAVA_HOME environment variable</p>
+<h1>[OPENEJB:Windows](openejb:windows.html)</h1>
+
+<p>Set JAVA_HOME environment variable</p>
<p>For Windows users, the Tomcat shell scripts must know the location of the
Java installation, and this is done with environment variables. The
@@ -250,10 +251,10 @@ following command will set the JAVA_HOME
C:>set JAVA_HOME =C:\your\java\installation</p>
<pre><code>{deck}
-
-h1. \[OPENEJB:Unix\]
</code></pre>
+<h1>[OPENEJB:Unix]</h1>
+
<p>Make shell scripts executable</p>
<pre><code>For Unix users, the shell scripts in the Tomcat installation are not
Modified: websites/staging/openejb/trunk/content/webadmin.html
==============================================================================
--- websites/staging/openejb/trunk/content/webadmin.html (original)
+++ websites/staging/openejb/trunk/content/webadmin.html Sun Jul 10 23:55:37 2011
@@ -228,12 +228,14 @@ subclass from WebAdminBean and include i
link that causes the EJB code to be execute. Very simple and makes it
possible to package administrative components with your EJB applications.</p>
-<pre><code>h1. WebAdmin Plugins
+<h1>WebAdmin Plugins</h1>
-Here is a project that already takes advantage of the new feature. [BeanGen|http://beangen.sourceforge.net]
+<pre><code>Here is a project that already takes advantage of the new feature. [BeanGen|http://beangen.sourceforge.net]
+</code></pre>
+
+<h1>Developers guide</h1>
-h1. Developers guide
-Below is David Blevins' email on how webadmin worked. Please have a look at
+<pre><code>Below is David Blevins' email on how webadmin worked. Please have a look at
</code></pre>
<p>the text below before you start working on porting the existing WebAdmin to