myfaces-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mmarinsc...@apache.org
Subject svn commit: r547130 - in /myfaces/orchestra/trunk/core/src/site/xdoc: index.xml installation.xml
Date Thu, 14 Jun 2007 05:40:43 GMT
Author: mmarinschek
Date: Wed Jun 13 22:40:42 2007
New Revision: 547130

URL: http://svn.apache.org/viewvc?view=rev&rev=547130
Log:
doc fixes

Modified:
    myfaces/orchestra/trunk/core/src/site/xdoc/index.xml
    myfaces/orchestra/trunk/core/src/site/xdoc/installation.xml

Modified: myfaces/orchestra/trunk/core/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/myfaces/orchestra/trunk/core/src/site/xdoc/index.xml?view=diff&rev=547130&r1=547129&r2=547130
==============================================================================
--- myfaces/orchestra/trunk/core/src/site/xdoc/index.xml (original)
+++ myfaces/orchestra/trunk/core/src/site/xdoc/index.xml Wed Jun 13 22:40:42 2007
@@ -18,9 +18,8 @@
 			</p>
 			<p>
 				Apache MyFaces Orchestra aims to provide a simple way to combine a web-framework with
a persistence
-				layer. Typically, an Apache MyFaces Orchestra stack might combine JavaServer Faces, Spring
and
-				a JPA implementation like Toplink, Hibernate, etc.
-				<br/>
+				layer. Typically, an Apache MyFaces Orchestra stack might combine JavaServer Faces (JSF),
Spring and
+				a Java Persistence API (JPA) implementation like Toplink, Hibernate, etc.
 				The underlying idea is to provide long persistence sessions to the web-developer - this
is
 				done by associating these sessions with a conversational context.
 				<br/>
@@ -125,6 +124,16 @@
 				</ul>
 			</subsection>
 
-		</section>
+			<subsection name="Context">
+                <p>
+                    Some historical context at the end: Apache Orchestra has been initiated
by members of the JavaServer
+                    Faces and Spring community to provide better interaction between the
projects and the persistence
+                    layer of a typical web-application. Namely, Spring founder
+                    Jürgen Höller,  MyFaces founder Manfred Geiler, and MyFaces committer
and PMC member
+                    Mario Ivankovits have worked together to lay-out the fundamentals of
this glue-code project.
+                </p>
+			</subsection>
+
+        </section>
 	</body>
 </document>

Modified: myfaces/orchestra/trunk/core/src/site/xdoc/installation.xml
URL: http://svn.apache.org/viewvc/myfaces/orchestra/trunk/core/src/site/xdoc/installation.xml?view=diff&rev=547130&r1=547129&r2=547130
==============================================================================
--- myfaces/orchestra/trunk/core/src/site/xdoc/installation.xml (original)
+++ myfaces/orchestra/trunk/core/src/site/xdoc/installation.xml Wed Jun 13 22:40:42 2007
@@ -133,39 +133,39 @@
 
 &lt;/beans&gt;
 				</pre>
-				<p>Ok, this might look a little bit much for the start of
-					an installation guide, though, its not that complicated. So, head up, lets
-					go through this configuration step by step.
-				</p>
+				<p>Basically, all you need to do is copy this configuration segment and paste it
+                    into your Spring configuration file. Then you'll need to adapt the settings
in the element
+                    entityManagerFactory - namely the jpaProperties.
+                </p>
 				<ul>
 					<li>1. the conversation scope
 						<br/>
-						There we configure the conversation
+						Here we configure the conversation
 						scope as a Spring custom scope. This configuration allows us to use
 						scope="conversation" with our beans. This scope implementation also
 						allows you to configure a number of advices. Advices intercept each
 						method call to your bean. We build on this mechanism to configure the
-						entity manager appropriate.
+						entity manager appropriately.
 						<br/>
-						If your application do not have to
-						deal with persistence, but you would like to use the conversation
+						If your application does not have to
+						deal with persistence, and you would still like to use the conversation
 						scope you can delete the advices from this configuration.
 					</li>
 
 					<li>2. the "entity manager" manager
 						<br/>
 						This is the interceptor which
-						ensures that the correct entity manager has been set before any method
-						of your conversation bean will be called.
+						ensures that the correct entity manager has been set - right before any method
+						of your conversation bean is called.
 					</li>
 
 					<li>3. conversation - persistence adapter
 						<br/>
 						Depending on the ORM
-						tool you use you have to configure a persistenceContextFactory. Apache
-						MyFaces Orchestra will provide a JPA implementation in its core15
-						package. Its under discussion that these adapter classes will be moved
-						into Spring.
+						tool you want to use you will have to configure a persistenceContextFactory. Apache
+						MyFaces Orchestra will provide a JPA-based implementation in its core15
+						package. It is under discussion that these adapter classes might be moved
+						to the Spring framework eventually.
 					</li>
 
 					<li>4.persistence



Mime
View raw message