[jboss-cvs] JBossAS SVN: r85805 - in projects/docs/enterprise: 4.3.4/JDK6_Compatibility_Notes/en-US and 2 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Mar 13 00:23:42 EDT 2009
Author: irooskov at redhat.com
Date: 2009-03-13 00:23:42 -0400 (Fri, 13 Mar 2009)
New Revision: 85805
Modified:
projects/docs/enterprise/4.2.7/Seam/Reference_Guide/en-US/Tutorial.xml
projects/docs/enterprise/4.3.4/JDK6_Compatibility_Notes/en-US/Preface.xml
projects/docs/enterprise/4.3.5/JDK6_Compatibility_Notes/en-US/Preface.xml
projects/docs/enterprise/4.3.5/Seam/Reference_Guide/en-US/Tutorial.xml
Log:
updated seam guide with overlapping fixes for JBPAPP-1707 and corrected the bug creation location for the JDK6 guide from being Bugzilla to being JIRA
Modified: projects/docs/enterprise/4.2.7/Seam/Reference_Guide/en-US/Tutorial.xml
===================================================================
--- projects/docs/enterprise/4.2.7/Seam/Reference_Guide/en-US/Tutorial.xml 2009-03-13 04:17:30 UTC (rev 85804)
+++ projects/docs/enterprise/4.2.7/Seam/Reference_Guide/en-US/Tutorial.xml 2009-03-13 04:23:42 UTC (rev 85805)
@@ -114,8 +114,8 @@
<para>
We need an EJB entity bean for user data. This class defines <emphasis>persistence</emphasis> and <emphasis>validation</emphasis> declaratively, via annotations. It also needs some extra annotations that define the class as a Seam component.
</para>
- <example>
- <title></title>
+ <!-- <example>
+ <title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="1" id="registration-entity-annotation" />
@@ -236,7 +236,7 @@
<para>
However, entity beans should not do transaction management or database access. So we can't use this component as a JSF action listener. For that we need a session bean.
</para>
- </example>
+ <!-- </example>-->
</section>
<section id="Understanding_the_code-The_stateless_session_bean_class_RegisterAction.java">
@@ -250,8 +250,8 @@
<para>
This is the only really interesting code in the example.
</para>
- <example>
- <title></title>
+ <!-- <example>
+ <title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="1" id="registration-stateless-annotation" />
@@ -357,7 +357,7 @@
<para>
Furthermore, notice that our session bean has simultaneous access to context associated with the web request (the form values in the <literal>User</literal> object, for example), and state held in transactional resources (the <literal>EntityManager</literal> object). This is a break from traditional J2EE architectures. Again, if you are more comfortable with the traditional J2EE layering, you can certainly implement that in a Seam application. <!--But for many applications, it's simply not very useful. -->
</para>
- </example>
+ <!-- </example> -->
</section>
<section id="Understanding_the_code-The_session_bean_local_interface_Register.java">
@@ -674,7 +674,8 @@
<para>
The <literal>Message</literal> entity defines the title, text, date and time of a message, and a flag indicating whether the message has been read:
</para>
- <example><title></title><programlisting>@Entity
+ <!-- <example><title></title>-->
+<programlisting>@Entity
@Name("message")
@Scope(EVENT)
public class Message implements Serializable
@@ -728,7 +729,7 @@
}
</programlisting>
- </example>
+ <!-- </example> -->
</section>
<section id="Understanding_the_code-The_stateful_session_bean_MessageManagerBean.java">
@@ -742,7 +743,7 @@
<para>
We want to cache the list of messages in memory between server requests, so we will make this a stateful session bean.
</para>
- <example><title></title>
+ <!-- <example><title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="7" id="messages-datamodel" />
@@ -837,7 +838,7 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example>--><para>
Note that this is a session-scoped Seam component. It is associated with the user login session, and all requests from a login session share the same instance of the component. (In Seam applications, we usually use session-scoped components sparingly.)
</para>
</section>
@@ -947,7 +948,7 @@
<para>
The center of this example is the jBPM process definition. There are also two JSPs and two trivial JavaBeans (There was no reason to use session beans, since they do not access the database, or have any other transactional behavior). Let's start with the process definition:
</para>
- <example><title></title>
+ <!-- <example><title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="3" id="todo-startstate" />
@@ -1002,7 +1003,7 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example>--><para>
If we view this process definition using the process definition editor provided by JBossIDE, this is what it looks like:
</para>
<mediaobject>
@@ -1289,7 +1290,7 @@
<para>
The example is implemented using one JavaBean, three JSP pages and a jPDL pageflow definition. Let's begin with the pageflow:
</para>
- <example><title></title>
+ <!-- <example><title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="7" id="numberguess-page" />
@@ -1352,7 +1353,7 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example>--><para>
Here is what the pageflow looks like in the JBossIDE pageflow editor:
</para>
<mediaobject>
@@ -1699,7 +1700,7 @@
<para>
The search functionality is implemented using a session-scope stateful session bean, similar to the one we saw in the message list example above.
</para>
- <example><title></title>
+ <!-- <example><title></title>-->
<!-- <programlistingco>
<areaspec>
<area coords="1" id="booking-stateful-annotation" />
@@ -1803,10 +1804,10 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example>--><para>
The main page of the application is a Facelets page. Let us look at the fragment which relates to searching for hotels:
</para>
- <example><title></title>
+ <!-- <example><title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="11" id="booking-support-element" />
@@ -1903,13 +1904,13 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example>--><para>
This page displays the search results dynamically as we type, and lets us choose a hotel and pass it to the <literal>selectHotel()</literal> method of the <literal>HotelBookingAction</literal>, which is where the <emphasis>really</emphasis> interesting stuff is going to happen.
</para>
<para>
Now lets see how the booking example application uses a conversation-scoped stateful session bean to achieve a natural cache of persistent data related to the conversation. The following code example is pretty long. But if you think of it as a list of scripted actions that implement the various steps of the conversation, it's understandable. Read the class from top to bottom, as if it were a story.
</para>
- <example><title></title>
+ <!-- <example><title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="7" id="booking-extendedpersistencecontext-annotation" />
@@ -2030,7 +2031,7 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example>--><para>
<literal>HotelBookingAction</literal> contains all the action listener methods that implement selection, booking and booking confirmation, and holds state related to this work in its instance variables. We think you'll agree that this code is much cleaner and simpler than getting and setting <literal>HttpSession</literal> attributes.
</para>
<para>
Modified: projects/docs/enterprise/4.3.4/JDK6_Compatibility_Notes/en-US/Preface.xml
===================================================================
--- projects/docs/enterprise/4.3.4/JDK6_Compatibility_Notes/en-US/Preface.xml 2009-03-13 04:17:30 UTC (rev 85804)
+++ projects/docs/enterprise/4.3.4/JDK6_Compatibility_Notes/en-US/Preface.xml 2009-03-13 04:23:42 UTC (rev 85805)
@@ -7,9 +7,10 @@
<para>
</para>
<xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude">
- <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude">
- <xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- </xi:fallback>
- </xi:include>
+ <section id="introduction-Feedback">
+ <title>Feedback</title>
+ <para>
+ If you spot a typo in this guide, or if you have thought of a way to make this manual better, we would love to hear from you! Submit a report in <ulink url="http://jira.jboss.com/jira/browse/JBPAPP">JIRA</ulink> against the Product: JBoss Enterprise Application Platform, Version: <replaceable><version></replaceable>, Component: <emphasis>Doc</emphasis>. If you have a suggestion for improving the documentation, try to be as specific as possible. If you have found an error, include the section number and some of the surrounding text so we can find it easily.
+ </para>
+ </section>
</preface>
Modified: projects/docs/enterprise/4.3.5/JDK6_Compatibility_Notes/en-US/Preface.xml
===================================================================
--- projects/docs/enterprise/4.3.5/JDK6_Compatibility_Notes/en-US/Preface.xml 2009-03-13 04:17:30 UTC (rev 85804)
+++ projects/docs/enterprise/4.3.5/JDK6_Compatibility_Notes/en-US/Preface.xml 2009-03-13 04:23:42 UTC (rev 85805)
@@ -7,9 +7,10 @@
<para>
</para>
<xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude">
- <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude">
- <xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- </xi:fallback>
- </xi:include>
+ <section id="introduction-Feedback">
+ <title>Feedback</title>
+ <para>
+ If you spot a typo in this guide, or if you have thought of a way to make this manual better, we would love to hear from you! Submit a report in <ulink url="http://jira.jboss.com/jira/browse/JBPAPP">JIRA</ulink> against the Product: JBoss Enterprise Application Platform, Version: <replaceable><version></replaceable>, Component: <emphasis>Doc</emphasis>. If you have a suggestion for improving the documentation, try to be as specific as possible. If you have found an error, include the section number and some of the surrounding text so we can find it easily.
+ </para>
+ </section>
</preface>
Modified: projects/docs/enterprise/4.3.5/Seam/Reference_Guide/en-US/Tutorial.xml
===================================================================
--- projects/docs/enterprise/4.3.5/Seam/Reference_Guide/en-US/Tutorial.xml 2009-03-13 04:17:30 UTC (rev 85804)
+++ projects/docs/enterprise/4.3.5/Seam/Reference_Guide/en-US/Tutorial.xml 2009-03-13 04:23:42 UTC (rev 85805)
@@ -121,7 +121,7 @@
<para>
We need an EJB entity bean for user data. This class defines <emphasis>persistence</emphasis> and <emphasis>validation</emphasis> declaratively, via annotations. It also needs some extra annotations that define the class as a Seam component.
</para>
- <example><title></title>
+ <!-- <example><title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="1" id="registration-entity-annotation" />
@@ -242,7 +242,7 @@
<para>
However, entity beans should not do transaction management or database access. So we cannot use this component as a JSF action listener. For that we need a session bean.
</para>
- </example>
+ <!-- </example> -->
</section>
<section id="Seam_Reference_Guide-Understanding_the_code-The_stateless_session_bean_class_RegisterAction.java">
@@ -256,7 +256,7 @@
<para>
This is the only really interesting code in the example.
</para>
- <example><title></title>
+ <!-- <example><title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="1" id="registration-stateless-annotation" />
@@ -362,7 +362,7 @@
<para>
Furthermore, notice that our session bean has simultaneous access to context associated with the web request (the form values in the <literal>User</literal> object, for example), and state held in transactional resources (the <literal>EntityManager</literal> object). This is a break from traditional J2EE architectures. Again, if you are more comfortable with the traditional J2EE layering, you can certainly implement that in a Seam application. But for many applications, it is not very useful.
</para>
- </example>
+ <!-- </example> -->
</section>
<section id="Seam_Reference_Guide-Understanding_the_code-The_session_bean_local_interface_Register.java">
@@ -679,7 +679,8 @@
<para>
The <literal>Message</literal> entity defines the title, text, date and time of a message, and a flag indicating whether the message has been read:
</para>
- <example><title></title><programlisting>@Entity
+ <!-- <example><title></title> -->
+<programlisting>@Entity
@Name("message")
@Scope(EVENT)
public class Message implements Serializable
@@ -733,7 +734,7 @@
}
</programlisting>
- </example>
+ <!-- </example> -->
</section>
<section id="Seam_Reference_Guide-Understanding_the_code-The_stateful_session_bean_MessageManagerBean.java">
@@ -747,7 +748,7 @@
<para>
We want to cache the list of messages in memory between server requests, so we will make this a stateful session bean.
</para>
- <example><title></title>
+ <!-- <example><title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="7" id="messages-datamodel" />
@@ -842,7 +843,8 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example> -->
+ <para>
Note that this is a session-scoped Seam component. It is associated with the user login session, and all requests from a login session share the same instance of the component. (In Seam applications, we usually use session-scoped components sparingly.)
</para>
</section>
@@ -955,7 +957,7 @@
<para>
The center of this example is the jBPM process definition. There are also two JSPs and two trivial JavaBeans (There was no reason to use session beans, since they do not access the database, or have any other transactional behavior). Let us start with the process definition:
</para>
- <example><title></title>
+ <!-- <example><title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="3" id="todo-startstate" />
@@ -1010,7 +1012,7 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example>--><para>
If we view this process definition using the process definition editor provided by JBossIDE, this is what it looks like:
</para>
<mediaobject>
@@ -1304,7 +1306,7 @@
<para>
The example is implemented using one JavaBean, three JSP pages and a jPDL pageflow definition. Let us begin with the pageflow:
</para>
- <example><title></title>
+ <!-- <example><title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="7" id="numberguess-page" />
@@ -1367,7 +1369,7 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example>--><para>
Here is what the pageflow looks like in the JBossIDE pageflow editor:
</para>
<mediaobject>
@@ -1715,7 +1717,7 @@
<para>
The search functionality is implemented using a session-scope stateful session bean, similar to the one we saw in the message list example above.
</para>
- <example><title></title>
+ <!-- <example><title></title> -->
<!-- <programlistingco>
<areaspec>
<area coords="1" id="booking-stateful-annotation" />
@@ -1819,10 +1821,10 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example>--><para>
The main page of the application is a Facelets page. Let us look at the fragment which relates to searching for hotels:
</para>
- <example><title></title>
+ <!-- <example><title></title>-->
<!-- <programlistingco>
<areaspec>
<area coords="11" id="booking-support-element" />
@@ -1919,7 +1921,7 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example>--><para>
This page displays the search results dynamically as we type, and lets us choose a hotel and pass it to the <literal>selectHotel()</literal> method of the <literal>HotelBookingAction</literal>, which is where the <emphasis>really</emphasis> interesting stuff is going to happen.
</para>
<para>
@@ -2046,7 +2048,7 @@
</orderedlist>
<!-- </programlistingco> -->
- </example><para>
+ <!-- </example>--><para>
<literal>HotelBookingAction</literal> contains all the action listener methods that implement selection, booking and booking confirmation, and holds state related to this work in its instance variables. We think you will agree that this code is much cleaner and simpler than getting and setting <literal>HttpSession</literal> attributes.
</para>
<para>
More information about the jboss-cvs-commits
mailing list