svn commit: r805332 - in /websites/staging/openejb/trunk: ./ content/examples-trunk/simple-webservice/README.html

[bu...@apache.org]

Author: buildbot
Date: Sun Feb 19 05:41:37 2012
New Revision: 805332

Log:
Staging update by buildbot for openejb

Modified:
    websites/staging/openejb/trunk/   (props changed)
    websites/staging/openejb/trunk/content/examples-trunk/simple-webservice/README.html

Propchange: websites/staging/openejb/trunk/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Feb 19 05:41:37 2012
@@ -1 +1 @@
-1290946
+1290950

Modified: websites/staging/openejb/trunk/content/examples-trunk/simple-webservice/README.html
==============================================================================
--- websites/staging/openejb/trunk/content/examples-trunk/simple-webservice/README.html (original)
+++ websites/staging/openejb/trunk/content/examples-trunk/simple-webservice/README.html Sun Feb 19 05:41:37 2012
@@ -464,6 +464,27 @@ Tests run: 1, Failures: 0, Errors: 0, Sk
 </soap:Envelope>
 </code></pre>
 
+<h2>Inside the jar</h2>
+
+<p>With so much going on it can make things look more complex than they are.  It can be hard to believe that so much can happen with such little code.  That's the benefit of having an app server.</p>
+
+<p>If we look at the jar built by maven, we'll see the application itself is quite small:</p>
+
+<pre><code>$ jar tvf target/simple-webservice-1.1-SNAPSHOT.jar
+     0 Sat Feb 18 19:17:06 PST 2012 META-INF/
+   127 Sat Feb 18 19:17:04 PST 2012 META-INF/MANIFEST.MF
+     0 Sat Feb 18 19:17:02 PST 2012 org/
+     0 Sat Feb 18 19:17:02 PST 2012 org/superbiz/
+     0 Sat Feb 18 19:17:02 PST 2012 org/superbiz/calculator/
+     0 Sat Feb 18 19:17:02 PST 2012 org/superbiz/calculator/ws/
+   855 Sat Feb 18 19:17:02 PST 2012 org/superbiz/calculator/ws/Calculator.class
+   288 Sat Feb 18 19:17:02 PST 2012 org/superbiz/calculator/ws/CalculatorWs.class
+</code></pre>
+
+<p>This single jar could be deployed any any compliant Java EE implementation.  In TomEE you'd simply place it in the <code>tomee.home/webapps/</code> directory.  No war file necessary.  If you did want to create a war, you'd simply place the jar in the <code>WEB-INF/lib/</code> directory of the war.</p>
+
+<p>The server already contains the right libraries to run the code, such as Apache CXF, so no need to include anything extra beyond your own application code.</p>
+
 
 <div class="page-header">&nbsp;</div>
 <h4>APIs Used</h4>