svn commit: r814652 - in /websites/staging/openejb/trunk: cgi-bin/ content/ content/jndi-names.html

[bu...@apache.org]

Author: buildbot
Date: Fri Apr 27 01:15:29 2012
New Revision: 814652

Log:
Staging update by buildbot for openejb

Modified:
    websites/staging/openejb/trunk/cgi-bin/   (props changed)
    websites/staging/openejb/trunk/content/   (props changed)
    websites/staging/openejb/trunk/content/jndi-names.html

Propchange: websites/staging/openejb/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Apr 27 01:15:29 2012
@@ -1 +1 @@
-1331166
+1331167

Propchange: websites/staging/openejb/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Apr 27 01:15:29 2012
@@ -1 +1 @@
-1331166
+1331167

Modified: websites/staging/openejb/trunk/content/jndi-names.html
==============================================================================
--- websites/staging/openejb/trunk/content/jndi-names.html (original)
+++ websites/staging/openejb/trunk/content/jndi-names.html Fri Apr 27 01:15:29 2012
@@ -457,7 +457,7 @@ continue loading your app.</p>
 
 <p><a name="JNDINames-AdvancedDetailsonEJB3.0BusinessProxies(thesimplepart)"></a></p>
 
-<h1>Advanced Details on EJB 3.0 Business Proxies (the simple part)</h1>
+<h3>Advanced Details on EJB 3.0 Business Proxies (the simple part)</h3>
 
 <p>If you implement your business interfaces, your life is simple as your
 proxies will also implement your business interfaces of the same type. 
@@ -468,17 +468,17 @@ other business remote interfaces.</p>
 
 <p><a name="JNDINames-AdvancedDetailsonEJB3.0BusinessProxies(thecomplicatedpart)"></a></p>
 
-<h1>Advanced Details on EJB 3.0 Business Proxies (the complicated part)</h1>
+<h3>Advanced Details on EJB 3.0 Business Proxies (the complicated part)</h3>
 
-<p><div class="info">:Who should read?}
-Read this section of either of these two apply to you:
- - You do not implement your business interfaces in your bean class
- - One or more of your business remote interfaces extend from
-javax.rmi.Remote</p>
+<p><em>Who should read?</em> <br />
+Read this section of either of these two apply to you: <br />
+ - You do not implement your business interfaces in your bean class <br />
+ - One or more of your business remote interfaces extend from javax.rmi.Remote</p>
 
 <p>If neither of these two items describe your apps, then there is no need to
-read further.  Go have fun.<div class="info">}
-<a name="JNDINames-Notimplementingbusinessinterfaces"></a></p>
+read further.  Go have fun.</p>
+
+<p><a name="JNDINames-Notimplementingbusinessinterfaces"></a></p>
 
 <h3>Not implementing business interfaces</h3>
 
@@ -497,13 +497,13 @@ are thrown from javax.rmi.Remote proxies
 is not a runtime exception and must be throwable via the proxy as a checked
 exception. The issue is that conflicting throws clauses are actually
 removed for two interfaces sharing the same method signature.  For example
-two methods such as these:
- - InterfaceA: void doIt() throws Foo;
- - InterfaceB: void doIt() throws RemoteException;</p>
+two methods such as these: <br />
+ - InterfaceA: void doIt() throws Foo; <br />
+ - InterfaceB: void doIt() throws RemoteException;    </p>
 
 <p>can be implemented by trimming out the conflicting throws clauses as
-follows:
-  - Implementation: void doIt(){}</p>
+follows: <br />
+  - Implementation: void doIt(){}    </p>
 
 <p>This is fine for a bean class as it does not need to throw the RMI required
 javax.rmi.RemoteException. However if we create a proxy from these two
@@ -515,7 +515,7 @@ attempts to throw a RemoteException from
 will result in an UndeclaredThrowableException thrown by the VM.</p>
 
 <p>The only way to guarantee the proxy has the 'doIt() throws RemoteException{{{{{}' method of InterfaceB is to cut out InterfaceA when we create the proxy
-dedicated to InterfaceB.<div class="excerpt">}</p>
+dedicated to InterfaceB.</p>