JBoss Tools SVN: r4855 - in trunk/documentation/whatsnew: as and 2 other directories.
by jbosstools-commits＠lists.jboss.org
Author: max.andersen(a)jboss.com
Date: 2007-11-12 12:02:52 -0500 (Mon, 12 Nov 2007)
New Revision: 4855
Added:
trunk/documentation/whatsnew/as/as-news-1.0.0.cr1.html
trunk/documentation/whatsnew/hibernate/
trunk/documentation/whatsnew/seam/seam-news-1.0.0.cr1.html
trunk/documentation/whatsnew/vpe/vpe-news-2.1.0.cr1.html
Removed:
trunk/documentation/whatsnew/vpe/vpe-news-cr1.html
Modified:
trunk/documentation/whatsnew/index.html
Log:
updated whatsnew for CR1
Added: trunk/documentation/whatsnew/as/as-news-1.0.0.cr1.html
===================================================================
--- trunk/documentation/whatsnew/as/as-news-1.0.0.cr1.html (rev 0)
+++ trunk/documentation/whatsnew/as/as-news-1.0.0.cr1.html 2007-11-12 17:02:52 UTC (rev 4855)
@@ -0,0 +1,104 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Language" content="en-us" />
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="stylesheet" href="../whatsnew.css"/>
+<title>JBoss AS Tools 1.0.0.CR1 What's New</title>
+</head>
+<body>
+<h1>JBoss AS Tools 1.0.0.CR1 What's New</h1>
+
+<table border="0" cellpadding="10" cellspacing="0" width="80%">
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Server view</h3>
+ <hr/>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right">
+ <a name="itemname3" id="itemname3"></a><b>"Mini" JMX Console</b>
+ </td>
+ <td valign="top">As part of the JBoss Server view there is now a JMX Console section which allows you to browse and use the JMX exposed beans on the server.</td>
+ <p><img src="images/jmxconsole.png"/></p>
+ </tr>
+ <tr>
+ <td colspan="2"><hr />
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right">
+ <a name="itemname3" id="itemname3"></a><b>Server publish Status</b>
+ </td>
+ <td valign="top">The server's publish status is now available in the JBoss Servers view, allowing you to see if changes are awaiting (Republish), are being updated (Publishing...) or are in-sync (Synchronized).</td>
+ <p><img src="images/serverpublishstate.png"/></p>
+ </tr>
+
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Server configuration</h3>
+ <hr/>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right">
+ <a name="itemname3" id="itemname3"></a><b>Temporary deploy location</b>
+ </td>
+ <td valign="top">The temporary directory location used when copying files to the server are now set to a temporary location within JBoss AS. Previously it was set to the default WTP deploy location within Eclipse but that had issues if your JBoss AS and Eclipse workspace were on different file systems. If you continue to have such issues, you can now configure the temporary deploy location.</td>
+ <p><img src="images/servertempdeploylocation.png"/></p>
+ </tr>
+ <tr>
+ <td colspan="2"><hr />
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right">
+ <b>Improved default VM arguments for servers</b>
+ </td>
+ <td valign="top"><p>Memory (especially permgen settings) and linux specific ipv6 VM arguments are now setup by default when server is created.</p>
+ <p><img src="images/serverdefaultarguments.png"/></p>
+ </td>
+ </tr>
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Deployment</h3>
+ <hr/>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right"><a name="itemname3" id="itemname3"></a><b>Incrementally deploy for EAR</b></td>
+ <td valign="top"><p>Previous versions of JBoss AS Tools had various issues with incrementally (and full) deploy of nested EARs. All these issues are now fixed and EAR deployment is now as fast and functional as the War deployments.</p>
+ </td>
+ </tr>
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Others</h3>
+ <hr/>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right">
+ <a name="itemnam2e" id="itemname2"></a><b>JSF/EL exception linking</b>
+ </td>
+ <td width="70%" valign="top">
+ <p>Exceptions related to JSF/EL are now possible to follow by clicking on the resource name in the exception messages</p>
+ <p><img src="images/elexceptionlinking.png"/></p>
+ <p>The linking is available in any java launch and the Stacktrace view</p>
+ </td>
+ </tr>
+
+
+</table>
+
+</body>
+
+</html>
+
+
Modified: trunk/documentation/whatsnew/index.html
===================================================================
--- trunk/documentation/whatsnew/index.html 2007-11-12 16:31:18 UTC (rev 4854)
+++ trunk/documentation/whatsnew/index.html 2007-11-12 17:02:52 UTC (rev 4855)
@@ -21,6 +21,16 @@
</tr>
<tr>
<td valign="top" align="left">
+ <p align="right"><b>Candidate Release 1</b></td>
+ <td valign="top">
+ <p><a href="as/as-news-1.0.0.cr1.html">JBoss AS Tools</a></p>
+ <p><a href="seam/seam-news-1.0.0.cr1.html">Seam Tools</a></p>
+ <p><a href="hibernate/hibernate-news-3.2.0.cr1.html">Hibernate Tools</a></p>
+ <p><a href="vpe/vpe-news-2.1.0.cr1.html">Visual Page Editor</a></p>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="left">
<p align="right"><b>Beta4</b></td>
<td valign="top">
<p><a href="as/as-news-1.0.0.beta4.html">JBoss AS Tools</a></p>
Added: trunk/documentation/whatsnew/seam/seam-news-1.0.0.cr1.html
===================================================================
--- trunk/documentation/whatsnew/seam/seam-news-1.0.0.cr1.html (rev 0)
+++ trunk/documentation/whatsnew/seam/seam-news-1.0.0.cr1.html 2007-11-12 17:02:52 UTC (rev 4855)
@@ -0,0 +1,104 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Language" content="en-us" />
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="stylesheet" href="../whatsnew.css"/>
+<title>Seam tools 1.0.0.CR1 What's New</title>
+</head>
+<body>
+<h1>Seam tools 1.0.0.CR1 What's New</h1>
+
+<table border="0" cellpadding="10" cellspacing="0" width="80%">
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Wizards</h3>
+ <hr/>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right">
+ <a name="itemnam2e" id="itemname2"></a><b>Seam 2 support</b>
+ </td>
+ <td width="70%" valign="top">Seam 2 are now supported as a valid runtime and can now be used together with the project and artifact creation wizards.</td>
+
+ <p><img src="images/seam2runtime.png"/></p>
+
+ <p>Seam code completion and validation now also supports the Seam 2 notion of <code>import</code>'s.</p>
+ </tr>
+ <tr>
+ <td colspan="2"><hr />
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right">
+ <a name="itemname3" id="itemname3"></a><b>Server selection at project creation</b>
+ </td>
+ <td valign="top">Seam Web Project wizard now has an option for selecting the actual Server (and not just WTP runtime) that will be used for the project.</td>
+<p>This allow the wizard to correctly identify where the needed datasource and driver libraries need to go.</p>
+ <p><img src="images/serverselection.png"/></p>
+ </tr>
+ <tr>
+ <td colspan="2"><hr />
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right"><a name="itemname3" id="itemname3"></a><b>Hibernate support fully enabled</b></td>
+ <td valign="top"><p>Hibernate support is now enabled by default on war, ejb and test projects generated by the Seam Web Project wizard.</p>
+<p>This enables all the HQL code completion and validation inside Java files. Code completion just requires the Hibernate Console configuration to opened/created, validation requires the Session Factory to be opened/created.</p>
+ <p><img src="images/hqlcodecompletionvalidation.png"/></p>
+ </td>
+ </tr>
+ <tr>
+ <td colspan="2"><hr />
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right">
+ <b>Automatic restart deployment after Wizard</b>
+ </td>
+ <td valign="top"><p>When the Seam Wizards (New Entity, Action, etc.) completes, it now (if necessary) automatically touch the right descriptors to get the new artifacts redeployed on the server.</p>
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Code editing</h3>
+ <hr/>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right"><a name="itemname3" id="itemname3"></a><b>EL code completion/validation</b></td>
+ <td valign="top"><p>EL code completion now support more of the enhancements to EL available in Seam. e.g. <code>size</code>, <code>values</code>, <code>keySet</code> etc. are now available in code completion for collections and will not be flagged during validation.</p>
+ <p><img src="images/elcompletion.png"/></p>
+ </td>
+ </tr>
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Preferences</h3>
+ <hr/>
+ </td>
+ </tr> <tr>
+ <td valign="top" align="right">
+ <a name="itemname3" id="itemname3"></a><b>Enable Seam Project now in preferences</b>
+ </td>
+ <td valign="top">To avoid cluttering of the context menu for projects the "Enable Seam project" is now only available in the preferences of a java project.
+ <p><img src="images/seam2preferences.png"/></p>
+ </tr>
+ <tr>
+ <td colspan="2"><hr />
+ </td>
+ </tr>
+
+</table>
+
+</body>
+
+</html>
+
+
Added: trunk/documentation/whatsnew/vpe/vpe-news-2.1.0.cr1.html
===================================================================
--- trunk/documentation/whatsnew/vpe/vpe-news-2.1.0.cr1.html (rev 0)
+++ trunk/documentation/whatsnew/vpe/vpe-news-2.1.0.cr1.html 2007-11-12 17:02:52 UTC (rev 4855)
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Language" content="en-us" />
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="stylesheet" href="../whatsnew.css"/>
+<title>Visual Page Editor 2.1.0.CR1 News</title>
+</head>
+<body>
+<h1>Visual Page Editor 2.1.0.CR1 News</h1>
+<p>Last revised November 12, 2007</p>
+
+<table border="0" cellpadding="10" cellspacing="0" width="80%">
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>General</h3>
+ <hr/>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right"><p><b>XUL Runner</b></p></td>
+ <td valign="top"><p>This release uses XUL Runner instead of a custom compiled Mozilla. This gives more stability, less memory usage, ATF compability and support for Mac OSX.</p>
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Source navigation</h3>
+ <hr/>
+ </td>
+ </tr>
+
+ <tr>
+ <td valign="top" align="right"><p><a name="selectionbar" id="selectionbar"></a><b>Selection bar</b></p></td>
+ <td width="70%" valign="top"><p>Selection bar now available on source tab too. It shows a path
+ from the current tag to the root.</p>
+ <p><img src="images/selection-bar.png" alt="Selection bar" /></p>
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Editors</h3>
+ <hr/>
+ </td>
+ </tr>
+
+ <tr>
+ <td valign="top" align="right"><p><a name="previewtab" id="previewtab"></a><b>Preview tab</b></p></td>
+ <td valign="top"><p>Now there is a preview tab that shows the edited page in Preview mode without the editing selections etc. Giving as close an preview as possible.</p>
+ <p><img src="images/preview-tab.png" alt="Selection bar" /></p>
+ </td>
+ </tr>
+ <tr>
+ <td colspan="2"><hr />
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right"><p><a name="previewtab" id="previewtab"></a><b>New components</b></p></td>
+ <td valign="top"><p>This release supports RichFaces 3.1.0.</p>
+ </td>
+ </tr>
+ <tr>
+ <td colspan="2"><hr />
+ </td>
+ </tr>
+
+</table>
+
+</body>
+
+</html>
+
+
Deleted: trunk/documentation/whatsnew/vpe/vpe-news-cr1.html
===================================================================
--- trunk/documentation/whatsnew/vpe/vpe-news-cr1.html 2007-11-12 16:31:18 UTC (rev 4854)
+++ trunk/documentation/whatsnew/vpe/vpe-news-cr1.html 2007-11-12 17:02:52 UTC (rev 4855)
@@ -1,79 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="../whatsnew.css"/>
-<title>Visual Page Editor News</title>
-</head>
-<body>
-<h1>Visual Page Editor News</h1>
-<p>Last revised November 12, 2007</p>
-
-<table border="0" cellpadding="10" cellspacing="0" width="80%">
- <tr>
- <td colspan="2">
- <hr/>
- <h3>Plugins</h3>
- <hr/>
- </td>
- </tr>
- <tr>
- <td valign="top" align="right"><p><b>XUL Runner</b></p></td>
- <td valign="top"><p>This release uses XULRunner as a render part of visual editor instead of custom compiled mozilla.</p>
- </td>
- </tr>
-
- <tr>
- <td colspan="2">
- <hr/>
- <h3>Source navigation</h3>
- <hr/>
- </td>
- </tr>
-
- <tr>
- <td valign="top" align="right"><p><a name="selectionbar" id="selectionbar"></a><b>Selection bar</b></p></td>
- <td width="70%" valign="top"><p>Selection bar now available on Source tab too. It shows a path
- from the current tag to its first parent.</p>
- <p><img src="images/selection-bar.png" alt="Selection bar" /></p>
- </td>
- </tr>
-
- <tr>
- <td colspan="2">
- <hr/>
- <h3>What You See Is What You Get</h3>
- <hr/>
- </td>
- </tr>
-
- <tr>
- <td valign="top" align="right"><p><a name="previewtab" id="previewtab"></a><b>Preview tab</b></p></td>
- <td valign="top"><p>Now there is the preview tab that shows a page very similar to its look in runtime.</p>
- <p><img src="images/preview-tab.png" alt="Selection bar" /></p>
- </td>
- </tr>
- <tr>
- <td colspan="2"><hr />
- </td>
- </tr>
- <tr>
- <td valign="top" align="right"><p><a name="previewtab" id="previewtab"></a><b>New components</b></p></td>
- <td valign="top"><p>This release supports RichFaces 3.1.0.</p>
- </td>
- </tr>
- <tr>
- <td colspan="2"><hr />
- </td>
- </tr>
-
-</table>
-
-</body>
-
-</html>
-
-
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4854 - trunk/documentation/whatsnew/vpe/images.
by jbosstools-commits＠lists.jboss.org
Author: svasilyev
Date: 2007-11-12 11:31:18 -0500 (Mon, 12 Nov 2007)
New Revision: 4854
Modified:
trunk/documentation/whatsnew/vpe/images/preview-tab.png
trunk/documentation/whatsnew/vpe/images/selection-bar.png
Log:
Images were adjusted
Modified: trunk/documentation/whatsnew/vpe/images/preview-tab.png
===================================================================
(Binary files differ)
Modified: trunk/documentation/whatsnew/vpe/images/selection-bar.png
===================================================================
(Binary files differ)
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4853 - in trunk/documentation/guides/userguide/Legacy-jsf-struts/en: images/struts_validation and 1 other directories.
by jbosstools-commits＠lists.jboss.org
Author: sabrashevich
Date: 2007-11-12 11:29:29 -0500 (Mon, 12 Nov 2007)
New Revision: 4853
Modified:
trunk/documentation/guides/userguide/Legacy-jsf-struts/en/images/jsf_application/jsf_application_10.png
trunk/documentation/guides/userguide/Legacy-jsf-struts/en/images/struts_validation/struts_validation_1.png
trunk/documentation/guides/userguide/Legacy-jsf-struts/en/modules/jsf_application.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-234 button Run and launching on server updated
Modified: trunk/documentation/guides/userguide/Legacy-jsf-struts/en/images/jsf_application/jsf_application_10.png
===================================================================
(Binary files differ)
Modified: trunk/documentation/guides/userguide/Legacy-jsf-struts/en/images/struts_validation/struts_validation_1.png
===================================================================
(Binary files differ)
Modified: trunk/documentation/guides/userguide/Legacy-jsf-struts/en/modules/jsf_application.xml
===================================================================
--- trunk/documentation/guides/userguide/Legacy-jsf-struts/en/modules/jsf_application.xml 2007-11-12 16:04:28 UTC (rev 4852)
+++ trunk/documentation/guides/userguide/Legacy-jsf-struts/en/modules/jsf_application.xml 2007-11-12 16:29:29 UTC (rev 4853)
@@ -335,7 +335,7 @@
<listitem><para>Start up JBoss by clicking on the icon in JBoss Server view. (If JBoss is already running,
stop it by clicking on the red icon and then start it again. Remember, the JSF run-time requires restarting the servlet engine when any changes have been made.) After the messages in the Console tabbed view stop scrolling, JBoss is available</para></listitem>
-<listitem><para>Click on the Red Hat run icon in the toolbar:</para></listitem>
+<listitem><para>Click the Run icon or right click your project folder and select <emphasis><property>Run As > Run on Server</property></emphasis>:</para></listitem>
</itemizedlist>
<figure>
<title>Red Hat Run Icon</title>
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4852 - in trunk/documentation/whatsnew: vpe and 1 other directories.
by jbosstools-commits＠lists.jboss.org
Author: svasilyev
Date: 2007-11-12 11:04:28 -0500 (Mon, 12 Nov 2007)
New Revision: 4852
Added:
trunk/documentation/whatsnew/vpe/
trunk/documentation/whatsnew/vpe/images/
trunk/documentation/whatsnew/vpe/images/preview-tab.png
trunk/documentation/whatsnew/vpe/images/selection-bar.png
trunk/documentation/whatsnew/vpe/vpe-news-cr1.html
Log:
What's new for VPE was added. It is necessary to adjust the images.
Added: trunk/documentation/whatsnew/vpe/images/preview-tab.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/vpe/images/preview-tab.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/vpe/images/selection-bar.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/vpe/images/selection-bar.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/vpe/vpe-news-cr1.html
===================================================================
--- trunk/documentation/whatsnew/vpe/vpe-news-cr1.html (rev 0)
+++ trunk/documentation/whatsnew/vpe/vpe-news-cr1.html 2007-11-12 16:04:28 UTC (rev 4852)
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Language" content="en-us" />
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="stylesheet" href="../whatsnew.css"/>
+<title>Visual Page Editor News</title>
+</head>
+<body>
+<h1>Visual Page Editor News</h1>
+<p>Last revised November 12, 2007</p>
+
+<table border="0" cellpadding="10" cellspacing="0" width="80%">
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Plugins</h3>
+ <hr/>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right"><p><b>XUL Runner</b></p></td>
+ <td valign="top"><p>This release uses XULRunner as a render part of visual editor instead of custom compiled mozilla.</p>
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>Source navigation</h3>
+ <hr/>
+ </td>
+ </tr>
+
+ <tr>
+ <td valign="top" align="right"><p><a name="selectionbar" id="selectionbar"></a><b>Selection bar</b></p></td>
+ <td width="70%" valign="top"><p>Selection bar now available on Source tab too. It shows a path
+ from the current tag to its first parent.</p>
+ <p><img src="images/selection-bar.png" alt="Selection bar" /></p>
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="2">
+ <hr/>
+ <h3>What You See Is What You Get</h3>
+ <hr/>
+ </td>
+ </tr>
+
+ <tr>
+ <td valign="top" align="right"><p><a name="previewtab" id="previewtab"></a><b>Preview tab</b></p></td>
+ <td valign="top"><p>Now there is the preview tab that shows a page very similar to its look in runtime.</p>
+ <p><img src="images/preview-tab.png" alt="Selection bar" /></p>
+ </td>
+ </tr>
+ <tr>
+ <td colspan="2"><hr />
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" align="right"><p><a name="previewtab" id="previewtab"></a><b>New components</b></p></td>
+ <td valign="top"><p>This release supports RichFaces 3.1.0.</p>
+ </td>
+ </tr>
+ <tr>
+ <td colspan="2"><hr />
+ </td>
+ </tr>
+
+</table>
+
+</body>
+
+</html>
+
+
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4851 - in trunk/seam/docs/reference/en: modules and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: sabrashevich
Date: 2007-11-12 10:41:35 -0500 (Mon, 12 Nov 2007)
New Revision: 4851
Modified:
trunk/seam/docs/reference/en/images/jsp_application/jsp_application_16.png
trunk/seam/docs/reference/en/modules/jsp_application.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-234 button Run and launching on server updated
Modified: trunk/seam/docs/reference/en/images/jsp_application/jsp_application_16.png
===================================================================
(Binary files differ)
Modified: trunk/seam/docs/reference/en/modules/jsp_application.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/jsp_application.xml 2007-11-12 15:29:09 UTC (rev 4850)
+++ trunk/seam/docs/reference/en/modules/jsp_application.xml 2007-11-12 15:41:35 UTC (rev 4851)
@@ -247,7 +247,7 @@
</mediaobject>
</figure>
<itemizedlist continuation="continues">
-<listitem><para>Click the Run icon or right click your project folder and select <emphasis><property>Run on Server</property></emphasis>. If you haven't made any changes in web.xml file or cleared it out you can launch the application by right clicking the hello.jsp page and selecting <emphasis><property>Run on the Server</property></emphasis>.</para></listitem>
+<listitem><para>Click the Run icon or right click your project folder and select <emphasis><property>Run As > Run on Server</property></emphasis>. If you haven't made any changes in web.xml file or cleared it out you can launch the application by right clicking the hello.jsp page and selecting <emphasis><property>Run on the Server</property></emphasis>.</para></listitem>
</itemizedlist>
<figure>
<title>Run Project</title>
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4850 - trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet.
by jbosstools-commits＠lists.jboss.org
Author: vrubezhny
Date: 2007-11-12 10:29:09 -0500 (Mon, 12 Nov 2007)
New Revision: 4850
Modified:
trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/SeamFacetProjectCreationDataModelProvider.java
Log:
http://jira.jboss.com/jira/browse/JBIDE-1282 Configured Server is not selected by default in Seam Wizard
Issue is fixed
Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/SeamFacetProjectCreationDataModelProvider.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/SeamFacetProjectCreationDataModelProvider.java 2007-11-12 14:58:15 UTC (rev 4849)
+++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/SeamFacetProjectCreationDataModelProvider.java 2007-11-12 15:29:09 UTC (rev 4850)
@@ -97,6 +97,18 @@
FacetDataModelMap map = (FacetDataModelMap) getProperty(FACET_DM_MAP);
IDataModel seamFacet = map.getFacetDataModel( ISeamCoreConstants.SEAM_CORE_FACET_ID );
seamFacet.setProperty( ISeamFacetDataModelProperties.JBOSS_AS_TARGET_RUNTIME, propertyValue );
+
+ if (propertyValue != null) {
+ // Fixes the empty/wrong server
+ IServer server = (IServer)model.getProperty(ISeamFacetDataModelProperties.JBOSS_AS_TARGET_SERVER);
+ if (!validateServer(server).isOK()) {
+ List<IServer> servers = getServers(getRuntimeName(propertyValue));
+ if (servers != null && !servers.isEmpty()) {
+ setProperty(ISeamFacetDataModelProperties.JBOSS_AS_TARGET_SERVER, servers.get(0));
+ }
+ }
+ }
+
} else if (propertyName.equals(ISeamFacetDataModelProperties.JBOSS_AS_TARGET_SERVER)) {
FacetDataModelMap map = (FacetDataModelMap) getProperty(FACET_DM_MAP);
IDataModel seamFacet = map.getFacetDataModel( ISeamCoreConstants.SEAM_CORE_FACET_ID );
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4849 - in trunk/jbpm/docs/reference/en: images/jBPMDesignerInstall and 1 other directories.
by jbosstools-commits＠lists.jboss.org
Author: sabrashevich
Date: 2007-11-12 09:58:15 -0500 (Mon, 12 Nov 2007)
New Revision: 4849
Added:
trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/
trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/default.png
trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMLocation.png
trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation.png
trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation2.png
trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation3.png
trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation4.png
Modified:
trunk/jbpm/docs/reference/en/modules/jBPMDesignerInstall.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-288 updated second chapter
Added: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/default.png
===================================================================
(Binary files differ)
Property changes on: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/default.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMLocation.png
===================================================================
(Binary files differ)
Property changes on: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMLocation.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation.png
===================================================================
(Binary files differ)
Property changes on: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation2.png
===================================================================
(Binary files differ)
Property changes on: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation3.png
===================================================================
(Binary files differ)
Property changes on: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation4.png
===================================================================
(Binary files differ)
Property changes on: trunk/jbpm/docs/reference/en/images/jBPMDesignerInstall/jBPMinstallation4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: trunk/jbpm/docs/reference/en/modules/jBPMDesignerInstall.xml
===================================================================
--- trunk/jbpm/docs/reference/en/modules/jBPMDesignerInstall.xml 2007-11-12 14:40:01 UTC (rev 4848)
+++ trunk/jbpm/docs/reference/en/modules/jBPMDesignerInstall.xml 2007-11-12 14:58:15 UTC (rev 4849)
@@ -11,6 +11,121 @@
</keywordset>
</chapterinfo>
<title>JBoss jBPM Graphical Process Designer Installation</title>
-
+ <para>The JBoss jBPM comes as a plugin for Red Hat Developer Studio. So a prerequisite to install the Designer is of course that you have a version of RHDS up and running.</para>
+<para>Before installation you should download <property>jBPM</property> installation pack from this page: <ulink url="http://labs.jboss.com/auth/jbossjbpm/">jBPM Downloads</ulink>. The 3.1 release of the designer comes bundled with the corresponding 3.2 releases of the core jBPM project and the jBPM database project. After downloading save the archive on your computer.</para>
+<section id="InstallationProcess">
+<?dbhtml filename="InstallationProcess.html"?>
+<title>jBPM Installation Process</title>
+<para>Having RHDS up and running and the JBoss jBPM package downloaded somewhere on your harddrive, let's describe the process of installing the plugin.</para>
+<figure>
+<title>Find And Install</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/jBPMinstallation.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>Experienced Eclipse users will feel very comfortable with this description as it is the normal plugin installation mechanism for local archive update sites. As is illustrated on the figure above "Find And Install" you have to navigate to the <emphasis><property>Find and Install...</property></emphasis> submenu of the Help menu.</para>
+<para>Clicking the <emphasis><property>Find and Install...</property></emphasis> submenu shown above results in the opening of a wizard, as shown in the next screen. This wizard enables you to choose between searching for updates of currently installed plugins and searching for new features. This is the option we need, so we select it and push the <emphasis><property>Next</property></emphasis> button.:</para>
+<figure>
+<title>Search New Features</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/jBPMinstallation2.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>On the next page of the wizard we click the <emphasis><property>New Archived Site...</property></emphasis> button.</para>
+<figure>
+<title>Update Sites to Visit</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/jBPMinstallation3.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>The <emphasis><property>Select Local Site Archive</property></emphasis> dialog opens, we navigate to the freshly downloaded zipped update site and select it.</para>
+<figure>
+<title>Select Local Site Archive</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/jBPMinstallation4.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>Selecting the archive file and clicking the <emphasis><property>OK</property></emphasis> button brings us to another dialog that enables us to edit the name of the update site.</para>
+<figure>
+<title>Edit Local Site Name</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/default.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>We accept the defaults and this brings us back to the installation wizard. The selected archive containing the jBPM Designer plugin site should appear. Make sure the checkbox next to it is selected before clicking the <emphasis><property>Finish</property></emphasis> button:</para>
+<figure>
+<title>Select Update Site to Visit</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/default.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>The <emphasis><property>Select Update Site</property></emphasis> wizard closes but we aren't done yet as the <emphasis><property>Updates</property></emphasis> wizard opens immediately. In this wizard expand the tree of your newly added update site, select the checkbox next to the <emphasis><property>org.jbpm.ide.feature feature 3.1.0</property></emphasis> feature and click the <emphasis><property>Next</property></emphasis> button:</para>
+<figure>
+<title>Select the Feature to Install</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/default.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>We arrive on the <emphasis><property>Accept Feature License</property></emphasis> page of the wizard. Select <emphasis><property>I accept the terms in the license agreement</property></emphasis> if you do and click the <emphasis><property>Next</property></emphasis> button again.</para>
+<figure>
+<title>Accept Feature License</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/default.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>Clicking on the <emphasis><property>Next</property></emphasis> button in the <emphasis><property>Accept Feature License</property></emphasis> page has brought us on the final page of this installation wizard: the <emphasis><property>Installation</property></emphasis> page. Click <emphasis><property>Finish</property></emphasis> to end this wizard.</para>
+<figure>
+<title>Install the Selected Feature</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/default.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>For a moment, a progress monitor appears, indicating that Red Hat Developer Studio is busy extracting the necessary information out of the archive file to be able to install the contained plugins.</para>
+<figure>
+<title>Progress of the Download</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/default.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>After a while a new wizard appears:</para>
+<figure>
+<title>Feature Verification</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/default.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>Clicking on the <emphasis><property>Install All</property></emphasis> button results in a progress dialog showing up. After the installation is finished another dialog asks us whether or not to restart the workbench immediately. We want to be able to use the newly installed plugins immediately so we click <emphasis><property>Yes</property></emphasis>:</para>
+<figure>
+<title>Restart the Workbench</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jBPMDesignerInstall/default.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>Congratulations. The JBoss jBPM GPD plugin is installed and ready to use. Let's see how we can set up a project and create a process definition in the following chapter.</para>
+</section>
</chapter>
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4848 - in trunk/seam/docs/reference/en: modules and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2007-11-12 09:40:01 -0500 (Mon, 12 Nov 2007)
New Revision: 4848
Added:
trunk/seam/docs/reference/en/modules/
trunk/seam/docs/reference/en/modules/business_application.xml
trunk/seam/docs/reference/en/modules/curd_application_walkthrough.xml
trunk/seam/docs/reference/en/modules/curd_database_application.xml
trunk/seam/docs/reference/en/modules/jsp_application.xml
trunk/seam/docs/reference/en/modules/rad_jsf_application.xml
trunk/seam/docs/reference/en/modules/testng.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-298 Seam Dev Tools Reference Guide. Xml files names changed + pictures sorted into corresponding folders and named as "chapter_name_?"
Added: trunk/seam/docs/reference/en/modules/business_application.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/business_application.xml (rev 0)
+++ trunk/seam/docs/reference/en/modules/business_application.xml 2007-11-12 14:40:01 UTC (rev 4848)
@@ -0,0 +1,461 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="business_application" xreflabel="business_application">
+ <?dbhtml filename="business_application.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>Business process</keyword>
+ <keyword>Seam</keyword>
+ <keyword>JBoss Rules</keyword>
+ <keyword>CURD-application</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Business process and rules application</title>
+ <para>Rules and business processes are important components in many enterprise applications.
+ They help business analysts to get involved in the design and implementation of the software
+ project. Rules and business processes are also essential to complex internal states of large,
+ multi-user systems. The JBoss Rules engine (formerly known as Drools) and jBPM business
+ process engine are two production-ready open source products supported by Red Hat. It is
+ very easy to incorporate rules and business processes into a Seam web application using the
+ Red Hat Developer Studio. In this section, we further re-factor the CRUD application we
+ already have and add support for an "order management" process.User scenario is to
+ simulate the following process and rules:</para>
+ <itemizedlist>
+ <listitem>The site administrator logs in and sees a list of outstanding orders</listitem>
+ <listitem>She goes through the inventory (by hand or using another computer system) and
+ determines the availability of the products in each order. She enters that information to
+ each order.</listitem>
+ <listitem>She starts a process for each order, which determines whether to ship the order
+ or refund the order based on a business rule applied to the availability status. For
+ instance, an "in stock" status triggers a "ship" action while the "back order" status
+ triggers a "refund" action.</listitem>
+ <listitem>When the business process reaches the "ship" or "refund" state, it will take
+ appropriate actions (e.g., to submit shipping orders to Fedex or to contact the credit
+ card company for refund). In this simple case, we will just print out a message on the
+ console to prove that we can execute any code in those stages.</listitem>
+ </itemizedlist>
+ <para>While this process sounds simple, it is the basis for very complex business
+ processes. In this section of the tutorial, we will show you how this is done via the
+ following steps:</para>
+ <itemizedlist>
+ <listitem>Add a rule definition to the application</listitem>
+ <listitem>Add a business process that uses that rule to the application</listitem>
+ <listitem>Start the business process from a web action</listitem>
+ </itemizedlist>
+<section id="ImportConfigurationFilesAndJavaCode">
+<?dbhtml filename="ImportConfigurationFilesAndJavaCode.html"?>
+<title>Import configuration files and Java code</title>
+<para>Before we start, we need to import some configuration and Java files for the demo project.
+Those files are very simple and we will review them as we go along with the tutorial. We import
+them here to reduce potential typos and other errors in the tutorial.</para>
+<orderedlist>
+<listitem>Choose the <emphasis>File > Import ...</emphasis> menu and then select <emphasis>General > Existing</emphasis> project into workspace and
+click on the Next button.</listitem>
+</orderedlist>
+<figure>
+<title>Importing Project</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_1.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<orderedlist continuation="continues">
+<listitem>To make this demo a little more manageable we have already created some demo code
+that is available in the rules-bpm directory of your tutorial distribution code. It is
+ located in the root directory of the distribution. Select the rules-bpm directory and check
+ the "Copy projects into the workspace" directory check box.</listitem>
+</orderedlist>
+<para>You will have a different directory on your machine than the screen shot shown below.</para>
+<figure>
+<title>Selecting Directory To Import</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_2.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<orderedlist continuation="continues">
+<listitem>After this step you will see a new project called "rules-bpm". If you expand that
+directory, you will see numerous files as shown below. We will look at these files in this
+ section of the demo. We will first start by copying these files into our EclipseCon project.</listitem>
+</orderedlist>
+
+<figure>
+<title>Project Structure</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_3.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<orderedlist continuation="continues">
+<listitem>Right click on the rules-bpm/build.xml file, and select <emphasis>Run AS ... > Ant</emphasis> Build.</listitem>
+</orderedlist>
+
+<figure>
+<title>AntBuild</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_4.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<orderedlist continuation="continues">
+<listitem>Right click on the EclipseCon project and select Refresh from the menu to pick up
+ the changes made to the demo application. The rules-bpm/build.xml script copies a bunch of files
+ into your existing EclipseCon project. We will look at them soon.</listitem>
+</orderedlist>
+</section>
+<section id="CreateARuledefinition">
+<?dbhtml filename="CreateARuledefinition.html"?>
+<title>Create a rule definition</title>
+<para>In this section, we create a business rule that can be used in junction with the business
+ process. When the rule is executed, it checks the status of the currently selected order. If the
+ order status is "in stock", meaning that a person has check off line and verified the
+ availability of the product ordered, the system changes the order status to "ship", meaning
+ that someone will now ship the product as the next step in the process. If the order status
+ is "back order", the rule changes the order status to "refund" automatically to trigger the
+ business process of refunding.</para>
+ <orderedlist>
+ <listitem>Select the<emphasis> EclipseCon/resources </emphasis>directory. That is where we are going to put the
+ rules definition file.</listitem>
+ <listitem>Select the following menu actions: <emphasis>File > New > Other ... > JBoss Rules > New
+ Rules Resource</emphasis> to bring up the JBoss Rules wizard.</listitem>
+ </orderedlist>
+ <figure>
+<title>New Rules File</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_5.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<orderedlist continuation="continues">
+<listitem>Fill out the above window with the following values.</listitem>
+</orderedlist>
+<table>
+ <title>Rule Table</title>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>Field Name</entry>
+ <entry>Field Value</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>File Name</entry>
+ <entry>process-order.drl</entry>
+ </row>
+ <row>
+ <entry>Type of Rule Resource</entry>
+ <entry>New DRL (rule package)</entry>
+ </row>
+ <row>
+ <entry>Rule Package Name</entry>
+ <entry>process.order</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <orderedlist continuation="continues">
+<listitem>Replace the content of the process-order.drl file with the follow rule.</listitem>
+</orderedlist>
+<programlisting role="JAVA"><![CDATA[package process.order
+ import com.mydomain.EclipseCon.Orders;
+
+rule "Ship order rule"
+ when
+ order : Orders(status == "in stock")
+ then
+ order.setStatus("ship");
+end
+
+rule "Refund order rule"
+ when
+ order : Orders(status == "back order")
+ then
+ order.setStatus("refund");
+end
+]]></programlisting>
+<para>Notice that the IDE automatically highlights the syntax and provides auto-completion help.
+ You may wonder how Seam knows to load the process-order.drl file for the application.</para>
+ <para>If you look in the <emphasis><property>resources/WEB-INF/components.xml</property></emphasis> file we copied from the imported
+ rules-bpm project. It has an element pointing to the process-order.drl file.</para>
+ <programlisting role="XML"><![CDATA[<drools:rule-base name="securityRules">
+ <drools:rule-files>
+ <value>/security.drl</value>
+ </drools:rule-files>
+ </drools:rule-base>
+]]></programlisting>
+</section>
+<section id="CreateABusinessProcessDefinition">
+<?dbhtml filename="CreateABusinessProcessDefinition.html"?>
+<title>Create a business process definition</title>
+<para>Next, let's create a business process that manages the order process. The business process
+ essentially specifies a sequence of actions that has to happen before an order is shipped or
+ refunded. Since the business analyst typically designs this process, it is very high level and
+ can be drawn up in a GUI designer.</para>
+ <orderedlist>
+ <listitem>Select the<emphasis> EclipseCon/resources </emphasis>folder and select menu actions <emphasis>File > New > File</emphasis>.
+ Add a new file called process-order.jpdl.xml as shown below:</listitem>
+ </orderedlist>
+ <figure>
+<title>Creating New File Resource</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_6.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+<orderedlist continuation="continues">
+<listitem>Add the following content to the process-order.jpdl.xml file. It is an empty jBPM
+process definition, and allows us to use the jBPM visual designer to further edit it.</listitem>
+</orderedlist>
+<programlisting role="XML"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
+<process-definition
+ xmlns="" name="process-order">
+</process-definition>
+]]></programlisting>
+<orderedlist continuation="continues">
+<listitem>Right click on the process-order.jpdl.xml file and select <emphasis>Open with ... > jBPM
+Graphical Process Designer</emphasis>.</listitem>
+</orderedlist>
+<figure>
+<title>Opening Graphical Process Designer</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_7.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<orderedlist continuation="continues">
+<listitem>In the designer, drag and drop nodes and transition lines until you have a process
+ shown in the following image. This is a high level process and aimed at business level non
+ technical users.</listitem>
+</orderedlist>
+<para>To draw a node, click on the type of the node in the palette. You should be able to see
+that based on the icon on the node as shown below. Draw a rectangle on the canvas and the
+ appropriate node will be rendered.</para>
+ <para>To draw a transition click on the transition icon in the palette, choose the source node
+ and then the destination node. This will draw a transition from the source to the destination.</para>
+ <para>To change the name on the node or transition, select the object and change the name in
+ the properties view or simply double click on the node or the transition line to change it.</para>
+ <figure>
+<title>Diagram View</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_8.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<orderedlist continuation="continues">
+<listitem>Save this file. You can click on the Source tab to view the generated XML file for
+ the process.</listitem>
+</orderedlist>
+</section>
+<section id="AssociateProcessNodesWithJavaCode">
+<?dbhtml filename="AssociateProcessNodesWithJavaCode.html"?>
+<title>Associate process nodes with Java code</title>
+<para>With the business process in the designer, we can now associate each node with Java code.
+ The Java code is executed when the node is reached in the process, and the Java code determines
+ the outcome of each node – hence the next node in the process.</para>
+ <para>Let's go through the exercise for the "Check Inventory" node first.</para>
+ <orderedlist>
+ <listitem>Right click on the "Check Inventory" node in the designer and select <emphasis>Add
+ Actions > Node Enter </emphasis>from the menu as shown below.</listitem>
+ </orderedlist>
+ <figure>
+<title>Node Entering</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_9.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<orderedlist continuation="continues">
+<listitem>In the Outline view tab, open the tree view of process-order > Check Inventory >
+node enter, and you will see action1. The Outline view may be hidden or on the left side of the
+ IDE.</listitem>
+</orderedlist>
+<figure>
+<title>Outline View</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_10.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<orderedlist continuation="continues">
+<listitem>Double click on action1 to bring up the wizard. Select Handler on the left and enter
+ com.mydomain.EclipseCon.process. CheckInventoryAction as the class and bean as the type as shown
+ below. You can can also search for the class by clicking on the <emphasis>Browse...</emphasis> button.</listitem>
+</orderedlist>
+<figure>
+<title>Action Handler</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_11.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>Explanation: Now, you must wonder where this
+com.mydomain.EclipseCon.process.CheckInventoryAction class come from It comes from the
+eclipsecon-rules-bpm project we imported. The Java class has a single method that is executed
+when the "Check Inventory" node is reached in the process. The method just fires the rule we
+previously defined in process-order.drl. After the rule is executed, it updates the
+"inventoryStatus" component. Here is the method:</para>
+<programlisting role="JAVA"><![CDATA[public void execute(ExecutionContext ctx) throws Exception {
+
+ //get a handle to the rules engine
+ Component c = (Component) Contexts.getApplicationContext().get(
+ "orderWorkingMemory.component");
+ WorkingMemory wm = (WorkingMemory) ((ManagedWorkingMemory) c
+ .newInstance()).getWorkingMemory();
+
+ //get the ordersHome variable that was set in OrderProcessor.
+ OrdersHome order = (OrdersHome) ctx.getVariable("ordersHome");
+
+ //Assert Orders to working memory and fire rules
+ wm.assertObject(order.getInstance());
+ wm.fireAllRules();
+
+
+ //persist the updated Orders object
+ order.persist();
+
+ //set inventory status so decision node knows what to do
+ ctx.setVariable("inventoryStatus", order.getInstance().getStatus());
+ System.out.println("CHECK INVENTORY - STATUS: "
+ + order.getInstance().getStatus());
+}
+]]></programlisting>
+<para>The "inventoryStatus" component is then used in the "Inventory Decision" node to determine
+which node to go to next. To do that, open the process-order.jpdl.xml file in the text editor and
+ change the node from this</para>
+ <programlisting role="XML"><![CDATA[<decision name="Inventory Decision">
+ <transition name="ship" to="Ship Order"></transition>
+ <transition name="refund" to="Refund Order"></transition>
+ </decision>
+]]></programlisting>
+<para>to this:</para>
+<programlisting role="XML"><![CDATA[<decision name="Inventory Decision" expression="#{inventoryStatus}">
+ <transition name="ship" to="Ship Order"></transition>
+ <transition name="refund" to="Refund Order"></transition>
+ </decision>
+]]></programlisting>
+<para>Now, let's repeat the exercise to assign handler Java classes to the "Ship Order" and "Refund Order" nodes. </para>
+<itemizedlist>
+<listitem>Associate "Ship Order" node with the com.mydomain.EclipseCon.process.ShipOrderAction
+bean</listitem>
+<listitem>Associate "Refund Order" node with the com.mydomain.EclipseCon.process.SendRefundAction bean</listitem>
+</itemizedlist>
+<para>As we described earlier, in a real world system, those two nodes would invoke Java code
+ that perform real shipping and refunding tasks. But here we just print out a message as a proof
+ of concept. You can look into their Java classes if you have time.</para>
+</section>
+<section id="StartTheProcessFromAWebAction">
+<?dbhtml filename="StartTheProcessFromAWebAction.html"?>
+<title>Start the process from a web action</title>
+<para>Finally, we need a "hook" to start the entire business process. We will add a new Process
+ Order button to the Orders.xhtml file.</para>
+ <para>You can add the new button right next to the existing "Add orderdetails" button.
+ Copy/paste the following button code in the actionButtons region:</para>
+ <programlisting role="XML"><![CDATA[<s:button id="buttonId" value="Process Order"
+ action="#{orderProcessor.startProcess}"
+ view="/Orders.xhtml"/>
+]]></programlisting>
+<para>Explanation: When you click on the Process Order button, Seam invokes
+the #{orderProcessor.startProcess} method, which in turn, starts the business process. The Java
+code for the #{orderProcessor} component is in the com.mydomain.EclipseCon.process.OrderProcessor
+class. Like other Java source files in the process package, the OrderProcessor.java is already
+copied to the EclipseCon project when you run the build.xml script from the imported rules-bpm
+ project. Here is the content of the OrderProcessor.java file. The startProcess() method, which
+ is invoked from the Process Order button, starts the process-order process we just created.</para>
+<programlisting role="JAVA"><![CDATA[@Name("orderProcessor")
+public class OrderProcessor {
+
+ //Set the Orders object as a jBPM context variable
+ @In(create = true)
+ @Out(scope = ScopeType.BUSINESS_PROCESS)
+ OrdersHome ordersHome;
+
+ //Execute the jBPM process
+ @CreateProcess(definition = "process-order")
+ public String startProcess() {
+ return "success";
+ }
+}
+]]></programlisting>
+</section>
+<section id="TryItOut">
+<?dbhtml filename="TryItOut.html"?>
+<title>Try it out</title>
+<para>Now save the project and restart the server to make sure that it is properly re-deployed.
+Navigate to the OrdersList page and enter "In Process" to the status field to search for
+un-processed orders.</para>
+<para>Select one order and edit the order and change the "status" field to "in stock" and
+click "Done". Please enter the case exactly as indicated here:</para>
+<figure>
+<title>Order Edit Page</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_12.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>Click the "Process Order" button.</para>
+<figure>
+<title>Order Details</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_13.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>The business process should lead to the ShipOrderAction bean, which will print out the
+ "SHIP ORDER" message in the console view tab at the bottom of the IDE screen.</para>
+ <figure>
+<title>Console View</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_14.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>Select one order and change the "status" field to "back order" and click "Done". Please
+enter the case exactly as indicated here:</para>
+<figure>
+<title>Changing Status Field</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_15.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>Click the "Process Order" button.</para>
+<figure>
+<title>Invoking Process Order</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_16.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>The business process should invoke the SendRefundAction bean, which will print out the
+"SEND REFUND" message in the console view tab at the bottom of the IDE screen.</para>
+<figure>
+<title>Console Panel</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/business_application/business_application_17.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>This example shows a simple example of the powerful jBPM and JBoss Rules runtimes
+integrated in a Seam application. We have also see how easy it is build these kinds of
+applications using the Red Hat Developer Studio.</para>
+</section>
+ </chapter>
Added: trunk/seam/docs/reference/en/modules/curd_application_walkthrough.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/curd_application_walkthrough.xml (rev 0)
+++ trunk/seam/docs/reference/en/modules/curd_application_walkthrough.xml 2007-11-12 14:40:01 UTC (rev 4848)
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="curd_application_walkthrough" xreflabel="curd_application_walkthrough">
+ <?dbhtml filename="curd_application_walkthrough.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>Red Hat Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>CURD</keyword>
+ <keyword>JBoss AS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>The CURD Application Walkthrough</title>
+
+</chapter>
+
Added: trunk/seam/docs/reference/en/modules/curd_database_application.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/curd_database_application.xml (rev 0)
+++ trunk/seam/docs/reference/en/modules/curd_database_application.xml 2007-11-12 14:40:01 UTC (rev 4848)
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="curd_database_application" xreflabel="curd_database_application">
+ <?dbhtml filename="curd_database_application.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>Red Hat Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>CURD</keyword>
+ <keyword>Database Application</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Generate a CURD Database Application</title>
+
+</chapter>
+
Added: trunk/seam/docs/reference/en/modules/jsp_application.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/jsp_application.xml (rev 0)
+++ trunk/seam/docs/reference/en/modules/jsp_application.xml 2007-11-12 14:40:01 UTC (rev 4848)
@@ -0,0 +1,272 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="jsp_application" xreflabel="jsp_application">
+ <?dbhtml filename="jsp_application.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>Red Hat Developer Studio</keyword>
+ <keyword>JSP</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Developing a simple JSP web application</title>
+ <para>In this chapter you'll find out how to create a simple JSP application using the Red Hat Developer Studio. The application will show a classic "Hello World!" on the page.</para>
+ <para>We'll assume that you have already launched Red Hat Developer Studio and
+also that the Web Development perspective is the current perspective. (If not, make it active by selecting <emphasis><property>Window > Open Perspective > Web Development</property></emphasis> from the menu bar or by selecting <emphasis><property>Window > Open Perspective > Other...</property></emphasis> from the menu bar and then selecting Web Development from
+the Select Perspective dialog box.)</para>
+ <section id="SettingUpTheProject">
+ <?dbhtml filename="SettingUpTheProject.html"?>
+ <title>Setting Up the Project</title>
+ <para>At first a new project for the application will be created.</para>
+ <itemizedlist>
+ <listitem><para>Go to the menu bar and select <emphasis><property>File > New > Project...</property></emphasis></para></listitem>
+ <listitem><para>Select <emphasis><property>Web > Dynamic Web Project</property></emphasis> in the New Project dialog box</para></listitem>
+ <listitem><para>Click <emphasis><property>Next</property></emphasis> </para></listitem>
+ <listitem><para>Enter "jspHello" as a project name</para></listitem>
+ <listitem><para>Leave everything else as is, and click <emphasis><property>Finish</property></emphasis></para></listitem>
+ </itemizedlist>
+ <figure>
+ <title>Create New Web Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>A jspHello node should appear in the upper-left Package Explorer view.</para>
+ <figure>
+ <title>New Web Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section id="CreatingJSPPage">
+ <?dbhtml filename="CreatingJSPPage.html"?>
+ <title>Creating JSP Page</title>
+ <para>In our simple application we need to create only one JSP page which displays a "Hello World!" message.</para>
+ <itemizedlist continuation="continues">
+<listitem><para>Right click <emphasis><property>WebContent > New > JSP</property></emphasis>.</para></listitem>
+<listitem><para>Type "hello.jsp" for a file name and click the <emphasis><property>Next</property></emphasis> button.</para></listitem>
+</itemizedlist>
+<para>In the next window you can choose a template for your jsp page and see its preview.</para>
+<itemizedlist continuation="continues">
+<listitem><para>Select <emphasis><property>New JSP File (xhtml)</property></emphasis> template and click <emphasis><property>Finish</property></emphasis> button.</para></listitem>
+</itemizedlist>
+<figure>
+ <title>Create JSP Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Our hello.jsp page will now appear in Project Explorer.</para>
+ <section id="EditingJSPPage">
+ <?dbhtml filename="EditingJSPPage.html"?>
+ <title>Editing a JSP Page</title>
+ <para>Let's now make a little change so that a jsp page displays "Hello World!" message.</para>
+ <itemizedlist continuation="continues">
+<listitem><para>Insert this line inside the <emphasis role="bold"><property><body></property></emphasis><emphasis role="bold"><property></body></property></emphasis> tag:
+</para></listitem>
+</itemizedlist>
+<programlisting role="XML"><![CDATA[<% System.out.println("Hello World!"); %>]]>
+</programlisting>
+
+<para>Notice that content assist functionality is always available when you are typing:</para>
+<figure>
+ <title>Content Assist in JSP Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>After changes made your hello.jsp page should look like this:</para>
+ <figure>
+ <title>Hello.jsp Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section id="WebXML">
+ <?dbhtml filename="WebXML.html"?>
+ <title>web.xml file</title>
+ <para>When you are creating web project the wizard creates the web.xml for you automatically. The web.xml file editor provided by Red Hat Developer Studio is available in two modes: design and source.</para>
+ <figure>
+ <title>Web.xml in Design Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <figure>
+ <title>Web.xml in Source Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Both modes are fully synchronized. Let's add mapping to our hello.jsp page in web.xml file.</para>
+ <itemizedlist>
+ <listitem><para>Switch to <property>source</property> mode.</para></listitem>
+ <listitem><para>Add the next code into <emphasis role="bold"><property><welcome-file-list></property></emphasis>:</para></listitem>
+ </itemizedlist>
+ <programlisting role="XML"><![CDATA[<welcome-file>hello.jsp</welcome-file>
+]]></programlisting>
+<para>If you come back to design mode you will see that the changes made are automatically reflected in that mode.</para>
+<para>Actually you don't really need any config right now. You can clear the web.xml file, save it and you'll still be able to launch your application.</para>
+ </section>
+
+ <section id="DeployTheProject">
+ <?dbhtml filename="DeployTheProject.html"?>
+ <title>Deploying the project</title>
+ <para>While creating any web project you could experience a pain writing ant scripts and managing the
+packaging even if a developer is writing the most trivial web applications. With Red Hat Developer Studio you are saved from such a pain. All you need is to start JBoss server and launch your application in your favorite browser.</para>
+ <para>You can also create a war archive with RHDS's Archive Tools and export it to any web server.</para>
+ <section id="WarConfig">
+ <?dbhtml filename="WarConfig.html"?>
+ <title>WAR Config</title>
+ <para>Project archives managing is available through <property>Project archives</property> view.</para>
+ <itemizedlist>
+ <listitem><para>Select <emphasis><property>Window > Show view > Other > JBoss Tools > Project archives</property></emphasis> from menu bar</para></listitem>
+ <listitem><para>Select a project in Package Explorer you want to be archived</para></listitem>
+ </itemizedlist>
+ <para>In Project Archives you will see available archive types for the project:</para>
+ <figure>
+ <title>Project Archives</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_8.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem><para>Click, for example, <emphasis><property>WAR</property></emphasis> option to create war archive</para></listitem>
+ </itemizedlist>
+ <para>In the dialog New WAR you can see automatically selected default values</para>
+ <figure>
+ <title>New WAR Archive</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_9.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem><para>Click <emphasis><property>Next</property></emphasis> to see a stub archive configuration for your project:
+ <figure>
+ <title>Stub Archive Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_10.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </para></listitem>
+ <listitem><para>Click <emphasis><property>Finish</property></emphasis>. The <emphasis>.war</emphasis> file will appear in Package Explorer and in Project archives view as structure tree:
+ <figure>
+ <title>Archive is Created</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_11.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <figure>
+ <title>Archive in Project Archives View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_12.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </para></listitem>
+ </itemizedlist>
+ <para>Via Project archives view you could now edit your archive, add new folders, publish to server, and so on:</para>
+ <figure>
+ <title>Configure Archive</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_13.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section id="AutoRedeploy">
+ <?dbhtml filename="AutoRedeploy.html"?>
+ <title>Auto redeploy</title>
+ <para>When you are creating a web application and register it on JBoss server it is automatically deployed into <emphasis>/deploy</emphasis> directory of the server. RHDS comes with the feature of auto-redeploy. It means that you don't need to restart JBoss. Any changes made in the application in exploded format will trigger a redeployment on the server.</para>
+ </section>
+ </section>
+
+ <section id="Previewtab">
+ <?dbhtml filename="Previewtab.html"?>
+ <title>JSP Page Preview</title>
+ <para>RHDS comes with JSP design-time preview features. When designing JSP pages you can easily preview how they will look during runtime. You can even attach your stylesheet to the preview.</para>
+ <itemizedlist>
+ <listitem><para>Make a little change to hello.jsp page, e.g. put this code snippet:</para></listitem>
+ </itemizedlist>
+ <programlisting role="XML"><![CDATA[<%= new java.util.Date() %>
+]]></programlisting>
+ <itemizedlist>
+ <listitem><para>Click <emphasis><property>Save</property></emphasis> button.</para></listitem>
+ <listitem><para>Switch to Preview page by clicking Preview tab at the bottom of the page. You will see how the page will look at runtime.</para></listitem>
+ </itemizedlist>
+ <figure>
+ <title>Preview Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_14.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="LaunchingTheProject">
+ <?dbhtml filename="LaunchingTheProject.html"?>
+ <title>Launch JSP Project</title>
+ <para>Let's now launch our project on server. We'll use JBoss server that is shipped with Red Hat Developer Studio.</para>
+ <itemizedlist continuation="continues">
+<listitem><para>Start JBoss server from JBoss Server view by clicking the Start icon.</para></listitem>
+</itemizedlist>
+<figure>
+ <title>Starting Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_15.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist continuation="continues">
+<listitem><para>Click the Run icon or right click your project folder and select <emphasis><property>Run on Server</property></emphasis>. If you haven't made any changes in web.xml file or cleared it out you can launch the application by right clicking the hello.jsp page and selecting <emphasis><property>Run on the Server</property></emphasis>.</para></listitem>
+</itemizedlist>
+<figure>
+ <title>Run Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_16.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>You should see the next page in a browser :</para>
+ <figure>
+ <title>Running Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsp_application/jsp_application_17.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ </section>
+
+</chapter>
\ No newline at end of file
Added: trunk/seam/docs/reference/en/modules/rad_jsf_application.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/rad_jsf_application.xml (rev 0)
+++ trunk/seam/docs/reference/en/modules/rad_jsf_application.xml 2007-11-12 14:40:01 UTC (rev 4848)
@@ -0,0 +1,633 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="rad_jsf_application" xreflabel="rad_jsf_application">
+ <?dbhtml filename="rad_jsf_application.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>Red Hat Developer Studio</keyword>
+ <keyword>JSF</keyword>
+ <keyword>JBoss</keyword>
+ <keyword>RAD</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>RAD development of a simple JSF application</title>
+ <para>In this chapter you will see how to create a simple JSF application being based on <property>"RAD"</property> philosophy. We will create the familiar Guess Number application. The scenario is the following. You are asked to guess a number between 0 and 100. If the guess is correct, a success page is displayed with a link to play again. If the guess is incorrect, a message is printed notifying the user that a smaller or a larger number should be entered and the game continues.</para>
+ <para>We'll show you how to create such an application from scratch, along the way demonstrating powerful features of Red Hat Developer Studio such as project templating, Visual Page Editor, code completion and others. You will design the
+JSF application and then run the application from inside Red Hat Developer Studio using the bundled JBoss server.</para>
+
+<section id="SettingUpTheProject12">
+<?dbhtml filename="SettingUpTheProject12.html"?>
+<title>Setting up the project</title>
+<para>We will create a JSF 1.2 project using an integrated RHDS's new project wizard and predefined templates.</para>
+<itemizedlist>
+ <listitem><para>In Web Projects View (if it is not open select <emphasis><property>Window > Show View > Others > JBoss Tools Web > Web Projects View</property></emphasis>) click <emphasis><property>Create New JSF Project</property></emphasis> button.
+<figure>
+<title>Create New JSF Project</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_1.png"/>
+ </imageobject>
+</mediaobject>
+</figure></para></listitem>
+
+<listitem><para>Put <property>GuessNumber</property> as a project name, in JSF Environment drop down list choose <property>JSF 1.2.</property></para></listitem>
+<listitem><para>Leave everything else as it is and click <emphasis><property>Finish</property></emphasis></para></listitem>
+</itemizedlist>
+<para>Our project will appear in Project Explorer and Web Projects Views. As you can see Red Had Developer Studio has created for us the whole skeleton for the project with all needed libraries, faces-config.xml and web.xml files.</para>
+<figure>
+<title>New JSF Project</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_2.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+</section>
+<section id="CreatingJSPPages">
+<?dbhtml filename="CreatingJSPPages.html"?>
+<title>Creating JSP Pages</title>
+<para>The application has two pages. The first page is inputnumber.jsp. It prompts you to enter a number. If the guess is incorrect, the same page will be redisplayed with a message indicating whether a smaller or a larger number should be tried. The second page is success.jsp. This page will be shown after you guess the number correctly. From this page you also have the option to play the game again.</para>
+
+<para>On the first page inputnumber.jsp you will enter a number.</para>
+<itemizedlist>
+ <listitem><para>Open <emphasis><property>faces-config.xml</property></emphasis> file</para></listitem>
+<listitem><para>Right click anywhere on the diagram mode</para></listitem>
+<listitem><para>From the context menu select <emphasis><property>New View</property></emphasis></para></listitem>
+</itemizedlist>
+<figure>
+<title>Create New View</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_3.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<itemizedlist>
+
+ <listitem><para>Type <emphasis><property>pages/inputnumber</property></emphasis> as the value for <emphasis><property>From-view-id</property></emphasis></para></listitem>
+ <listitem><para>Leave everything else as is and click <emphasis><property>Finish</property></emphasis></para></listitem>
+ <listitem><para>In the same way create another jsf view. Type <emphasis><property>pages/success</property></emphasis> as the value for <emphasis><property>From-view-id</property></emphasis></para></listitem>
+<listitem><para>Select <emphasis><property>File > Save</property></emphasis></para></listitem>
+</itemizedlist>
+<para>On the diagram you will see two created views.</para>
+<figure>
+<title>New Views</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_4.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</section>
+
+<section id="CreatingTransition">
+<?dbhtml filename="CreatingTransition.html"?>
+<title>Creating Transition between two views</title>
+<para>We should now create connection between jsp pages.</para>
+<itemizedlist>
+ <listitem><para>In the diagram, select the <emphasis><property>Create New Connection</property></emphasis> icon third from the top along the upper left side of the diagram to get an arrow cursor with a two-pronged plug at the arrow's bottom
+<figure>
+<title>Create Connection</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_5.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</para></listitem>
+<listitem><para>Click on the <emphasis><property>pages/inputnumber</property></emphasis> page icon and then click on the <emphasis><property>pages/success</property></emphasis> page icon</para></listitem>
+</itemizedlist>
+<para>A transition should appear between the two icons of views.</para>
+<figure>
+<title>Created Connection</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_6.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<itemizedlist>
+<listitem><para>Select <emphasis><property>File > Save</property></emphasis> from the menu bar</para></listitem>
+</itemizedlist>
+</section>
+<section id="CreatingResourceFile">
+<?dbhtml filename="CreatingResourceFile.html"?>
+<title>Creating Resource File</title>
+<para>Red Hat Developer Studio allows to create quickly a resource file. Using this feature you can collect text messages in one central place. A resource file is just a file with a <emphasis>.properties</emphasis> extension. The messages stored in resource file can be displayed to you on a Web page during application execution. </para>
+<para>With resource file first, you don't hard code anything into the JSP pages. And second, it makes it easier to translate your application to other languages. All you have to do is to translate all your messages to the other language and save them in a new properties file with a name that ends with the appropriate ISO-639 language code.</para>
+<para>It is a good idea to keep your resources inside the <emphasis><property>JavaSource</property></emphasis> folder, where you keep your .java files. Every time you build the project, all <emphasis>.properties</emphasis> files will then be copied to the <emphasis>classes</emphasis> folder by default.</para>
+<itemizedlist>
+<listitem><para>Right click <emphasis><property>JavaSource</property></emphasis> folder and select <emphasis><property>New > Folder</property></emphasis></para></listitem>
+ <listitem><para>Type <emphasis><property>game</property></emphasis> for Folder name and click <emphasis><property>Finish</property></emphasis></para></listitem>
+</itemizedlist>
+<para>We will store in this folder our resource file and java bean.</para>
+<itemizedlist>
+ <listitem><para>Right click on <emphasis><property>game folder</property></emphasis> and select <emphasis><property>New > Properties File</property></emphasis></para></listitem>
+<listitem><para>Type <emphasis><property>messages</property></emphasis> as the value for "name" attribute and click <emphasis><property>Finish</property></emphasis></para></listitem>
+</itemizedlist>
+<para>Red Hat Developer Studio will automatically open <property>messages.properties</property> file for editing.</para>
+<figure>
+<title>Messages.properties File</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_7.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<itemizedlist>
+<listitem><para>Click <emphasis><property>Add</property></emphasis> button</para></listitem>
+<listitem><para>Type <emphasis role="italic"><property>how_to_play</property></emphasis> for "name" and <emphasis role="italic"><property>Please pick a number between 0 and 100.</property></emphasis> for value</para></listitem>
+<listitem><para>Click <emphasis><property>Finish</property></emphasis></para></listitem>
+<listitem><para>In such a way add the next properties:</para></listitem>
+</itemizedlist>
+<programlisting role="JAVA"><![CDATA[makeguess_button=Make Guess
+trayagain_button=Play Again?
+success_text=How cool.. You have guessed the number, {0} is correct!
+tryagain_smaller=Oops..incorrect guess. Please try a smaller number.
+tryagain_bigger=Oops..incorrect guess. Please try a bigger number.
+]]></programlisting>
+<itemizedlist>
+<listitem><para>Click <emphasis><property>File > Save</property></emphasis> from the menu bar</para></listitem>
+</itemizedlist>
+<para>Your .properties file should now look like follows:</para>
+<figure>
+<title>Properties are Added</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_8.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</section>
+
+<section id="CreatingJavaBean">
+<?dbhtml filename="CreatingJavaBean.html"?>
+<title>Creating Java Bean</title>
+<para>Now we create a Java bean that will hold business logic of our application.</para>
+<itemizedlist>
+<listitem><para>Right click <emphasis><property>game folder</property></emphasis></para></listitem>
+<listitem><para>Select <emphasis><property>New > Class</property></emphasis></para></listitem>
+<listitem><para>Type <emphasis><property>NumberBean</property></emphasis> for bean name</para></listitem>
+</itemizedlist>
+<para>A java bean is created.</para>
+<itemizedlist>
+<listitem><para>Declare the variable of your entered number:</para></listitem>
+</itemizedlist>
+<programlisting role="JAVA"><![CDATA[Integer userNumber;
+]]></programlisting>
+<para>Red Hat Studio allows to quickly generate getters and setters for java bean.</para>
+<itemizedlist>
+ <listitem><para>Right click <emphasis><property>NumberBean.java</property></emphasis> in Package Explorer</para></listitem>
+<listitem><para>Select <emphasis><property>Source > Generate Getters and Setters...</property></emphasis></para></listitem>
+<listitem><para>Check <emphasis><property>userNumber</property></emphasis> box and click <emphasis><property>OK</property></emphasis>
+<figure>
+<title>Generate Getters and Setters</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_9.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</para></listitem>
+<listitem><para>Add the declaration of the second variable</para></listitem>
+</itemizedlist>
+<programlisting role="JAVA"><![CDATA[int randomNumber;
+]]></programlisting>
+<itemizedlist>
+<listitem><para>.. other bean methods:</para></listitem>
+</itemizedlist>
+<programlisting role="JAVA"><![CDATA[public NumberBean ()
+{
+ randomNumber = (int)(Math.random()*100);
+ System.out.println ( "Random number: "+randomNumber);
+ }
+ public String playagain ()
+ {
+ FacesContext context = FacesContext.getCurrentInstance();
+ HttpSession session = (HttpSession) context.getExternalContext().getSession(false);
+ session.invalidate();
+ return "playagain";
+ }
+ public String checkGuess ()
+ {
+
+ // if guessed, return 'success' for navigation
+ if ( userNumber.intValue() == randomNumber )
+ {
+ return "success";
+ }
+else
+ {
+ FacesContext context = FacesContext.getCurrentInstance();
+ ResourceBundle bundle = ResourceBundle.getBundle("game.messages", context.getViewRoot().getLocale());
+ String msg = "";
+ // if number bigger, get appropriate message
+ if ( userNumber.intValue() > randomNumber )
+ msg = bundle.getString("tryagain_smaller");
+ else // if number smaller, get appropriate message
+ msg = bundle.getString("tryagain_bigger");
+ // add message to be displayed on the page via <h:messages> tag
+ context.addMessage (null, new FacesMessage(msg));
+ // return 'tryagain' for navigation
+ return "tryagain";
+ }
+ }
+]]></programlisting>
+<itemizedlist>
+<listitem><para>And the import declarations:</para></listitem>
+</itemizedlist>
+<programlisting role="JAVA"><![CDATA[import javax.faces.context.FacesContext;
+import javax.servlet.http.HttpSession;
+import javax.faces.application.FacesMessage;
+import java.util.Locale;
+import java.util.ResourceBundle;
+]]></programlisting>
+<para>The whole java bean should look as follows:</para>
+<programlisting role="JAVA"><![CDATA[import javax.faces.context.FacesContext;
+import javax.servlet.http.HttpSession;
+import javax.faces.application.FacesMessage;
+import java.util.Locale;
+import java.util.ResourceBundle;
+
+public class NumberBean
+{
+ Integer userNumber;
+ int randomNumber; // random number generated by application
+public Integer getUserNumber ()
+ {
+ return userNumber;
+ }
+ public void setUserNumber (Integer value)
+ {
+ this.userNumber = value;
+ }
+
+ // constructor, generates random number
+ public NumberBean ()
+ {
+ randomNumber = (int)(Math.random()*100);
+ System.out.println (
+ "Random number: " + randomNumber);
+ }
+
+ public String playagain ()
+ {
+ FacesContext context = FacesContext.getCurrentInstance();
+ HttpSession session = (HttpSession) context.getExternalContext().getSession(false);
+ session.invalidate();
+ return "playagain";
+ }
+
+ // check if user guessed the number
+ public String checkGuess ()
+ {
+ // if guessed, return 'success' for navigation
+ if ( userNumber.intValue() == randomNumber )
+ {
+ return "success";
+ }
+ // incorrect guess
+ else
+ {
+ // get a reference to properties file to retrieve messages
+ FacesContext context = FacesContext.getCurrentInstance();
+ ResourceBundle bundle = ResourceBundle.getBundle("game.messages", context.getViewRoot().getLocale());
+ String msg = "";
+ // if number is bigger, get appropriate message
+ if ( userNumber.intValue() > randomNumber )
+ msg = bundle.getString("tryagain_smaller");
+ else // if number smaller, get appropriate message
+ msg = bundle.getString("tryagain_bigger");
+
+ // add message to be displayed on the page via <h:messages> tag
+ context.addMessage (null, new FacesMessage(msg));
+ // return 'tryagain' for navigation
+ return "tryagain";
+ }
+ }
+}
+]]></programlisting>
+</section>
+
+<section id="EditingFacesConfig">
+<?dbhtml filename="EditingFacesConfig.html"?>
+<title>Editing faces-config.xml File</title>
+<para>This file holds two navigation rules and defines the backing bean used.</para>
+<itemizedlist>
+<listitem><para>Open faces-config.xml file in a source mode</para></listitem>
+<listitem><para>Add here one more navigation rule and a managed bean declarations that the content of the file looks like this:</para></listitem>
+</itemizedlist>
+<programlisting role="XML"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
+<faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee
+xmlns:xi="http://www.w3.org/2001/XInclude"
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2_.xsd">
+
+ <navigation-rule>
+ <from-view-id>*</from-view-id>
+ <navigation-case>
+ <from-outcome>playagain</from-outcome>
+ <to-view-id>/pages/inputnumber.jsp</to-view-id>
+ </navigation-case>
+ </navigation-rule>
+
+ <navigation-rule>
+ <from-view-id>/pages/inputnumber.jsp</from-view-id>
+ <navigation-case>
+ <from-outcome>success</from-outcome>
+ <to-view-id>/pages/success.jsp</to-view-id>
+ </navigation-case>
+ </navigation-rule>
+
+ <managed-bean>
+ <managed-bean-name>NumberBean</managed-bean-name>
+ <managed-bean-class>game.NumberBean</managed-bean-class>
+ <managed-bean-scope>session</managed-bean-scope>
+ </managed-bean>
+
+</faces-config>
+]]></programlisting>
+<para>The first navigation rule states that from any page (<property>*</property> stands for any page) an outcome of playagain will take you to <emphasis>/pages/inputnumber.jsp</emphasis>. Outcome values are returned from backing bean methods in this example. The second navigation rule states that if you are at the page <emphasis>/pages/inputnumber.jsp</emphasis>, and the outcome is success, then navigate to the <emphasis>/pages/success.jsp</emphasis> page.
+</para>
+</section>
+<section id="EditingTheJSPViewFiles2">
+<?dbhtml filename="EditingTheJSPViewFiles2.html"?>
+<title>Editing the JSP View Files</title>
+<para>Now we will finish editing the JSP files for our two "views" using Visual Page
+Editor.</para>
+<section id="EditingInputjsp">
+<?dbhtml filename="EditingInputjsp.html"?>
+<title>Editing inputnumber.jsp page</title>
+<para>On this page we will have an output text component displaying a message, a text field for user's number entering and a button for input submission.</para>
+<itemizedlist>
+<listitem><para>Open inputnumber.jsp by double-clicking on the <emphasis><property>/pages/inputnumber.
+jsp</property></emphasis> icon</para></listitem>
+</itemizedlist>
+<para>The Visual Page Editor will open in a screen split between source code along the top and
+a WYSIWIG view along the bottom. You can see that some JSF code will be already generated as we choose a template when creating the page.</para>
+<para>At the beginning it's necessary to create a <emphasis role="bold"><property><h:form></property></emphasis> component where all others components are put.</para>
+<itemizedlist>
+<listitem><para>Place the mouse cursor inside <emphasis role="bold"><property><f:view></property></emphasis><emphasis role="bold"><property></f:view></property></emphasis></para></listitem>
+<listitem><para>Go to JBoss Tools Palette and expand JSF HTML folder by selecting it</para></listitem>
+<listitem><para>Click on <emphasis role="bold"><property><h:form></property></emphasis> tag
+<figure>
+<title>Insert h:form</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_10.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</para></listitem>
+<listitem><para>In the dialog Insert Tag select <emphasis><property>id</property></emphasis> and click on this line below the value header. A blinking cursor will appear in a input text field inviting to enter a value of id
+<figure>
+<title>Define Id of Form</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_11.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</para></listitem>
+<listitem><para>Type <emphasis><property>inputNumbers</property></emphasis> and click <emphasis><property>Finish</property></emphasis></para></listitem>
+</itemizedlist>
+<para>In source view you can see the declaration of a form.</para>
+<figure>
+<title>Created Form</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_12.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>First let's declare the properties file in inputnumber.jsp page using the loadBundle JSF tag.</para>
+<itemizedlist>
+<listitem><para>Put this declaration on the top of a page, right after the first two lines:</para></listitem>
+</itemizedlist>
+<programlisting role="XML"><![CDATA[<f:loadBundle basename="game.messages" var="msg"/>
+]]></programlisting>
+<para>As always Red Hat Studio provides code assist:</para>
+<figure>
+<title>Code Assist</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_13.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<itemizedlist>
+<listitem><para>Switch to Visual tab, so it could be possible to work with the editor completely in its WYSIWYG mode</para></listitem>
+<listitem><para>Click on <emphasis><property>outputText</property></emphasis>, drag the cursor over to the editor, and drop it inside the blue box in the editor</para></listitem>
+
+<listitem><para>Select <emphasis><property>value</property></emphasis> and click on this line below "value" header</para></listitem>
+<listitem><para>Click <property>...</property> button next to the value field</para></listitem>
+</itemizedlist>
+<para>RHDS will nicely propose you to choose within available values:</para>
+<figure>
+<title>Choose Value</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_14.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<itemizedlist>
+<listitem><para>Expand <emphasis><property>Resource Bundles > msg</property></emphasis></para></listitem>
+ <listitem><para>Select <emphasis><property>how_to_play</property></emphasis> value and click <emphasis><property>Ok</property></emphasis>. Then click <emphasis><property>Finish</property></emphasis>
+<figure>
+<title>Selecting Value</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_15.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</para></listitem>
+</itemizedlist>
+<para>The text will appear on the page:</para>
+<figure>
+<title>Created OutputText Component</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_16.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<itemizedlist>
+<listitem><para>Switch to Source mode and insert <emphasis role="bold"><property><br/></property></emphasis> tag after <emphasis role="bold"><property><h:outputText></property></emphasis> component to make a new line.</para></listitem>
+<listitem><para>Click <emphasis><property>Save</property></emphasis> button.</para></listitem>
+<listitem><para>On the Palette click on <emphasis><property>inputText</property></emphasis>, drag the cursor over to the editor, and drop it inside the editor after the text.</para></listitem>
+<listitem><para>Switch to a Source mode and insert <emphasis role="bold"><property><br/></property></emphasis> tag after <emphasis role="bold"><property><h:outputText></property></emphasis> component to make a new line</para></listitem>
+<listitem><para>Click <emphasis><property>Save</property></emphasis> button</para></listitem>
+<listitem><para>On the Palette click on <emphasis><property>inputText</property></emphasis>, drag the cursor over to the editor, and drop it inside the editor after the text</para></listitem>
+<listitem><para>Select <emphasis><property>value</property></emphasis> and click on this line below "value" header</para></listitem>
+<listitem><para>Click <property>...</property> button next to the value field</para></listitem>
+<listitem><para>Expand <emphasis><property>Managed Beans > NumberBean</property></emphasis></para></listitem>
+ <listitem><para>Select <emphasis><property>userNumber</property></emphasis> value and click <emphasis><property>Ok</property></emphasis></para></listitem>
+<listitem><para>Switch <emphasis><property>Advanced</property></emphasis> tab</para></listitem>
+<listitem><para>Select <emphasis><property>id</property></emphasis> and click on this line below "value" header</para></listitem>
+ <listitem><para>Type <emphasis><property>userNumber</property></emphasis> in text field</para></listitem>
+<listitem><para>Select <emphasis><property>required</property></emphasis> and click on this line below "value" header</para></listitem>
+<listitem><para>Click <property>...</property> button next to the value field</para></listitem>
+<listitem><para>Expand <emphasis><property>Enumeration</property></emphasis> and select <emphasis><property>true</property></emphasis> as a value</para></listitem>
+</itemizedlist>
+<figure>
+<title>Add "required" Attribute</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_17.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<itemizedlist>
+<listitem><para>Click <emphasis><property>Ok</property></emphasis>, then click <emphasis><property>Finish</property></emphasis></para></listitem>
+<listitem><para>Go to Source mode</para></listitem>
+<listitem><para>Add the validation attribute to <emphasis role="bold"><property><f:validateLongRange></property></emphasis> for user input validation</para></listitem></itemizedlist>
+<programlisting role="XML"><![CDATA[<h:inputText id="userNumber" value="#{NumberBean.userNumber}" required="true">
+ <f:validateLongRange minimum="0" maximum="100"/>
+</h:inputText>
+]]></programlisting>
+<itemizedlist>
+<listitem><para>Click <emphasis><property>Save</property></emphasis> button</para></listitem>
+ <listitem><para>Again select <emphasis><property>Visual</property></emphasis> mode</para></listitem>
+<listitem><para>On the Palette, click on <emphasis><property>commandButton</property></emphasis>, drag the cursor over to the editor, and drop it inside the editor after the inputText component.</para></listitem>
+<listitem><para>In the editing dialog select <emphasis><property>value</property></emphasis> and click on this line below "value" header</para></listitem>
+<listitem><para>Click <property>...</property> button next to the value field</para></listitem>
+<listitem><para>Expand <emphasis><property>Resource Bundles > msg</property></emphasis> and select <emphasis><property>makeguess_button</property></emphasis> as a value</para></listitem>
+ <listitem><para>Click <emphasis><property>Ok</property></emphasis></para></listitem>
+<listitem><para>Select <emphasis><property>action</property></emphasis> and click on this line below "value" header</para></listitem>
+ <listitem><para>Type <emphasis><property>NumberBean.checkGuess</property></emphasis> in text field</para></listitem>
+<listitem><para>Click <emphasis><property>Finish</property></emphasis></para></listitem>
+<listitem><para>In Source mode add <emphasis role="bold"><property><br/></property></emphasis> tags between <emphasis role="bold"><property><outputText></property></emphasis>, <emphasis role="bold"><property><inputText></property></emphasis> and <emphasis role="bold"><property><commandButton></property></emphasis> components to place them on different lines</para></listitem>
+</itemizedlist>
+<para>inputnumber.jsp page should look like this:</para>
+<programlisting role="XML"><![CDATA[<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
+<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
+<f:loadBundle basename="game.messages" var="msg"/>
+
+<html>
+ <f:view>
+ <h:form id="inputNumbers">
+ <h:outputText value="#{msg.how_to_play}"/>
+ <br/>
+ <h:messages style="color: blue"/>
+ <br/>
+ <h:inputText id="userNumber" value="#{NumberBean.userNumber}" required="true">
+ <f:validateLongRange minimum="0" maximum="100"/>
+ </h:inputText>
+ <br/><br/>
+ <h:commandButton value="#{msg.makeguess_button}" action="#{NumberBean.checkGuess}"/>
+ </h:form>
+ </f:view>
+</html>
+]]></programlisting>
+</section>
+<section id="EditingSuccessJsp">
+<?dbhtml filename="EditingSuccessJsp.html"?>
+<title>Editing success.jsp page</title>
+<para>In the same way like inputnumber.jsp, edit success.jsp page. Its whole source should be the next:</para>
+<programlisting role="XML"><![CDATA[<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
+<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
+<f:loadBundle basename="game.messages" var="msg"/>
+
+<html>
+ <f:view>
+ <h:form id="result">
+ <h:outputFormat value="#{msg.success_text}">
+ <f:param value="#{NumberBean.userNumber}"/>
+ </h:outputFormat>
+ <br/><br/>
+ <h:commandButton value="#{msg.trayagain_button}" action="#{NumberBean.playagain}"/>
+ </h:form>
+ </f:view>
+</html>
+]]></programlisting>
+<para>Again you can use code assist provided by RHDS when editing jsp page:</para>
+<figure>
+<title>Code Assist for <f:param></title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_18.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>This page, success.jsp, is shown if you correctly guessed the number. The <emphasis role="bold"><property><h:outputFormat></property></emphasis> tag will get the value of success_text from the properties file. The {0} in success_text will be substituted for by the value of the value attribute within the <emphasis role="bold"><property><f:param></property></emphasis> tag during runtime.</para>
+<para>At the end, you have a button which allows you to replay the game. The action value references a backing bean method. In this case, the method only terminates the current session so that when you are shown the first page, the input text box is clear and a new random number is generated.</para>
+<itemizedlist>
+<listitem><para>Switch to Preview mode to see how this page will look in a browser:</para></listitem>
+</itemizedlist>
+<figure>
+<title>Success.jsp in Preview Mode</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_19.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</section>
+</section>
+ <section id="CreatingIndexjsp">
+<?dbhtml filename="CreatingIndexjsp.html"?>
+<title>Creating index.jsp page</title>
+<para>The index.jsp page is the entry point of our application. It's just forwarding to inputnumber.jsp page.</para>
+<itemizedlist>
+<listitem><para>Right click <emphasis><property>WebContent > New > JSP File</property></emphasis></para></listitem>
+ <listitem><para>Type <emphasis><property>index</property></emphasis> for name field and choose <emphasis><property>JSPRedirect</property></emphasis> as a template</para></listitem>
+<listitem><para>Click <emphasis><property>Finish</property></emphasis></para></listitem>
+<listitem><para>The source for this page should be like the following:</para></listitem>
+</itemizedlist>
+<programlisting role="XML"><![CDATA[<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+<html>
+ <body>
+ <jsp:forward page="/pages/inputnumber.jsf" />
+ </body>
+</html>
+
+]]></programlisting>
+<para>Note the <emphasis>.jsf</emphasis> extension of a page. It means that we trigger the JSF controller servlet to handle the page according the servlet mapping in the faces-config.xml file.</para>
+</section>
+<section id="RunningTheApplication33">
+<?dbhtml filename="RunningTheApplication33.html"?>
+<title>Running the Application</title>
+<para>Everything is ready to run the application.</para>
+<itemizedlist>
+ <listitem><para>Start up JBoss server by clicking on the <emphasis><property>Start</property></emphasis> icon in JBoss Server view. (If JBoss is already running, stop it by clicking on the red icon and then start it again. After the messages in the Console tabbed view stop scrolling, JBoss is available</para></listitem>
+ <listitem><para>Click on the <emphasis><property>Red Hat</property></emphasis> run icon in the toolbar</para></listitem>
+<listitem><para>Play with the application by entering correct as well as incorrect values</para></listitem>
+</itemizedlist>
+<figure>
+<title>You are Asked to Enter a Number Between 0 and 100</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_20.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<figure>
+<title>Your Input is Validated and an Error Message is Displayed if Invalid Input was Entered</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_21.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+<figure>
+<title>After You Enter a Guess, the Application Tells You Whether a Smaller or a Larger Number Should be Tried</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_22.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+<figure>
+<title>Your Guess is Correct</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/rad_jsf_application/rad_jsf_application_23.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</section>
+</chapter>
Added: trunk/seam/docs/reference/en/modules/testng.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/testng.xml (rev 0)
+++ trunk/seam/docs/reference/en/modules/testng.xml 2007-11-12 14:40:01 UTC (rev 4848)
@@ -0,0 +1,221 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="testNG" xreflabel="testNG">
+ <?dbhtml filename="testNG.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>Red Hat Developer Studio</keyword>
+ <keyword>RHDS</keyword>
+ <keyword>testNG</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Using TestNG project</title>
+ <section>
+ <title>What is TestNG?</title>
+ <para><property>TestNG</property> ("Testing, the Next Generation") is a Java unit testing framework that aims to overcome many limitations of JUnit.
+ TestNG introduces some new functionalities that make it more powerful and easier to use, such as:</para>
+ <itemizedlist>
+ <listitem><para>JDK 5 Annotations (JDK 1.4 is also supported with JavaDoc annotations).</para></listitem>
+ <listitem><para>Flexible test configuration.</para></listitem>
+ <listitem><para>Support for data-driven testing (with @DataProvider).</para></listitem>
+ <listitem><para>Support for parameters.</para></listitem>
+ <listitem><para>Allows distribution of tests on slave machines.</para></listitem>
+ <listitem><para>Powerful execution model (no more TestSuite).</para></listitem>
+ <listitem><para>Supported by a variety of tools and plug-ins (Eclipse, IDEA, Maven, etc...).</para></listitem>
+ <listitem><para>Embeds BeanShell for further flexibility.</para></listitem>
+ <listitem><para>Default JDK functions for runtime and logging (no dependencies).</para></listitem>
+ <listitem><para>Dependent methods for application server testing.</para></listitem>
+ </itemizedlist>
+
+ <para>More information can be found on home page: <ulink url="http://testng.org">www.testng.org</ulink></para>
+ </section>
+ <section id="OtherRelevantResourcesOnTheTopic5">
+ <?dbhtml filename="OtherRelevantResourcesOnTheTopic5.html"?>
+ <title>Other relevant resources on the topic</title>
+ <para><ulink url="http://www.artima.com/lejava/articles/testng.html">Next-Generation Testing with TestNG (An Interview with Cédric Beust)</ulink></para>
+ <para><ulink url="http://www.javaworld.com/javaworld/jw-04-2005/jw-0404-testng.html">TestNG: The next generation of unit testing</ulink></para>
+ <para><ulink url="http://dev2dev.bea.com/pub/a/2006/09/testng-categorization.html">Test Categorization Techniques with TestNG</ulink></para>
+ <para><ulink url="http://www-128.ibm.com/developerworks/java/library/j-testng/">TestNG makes Java unit testing a breeze</ulink></para>
+ <para><ulink url="http://www-128.ibm.com/developerworks/java/library/j-cq08296/index.html">In pursuit of code quality: JUnit 4 vs. TestNG</ulink></para>
+ </section>
+ <section>
+ <title>How to use the generated Seam-test project to run Seam tests in Red Hat Developer Studio</title>
+
+ <itemizedlist>
+ <listitem><para>Create a new Seam Web Project using New Project wizard or main menu <emphasis><property>File > New > Seam Web Project</property>.</emphasis></para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Seam Web Project Creation</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem><para>Name your project and follow the next wizard steps keeping default settings.</para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>New Seam Project Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem><para>Check <emphasis><property>Server Supplied JSF Implementation</property>.</emphasis></para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Adding JSF Capabilities</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem><para>Select <emphasis><property>EAR</property></emphasis> next to <emphasis><property>Deploy as:</property></emphasis> field.</para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Select Deployment Type</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem><para>After project is created you will have the generated Seam-test project that is setup to run TestNG directly against the proper libraries and server runtime libraries.</para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Seam-test Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem><para>Add Seam Action to your project via <emphasis><property>File > New > Seam Action</property>.</emphasis></para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Seam Action Creation</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem><para>Fill out the wizard fields. New Seam Action wizard will create resources and place them in the apropriate folders dependent on EAR project structure.</para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>New Seam Action Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem><para>When Action is created you will see <property>actionPage.xhtml</property> in Package Explorer view. <property>ActionBean.java</property> will be automatically opened in Java Editor.</para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Created Action</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_8.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ <itemizedlist>
+ <listitem><para>Select <property>ActionLocalTest.xml</property> in Seam-test project and run the test via right click <emphasis><property>Run As > TestNG Suite</property>.</emphasis></para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Running TestNG</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_9.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The test process will start and its ouput will be written in Console View.</para>
+
+ <figure>
+ <title>Test is Finished</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_10.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ <itemizedlist>
+ <listitem><para>After running TestNG you will have the test results in <emphasis><property>test-output</property></emphasis> folder in Seam-test project (press F5 to refresh the Package Explorer view). Open <property>index.html</property> file with Web Browser.</para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Opening Test Results in Web Browser</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_11.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can see the test results in Web Browser.</para>
+
+ <figure>
+ <title>Test Results</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_12.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>After clicking on <emphasis><property>ActionLocal Tests</property></emphasis> link you will see the Results for ActionLocal Tests.</para>
+
+ <figure>
+ <title>Test Information</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_13.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Select a result on the left-hand pane and its details will be displayed on the right-hand one.</para>
+
+ <figure>
+ <title>ActionLocal Test Details</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/testng/testng_14.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ </section>
+ </chapter>
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4847 - in trunk/seam/docs/reference/en/images: testng and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2007-11-12 09:39:46 -0500 (Mon, 12 Nov 2007)
New Revision: 4847
Added:
trunk/seam/docs/reference/en/images/testng/
trunk/seam/docs/reference/en/images/testng/testNG29.png
trunk/seam/docs/reference/en/images/testng/testNG30.png
trunk/seam/docs/reference/en/images/testng/testNG9.png
trunk/seam/docs/reference/en/images/testng/testng_1.png
trunk/seam/docs/reference/en/images/testng/testng_10.png
trunk/seam/docs/reference/en/images/testng/testng_11.png
trunk/seam/docs/reference/en/images/testng/testng_12.png
trunk/seam/docs/reference/en/images/testng/testng_13.png
trunk/seam/docs/reference/en/images/testng/testng_14.png
trunk/seam/docs/reference/en/images/testng/testng_2.png
trunk/seam/docs/reference/en/images/testng/testng_3.png
trunk/seam/docs/reference/en/images/testng/testng_4.png
trunk/seam/docs/reference/en/images/testng/testng_5.png
trunk/seam/docs/reference/en/images/testng/testng_6.png
trunk/seam/docs/reference/en/images/testng/testng_7.png
trunk/seam/docs/reference/en/images/testng/testng_8.png
trunk/seam/docs/reference/en/images/testng/testng_9.png
Log:
http://jira.jboss.com/jira/browse/RHDS-298 Seam Dev Tools Reference Guide. Xml files names changed + pictures sorted into corresponding folders and named as "chapter_name_?"
Added: trunk/seam/docs/reference/en/images/testng/testNG29.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testNG29.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testNG30.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testNG30.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testNG9.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testNG9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_1.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_10.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_10.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_11.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_11.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_12.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_12.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_13.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_13.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_14.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_14.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_2.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_3.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_4.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_5.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_6.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_7.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_8.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/testng/testng_9.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/testng/testng_9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4846 - in trunk/seam/docs/reference/en/images: rad_jsf_application and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2007-11-12 09:39:08 -0500 (Mon, 12 Nov 2007)
New Revision: 4846
Added:
trunk/seam/docs/reference/en/images/rad_jsf_application/
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_1.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_10.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_11.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_12.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_13.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_14.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_15.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_16.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_17.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_18.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_19.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_2.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_20.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_21.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_22.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_23.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_3.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_4.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_5.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_6.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_7.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_8.png
trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_9.png
Log:
http://jira.jboss.com/jira/browse/RHDS-298 Seam Dev Tools Reference Guide. Xml files names changed + pictures sorted into corresponding folders and named as "chapter_name_?"
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_1.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_10.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_10.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_11.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_11.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_12.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_12.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_13.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_13.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_14.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_14.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_15.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_15.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_16.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_16.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_17.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_17.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_18.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_18.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_19.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_19.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_2.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_20.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_20.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_21.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_21.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_22.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_22.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_23.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_23.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_3.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_4.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_5.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_6.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_7.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_8.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_9.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/rad_jsf_application/rad_jsf_application_9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
17 years, 2 months
- 1
- 0