myfaces-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r513949 - in /myfaces/fusion/trunk/core/src/site: site.xml xdoc/todo.xml
Date Fri, 02 Mar 2007 21:03:15 GMT
Author: imario
Date: Fri Mar  2 13:03:14 2007
New Revision: 513949

added todo list

      - copied, changed from r513820, myfaces/fusion/trunk/core/src/site/xdoc/about.xml

Modified: myfaces/fusion/trunk/core/src/site/site.xml
--- myfaces/fusion/trunk/core/src/site/site.xml (original)
+++ myfaces/fusion/trunk/core/src/site/site.xml Fri Mar  2 13:03:14 2007
@@ -39,6 +39,7 @@
 			<item name="Installation" href="installation.html"/>
 			<item name="Management" href="conversationManagement.html"/>
 			<item name="Best Practice" href="bestPractice.html"/>
+			<item name="TODO" href="todo.html"/>

Copied: myfaces/fusion/trunk/core/src/site/xdoc/todo.xml (from r513820, myfaces/fusion/trunk/core/src/site/xdoc/about.xml)
--- myfaces/fusion/trunk/core/src/site/xdoc/about.xml (original)
+++ myfaces/fusion/trunk/core/src/site/xdoc/todo.xml Fri Mar  2 13:03:14 2007
@@ -3,200 +3,14 @@
-		<title>About Apache MyFaces Fusion</title>
+		<title>Apache MyFaces Fusion - TODO</title>
-		<section name="Apache MyFaces Fusion">
-			<p>Apache MyFaces Fusion aims to
-				simplify developers life when it comes to build web based applications,
-				especially when they have to deal with Object-Relational-Mapping tools
-				like JPA or Hibernate.
-			</p>
-			<p>Everyone who ever developed an application
-				without a framework like JBoss Seam, but wanted to use such a ORM tool,
-				might have seen all those anoying things like LazyInitializationException
-				or the problems you have if you try to
-				<code>merge</code>
-				your detached
-				objects back into the session. Most of those problems, if not all, result
-				from the fact that opening and closing a session for each HTTP request,
-				wich means, that the ORM tool has no chance to manage your entities any
-				more. Once you closed a session all your entities are detached from it. At
-				the next request the ORM tool has no knowledge of these entities and can't
-				manage them any more.
-			</p>
-			<p>So, the magic is to keep such a session open
-				as long as required, but as short as possible.
-			</p>
-			<p>Later a so called
-				OpenSessionInView technologie come up which allowed you to use a session
-				at least for the same page. This is fine, but didn't help if you have to
-				deal with a pageflow or dialogs where more than a single page is required
-				to finish a job.
-			</p>
-			<p>The next buzzword in this context is
-				"ApplicationTransaction", now we reached the conversation scope. The
-				duration of an ApplicationTransaction is given - what a wonder - from the
-				application. It is completely detached from the pageflow. Regardless if it
-				spans multiple requests on an single page or multiple pages, the
-				application will start and stop the ApplicationTransation.
-			</p>
-			<p>Apache
-				MyFaces Fusion; inspired from JBoss Seam; introduce the conversation scope
-				to deal with this kind of workflow.
-			</p>
-			<p>A conversation scope is like the
-				request or session scope a place where you can put your beans to. The
-				difference between the latter two and the conversation scope is, that it
-				will also provide a way how to deal with - so called - long
-				sessions.
-			</p>
-			<p>A bean, put into the conversation scope, will get an
-				entity manager attached which will be used for each database access until
-				the application ends the conversation.
-			</p>
-			<p>There are tons of buzzwords
-				in the area of persistence, so, before we start I'll make some definitions
-				so that we surely talk about the same things.
-			</p>
-			<subsection
-				name="Definitions">
-				<ul>
-					<li>pojo
-						<br/>
-						Plain-Old-Java-Object, following the Java Bean standard
-						this is a class with (mostly) private members and a get and set method
-						(also called as getter and setter) for each of them. The original aim
-						of the ORM tools was to persist such pojos into the database with the
-						help of e.g. an external xml configuration per pojo. When Java 5 came
-						up this changed a bit, now its common to use annotations in the java
-						source itself, though, now its hard to speak from pojos again.
-					</li>
-					<li>entity
-						<br/>
-						A pojo with an extended description for the entitiy
-						manger to allow it to be persisted into the database. Common
-						descriptions are XML files or annotations in the java source. This
-						data is called metadata.
-					</li>
-					<li>property
-						<br/>
-						A property is a member variable of your pojo with a
-						set and get method defined. You have to follow the Java Bean
-						specification. Some examples are:
-						<table width="40%">
-							<tr>
-								<th>Member</th>
-								<th>getter</th>
-								<th>setter</th>
-							</tr>
-							<tr>
-								<th>userId</th>
-								<td>getUserId</td>
-								<td>setUserId</td>
-							</tr>
-							<tr>
-								<th>_userName</th>
-								<td>getUserName</td>
-								<td>setUserName</td>
-							</tr>
-						</table>
-					</li>
-					<li>entity manager
-						<br/>
-						The "entity manager" manage all your entities,
-						keeps track of property updates and issues the database statements
-						required to synchronize the entity state with the database. If you
-						close an entity manager you will loose the coupling between its
-						internal state and your entities, they are so called "detached object"
-						afterwards.
-					</li>
-					<li>entity manager factory
-						<br/>
-						The "entity manager factory" is
-						responsible for processing all the entity metadata and to create an
-						entity manager based on them.
-					</li>
-					<li>DAO - Data Access Object
-						<br/>
-						Mostly a singleton which contains
-						all (or most) of the database requests your application will issue.
-						Thus, the DAO is the one which has to get access to an entity
-						manager.
-					</li>
-					<li>conversation
-						<br/>
-						A conversation is the bracket for all the
-						database operations required to finish a job. Aliases are: application
-						transaction, unit-of-work
-					</li>
-					<li>session scope
-						<br/>
-						The session scope of your servlet container.
-						Beans put into this scope live until a inactivity timout has been
-						reached
-					</li>
-					<li>request scope
-						<br/>
-						The request scope of your servlet container.
-						The lifetime of those beans is only as long as the duration of a
-						single HTTP request. Say, once the servlet container finished sending
-						the page data, the request will die and with it all the beans put into
-						this scope.
-					</li>
-					<li>JPA - Java Persistence API
-						<br/>
-						The JPA standardize the way how
-						you have to annotate your entities. That way you can change (in
-						theory) the ORM tool as long as the ORM tool follows the JPA
-						specificatoins.
-					</li>
-					<li>backing bean
-						<br/>
-						A backing bean is the bean behind a JSF view
-						(jsp, facelet, etc page). While JSF does not require such a bean, its
-						good practice to do it that way.
-					</li>
-				</ul>
-			</subsection>
-			<subsection name="Structure">As pre now, the Apache
-				MyFaces Fusion contains 3 modules.
-				<ul>
-					<li>core
-						<br/>
-						The core is compatible with Java 1.4, means, you are
-						able to use all this comfortable stuff without the need to migrate to
-						Java 5.0
-					</li>
-					<li>core15
-						<br/>
-						Ok, but we couldn't resist, this package will contain
-						Java 5.0 enhancements to the core.
-					</li>
-					<li>examples</li>
-				</ul>
-			</subsection>
+		<section name="TODO">
+			<ul>
+				<li>provide a flash like scope</li>
+			</ul>

View raw message