JBoss Tools SVN: r4896 - in trunk/jbpm/docs/reference/en: modules and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: sabrashevich
Date: 2007-11-14 02:59:38 -0500 (Wed, 14 Nov 2007)
New Revision: 4896
Added:
trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml
Removed:
trunk/jbpm/docs/reference/en/modules/jbpm_designer_install.xml
Modified:
trunk/jbpm/docs/reference/en/master.xml
trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-288 updated second and third chapters
Modified: trunk/jbpm/docs/reference/en/master.xml
===================================================================
--- trunk/jbpm/docs/reference/en/master.xml 2007-11-14 01:10:59 UTC (rev 4895)
+++ trunk/jbpm/docs/reference/en/master.xml 2007-11-14 07:59:38 UTC (rev 4896)
@@ -3,9 +3,9 @@
"../../resources/support/docbook-dtd/docbookx.dtd"
-[<!ENTITY Introduction SYSTEM "modules/introduction.xml">
-<!ENTITY jBPMDesignerInstall SYSTEM "modules/jbpm_designer_install.xml">
-<!ENTITY GuidedTourJBossjBPMGPD SYSTEM "modules/guided_tour_jboss_jbpmgpd.xml">
+[<!ENTITY introduction SYSTEM "modules/introduction.xml">
+<!ENTITY jboss_jbpm_runtime_installation SYSTEM "modules/jboss_jbpm_runtime_installation.xml">
+<!ENTITY guided_tour_jboss_jbpmgpd SYSTEM "modules/guided_tour_jboss_jbpmgpd.xml">
<!ENTITY Test_Drive_Proc SYSTEM "modules/Test_Drive_Proc.xml">
<!ENTITY The_JBoss_jBPM_Int_Mech SYSTEM "modules/The_JBoss_jBPM_Int_Mech.xml">
<!ENTITY Quick_Howto_Guide SYSTEM "modules/Quick_Howto_Guide.xml">
@@ -27,9 +27,9 @@
<toc/>
-&Introduction;
-&jBPMDesignerInstall;
-&GuidedTourJBossjBPMGPD;
+&introduction;
+&jboss_jbpm_runtime_installation;
+&guided_tour_jboss_jbpmgpd;
&Test_Drive_Proc;
&The_JBoss_jBPM_Int_Mech;
&Quick_Howto_Guide;
Modified: trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml
===================================================================
--- trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml 2007-11-14 01:10:59 UTC (rev 4895)
+++ trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml 2007-11-14 07:59:38 UTC (rev 4896)
@@ -82,7 +82,7 @@
<section id="adding_the_nodes">
<?dbhtml filename="adding_the_nodes.html"?>
<title>Adding the Nodes</title>
- <para>Select respectively 'Start', 'State' and 'End' on the tools palette and click on the canvas to add these nodes to the process definition. The result should look similar to this:</para>
+ <para>Select respectively <emphasis><property>Start</property></emphasis>, <emphasis><property>State</property></emphasis> and <emphasis><property>End</property></emphasis> on the tools palette and click on the canvas to add these nodes to the process definition. The result should look similar to this:</para>
<figure>
<title>A Simple Process With Three Nodes</title>
<mediaobject>
@@ -95,7 +95,7 @@
<section id="adding_transitions">
<?dbhtml filename="adding_transitions.html"?>
<title>Adding Transitions</title>
- <para>We will connect the nodes with transitions. Select the <emphasis><property>Transition</property></emphasis> tool in the tools palette and click on the <emphasis><property>Start</property></emphasis> node, then move to the <emphasis><property>State</property></emphasis> node and click again to see the transition being drawn. Perform the same steps to create a transition from the <emphasis><property>State</property></emphasis> node to the <emphasis><property>End</property></emphasis> node. The result looks like:</para>
+ <para>We will connect the nodes with transitions. Select the <emphasis><property>Transition</property></emphasis> tool in the tools palette and click on the <emphasis><property>Start</property></emphasis> node, then move to the <emphasis><property>State</property></emphasis> node and click again to see the transition being drawn. Perform the same steps to create a transition from the <emphasis><property>State</property></emphasis> node to the <emphasis><property>End</property></emphasis> node. The result will look like:</para>
<figure>
<title>A Simple Process With Transitions</title>
<mediaobject>
@@ -110,7 +110,7 @@
<section id="the_outline_view">
<?dbhtml filename="the_outline_view.html"?>
<title>The Outline View</title>
- <para>You can see an outline of the process being drawn in the RHDS outline view if it is visible (if not select <emphasis><property>Window > Show view > Outline</property></emphasis>). It is presented as the classical tree view. Also you use <emphasis><property>Overview</property></emphasis> that comes as as a scrollable thumbnail.</para>
+ <para>You can see an outline of the process being drawn in the RHDS outline view if it is visible (if not select <emphasis><property>Window > Show view > Outline</property></emphasis>). It is presented as the classical tree view. Also you can use <emphasis><property>Overview</property></emphasis> that comes as as a scrollable thumbnail.</para>
<figure>
<title>The Outline and Overview Views</title>
<mediaobject>
Added: trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml
===================================================================
--- trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml (rev 0)
+++ trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml 2007-11-14 07:59:38 UTC (rev 4896)
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="jboss_jbpm_runtime_installation" xreflabel="jboss_jbpm_runtime_installation">
+ <?dbhtml filename="jboss_jbpm_runtime_installation.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword>designer</keyword>
+ <keyword>process</keyword>
+ <keyword>Red Hat Developer Studio</keyword>
+ <keyword>jBPM runtime</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>JBoss jBPM Runtime Installation</title>
+ <para>The jBPM plugin (jBPM Designer) is already included in RHDS. To make it work, you should only download the jBPM runtime (jbpm-jpdl-3.2.2 currently) from <ulink url="http://labs.jboss.com/jbossjbpm/downloads/">here</ulink> and specify the
+directory where you extracted the runtime either when you create a jBPM project or by using the jBPM preference pages.</para>
+ <para>Navigate to <emphasis><property>Window > Preferences > JBoss jBPM > Runtime Locations</property></emphasis>. Here you can add, edit and remove JBoss jBPM installation locations.</para>
+ <para>Click <emphasis><property>Add</property></emphasis> button. In the diallog that appeared enter a name for a newly added jBPM runtime and point to the correct location of this package on your harddrive. Click <emphasis><property>OK</property></emphasis> then click <emphasis><property>OK</property></emphasis> again.</para>
+ <figure>
+<title>Adding jBPM Location</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jbpm_designer_install/jbpm_location.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</chapter>
+
Deleted: trunk/jbpm/docs/reference/en/modules/jbpm_designer_install.xml
===================================================================
--- trunk/jbpm/docs/reference/en/modules/jbpm_designer_install.xml 2007-11-14 01:10:59 UTC (rev 4895)
+++ trunk/jbpm/docs/reference/en/modules/jbpm_designer_install.xml 2007-11-14 07:59:38 UTC (rev 4896)
@@ -1,131 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="jBPMDesignerInstall" xreflabel="jBPMDesignerInstall">
- <?dbhtml filename="jBPMDesignerInstall.html"?>
- <chapterinfo>
- <keywordset>
- <keyword>jBPM</keyword>
- <keyword></keyword>
- <keyword></keyword>
- <keyword></keyword>
- <keyword></keyword>
- </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/jbpm_designer_install/jbpm_installation.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/jbpm_designer_install/jbpm_installation2.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/jbpm_designer_install/jbpm_installation3.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/jbpm_designer_install/jbpm_installation4.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/jbpm_designer_install/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/jbpm_designer_install/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/jbpm_designer_install/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/jbpm_designer_install/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/jbpm_designer_install/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/jbpm_designer_install/default.png"/>
- </imageobject>
-</mediaobject>
-</figure>
-<para>After a while a new wizard appears:</para>
-<figure>
-<title>Feature Verification</title>
-<mediaobject>
- <imageobject>
- <imagedata fileref="images/jbpm_designer_install/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/jbpm_designer_install/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, 1 month
JBoss Tools SVN: r4895 - trunk/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/util.
by jbosstools-commits＠lists.jboss.org
Author: dgolovin
Date: 2007-11-13 20:10:59 -0500 (Tue, 13 Nov 2007)
New Revision: 4895
Modified:
trunk/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/util/ResourcesUtils.java
Log:
http://jira.jboss.com/jira/browse/JBIDE-1310
project.open(IResource.BACKGROUND_REFRESH, new NullProgressMonitor());
replaced to
project.open(IResource.NONE, new NullProgressMonitor());
Modified: trunk/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/util/ResourcesUtils.java
===================================================================
--- trunk/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/util/ResourcesUtils.java 2007-11-13 19:22:50 UTC (rev 4894)
+++ trunk/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/util/ResourcesUtils.java 2007-11-14 01:10:59 UTC (rev 4895)
@@ -75,7 +75,7 @@
IProjectDescription description = ResourcesPlugin.getWorkspace().loadProjectDescription(path);
description.setName(name);
project.create(description, new NullProgressMonitor());
- project.open(IResource.BACKGROUND_REFRESH, new NullProgressMonitor());
+ project.open(IResource.NONE, new NullProgressMonitor());
ResourcesPlugin.getWorkspace().getRoot().refreshLocal(IResource.DEPTH_INFINITE, new NullProgressMonitor());
return project;
}
17 years, 1 month
JBoss Tools SVN: r4894 - in trunk/documentation/whatsnew/hibernate: images and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: max.andersen(a)jboss.com
Date: 2007-11-13 14:22:50 -0500 (Tue, 13 Nov 2007)
New Revision: 4894
Added:
trunk/documentation/whatsnew/hibernate/images/
trunk/documentation/whatsnew/hibernate/images/cfgpropertyvaluecompletion.png
trunk/documentation/whatsnew/hibernate/images/dynamicsqlhighlighting.png
trunk/documentation/whatsnew/hibernate/images/openmappingdblclick.png
trunk/documentation/whatsnew/hibernate/images/reloadconfiguration.png
trunk/documentation/whatsnew/hibernate/images/sortedconfiguration.png
trunk/documentation/whatsnew/hibernate/images/structuredcfgxml.png
trunk/documentation/whatsnew/hibernate/images/structuredhbmxml.png
Modified:
trunk/documentation/whatsnew/hibernate/hibernate-news-3.2.0.cr1.html
Log:
images for hibernate whatsnew
Modified: trunk/documentation/whatsnew/hibernate/hibernate-news-3.2.0.cr1.html
===================================================================
--- trunk/documentation/whatsnew/hibernate/hibernate-news-3.2.0.cr1.html 2007-11-13 17:55:54 UTC (rev 4893)
+++ trunk/documentation/whatsnew/hibernate/hibernate-news-3.2.0.cr1.html 2007-11-13 19:22:50 UTC (rev 4894)
@@ -21,8 +21,11 @@
</tr>
<tr>
<td valign="top" align="right"><a name="itemname3" id="itemname3"></a><b>Easy reload of Hibernate Configuration</b></td>
- <td valign="top">You can now click the "Reload" icon for a Hibernate Console Configuration to quickly reload the Configuration to get the configuration in sync with the latest changes.</td>
+ <td valign="top">
+ <p>You can now click the "Reload" icon for a Hibernate Console Configuration to quickly reload the Configuration to get the configuration in sync with the latest changes.</p>
<p><img src="images/reloadconfiguration.png"/></p>
+ </td>
+
</tr>
<tr>
<td colspan="2"><hr />
@@ -47,8 +50,10 @@
<td valign="top" align="right">
<a name="itemnam2e" id="itemname2"></a><b>Sorted entity and table list</b>
</td>
- <td width="70%" valign="top">Previously the list of entities and tables in the configuration view was ordered in the order they were mapped; with auto-discovery that order makes very little sense thus we now sort the entities and table list by name.</td>
+ <td width="70%" valign="top">Previously the list of entities and tables in the configuration view was ordered in the order they were mapped; with auto-discovery that order makes very little sense thus we now sort the entities and table list by name.
<p><img src="images/sortedconfiguration.png"/></p>
+</td>
+
</tr>
<tr>
<td colspan="2"><hr />
@@ -58,8 +63,10 @@
<td valign="top" align="right">
<a name="itemname3" id="itemname3"></a><b>Syntax highlighting in Dynamic SQL Preview</b>
</td>
- <td valign="top">The Dynamic SQL Preview now has syntax highlighting enabled for the previewed SQL.</td>
+ <td valign="top">The Dynamic SQL Preview now has syntax highlighting enabled for the previewed SQL.
<p><img src="images/dynamicsqlhighlighting.png"/></p>
+ </td>
+
</tr>
<tr>
<td colspan="2">
@@ -71,8 +78,10 @@
<td valign="top" align="right">
<a name="itemname3" id="itemname3"></a><b>Code completion for Hibernate configuration properties</b>
</td>
- <td valign="top"><code>hibernate.cfg.xml</code> and <code>persistence.xml</code> has had support for code completing hibernate property keys, now it includes code completion for the values.</td>
+ <td valign="top"><code>hibernate.cfg.xml</code> and <code>persistence.xml</code> previously only had support for code completing hibernate property keys, now it includes code completion for the values.
<p><img src="images/cfgpropertyvaluecompletion.png"/></p>
+</td>
+
</tr>
<tr>
<td colspan="2"><hr />
@@ -82,9 +91,11 @@
<td valign="top" align="right">
<a name="itemname3" id="itemname3"></a><b>Structured hbm.xml and cfg.xml editor</b>
</td>
- <td valign="top">The structured hbm.xml and cfg.xml editors known from Exadel Studio are now available in Hibernate Tools instead of the generic xml tree editor.</td>
+ <td valign="top">The structured hbm.xml and cfg.xml editors known from Exadel Studio are now available in Hibernate Tools instead of the generic xml tree editor.
+
<p><img src="images/structuredhbmxml.png"/></p>
<p><img src="images/structuredcfgxml.png"/></p>
+</td>
</tr>
<tr>
<td colspan="2"><hr />
Added: trunk/documentation/whatsnew/hibernate/images/cfgpropertyvaluecompletion.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/hibernate/images/cfgpropertyvaluecompletion.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/hibernate/images/dynamicsqlhighlighting.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/hibernate/images/dynamicsqlhighlighting.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/hibernate/images/openmappingdblclick.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/hibernate/images/openmappingdblclick.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/hibernate/images/reloadconfiguration.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/hibernate/images/reloadconfiguration.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/hibernate/images/sortedconfiguration.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/hibernate/images/sortedconfiguration.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/hibernate/images/structuredcfgxml.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/hibernate/images/structuredcfgxml.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/hibernate/images/structuredhbmxml.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/hibernate/images/structuredhbmxml.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
17 years, 1 month
JBoss Tools SVN: r4893 - trunk/jsf/docs/userguide/en/images.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2007-11-13 12:55:54 -0500 (Tue, 13 Nov 2007)
New Revision: 4893
Removed:
trunk/jsf/docs/userguide/en/images/JBossToolsPalette/
trunk/jsf/docs/userguide/en/images/JSFSupport/
trunk/jsf/docs/userguide/en/images/MoreEditors/
trunk/jsf/docs/userguide/en/images/Preferences/
trunk/jsf/docs/userguide/en/images/Roadmap/
trunk/jsf/docs/userguide/en/images/Struts/
trunk/jsf/docs/userguide/en/images/VerificationValidation/
trunk/jsf/docs/userguide/en/images/VisualPageEditor/
trunk/jsf/docs/userguide/en/images/WebProjectsView/
Log:
http://jira.jboss.com/jira/browse/RHDS-298
17 years, 2 months
JBoss Tools SVN: r4892 - in trunk/documentation/whatsnew/seam: images and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: max.andersen(a)jboss.com
Date: 2007-11-13 12:53:39 -0500 (Tue, 13 Nov 2007)
New Revision: 4892
Added:
trunk/documentation/whatsnew/seam/images/
trunk/documentation/whatsnew/seam/images/hqlcriteriaquicknavigation.png
trunk/documentation/whatsnew/seam/images/inlinequeryvalidation.png
trunk/documentation/whatsnew/seam/images/seampreferences.png
trunk/documentation/whatsnew/seam/images/serverselection.png
Modified:
trunk/documentation/whatsnew/seam/seam-news-1.0.0.cr1.html
Log:
images for seam whatsnew
Added: trunk/documentation/whatsnew/seam/images/hqlcriteriaquicknavigation.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/seam/images/hqlcriteriaquicknavigation.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/seam/images/inlinequeryvalidation.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/seam/images/inlinequeryvalidation.png
___________________________________________________________________
Name: svn:executable
+ *
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/seam/images/seampreferences.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/seam/images/seampreferences.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/seam/images/serverselection.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/seam/images/serverselection.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: trunk/documentation/whatsnew/seam/seam-news-1.0.0.cr1.html
===================================================================
--- trunk/documentation/whatsnew/seam/seam-news-1.0.0.cr1.html 2007-11-13 17:51:19 UTC (rev 4891)
+++ trunk/documentation/whatsnew/seam/seam-news-1.0.0.cr1.html 2007-11-13 17:53:39 UTC (rev 4892)
@@ -23,11 +23,13 @@
<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>
-
+ <td width="70%" valign="top">Seam 2 are now supported as a valid runtime and can be used together with the project and artifact creation wizards.
<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>
+
+ </td>
+
</tr>
<tr>
<td colspan="2"><hr />
@@ -37,9 +39,12 @@
<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>
+ <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.
<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>
+
+
+</td>
</tr>
<tr>
<td colspan="2"><hr />
@@ -48,8 +53,9 @@
<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>
+<p>This enables all the HQL code completion and validation inside Java files. Code completion just requires the Hibernate Console configuration to be opened/created, validation requires the Session Factory to be opened/created.</p>
+ <p><img src="images/hqlcriteriaquicknavigation.png"/></p>
+ <p><img src="images/inlinequeryvalidation.png"/></p>
</td>
</tr>
<tr>
@@ -73,7 +79,7 @@
</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>
+ <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> and more 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>
@@ -88,7 +94,7 @@
<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>
+ <p><img src="images/seampreferences.png"/></p>
</tr>
<tr>
<td colspan="2"><hr />
17 years, 2 months
JBoss Tools SVN: r4890 - trunk/documentation/whatsnew/vpe/images.
by jbosstools-commits＠lists.jboss.org
Author: svasilyev
Date: 2007-11-13 12:37:15 -0500 (Tue, 13 Nov 2007)
New Revision: 4890
Modified:
trunk/documentation/whatsnew/vpe/images/richfaces_3_1_0.png
Log:
The screenshot with RichFaces was updated.
Modified: trunk/documentation/whatsnew/vpe/images/richfaces_3_1_0.png
===================================================================
(Binary files differ)
17 years, 2 months
JBoss Tools SVN: r4889 - in trunk/documentation/whatsnew/as: images and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: max.andersen(a)jboss.com
Date: 2007-11-13 12:34:13 -0500 (Tue, 13 Nov 2007)
New Revision: 4889
Added:
trunk/documentation/whatsnew/as/images/
trunk/documentation/whatsnew/as/images/elexceptionlinking.png
trunk/documentation/whatsnew/as/images/jmxconsole.png
trunk/documentation/whatsnew/as/images/serverdefaultarguments.png
trunk/documentation/whatsnew/as/images/serverpublishstate.png
Modified:
trunk/documentation/whatsnew/as/as-news-1.0.0.cr1.html
Log:
images for as whatsnew
Modified: trunk/documentation/whatsnew/as/as-news-1.0.0.cr1.html
===================================================================
--- trunk/documentation/whatsnew/as/as-news-1.0.0.cr1.html 2007-11-13 17:23:25 UTC (rev 4888)
+++ trunk/documentation/whatsnew/as/as-news-1.0.0.cr1.html 2007-11-13 17:34:13 UTC (rev 4889)
@@ -23,8 +23,10 @@
<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>
+ <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.
+
+<p><img src="images/jmxconsole.png"/></p></td>
+
</tr>
<tr>
<td colspan="2"><hr />
@@ -34,8 +36,10 @@
<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>
+ <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).
<p><img src="images/serverpublishstate.png"/></p>
+ </td>
+
</tr>
<tr>
Added: trunk/documentation/whatsnew/as/images/elexceptionlinking.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/as/images/elexceptionlinking.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/as/images/jmxconsole.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/as/images/jmxconsole.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/as/images/serverdefaultarguments.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/as/images/serverdefaultarguments.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/whatsnew/as/images/serverpublishstate.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/whatsnew/as/images/serverpublishstate.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
17 years, 2 months
JBoss Tools SVN: r4888 - trunk/jsf/docs/userguide/en.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2007-11-13 12:23:25 -0500 (Tue, 13 Nov 2007)
New Revision: 4888
Modified:
trunk/jsf/docs/userguide/en/master.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-298 JBossTools .Xml files names changed + pictures sorted into corresponding folders and named as "chapter_name_?"
Modified: trunk/jsf/docs/userguide/en/master.xml
===================================================================
--- trunk/jsf/docs/userguide/en/master.xml 2007-11-13 17:23:16 UTC (rev 4887)
+++ trunk/jsf/docs/userguide/en/master.xml 2007-11-13 17:23:25 UTC (rev 4888)
@@ -2,34 +2,34 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN"
"../../resources/support/docbook-dtd/docbookx.dtd"
-[<!ENTITY AbouttheRHDS SYSTEM "modules/AbouttheRHDS.xml">
-<!ENTITY RoadmaptoLearnStudio SYSTEM "modules/RoadmaptoLearnStudio.xml">
-<!ENTITY JavaServerFacesSupport SYSTEM "modules/JavaServerFacesSupport.xml">
-<!ENTITY Struts SYSTEM "modules/Struts.xml">
+[<!ENTITY rhds SYSTEM "modules/rhds.xml">
+<!ENTITY roadmap SYSTEM "modules/roadmap.xml">
+<!ENTITY jsf_support SYSTEM "modules/jsf_support.xml">
+<!ENTITY struts SYSTEM "modules/struts.xml">
<!-- <!ENTITY HibernateTools SYSTEM "modules/HibernateTools.xml"> -->
<!-- <!ENTITY DeploymentandRunning SYSTEM "modules/DeploymentandRunning.xml"> -->
<!--<!ENTITY AddingCustomCapabilityFeaturesTemplates SYSTEM "modules/AddingCustomCapabilityFeaturesTemplates.xml">-->
-<!ENTITY JBossToolsPalette SYSTEM "modules/JBossToolsPalette.xml">
+<!ENTITY palette SYSTEM "modules/palette.xml">
-<!ENTITY WebProjectsView SYSTEM "modules/WebProjectsView.xml">
+<!ENTITY web_projects SYSTEM "modules/web_projects.xml">
<!-- <!ENTITY J2EEandOtherTools SYSTEM "modules/J2EEandOtherTools.xml"> -->
-<!ENTITY VisualPageEditor SYSTEM "modules/VisualPageEditor.xml">
-<!ENTITY VerificationandValidation SYSTEM "modules/VerificationandValidation.xml">
-<!ENTITY EditorsFeatures SYSTEM "modules/EditorsFeatures.xml">
+<!ENTITY visual_page SYSTEM "modules/visual_page.xml">
+<!ENTITY verif_valid SYSTEM "modules/verif_valid.xml">
+<!ENTITY editors_features SYSTEM "modules/editors_features.xml">
<!-- <!ENTITY DatabaseTools SYSTEM "modules/DatabaseTools.xml"> -->
-<!ENTITY VerificationandValidation SYSTEM "modules/VerificationandValidation.xml">
+<!ENTITY verif_valid SYSTEM "modules/verif_valid.xml">
-<!ENTITY VisualPageEditor SYSTEM "modules/VisualPageEditor.xml">
+<!ENTITY visual_page SYSTEM "modules/visual_page.xml">
-<!ENTITY MoreEditors SYSTEM "modules/MoreEditors.xml">
-<!ENTITY StudioPreferences SYSTEM "modules/StudioPreferences.xml">
-<!ENTITY FAQ SYSTEM "modules/FAQ.xml">
+<!ENTITY more_editors SYSTEM "modules/more_editors.xml">
+<!ENTITY preferences SYSTEM "modules/preferences.xml">
+<!ENTITY faq SYSTEM "modules/faq.xml">
]>
<book>
<bookinfo>
@@ -46,29 +46,29 @@
<toc/>
- &AbouttheRHDS;
- &RoadmaptoLearnStudio;
- &JavaServerFacesSupport;
- &Struts;
+ &rhds;
+ &roadmap;
+ &jsf_support;
+ &struts;
<!-- &HibernateTools; -->
<!--&AddingCustomCapabilityFeaturesTemplates; -->
<!-- &DeploymentandRunning; -->
- &JBossToolsPalette;
+ &palette;
- &WebProjectsView;
+ &web_projects;
<!-- &DatabaseTools;
&J2EEandOtherTools; -->
- &VerificationandValidation;
- &EditorsFeatures;
- &VisualPageEditor;
- &MoreEditors;
- &StudioPreferences;
- &FAQ;
+ &verif_valid;
+ &editors_features;
+ &visual_page;
+ &more_editors;
+ &preferences;
+ &faq;
</book>
17 years, 2 months
JBoss Tools SVN: r4887 - trunk/jsf/docs/userguide/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2007-11-13 12:23:16 -0500 (Tue, 13 Nov 2007)
New Revision: 4887
Added:
trunk/jsf/docs/userguide/en/modules/faq.xml
trunk/jsf/docs/userguide/en/modules/struts.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-298 JBossTools .Xml files names changed + pictures sorted into corresponding folders and named as "chapter_name_?"
Added: trunk/jsf/docs/userguide/en/modules/faq.xml
===================================================================
--- trunk/jsf/docs/userguide/en/modules/faq.xml (rev 0)
+++ trunk/jsf/docs/userguide/en/modules/faq.xml 2007-11-13 17:23:16 UTC (rev 4887)
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="faq">
+ <?dbhtml filename="faq.html"?>
+ <title>FAQ</title>
+ <para>If something still remains unclear after studying this guide you can always post your question on our <ulink url="http://jboss.com/index.html?module=bb&op=viewforum&f=258">forum</ulink>.</para>
+ <section id="faq_facelets">
+ <title>Facelets</title>
+ <para>Q: Could you give me more information on templates for the MyFaces JSF implementation?</para>
+ <para>A: Red Hat Developer Studio does not provide templates for MyFaces right out of the box, but you can easily do it
+ yourself with the "Save As Template" feature (available on the File submenu). Just create a small project
+ with MyFaces and Facelets and then save it as a template for future use.</para>
+
+ <para>Q: How can I add Facelets support to an existing project?</para>
+ <para>A: Right-click on the folder of existing project and select <emphasis>JBoss Tools > Add Custom Capabilities.. > Facelets</emphasis>. </para>
+ </section>
+ </chapter>
Added: trunk/jsf/docs/userguide/en/modules/struts.xml
===================================================================
--- trunk/jsf/docs/userguide/en/modules/struts.xml (rev 0)
+++ trunk/jsf/docs/userguide/en/modules/struts.xml 2007-11-13 17:23:16 UTC (rev 4887)
@@ -0,0 +1,734 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<chapter id="struts1" xreflabel="struts">
+ <?dbhtml filename="struts.html"?>
+<title>Struts</title>
+<para>If you prefer develop web applications using <property>Struts</property> technology Red Hat Developer Studio also meets your needs.</para>
+ <para>RHDS supports the Struts 1.1, 1.2.x versions.</para>
+
+<section id="SupportForStruts1.2.x1.1">
+<?dbhtml filename="SupportForStruts1.1.1.2.x.html"?>
+<title>Support for Struts 1.1, 1.2.x</title>
+
+
+<para>When you create a brand new or import an existing project you can set which Struts version to use:</para>
+<figure>
+<title>Choosing Struts Environment</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_1.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</section>
+<section id="WorkingWithStrutsProjects866">
+<?dbhtml filename="WorkingWithStrutsProjects.html"?>
+<title>Working with Projects</title>
+<section id="CreatingANewStrutsProjec745t">
+<?dbhtml filename="CreatingANewStrutsProject.html"?>
+<title>Creating a New Struts Project</title>
+
+<para>Red Hat Developer Studio provides the following when working with Struts.</para>
+
+<itemizedlist>
+ <listitem><para>Create new <property>Struts projects</property></para></listitem>
+<listitem><para>Import (open) existing Struts projects</para>
+ <para>You can import any project structure</para>
+</listitem>
+ <listitem><para>Add <property>Struts capabilities</property> to any existing Eclipse project</para></listitem>
+<listitem><para>Import and add Struts capabilities to any existing project created outside Eclipse</para></listitem>
+</itemizedlist>
+<para>Red Hat Developer Studio includes a New Struts Project Wizard that radically simplifies the process
+for getting started with a new Struts project. You just need to follow these 4 steps:</para>
+<orderedlist>
+ <listitem><para>Select<emphasis><property> File > New > Project...</property></emphasis> from the menu bar. Then, select <emphasis><property>JBoss Tools Web > Struts > Struts Project</property></emphasis> in this dialog box. Click <emphasis><property>Next</property></emphasis>:</para></listitem>
+</orderedlist>
+<figure>
+<title>Selecting Struts Wizard</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_2.png"/>
+ </imageobject>
+ </mediaobject>
+</figure>
+ <orderedlist continuation="continues">
+ <listitem><para>On this screen, provide the project name. You can leave all other values as they are:</para></listitem>
+</orderedlist>
+
+<figure>
+<title>Creating Struts Project</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<tip><title>Tip:</title><para>Don't put spaces in project names.</para></tip>
+<note>
+ <title>Note:</title>
+ <para>If you select the KickStart template, then the project created will include a simple Hello
+ World type application that is ready-to-run.</para>
+ </note>
+<orderedlist continuation="continues">
+<listitem><para>Next, you can register this application with the current servlet container defined for your
+workspace (JBoss AS, by default) in order to allow you to test your application more easily while still
+ developing it. A new entry will be added in the servlet container configuration file to enable running
+ the application in-place (called null deployment or link deployment). Uncheck the <emphasis role="italic"><property>"Target Server"</property></emphasis>
+ check box if for some reason you don't want to register your application at this point.</para></listitem>
+</orderedlist>
+<figure><title>Registering The Project at Server</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_4.png"/>
+ </imageobject>
+ </mediaobject>
+</figure>
+<orderedlist continuation="continues">
+<listitem><para>On the next screen, you can select the TLD files to include in this project:</para></listitem>
+</orderedlist>
+<figure><title>Selecting Tag Libraries</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_5.png"/>
+ </imageobject>
+ </mediaobject>
+</figure>
+
+<para>After the project is created, you should have the following project structure (if you used the
+KickStart template):</para>
+
+<figure>
+<title>Project Structure</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<tip><title>Tip:</title><para>If you want to hide the jar files from Web App Libraries in view, select the down-pointing
+arrow in the upper right corner, select <emphasis>Filters...</emphasis>, check the box next to Name filter patterns (matching names will be hidden), and type *.jar into the field. Then, click OK. </para></tip>
+</section>
+<section id="ImportingAnExistingStrutsProjectWithAnyStructure9653">
+<?dbhtml filename="ImportingAnExistingStrutsProjectWithAnyStructure.html"?>
+<title>Importing an Existing Struts Project with Any Structure</title>
+
+ <para>For detailed information on migration projects to Red Hat Developer Studio see <ulink url="http://www.redhat.com/developers/rhds/Exadel_Studio_Single/">Migration Guide</ulink>.</para>
+
+ </section>
+ <section id="AddingStrutsCapabilityToAnExistingWebApplication532">
+ <?dbhtml filename="AddingStrutsCapabilityToAnExistingWebApplication.html"?>
+<title>Adding Struts Capability to an Existing Web Application</title>
+
+ <para>With Red Hat Developer Studio you can add <property>Struts capabilities</property> (including Struts libraries, tag libraries and a Struts configuration file) to any existing Web application project in your Eclipse workspace. By adding a
+ Struts Nature to your project, you can now edit files using Red Hat Developer Studio editors, such as the Struts
+ configuration editor and the JBoss Tools JSP editor.</para>
+<para>Right-click the project and select <emphasis><property>JBoss Tools > Add Struts Capabilities</property></emphasis> from the context menu. This will start the process of adding all necessary libraries and files to make this a Web JSF project.</para>
+
+<figure>
+<title>Adding Struts Capabilities</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_7.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+<para>The wizard will first show you the web.xml file location and the project name.</para>
+
+<figure>
+<title>Choosing Project Location</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_8.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+ <para>After hitting <emphasis><property>Next</property></emphasis>, you will see the following screen. This screen simply means that you need to add
+at least one Struts module to your project to make this project a Struts project. Adding a Struts module
+means that a new struts-config.xml will be added to your project and registered in the web.xml file. In
+addition, all required Struts libraries will be added. To add a Struts module, select the <emphasis><property>Add Struts Support</property></emphasis> button.</para>
+<figure>
+<title>Project Modules</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_9.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+<para>Here you can select what Struts version, Servlet class, URL pattern and TLDs to add to this project.</para>
+
+<figure>
+<title>Selecting Struts Support Options</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_10.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+<para>When done, you will see the default Struts module configuration information. See how to Edit
+<link linkend="SupportForMultipleStrutsModules75">Struts modules</link>.</para>
+
+<figure>
+<title>Project Configuration Information</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_11.png" />
+ </imageobject>
+</mediaobject>
+</figure>
+
+<para>On the last screen you can set the different folders for your project as well as register this
+application with a servlet container.</para>
+
+<figure>
+<title>Registering the Project at Server</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_12.png" />
+ </imageobject>
+</mediaobject>
+</figure>
+
+<para>When done, you can open the struts-config.xml file. (The Struts configuration is shown below in the
+Tree viewer).</para>
+
+<figure>
+<title>Struts-config.xml File</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_13.png" />
+ </imageobject>
+</mediaobject>
+</figure>
+</section>
+</section>
+<section id="GraphicalEditorForStrutsConfigurationFiles564">
+<?dbhtml filename="GraphicalEditorForStrutsConfigurationFiles.html"?>
+<title>Graphical Editor for Struts Configuration Files</title>
+
+<para><property>The Struts configuration file editor</property> has three main viewers (modes): Diagram (shown), Tree and Source. The modes can be selected via the tabs at the bottom of the editor. Any changes made in one mode are
+ immediately visible when you switch to any other mode.</para>
+
+<para>When working in Source view, you always have all the following features available:</para>
+<itemizedlist>
+<listitem><para>Content Assist</para></listitem>
+<listitem><para>Open On Selection</para></listitem>
+<listitem><para>File Folding</para></listitem>
+</itemizedlist>
+<section id="StrutsDiagramMode453">
+<?dbhtml filename="DiagramMode.html"?>
+<title>Diagram Mode</title>
+
+<para>The Diagram mode graphically displays the Web flow of the application defined in the Struts
+configuration file.</para>
+
+<figure>
+<title>Diagram Mode</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_14.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>Just by right-clicking anywhere on the diagram, you can use a context menu to create the building
+ blocks of a Struts application:</para>
+<itemizedlist>
+<listitem><para>Actions</para></listitem>
+<listitem><para>Global forwards</para></listitem>
+<listitem><para>Global exceptions</para></listitem>
+<listitem><para>JSP Pages</para></listitem>
+</itemizedlist>
+
+<figure><title>Diagram Context Menu</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_15.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>Along the upper-left side of the editor is a stack of seven icons for changing the behavior of the
+cursor in the diagram. The first icon switches to the default regular selection cursor, the second to the
+ marquee selection cursor and the third to the new connection cursor. The last four icons switch the cursor
+ to an insert cursor for each type of Struts build block listed above (and in the order listed).</para>
+
+<para>For instance, clicking on the first of these four icons (the one with the gears) will switch the
+cursor to insert actions. Clicking anywhere in the diagram with this cursor has the same effect as
+right-click and selecting <emphasis><property>Add > Action...</property></emphasis> from the context menu with the regular cursor active. It's just more efficient to use this cursor if you're adding more than one action at once.</para>
+
+<figure><title>Insert Actions Cursor</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_16.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="StrutsTreeMode42">
+ <?dbhtml filename="TreeMode.html"?>
+<title>Tree Mode</title>
+
+<para>In the Tree mode, the different elements of the Struts application are organized into functional
+ categories on the left-hand side and a form for editing the properties of currently selected items on
+ the right-hand side.</para>
+
+<figure><title>Tree Mode</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_17.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>You can also right-click on any node in the category tree and perform appropriate operations through
+ a context menu. For instance, by right-clicking on the action-mappings category node, you can add new
+ actions to the application.</para>
+
+<figure><title>Tree Context Menu</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_18.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="StrutsSourceMode9655">
+ <?dbhtml filename="SourceMode.html"?>
+<title>Source Mode</title>
+
+<para>In the Source mode, you have complete editing control of the underlying XML coding:</para>
+
+<figure>
+<title>Source Mode</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_19.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>You can take advantage of code assist:</para>
+
+<figure><title>Code Assist</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_20.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>The editor will also immediately flag any errors:</para>
+
+<figure>
+<title>Errors in Source Mode</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_21.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>Finally, you can use the Outline view with the editor to easily navigate through the file:</para>
+
+<figure><title>Outline View</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_22.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+</section>
+</section>
+
+<section id="GraphicalEditorForTilesFiles132">
+<?dbhtml filename="GraphicalEditorForTilesFiles.html"?>
+<title>Graphical Editor for Tiles Files</title>
+
+<para><property>The Tiles configuration file editor</property> has three main viewers (modes): Tree (shown), Diagram and
+Source. The modes can be selected via the tabs at the bottom of the editor. Any changes made in one mode
+ are immediately visible when you switch to any other mode.</para>
+
+<para>When working in Source view, you always have all following features available:</para>
+<itemizedlist>
+<listitem><para>Content Assist</para></listitem>
+<listitem><para>Open On Selection</para></listitem>
+</itemizedlist>
+<section id="CreateNewTilesFile1422">
+<?dbhtml filename="CreateNewTilesFile.html"?>
+<title>Create New Tiles File</title>
+
+<para>To create a new Tiles files, right click any folder and select <emphasis><property>New > Tiles File</property></emphasis>.</para>
+<figure><title>Creating a New Tiles File</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_23.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="StrutsTreeView896">
+<?dbhtml filename="TreeView.html"?>
+<title>Tree View</title>
+
+<para>In the Tree mode, the different elements of the Tiles file are organized into functional
+categories on the left-hand side and a form for editing the properties of currently selected items on
+the right-hand side.</para>
+<figure><title>Tree View</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_24.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>To edit the file, simply right click any node and select among the available actions:</para>
+<figure>
+<title>Editing in Tiles Editor</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_25.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+</section>
+<section id="StrutsDiagramView4643">
+<?dbhtml filename="DigramView.html"?>
+<title>Diagram View</title>
+
+<para>The Diagram mode is shown below:</para>
+<figure>
+<title>Diagram Mode</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_26.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>To create new definitions, simply right click anywhere in the diagram:</para>
+<figure>
+<title>Creating New Definition</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_27.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>You can also use the Diagram toolbar to make editing easier:</para>
+<figure>
+<title>Diagram Toolbar</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_28.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+</section>
+<section id="StrutsSource75">
+<?dbhtml filename="Source.html"?>
+<title>Source</title>
+
+<para><property>The Tiles</property> editor also comes with a Source view that gives you full control over the source. Any
+ changes here will immediately appear in other viewers when you switch to them.</para>
+<figure>
+<title>Source View</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_29.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+<para>Content assist is available in the Source mode:</para>
+<figure>
+<title>Content Assist in Source Mode</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_30.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+<para>Any errors are immediately reported as shown below:</para>
+<figure>
+<title>Errors Reporting</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_31.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>You can also use the Outline view together with the editor's Source mode. Selecting any node in
+ the Outline view will jump to that place in the source.</para>
+<figure>
+<title>Outline View</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_32.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+</section>
+</section>
+<section id="GraphicalEditorForStrutsValidationFiles86">
+<?dbhtml filename="GraphicalEditorForStrutsValidationFiles.html"?>
+<title>Graphical Editor for Struts Validation Files</title>
+
+<para>Red Hat Developer Studio comes with a <property>visual validation editor</property>. To create a new validation file,
+ right click any folder and select <emphasis><property>File > Validation File</property></emphasis> from the context menu.</para>
+<figure>
+<title>Creating New Validation File</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_33.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+<para>The validation editor works through a number of viewers.</para>
+<para>The Formsets viewer shows forms and their elements for which to define validation rules.</para>
+<figure>
+<title>Formsets Viewer</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_34.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+<para>The Constants viewer lets you set constant values for your validation rules.</para>
+<figure>
+<title>Constansts Viewer</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_35.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+<para>The validation file also can be viewed in a Tree viewer.</para>
+<figure>
+<title>Tree Viewer</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_36.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+<para>At any point you have full control over the source by switching to the Source viewer. Any editing
+ in this viewer will immediately be available in other viewers of this editor.</para>
+<figure>
+<title>Source Viewer</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_37.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+
+<para>You can also open your own custom or Struts-standard validation-rules.xml file.</para>
+<para>The Validators viewer shows the validation rules for a selected validator. You can of course add
+your own rules.</para>
+<figure>
+<title>Validators Viewer</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_38.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>Here are the validation rules shown in the Source viewer.</para>
+<figure>
+<title>Validation Rules</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_39.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</section>
+<section id="SupportForMultipleStrutsModules75">
+<?dbhtml filename="SupportForMultipleStrutsModules.html"?>
+<title>Support for Multiple Struts Modules</title>
+<section id="StrutsModulesghf07">
+<?dbhtml filename="StrutsModules.html"?>
+<title>Struts Modules</title>
+<para>Red Hat Developer Studio supports working with Struts projects that have multiple <property>modules</property>. You can easily do the following:</para>
+<itemizedlist>
+<listitem><para>Add new modules</para></listitem>
+<listitem><para>Edit modules for an existing project or during Struts project import</para></listitem>
+</itemizedlist>
+</section>
+<section id="WhenImportingAStrutsProject432">
+<?dbhtml filename="WhenImportingAStrutsProject.html"?>
+<title>When Importing a Struts Project</title>
+
+<para>During Struts project import, if the project has multiple modules, you will see a screen with all
+ existing modules. You can select each module and edit its details.</para>
+
+<figure>
+<title>Configuring Project Modules</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_40.png" />
+ </imageobject>
+</mediaobject>
+</figure>
+</section>
+<section id="EditingModulesInAnExistingProject1">
+<?dbhtml filename="EditingModulesInAnExistingProject.html"?>
+<title>Editing Modules in an Existing Project</title>
+<para>To edit modules in an existing project, right click the project and select
+<emphasis><property>JBoss Tools > Modules Configuration</property></emphasis>.</para>
+<figure>
+<title>Choosing Modules Configuration</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_41.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<para>You will see the same screen as above where you will be able to select a module and edit its details:</para>
+<figure>
+<title>Modules Configuration</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_42.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</section>
+<section id="AddingNewModules1">
+<?dbhtml filename="AddingMewModules.html"?>
+<title>Adding New Modules</title>
+
+<para>Adding a new module is very simple. First switch to Web Project view. Expand your project to
+ the Configuration folder. Under that folder you should see the current modules. Right click on Configuration
+ and select <emphasis><property>New > Struts Config</property></emphasis>.</para>
+ <figure>
+ <title>Adding New Modules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_43.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>You will see the screen below. You can specify a new module name and also
+ add the new Struts configuration file to web.xml file.</para>
+<figure>
+<title>Adding New Modules</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_44.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+</section>
+</section>
+<section id="CodeGenerationForActionFormBeanForwardAndExceptionClasses1">
+<?dbhtml filename="CodeGenerationForActionFormBeanForwardAndExceptionClasses.html"?>
+<title>Code Generation for Action, FormBean, Forward and Exception Classes</title>
+
+<para>Red Hat Developer Studio comes with a <property>code generation</property> feature. You can generate stub code for
+ Struts Actions, FormBeans, Forwards and Exceptions.</para>
+
+ <para>The code generation in Red Hat Developer Studio is based on Velocity templates which can be modified for your use. The templates are located at <emphasis><property> {RedHatDeveloperStudioHome} > templates > codegeneration</property> </emphasis>.</para>
+
+<para>There are a number of ways to invoke code generation. One is simply right-clicking the Struts
+ diagram and selecting <emphasis><property>Generate Java Code....</property></emphasis></para>
+
+<figure><title>Selecting Generate Java Code</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_45.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>On this screen you can select for which elements to generate code. If you select Next you will be
+ able to specify more options for each of the categories you selected.</para>
+
+<figure>
+<title>Generate - Step 1</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_46.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<tip><title>Tip:</title><para>please be careful not to override your existing files.</para></tip>
+
+<para>When generation is complete, a result window will appear letting you know how many classes were
+generated:</para>
+
+<figure>
+<title>Generation Finished</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_47.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>You don't always have to generate code for all elements at once. You can invoke generation
+ for just an individual Struts artifact as well. Right-click an element on the diagram of the Struts
+ configuration file and select <emphasis><property>Generate Java Code...</property></emphasis> from the context menu.</para>
+
+<figure>
+<title>Generation For Individual Struts Artifact</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_48.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+<para>The same can be done from within the Tree viewer for the editor of the Struts configuration file.</para>
+
+<figure>
+<title>Generation in Struts Config Editor</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_49.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+</section>
+<section id="StrutsConfigurationFileDebugger097">
+<?dbhtml filename="StrutsConfigurationFileDebugger.html"?>
+<title>Struts Configuration File Debugger</title>
+
+<para>Red Hat Developer Studio comes with <property>Struts configuration file debugger</property>. It allows you to set break points on Struts diagram and then simply launch the server in debug mode.</para>
+
+ <para>Simply right click an Action or a page and select Add <emphasis><property>Breakpoint</property></emphasis>. </para>
+<figure>
+<title>Adding Breakpoint</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_50.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+<section id="CustomizablePageLinksRecognizer1">
+ <?dbhtml filename="CustomizablePageLinksRecognizer.html"?>
+<title>Customizable Page Links Recognizer</title>
+
+<para><property>Custom page links</property> allow you to define custom Struts page links that will be recognizable in the
+ Struts application diagram. You can define these links by selecting <emphasis><property>Window > Preferences</property></emphasis> from the menu bar and then selecting <emphasis><property>JBoss Tools > Web > Struts > Customization</property></emphasis> from the Preferences dialog box.</para>
+ <figure>
+<title>Customization Panel</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_51.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+</section>
+</chapter>
17 years, 2 months