JBoss Tools SVN: r20794 - trunk/hibernatetools/plugins/org.hibernate.eclipse.jdt.ui/src/org/hibernate/eclipse/jdt/ui/wizards.
by jbosstools-commits＠lists.jboss.org
Author: dgeraskov
Date: 2010-03-12 04:29:13 -0500 (Fri, 12 Mar 2010)
New Revision: 20794
Modified:
trunk/hibernatetools/plugins/org.hibernate.eclipse.jdt.ui/src/org/hibernate/eclipse/jdt/ui/wizards/ConfigurationActor.java
Log:
https://jira.jboss.org/jira/browse/JBIDE-6040
enum property mapping added
Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse.jdt.ui/src/org/hibernate/eclipse/jdt/ui/wizards/ConfigurationActor.java
===================================================================
--- trunk/hibernatetools/plugins/org.hibernate.eclipse.jdt.ui/src/org/hibernate/eclipse/jdt/ui/wizards/ConfigurationActor.java 2010-03-12 08:27:19 UTC (rev 20793)
+++ trunk/hibernatetools/plugins/org.hibernate.eclipse.jdt.ui/src/org/hibernate/eclipse/jdt/ui/wizards/ConfigurationActor.java 2010-03-12 09:29:13 UTC (rev 20794)
@@ -16,6 +16,7 @@
import java.util.Iterator;
import java.util.List;
import java.util.Map;
+import java.util.Properties;
import java.util.Set;
import java.util.Map.Entry;
@@ -561,6 +562,13 @@
((IndexedCollection)value).setIndex(map_key);
}
prop.setCascade("none");//$NON-NLS-1$
+ } else if (tb.isEnum()){
+ value = buildSimpleValue(org.hibernate.type.EnumType.class.getName());
+ Properties typeParameters = new Properties();
+ typeParameters.put(org.hibernate.type.EnumType.ENUM, tb.getBinaryName());
+ typeParameters.put(org.hibernate.type.EnumType.TYPE, java.sql.Types.VARCHAR);
+ ((SimpleValue)value).setTypeParameters(typeParameters);
+ buildProperty(value);
} else if (ref != null){
ToOne sValue = null;
if (ref.refType == RefType.MANY2ONE){
14 years, 3 months
- 1
- 0
JBoss Tools SVN: r20793 - trunk/common/plugins/org.jboss.tools.common.text.ext/src/org/jboss/tools/common/text/ext/hyperlink.
by jbosstools-commits＠lists.jboss.org
Author: dazarov
Date: 2010-03-12 03:27:19 -0500 (Fri, 12 Mar 2010)
New Revision: 20793
Modified:
trunk/common/plugins/org.jboss.tools.common.text.ext/src/org/jboss/tools/common/text/ext/hyperlink/HyperlinkPartitionerDefinition.java
Log:
https://jira.jboss.org/jira/browse/JBIDE-5986
Modified: trunk/common/plugins/org.jboss.tools.common.text.ext/src/org/jboss/tools/common/text/ext/hyperlink/HyperlinkPartitionerDefinition.java
===================================================================
--- trunk/common/plugins/org.jboss.tools.common.text.ext/src/org/jboss/tools/common/text/ext/hyperlink/HyperlinkPartitionerDefinition.java 2010-03-12 08:13:29 UTC (rev 20792)
+++ trunk/common/plugins/org.jboss.tools.common.text.ext/src/org/jboss/tools/common/text/ext/hyperlink/HyperlinkPartitionerDefinition.java 2010-03-12 08:27:19 UTC (rev 20793)
@@ -376,7 +376,7 @@
return false;
}
} else {
- int currentIndex = path.indexOf(fDelimitedPathElements[i]);
+ int currentIndex = path.lastIndexOf(fDelimitedPathElements[i]);
if(currentIndex>-1 && currentIndex>lastIndex) {
lastIndex = currentIndex;
if(fDelimitedPathElements[i].startsWith(TAGLIB))
14 years, 3 months
- 1
- 0
JBoss Tools SVN: r20792 - in trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor: mozilla and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: yradtsevich
Date: 2010-03-12 03:13:29 -0500 (Fri, 12 Mar 2010)
New Revision: 20792
Modified:
trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/VpeEditorPart.java
trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/MozillaEditor.java
trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/XulRunnerEditor2.java
trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/XulRunnerPreview.java
Log:
https://jira.jboss.org/jira/browse/JBIDE-5042
Enhance DnD support in VPE
VPE Refactoring in progress.
- double initialization of VpeController has been replaced by single initialization.
- MozillaEditor tooltip- and resize- listeners have been separated.
Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/VpeEditorPart.java
===================================================================
--- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/VpeEditorPart.java 2010-03-12 02:24:37 UTC (rev 20791)
+++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/VpeEditorPart.java 2010-03-12 08:13:29 UTC (rev 20792)
@@ -874,11 +874,11 @@
visualEditor.setEditorLoadWindowListener(new EditorLoadWindowListener() {
public void load() {
visualEditor.setEditorLoadWindowListener(null);
- visualEditor.setController(new VpeController(
- VpeEditorPart.this));
- selectionBar.setVpeController(visualEditor.getController());
- visualEditor.getController().setSelectionBarController(selectionBar);
- visualEditor.getController().init(sourceEditor, visualEditor);
+ VpeController vpeController = new VpeController(
+ VpeEditorPart.this);
+ selectionBar.setVpeController(vpeController);
+ vpeController.setSelectionBarController(selectionBar);
+ vpeController.init(sourceEditor, visualEditor);
}
});
Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/MozillaEditor.java
===================================================================
--- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/MozillaEditor.java 2010-03-12 02:24:37 UTC (rev 20791)
+++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/MozillaEditor.java 2010-03-12 08:13:29 UTC (rev 20792)
@@ -63,6 +63,8 @@
import org.jboss.tools.vpe.editor.VpeController;
import org.jboss.tools.vpe.editor.mozilla.listener.MozillaEventListener;
import org.jboss.tools.vpe.editor.mozilla.listener.EditorLoadWindowListener;
+import org.jboss.tools.vpe.editor.mozilla.listener.MozillaResizeListener;
+import org.jboss.tools.vpe.editor.mozilla.listener.MozillaTooltipListener;
import org.jboss.tools.vpe.editor.preferences.VpeEditorPreferencesPage;
import org.jboss.tools.vpe.editor.toolbar.IVpeToolBarManager;
import org.jboss.tools.vpe.editor.toolbar.VpeDropDownMenu;
@@ -1097,7 +1099,11 @@
showSelectionBarAction.setChecked(checked);
}
- public MozillaEventListener getEditorDomEventListener() {
+ public MozillaResizeListener getResizeListener() {
return mozillaEventListener;
}
+
+ public MozillaTooltipListener getTooltipListener() {
+ return mozillaEventListener;
+ }
}
Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/XulRunnerEditor2.java
===================================================================
--- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/XulRunnerEditor2.java 2010-03-12 02:24:37 UTC (rev 20791)
+++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/XulRunnerEditor2.java 2010-03-12 08:13:29 UTC (rev 20792)
@@ -41,18 +41,18 @@
}
public void onElementResize(nsIDOMElement element, int constrains, int top, int left, int width, int height) {
- if (mozillaEditor != null && mozillaEditor.getEditorDomEventListener() != null) {
- mozillaEditor.getEditorDomEventListener().elementResized(element, constrains, top, left, width, height);
+ if (mozillaEditor != null && mozillaEditor.getResizeListener() != null) {
+ mozillaEditor.getResizeListener().elementResized(element, constrains, top, left, width, height);
}
}
public void onShowTooltip(int x, int y, String text) {
- if (mozillaEditor != null && mozillaEditor.getEditorDomEventListener() != null) {
- mozillaEditor.getEditorDomEventListener().onShowTooltip(x, y, text);
+ if (mozillaEditor != null && mozillaEditor.getTooltipListener() != null) {
+ mozillaEditor.getTooltipListener().onShowTooltip(x, y, text);
}
}
public void onHideTooltip() {
- if (mozillaEditor != null && mozillaEditor.getEditorDomEventListener() != null) {
- mozillaEditor.getEditorDomEventListener().onHideTooltip();
+ if (mozillaEditor != null && mozillaEditor.getTooltipListener() != null) {
+ mozillaEditor.getTooltipListener().onHideTooltip();
}
}
public void onDispose() {
Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/XulRunnerPreview.java
===================================================================
--- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/XulRunnerPreview.java 2010-03-12 02:24:37 UTC (rev 20791)
+++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/mozilla/XulRunnerPreview.java 2010-03-12 08:13:29 UTC (rev 20792)
@@ -29,13 +29,13 @@
}
public void onShowTooltip(int x, int y, String text) {
- if (mozillaPreview != null && mozillaPreview.getEditorDomEventListener() != null) {
- mozillaPreview.getEditorDomEventListener().onShowTooltip(x, y, text);
+ if (mozillaPreview != null && mozillaPreview.getTooltipListener() != null) {
+ mozillaPreview.getTooltipListener().onShowTooltip(x, y, text);
}
}
public void onHideTooltip() {
- if (mozillaPreview != null && mozillaPreview.getEditorDomEventListener() != null) {
- mozillaPreview.getEditorDomEventListener().onHideTooltip();
+ if (mozillaPreview != null && mozillaPreview.getTooltipListener() != null) {
+ mozillaPreview.getTooltipListener().onHideTooltip();
}
}
14 years, 3 months
- 1
- 0
JBoss Tools SVN: r20791 - in trunk/download.jboss.org/jbosstools: builds and 2 other directories.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2010-03-11 21:24:37 -0500 (Thu, 11 Mar 2010)
New Revision: 20791
Modified:
trunk/download.jboss.org/jbosstools/builds/index.html
trunk/download.jboss.org/jbosstools/examples/index.html
trunk/download.jboss.org/jbosstools/index.html
trunk/download.jboss.org/jbosstools/updates/index.html
Log:
fix link to banner image
Modified: trunk/download.jboss.org/jbosstools/builds/index.html
===================================================================
--- trunk/download.jboss.org/jbosstools/builds/index.html 2010-03-12 01:23:54 UTC (rev 20790)
+++ trunk/download.jboss.org/jbosstools/builds/index.html 2010-03-12 02:24:37 UTC (rev 20791)
@@ -10,7 +10,7 @@
cellspacing="0" cellpadding="0">
<tr>
<td colspan="2"><a href="https://www.jboss.org/tools"><img
- src="http://www.jboss.org/theme/images/banners/tools-banner.png" border="0"/></a></td>
+ src="https://www.jboss.org/dms/tools/images/tools-banner.png" border="0"/></a></td>
</tr>
<tr>
<td>  </td>
Modified: trunk/download.jboss.org/jbosstools/examples/index.html
===================================================================
--- trunk/download.jboss.org/jbosstools/examples/index.html 2010-03-12 01:23:54 UTC (rev 20790)
+++ trunk/download.jboss.org/jbosstools/examples/index.html 2010-03-12 02:24:37 UTC (rev 20791)
@@ -10,7 +10,7 @@
cellspacing="0" cellpadding="0">
<tr>
<td colspan="2"><img
- src="http://www.jboss.org/theme/images/banners/tools-banner.png" /></td>
+ src="https://www.jboss.org/dms/tools/images/tools-banner.png" /></td>
</tr>
<tr>
<td>  </td>
Modified: trunk/download.jboss.org/jbosstools/index.html
===================================================================
--- trunk/download.jboss.org/jbosstools/index.html 2010-03-12 01:23:54 UTC (rev 20790)
+++ trunk/download.jboss.org/jbosstools/index.html 2010-03-12 02:24:37 UTC (rev 20791)
@@ -10,7 +10,7 @@
cellspacing="0" cellpadding="0">
<tr>
<td colspan="2"><img
- src="http://www.jboss.org/theme/images/banners/tools-banner.png" /></td>
+ src="https://www.jboss.org/dms/tools/images/tools-banner.png" /></td>
</tr>
<tr>
<td>  </td>
Modified: trunk/download.jboss.org/jbosstools/updates/index.html
===================================================================
--- trunk/download.jboss.org/jbosstools/updates/index.html 2010-03-12 01:23:54 UTC (rev 20790)
+++ trunk/download.jboss.org/jbosstools/updates/index.html 2010-03-12 02:24:37 UTC (rev 20791)
@@ -10,7 +10,7 @@
cellspacing="0" cellpadding="0">
<tr>
<td colspan="2"><img
- src="http://www.jboss.org/theme/images/banners/tools-banner.png" /></td>
+ src="https://www.jboss.org/dms/tools/images/tools-banner.png" /></td>
</tr>
<tr>
<td>  </td>
14 years, 3 months
- 1
- 0
JBoss Tools SVN: r20790 - in branches/jbosstools-3.1.x/documentation/guides: JBDS_Release_Notes and 1 other directories.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-11 20:23:54 -0500 (Thu, 11 Mar 2010)
New Revision: 20790
Added:
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Component_Versions.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/New_Features.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.ent
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Revision_History.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/images/
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/master.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/pom.xml
branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/publican.cfg
Removed:
branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/
Log:
changed directory name as per Max's instructions
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,3 @@
+<?xml version='1.0' encoding='utf-8' ?>
+
+<articleinfo><title>Release Notes</title><subtitle>Information about the changes made for this release of the JBoss Developer Studio.</subtitle><productname>JBoss Developer Studio</productname><productnumber>3.0</productnumber><edition>0</edition><pubsnumber>0</pubsnumber><abstract><para>These release notes contain important information related to the JBoss Developer Studio. New features,<!-- known problems,--> resources, and other current issues are addressed here.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></articleinfo>
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.xml (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.xml 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<authorgroup><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author></authorgroup>
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Component_Versions.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Component_Versions.xml (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Component_Versions.xml 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,29 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<section id="Component_Versions">
+ <title>Component Versions</title>
+ <para>
+ This section details the versions of the components which create the JBoss Developer Studio that can be found in this release.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Eclipse 3.5 (Galileo)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Tools 3.1.0
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Enterprise Application Platform 5.0
+ </para>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <para>
+ The Enterprise Application Platform Server has been redefined for the enterprise market to a level where direct association to a community release can no longer be drawn.
+ </para>
+ </note>
+</section>
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,975 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<section id="Issues-fixed-in-this-release">
+ <title>
+ Features added and issues fixed in this release
+ </title>
+
+ <para>
+ Following is a list of new and noteworthy features and bug fixes in this release:
+ </para>
+ <formalpara>
+ <title>Contexts and Dependency Injection (CDI)</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5770">JBIDE-5770</ulink>: The EL code completion icon has been updated to use the <application>JBoss Weld</application> icon.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5355">JBIDE-5355</ulink>: A Contexts and Dependency Injection Project Facet has been added to <application>JBoss Developer Studio</application>. This makes it possible to enable CDI support for a faceted project via the <guilabel>New Dynamic Web Project</guilabel> wizard or the <guilabel>Project Facets</guilabel> setting page available at <menuchoice><guimenuitem>Project</guimenuitem><guimenuitem>Properties</guimenuitem><guimenuitem>Project Facets</guimenuitem></menuchoice>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5276">JBIDE-5276</ulink>: The <guimenuitem>Add CDI Support</guimenuitem> and <guimenuitem>Remove CDI Support</guimenuitem> items have been added to the Project menu.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>ESB</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5653">JBIDE-5653</ulink>: The <guilabel>ESB Content Based Router </guilabel> dialog box has been modified so that the <guilabel>CBR Alias</guilabel> field is now mandatory, allowing the value of it to determine what other fields are available. The <guilabel>Rule Set</guilabel> field is now not required when a <guilabel>CBR Alias</guilabel> of Regex or XPath is provided, since with these alias the rules can be specified in-line and the <guilabel>Rule Language</guilabel> field is now set to apply only when the <guilabel>CBR Alias</guilabel> is Drools. The <guilabel>Rules Reload</guilabel> field will only apply when a <guilabel>Rule Set</guilabel> has been specified.
+ </para>
+ <para>
+ The table <guilabel>Route List</guilabel> found in the <guilabel>JBoss ESB Editor</guilabel> now lists the <emphasis>expression</emphasis> since this is a common undertaking by users.
+ </para>
+ <para>
+ In the <guilabel> Add Route To</guilabel> dialog box, the <guilabel>Service Category</guilabel> field has been made mandatory. Other changes to this dialog box include the <guilabel>Destination name</guilabel> only being required if the previous CBR action contained a <guilabel>Rule Set</guilabel> and if the CBR action did not contain a <guilabel>Rule Set</guilabel>, an <guilabel>Expression</guilabel> field is included.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5627">JBIDE-5627</ulink>: For this release of the <application>JBoss Developer Studio</application> variations of the <guilabel>Content Based Router</guilabel> menu have been added to the ESB editor for Drools, Drools XPath, Generic, XPath and Regex.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5548">JBIDE-5548</ulink>: In the ESB Configuration Editor, when selecting a JBR Listener, JBR Bus or JBR Provider, new functionality has been added to allow a user to configure the properties: <property>synchronous</property>, <property>serviceInvokerTimeout</property> and <property>asyncResponse</property> through the new child object <property>Config</property>. These new configurable properties allow a user increased control over the execution of the JBR components.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5547">JBIDE-5547</ulink>: In the ESB Configuration Editor, when selecting a FTP Listener in read-only mode new functionality has been added to allow a user to configure the properties: <property>maxNodes</property>, <property>timeToLiveSeconds</property> and <property>maxAgeSeconds</property> through the new child object <property>Cache</property>. In addition the following properties have been added to allow a user to select their own values for the: <property>Class</property>, <property>Config File</property> and <property>Cache Listener</property> available through the new child object <property>Remote Filesystem Strategy</property>. These new configurable properties allow a user increased control over the execution of the FTP Listener.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5489">JBIDE-5489</ulink>: For the <guilabel>BPMProcessor</guilabel> within the ESB Editor, the <property>Command</property> property has been modified to include possible values of <emphasis>NewProcessInstanceCommand</emphasis>, <emphasis>StartProcessCommand</emphasis> and <emphasis>CancelProcessInstanceCommand</emphasis> in a drop-down box.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5486">JBIDE-5486</ulink>: When a user would try to open an editor for a property that didn't exist nothing would occur. With this update, a <guilabel>New File</guilabel> wizard opens to guide the user through the creation of the property they were attempting to open. Once this is completed, the ESB Editor fields are then populated with the new file name and path for the property.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5427">JBIDE-5427</ulink>: In the ESB Editor, the items that displayed when right clicking and going to <menuchoice><guimenuitem>Provider</guimenuitem><guimenuitem>New</guimenuitem></menuchoice> were presented in a different order to those of the <menuchoice><guimenuitem>Listener</guimenuitem><guimenuitem>New</guimenuitem></menuchoice> list. To ensure consistency the <guimenuitem>Provider</guimenuitem> list of items has been reordered to match the <guimenuitem>Listener</guimenuitem> menu.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5229">JBIDE-5229</ulink>: ESB 4.7 that is contained within <application>JBoss SOA Platform 5.0</application> is now officially supported in this version of the <application>JBoss Developer Studio</application>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5191">JBIDE-5191</ulink>: The Smooks, Drools, jPDL, XSLT and Groovy editors have been linked to the ESB Editor, providing an improved user experience. <guibutton>Browse</guibutton> buttons that allow for file association and use have been added to the <property>Smooks Transformer</property>, <property>GroovyActionProcessor</property>, <property>Rule Set</property> and <property>Rule Language</property> properties.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5108">JBIDE-5108</ulink>: The JBoss Runtime Manager was setup to search for ESB Runtime files from a specified location regardless of how it was installed. This caused issue when the ESB Runtime was installed as a user defined runtime. The issue has been rectified by adding a <guilabel>Configuration</guilabel> field to the <guilabel>Preference</guilabel> page. If the user sets the <guilabel>Configuration</guilabel> field to the home location of the <application>JBoss Enterprise Application Platform</application> or <application>JBoss SOA Platform</application>, there configuration combination will list all available configurations. If the user selects a standalone ESB Runtime location, the configuration combination will be empty and the user should ignore the field. The ESB runtime classpath container now gathers configuration information from the selected server runtime and then selects JARs accordingly or the st!
andalone ESB Runtime.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4730">JBIDE-4730</ulink>: The ESB project creation wizard receives a new logo following this update. Instead of using the generic <application>JBoss Developer Studio</application> logo within the ESB project wizard, a new ESB wizard logo is displayed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4320">JBIDE-4320</ulink>: ESB projects are now Web Tools Platform (WTP) modules. This ensures that it is possible to use an ESB module inside a WAR or EAR archive within WTP. ESB project deployment has not been limited though and they can still be deployed as an individual module.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4168">JBIDE-4168</ulink>: The ability to select a directory using a browser window has been added for the FS Message Filter and the FTP Message filter attributes of <property>directory</property>, <property>post-directory</property> and <property>error-directory</property>. This added feature ensures that a user does not need to manually type the entire path to a directory but instead they just select the path from a browser.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2024">JBIDE-2024</ulink>: The <guilabel>Process</guilabel> field f the <guilabel>Action</guilabel> tab in the ESB now includes a <guibutton>Browse</guibutton> button that allows a user to select which method of the <classname>Action</classname> class should be used for the process. The list in the dialog will show all public methods that has a <property>Message</property> parameter. Multiple methods can be selected if necessary.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2023">JBIDE-2023</ulink>: The <guilabel>Class</guilabel> field of the <guilabel>Action</guilabel> tab now includes a <guibutton>Browse</guibutton> button that displays the possible classes that extend from the <classname>AbstractActionLifecycle</classname> class.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Hibernate</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5824">JBIDE-5824</ulink>: The <filename>reveng.xml</filename> editor provided an option to <guilabel>Exclude column from reverse engineering</guilabel>. Selecting this option did not change any functioning of the column and the specified option should not have been part of the interface. This update removes the unnecessary option as to not confuse users.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5643">JBIDE-5643</ulink>: Within the <guilabel>Hibernate</guilabel> tab of the <filename>persistence.xml</filename> editor, the button beside the <guilabel>Configuration file</guilabel> line was labeled <guibutton>Browse</guibutton>. This was misleading as upon clicking the button the user would be asked setup a configuration file. To provide an improved user experience, the button has now been altered to be called <guibutton>Setup</guibutton> and correctly guides the user through configuration file creation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5641">JBIDE-5641</ulink>: When specifying the persistence property: <property><property name="hibernate.ejb.cfgfile" value="hibernate.cfg.xml"/></property>, an error could display saying that the <filename>hibernate.cfg.xml</filename> file could not be found. This occurred because the validator only considered full paths and not relative path naming. This has since been corrected through the modification of the <classname>HibernatePersistenceUnit</classname> class.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5499">JBIDE-5499</ulink>: Refactoring support has been added to <guilabel>Hibernate Code Generation Configurations</guilabel>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5411">JBIDE-5411</ulink>: The <guilabel>New Hibernate XML Mapping file</guilabel> wizard used to show all available packages. This update ensures that only packages containing java classes are shown.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5408">JBIDE-5408</ulink>: Three issues are fixed:
+ <itemizedlist>
+ <listitem>
+ <para>
+ The new Hibernate XML Mapping file (<filename>hbm.xml</filename>) would rewrite all <filename>hbm.xml</filename> files without warning. To correct this the entire result is written into the systems' temporary directory and then the merge of results is conducted.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ After the merge of results is conducted, clicking the <guibutton>Finish without Preview</guibutton> button should change the page, however this did not work. The <guibutton>Finish without Preview</guibutton> now works as expected.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ After the merge, following the button clicks <guibutton>GoTo</guibutton>, <guibutton>Next</guibutton>, <guibutton>Back</guibutton> and then <guibutton>Finish</guibutton> would not work correctly. This method of steps now functions as users would expect.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5222">JBIDE-5222</ulink>: A new feature as been added that allows for support of <guilabel>filter configurations in closed projects</guilabel> for console configuration. This option is available through <menuchoice><guimenuitem>Preferences</guimenuitem><guimenuitem>Run/Debug</guimenuitem><guimenuitem>Launching</guimenuitem><guimenuitem>Launch Configurations</guimenuitem></menuchoice>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5124">JBIDE-5124</ulink>: In the Hibernate Diagram Viewer new functionality has been added that allows a user to choose between two different connection routers: Manhattan connection router for small diagrams and Fan connection router for larger diagrams.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5031">JBIDE-5031</ulink>: To close a database connection a user would have to close the <application>JBoss Developer Studio</application> and then restart the application to continue work without the connection. The database connection can now be closed from within the <application>JBoss Developer Studio</application> by choosing the <guimenuitem>Close Configuration</guimenuitem> menu item from the right-click menu in <guilabel>Hibernate Configurations</guilabel> tab.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4956">JBIDE-4956</ulink>: A feature has been added to the <guilabel>Mapping Diagram</guilabel> viewer so that it now displays relationships between database tables.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4916">JBIDE-4916</ulink>: An editor for the <filename>hibernate.properties</filename> file has been added to the <application>JBoss Developer Studio</application>. The editor supports content assist authoring.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4899">JBIDE-4899</ulink>: The <guilabel>Hibernate Configurations</guilabel> view was not updated after a hibernate console enabled project with console configuration was deleted from the workspace. This meant that the console configuration was not removed along with the project. This bug is rectified with this update.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4780">JBIDE-4780</ulink>: The <guilabel>Options</guilabel> tab now allows you to browse and set the <property>NamingStrategy</property> and <property>EntityResolver</property>. The console configuration option has also been updated to react when one of the packages of a referenced class changes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4733">JBIDE-4733</ulink>: A new feature has been added that allows a user to select wheather JPA-Generate DDL should be executed in the database. Before this update this feature was automatic, always executing JPA-Generate in the database.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4715">JBIDE-4715</ulink>: A toggle button has been added to the Hibernate Mapping diagram to allow the outline view to be ordered either alphabetically or by the structure outlined in the file. The toggle button interface ensures the experience remains consistent across all tools included within the <application>JBoss Developer Studio</application>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4666">JBIDE-4662</ulink>: Annotations support has been added to Hibernate Tools. The addition of annotations support allows for interaction with the Eclipse Dali Java Persistence Tools Project plug-in.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4451">JBIDE-4451</ulink>: The option is now given to the user to enable the <guilabel>HQL Editor</guilabel> and <guilabel>Hibernate Criteria Editor</guilabel> to be dynamically updated when opening a new query instead of opening an instance of each editor for each query. This can be achieved by clicking the button of a tack to the right of the <guilabel>Max results:</guilabel> drop-won box in the editor.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4450">JBIDE-4450</ulink>: The <guilabel>Properties</guilabel> view has been updated with a new property called <property>Tab name</property>. The addition of this property allows for a user to individually name each query tab, allowing for improved tab management.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4227">JBIDE-4227</ulink>: The <guimenuitem>Open Mapping File</guimenuitem> option now supports all possible configuration files. In the past only files called <filename>orm.xml</filename> have been supported and this update now provides increased user functionality.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JavaServer Faces (JSF)</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5670">JBIDE-5670</ulink>: The <filename>faceleted-taglib</filename> tag library was not supported in <filename>*taglib.xml</filename> with XML Schema Definition (XSD). Support for this library has been added to this release of the <application>JBoss Developers Studio</application>, allowing for support of <application>JavaServer Faces 2</application>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5660">JBIDE-5660</ulink>: When setting the location of an <property><error-page></property> within <filename>web.xml</filename>, the location would not be recognized if it included a query string. For example the location <filename>views/error/error.xhtml</filename> would be valid, whereas the location <filename>/views/error/error.xhtml?statusCode=403</filename> would not be valid. This has been corrected by adding a test for a query string into the <filename>CheckResource.java</filename> file, allowing for locations to be specified that include a query string.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5471">JBIDE-5471</ulink>: <filename>web-facesconfig_2_0.xsd</filename> support has been added to the <guilabel>JavaServer Faces Configuration</guilabel> editor. This file provides the XML Schema for the JavaServer Faces Application Configuration File Version 2.0.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5381">JBIDE-5381</ulink>: Content Assist has been added for use with the elements defined using the default namespace.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5277">JBIDE-5277</ulink>: The options to Add and Remove JSF support have been added to the project menu.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5670">JBIDE-5237</ulink>: CSS Class Hyperlink for the <property>class</property> attribute of HTML tags would not search through CSS loaded using JSF tags (for example: <a:loadStyle />). This has now been fixed so that the searching of CSS classes returns the correct user expected results.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5099">JBIDE-5099</ulink>: OpenOn support has been added for custom JSF 2.0 components.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5097">JBIDE-5097</ulink>: Content Assist did not support multiple namespaces with the same Uniform Resource Identifier (URI).This issue has been fixed by modifying <classname>XmlContextImpl</classname> class within the <filename>XmlContextImpl.java</filename> file from: <code>nameSpaces.get(region).put(nameSpace.getURI(), nameSpace);</code> to <code>nameSpaces.get(region).put(nameSpace.getPrefix(), nameSpace);</code>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5089">JBIDE-5089</ulink>: JSF Expression Language (EL) validation has been added for message bundles. This improves the performance of the <classname>PageContextFactory</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5015">JBIDE-5015</ulink>: Support for JSF 2.0 composition components has been added in this update.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4978">JBIDE-4978</ulink>: JSF has been upgraded with the addition of Seam Expression Language (EL) support. This now allows for JSF EL validation to use all available EL resolvers, providing increased validation over past releases.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4978">JBIDE-4970</ulink>: <application>KBbuilder</application> now loads composite components from the JSF resource folders and adds them to the KB module. This allows for the components to be available for code assistance.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4771">JBIDE-4771</ulink>: The <property>Find Usages</property> function has been improved to provide information about methods when inside an EL expression.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2806">JBIDE-2806</ulink>: The Eclipse OpenOn feature that allows a user to click any reference to a template as if it was a hyperlink did not work if the template path was set using an EL variable. This limitation has now been corrected so that OpenOn works with all paths, including those set using the EL variable. This is a great advantage to users as the Expression Language variable is a frequently used feature.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-816">JBIDE-816</ulink>: A bug existed within the JSF component of the <application>JBoss Developer Studio</application> where if a resource bundle is defined in a template page code completion for the bundle would not be available within the file that includes the template with the loadbundles. The workaround for this was to also define the resource bundle in this template client file, however that meant the same component was defined twice in the component tree.
+ </para>
+ <para>
+ The bug has since been fixed by adding a schema for included page contexts. This schema enables the creation of contexts for all the pages included in the source and for the gathering of information on bundles declared in the included pages. The information collected is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Namespaces that are declared
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Tag libraries that are used
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Resource bundles that are declared
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-512">JBIDE-512</ulink>: The drop-down box for context variable code completion has been upgraded for enhanced usability. The source of the variable is now outlined during code completion and the code is highlighted in a different colour for improved reading and overall understanding of each file.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>RichFaces</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5743">JBIDE-5743</ulink>: Content assistance in coding did not show anything for the tag <property><rich:menuItem ... icon="|" /></property>. The content assistance has been corrected by adding the <property>icon</property> attribute to the <filename>RichFaces.xml</filename> tag library.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5025">JBIDE-5025</ulink>: The RichFaces libraries have been updated to version 3.3.2.SR1.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Seam</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5275">JBIDE-5275</ulink>: The <guimenuitem>Add Seam Support</guimenuitem> and <guimenuitem>Remove Seam Support</guimenuitem> items have been added to the Project menu.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5221">JBIDE-5221</ulink>: The <guilabel>JBoss Server View</guilabel> has now been replaced with the <guilabel>Server View</guilabel> in the Seam perspective. This has occurred out of the <guilabel>JBoss Server View</guilabel> being deprecated.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5192">JBIDE-5192</ulink>: The name of the editor when using the <guilabel>Diagram Viewer</guilabel> was a concatenation of the names of the diagram entities, leading to a long name in some cases. This issue has been corrected by modifying the <filename>OrmDiagram.java</filename> and <filename>DiagramViewer.java</filename> files to display a name from the following three options (based on the number of entities):
+ <itemizedlist>
+ <listitem>
+ <para>
+ Console name: Entity name
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Console name: First Entity name and Second Entity name
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Console name: First Entity name and <number of other entities> others
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5170">JBIDE-5170</ulink>: When changing, adding or removing a Seam runtime from within <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>JBoss Tools</guimenuitem><guimenuitem>Web</guimenuitem><guimenuitem>Seam</guimenuitem></menuchoice>, Seam projects would not be built or validated. The behavior has been changed to build and validate Seam projects upon changes in the <guimenuitem>Preferences</guimenuitem> section to ensure correct functioning of the project. The <filename>SeamRuntimeManager.java</filename> file was updated to correct this.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5012">JBIDE-5012</ulink>: The Booking and DVDStore Seam examples have been updated for Seam 2.2 within the <application>JBoss Enterprise Application Platform</application>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4987">JBIDE-4987</ulink>: Seam and JPA Connection Profiles have been synchronized for this release. The <filename>jpa-connection</filename> profile is used in the launch configuration instead of <filename>hibernate.properties</filename> if the JPA facet is installed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4985">JBIDE-4985</ulink>: Seam projects now create a Hibernate configuration that uses the selected connection profile directly (without copying its settings into the <filename>hibernate.properties</filename> file).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4944">JBIDE-4944</ulink>: The Seam wizards <guilabel>Action</guilabel>, <guilabel>Entity</guilabel> and <guilabel>Conversation</guilabel> had the ability to overwrite resources when they generated code. The wizards would warn the user that some resources already existed and yet overwrite them. This has been corrected through the modification of the <filename>SeamBaseOperation.java</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4856">JBIDE-4856</ulink>: Seam component methods and properties used in the Expression Language (EL) have been refactored. This has caused the internal structure of the components to be modified so that the <classname>Query Participant</classname> works with the JDT Java Search to find usages and append them to search results. The <classname>Rename Participant</classname> has also been modified to work with the JDT Java Refactor to rename usages and apply changes to the Java Refactor, allowing for a user to rename a <emphasis>setter</emphasis> or <emphasis>getter</emphasis> method and have the <classname>Rename Participant</classname> warn the user of the consequences of renaming a paired method.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4136">JBIDE-4136</ulink>: Classloading issues were being faced by users of Seam Tools because the <application>JBoss Developer Studio</application> used the <filename>MANIFEST.MF</filename> file for creating an artifact classpath instead of using the EAR <filename>lib/</filename> directory that is recommended by Seam. Until now the <application>JBoss Developer Studio</application> has not been able to use the EAR <filename>lib/</filename> directory because this functionality has not been supported by Eclipse. With the introduction of Eclipse 3.5 in this release the use of the EAR <filename>lib/</filename> directory is now supported and the process of creating an artifact classpath has been updated.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2807">JBIDE-2807</ulink>: An option is now provided when creating a <guilabel>New Seam Project</guilabel>, to not create a test project. This has become an option since the Seam model does not require the test project to exist and so allows the user to decide if it is of importance. Selecting to create or not create a test project is achieved through the ticking of a <guilabel>Create Test Project</guilabel> check box within the <guilabel>New Seam Project</guilabel> wizard.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-1452">JBIDE-1452</ulink>: Support has been added for the Seam PDF Facelet tag library. This Facelet library allows for PDF creation from within Seam.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-1451">JBIDE-1451</ulink>: Support has been added for the Seam Mail Facelet tag library. This Facelet library allows for email forms to be created from within Seam. All components of the Facelet have been included except <property>mail:message</property> and <property>mail:body</property> as these components are rendered as divisions (using the <div> tag).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-1176">JBIDE-1176</ulink>: The Seam Web Project now supports the JPA facet. Addition of the Java Persistence API allows for the management of relational data within applications.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Smooks</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5275">JBIDE-5259</ulink>: The Smooks configuration has received a test facility through the modification of the <guibutton>Run</guibutton> button to output a java result to the <guilabel>Console</guilabel>. This allows a user to test Smooks projects in a simplified way.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5088">JBIDE-5088</ulink>: When opening an existing Smooks configuration file it wouldn't contain any process information. To correct this an input task is automatically created and the Smooks configuration file is analyzed to add any missing task types if necessary. During the course of this update a <exceptionname>NullPointerException</exceptionname> was also fixed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5086">JBIDE-5086</ulink>: A default layout is added in the Java-Mapping viewer. This allows for the layout of the information in the Smooks editor to be rearranged into a predefined default layout.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4878">JBIDE-4878</ulink>: The Smooks <guilabel>Reader</guilabel> page has been replaced with a new <guilabel>Input</guilabel> page. While the <guilabel>Input</guilabel> page inherits many functions from the <guilabel>Reader</guilabel> page there are some differences as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The <guilabel>Reader</guilabel> page allowed for multiple Readers to be created. <guilabel>Input</guilabel> page only allows for one Reader.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <guilabel>Reader</guilabel> page supported the addition of multiple input data , where each was usable. The <guilabel>Input</guilabel> page only allows for one piece of input data to be used, while still allowing for multiple pieces of input data.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <guilabel>Reader</guilabel> page could view the transformation results of the Reader. The new <guilabel>Input</guilabel> page utilizes an input model view to check the transform result.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Struts</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5278">JBIDE-5278</ulink>: The options to Add and Remove Struts support have been added to the project menu.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Visual Page Editor</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5184">JBIDE-5184</ulink>: A memory leak existed in the Visual Page Editor. To fix this leak, the following plug-ins have been modified:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>org.jboss.tools.vpe</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>org.jboss.tools.vpe.xulrunner</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>org.jboss.tools.jst.jsp</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ The issues that caused the memory leak were:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>JSPMultiPageEditorSite</emphasis>: The constructor created the <classname>serviceLocator</classname> that wasn't disposed of after use.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <methodname>XulRunnerBrowser.dispose()</methodname> method would remove the <classname>progressListener</classname>, however this would only be done after all SWT objects and controls were already disposed. This meant the method had no effect. The dispose method is now called before the SWT objects and controls are disposed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <methodname>MozillaEditor.getEditor()</methodname> madethe Mozilla window editable using <methodname>nsIEditingSession.setupEditorOnWindow()</methodname>. To counteract this the objects created are now removed by using <methodname>nsIEditingSession.tearDownEditorOnWindow()</methodname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <methodname>createPartControl()</methodname> method in the <classname>MozillaEditor</classname> and <classname>MozillaPreview</classname> classes create <classname>XullRunnerEditor</classname> as an inner class. The issue was that the <classname>XullRunnerEditor</classname> class retained a reference to <classname>MozillaEditor(MozillaPreview)</classname> that caused it not to be released and instead retain references to WST and EMF classes. This has now been corrected so that <classname>MozillaEditor(MozillaPreview)</classname> is now released after use and references are not retained.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5100">JBIDE-5100</ulink>: Support for JSF 2.0 attributes have been added to the Visual Page Editor.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5091">JBIDE-5091</ulink>: Support for JSF 2.0 Composition components that come packaged into the Web Application Root has been added to the Visual Page Editor.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5065">JBIDE-5065</ulink>: The icons in the Visual Page Editor have been redesigned for improved aesthetic appearance.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4945">JBIDE-4945</ulink>: A new feature has been added to the Visual Page Editor that allows a user to select both the element before and the element after a central element. This has been achieved through the modification of the <filename>SelectionBar.java</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4934">JBIDE-4934</ulink>: Facelets tag library support has been added to the <guilabel>Palette</guilabel> for the Visual Page Editor.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4914">JBIDE-4914</ulink>: The Visual Page Editor has been redesigned so that all drop-down menu items are placed in the toolbar as buttons.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4323">JBIDE-4323</ulink>: Zoom actions have been added to the visual context menu so that a user can now resize the content of the Visual Page Editor to make it easier to read and manage.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2820">JBIDE-2820</ulink>: Support for new JSF 2.0 elements has been added to the Visual Page Editor. The tags that are newly supported are:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ h:head
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ h:body
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ h:outputscript
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ h:outputstyle
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ h:button
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ h:link
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:ajax
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:event
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:validateBean
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:validateRequired
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:viewParam
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f:metadata
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2571">JBIDE-2571</ulink>: Selection of the <property><h:selectOneMenu></property> did not function correctly. Instead of being selected with one mouse click, two clicks were necessary. A bug was also present that made the nested components <property><f:selectItem></property> and <property><f:selectItems></property> unable to be selected from within the Visual Page Editor. Correction of the two clicks necessary to select the <property><h:selectOneMenu></property> component has been completed by removing the check within <filename>VpeController.java</filename> that ensures the node is of type text. The issue that did not allow for the selection of the <property><f:selectItem></property> and <property><f:selectItems></property> components was found to be a bug in XULRunner. To correct this the XULRunner component has been updated to version 1.9, which corrects this error and provides!
numerous other small bug fixes (<ulink url="http://jira.jboss.com/jira/browse/JBIDE-2248">JBIDE-2248</ulink>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2248">JBIDE-2248</ulink>: The XULRunner component has been upgraded to version 1.9. This new version of XULRunner adds support for the newest HTML and CSS features to the Visual Page Editor. Included in this is support for CSS3.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-1592">JBIDE-1592</ulink>: A new feature has been added that allows for Facelets tag libraries from <filename>file.jar/META-INF/*.tablib.xml</filename> or those that are registered within <filename>web.xml</filename> by the <filename>facelets.LIBRARIES</filename> context parameter to now be used within content assist for source editing in the Visual Page Editor.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-527">JBIDE-527</ulink>: A bug existed within the Visual Page Editor that inhibited the <guibutton>Previous</guibutton> and <guibutton>Next</guibutton> buttons for detected occurrences of searched annotations to not function correctly. The action of these buttons has now been corrected so that a user can navigate their way through all found occurrences of a searched annotation. This functionality works in the Visual Page Editor as it would work in a text editor.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>XHTML Editor</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4946">JBIDE-4946</ulink>: Tool tips for tags and attributes in the XHTML Editor have been added.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>XML Structured Editor</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5521">JBIDE-5521</ulink>: The Web Servlet Mapping dialog box now contains a drop-down list for the <guilabel>Servlet-Name</guilabel> field so that servlets that have been entered into the <filename>web.xml</filename> file can be selected easily.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5426">JBIDE-5426</ulink>: The Servlet Mapping Editor <guilabel>Servlet-Name</guilabel> field has been improved with a drop-down menu to fill it in.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>General Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5743">JBIDE-5743</ulink>: The Web Servlet Mapping dialog box now contains a drop-down list for the <guilabel>Servlet-Name</guilabel> field so that servlets that have been entered into the <filename>web.xml</filename> file can be selected easily.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5734">JBIDE-5734</ulink>: The shortcut keys for full publishing a project to the server and building a full archive have been combined under then shortcut key menu accessed with <keycombo><keycap>Alt</keycap><keycap>Shift</keycap><keycap>Y</keycap></keycombo>. From this menu press <keycap>F</keycap> to full publish the project or <keycap>B</keycap> to build the full archive.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5690">JBIDE-5690</ulink>: The <guibutton>Full-Publish</guibutton> hotkey would only accept the first module and re-deploy it to the first server the module is deployed on. For the user this meant that if the module was already deployed on several servers, using <guibutton>Full-Publish</guibutton> would only re-deploy it to the first server returned in the list. To solve this issue a user interface has been added for the <guibutton>Full-Publish</guibutton> hotkey that allows for the selection of the server to re-deploy to. During the implementation of this fix, the package has been renamed to XPL.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2541">JBIDE-5383</ulink>: Expression Language Code Assistance has been added for the <property>@Name</property> beans. This allows for users to begin typing code and for suggestions of automatic completion to be suggested, improving user efficiency.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5743">JBIDE-5267</ulink>: The <application>JBoss Enterprise Application Platform</application> server would start correctly, however the <application>JBoss Developer Studio</application> would not acknowledge that it had started. To counteract this the <filename>JMXPoller.java</filename> timeout behavior has been modified to always return that the server succeeded in starting instead of ignoring the timeout. This fix ensures that a user is not informed that the server did not start correctly when it did.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5153">JBIDE-5153</ulink>: A <guilabel>JavaMain</guilabel> tab has been added to the tab group to allow for customization of the main class of the server. The changes to the main class are verified to persist by server startup checks.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5122">JBIDE-5122</ulink>: <guilabel>JBoss Servers View</guilabel> has been removed with this release. All the functionality provided by this view can be found in the <guilabel>Servers View</guilabel>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5048">JBIDE-5048</ulink>: SSH deployment has been added to the <application>JBoss Developer Studio</application> with this update. Specifically the following improvements have been made:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ A server type has been created that accepts SSH deployment for Eclipse Web Tools Platform (WTP) archives
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ WTP, single-file and project archives can now be published
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Java Secure Channel (JSch) errors are now verified
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ All situations return IStatus objects and their associated user interface (an IStatus object represents the outcome of an operation)
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5041">JBIDE-5041</ulink>: The <keycap>menu</keycap> key on the keyboard would not work in the <guilabel>Web Projects</guilabel> view, <guilabel>Seam Components</guilabel> view or JBoss Tools XML Editor. The functioning of this key has now been corrected so it behaves as a user would expect.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5005">JBIDE-5005</ulink>: A new export wizard has been added to the <application>JBoss Developer Studio</application>. The new wizard allows the export operation to utilize IModule objects. This added feature reduces redundancy and inconsistency for the export operation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4976">JBIDE-4976</ulink>: The <guilabel>JBoss Tools Palette</guilabel> has been intergrated into the standard Eclipse GEF <guilabel>Palette</guilabel> view. The standard <guilabel>Palette</guilabel> view, accessible at <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Others</guimenuitem><guimenuitem>General</guimenuitem><guimenuitem>Palette</guimenuitem></menuchoice> is now shown in the right top part of the <guilabel>Web Development</guilabel> and <guilabel>Seam</guilabel> perspectives. The <guilabel>JBoss Tools Palette</guilabel> remains at <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Others</guimenuitem><guimenuitem>JBoss Tools Web</guimenuitem><guimenuitem>JBoss Tools Palette</guimenuitem></menuchoice>.
+ </para>
+ <para>
+ The differences in behavior between the palettes are:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The new <guilabel>Palette</guilabel> is filled only when the <guilabel>Visual Page Editor</guilabel> is open and activated. The old palette remains static.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The expanded and collapsed state of tabs in the new palette is associated with the opened instance of the <guilabel>Visual Page Editor</guilabel> and not globally set as they were in the old palette. This allows for the state of tabs to be different for individual files. Each new file opened in the <guilabel>Visual Page Editor</guilabel> will have the default <guilabel>Palette</guilabel> state with all tabs collapsed.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Though the behavior of the new palette is standard for Eclipse, for customers used to the globally set state of tabs and perfer to customize the palette before opening the <guilabel>Visual Page Editor</guilabel>, the old palette will remain accessible.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4955">JBIDE-4955</ulink>: BPEL and ESB projects can now be excluded from deployment through the addition of new fileset capability. When the fileset is referenced the includes, excludes and root folder layout is implemented just as it is for archives.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4922">JBIDE-4922</ulink>: Seam and RichFaces portletbridge archetypes have been added to the <application>JBoss Developer Studio</application> foruse with the Maven plug-in <application>m2eclipse</application>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4888">JBIDE-4888</ulink>: The portlet facets configuration utility has been added for m2eclipse. This configuration utility allows for the following:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ If the <filename>pom.xml</filename> file contains a <property>portlet-api</property> dependency, the JBoss Core Portlet facet is added.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If the <filename>pom.xml</filename> file contains portletbridge dependencies, the JBoss JSF Portlet facet is added.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If the project contains Seam, JBoss Core Portlet and JBoss JSF Portlet facet, the JBoss Seam Portlet facet is added.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4877">JBIDE-4877</ulink>: Tag completion has been upgraded so that partial matches are displayed and selectable following direct tag matches.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4850">JBIDE-4850</ulink>: A new feature has been added to the CSS Views with this release that allows a user to edit styles inside HTML and xhtm.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4690">JBIDE-4690</ulink>: The Maven Portlet library provider has been added to the <application>JBoss Developer Studio</application> with this release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4689">JBIDE-4689</ulink>: The portlet libraries engine has been updated to use the WTP 3.1 Library Framework. This framework is implemented in the Portlet Core and JSF Portlet installation page. The following library providers are now available to the user:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Library provider:
+ </para>
+ <itemizedlist>
+ <listitem>
+
+ <para>
+ User Library
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ Library provided by Target Runtime
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ Disable Library Configuration
+ </para> </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ Portlet Core Facet library providers:
+ </para>
+ <itemizedlist>
+ <listitem>
+
+ <para>
+ Portlet Target Runtime Provider
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ Maven Portlet 1.0 and 2.0 Libraries
+ </para> </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ JSF Portlet Facet library providers:
+ <itemizedlist>
+ <listitem>
+
+ <para>
+ JSF Portletbridge Runtime provider
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ JSF Portlet Target Runtime Provider
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ Maven Portletbridge 2.0.0 ALPHA Libraries
+ </para> </listitem>
+ <listitem>
+
+ <para>
+ Maven Portletbridge 2.0.0 ALPHA Libraries with dependencies
+ </para> </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-3563">JBIDE-3563</ulink>: Code assist has been added for classes that are defined in linked CSS. The schema for included page contexts has been added. This has occurred as it is needed to create the contexts for all the pages included in the source. It allows for the gathering of information on bundles declared in included pages.
+ </para>
+ <para>
+ The included page contexts are created and the following information is collected within the included contexts:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Namespaces are declared within the included pages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Tag libraries are used in the included pages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Resource bundles are declared within the included pages
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-3125">JBIDE-3125</ulink>: Exadel OpenOn support has been added to the code editors. This new functionality allows for a user to open a file that is being referenced within the code, in a new editor window. Related CDI Beans will also appear from a search of references to an object within the code, allowing for a user to quickly see where else an object is referenced.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2541">JBIDE-2541</ulink>: A new feature has been added to this release that allows for the JavaDoc documentation to be available for the EL proposals as it is for Java methods. The JavaDoc comments are also available if they originated from a projects source folders.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ </section>
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,36 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<section id="Known_Issues_with_this_release">
+ <title>
+ Known Issues with this release
+ </title>
+ <para>
+ Following is a list of known issues at the time of release.
+ </para>
+ <formalpara>
+ <title>General Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-3623">JBIDE-3623</ulink>: If you use the community Seam versions 2.1.0.SP1 or 2.1.1 TestNG for WAR projects they will fail with the error <errorname>Two components with the same name and precedence</errorname>. There is no known workaround, however all other Seam releases work correctly and all Seam 2.1 EAR projects are successful.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2700">JBIDE-2700</ulink>: The functionality of the <guilabel>Console</guilabel> view is dependant on the Debug-UI plug-in being loaded. Starting a server does not ensure the running of the Debug-UI plug-in and without it started the <guilabel>Console</guilabel> view will not show any output. When accessing the <guilabel>Console</guilabel> tab, if no data is shown, right-click with your mouse and select <menuchoice><guimenuitem>Show In</guimenuitem><guimenuitem>Console</guimenuitem></menuchoice>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-779">JBIDE-779</ulink>: Currently Facelet pages contain false warnings.This has occured due to Eclipse WTP's HTML Syntax Validation not allowing for Facelet specific attributes. These warnings can be stopped by disabling validation. To disable validation follow <menuchoice><guimenuitem>Windows</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>Validation</guimenuitem><guimenuitem>HTML Syntax Validation</guimenuitem></menuchoice> .
+ </para>
+ <caution>
+ <para>
+ Disabling validation has the potential to remove usefull warning information.
+ </para>
+ </caution>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+</section>
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/New_Features.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/New_Features.xml (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/New_Features.xml 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,7 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<section id="New_Features">
+ <title>New Features in JBoss Developer Studio 3.0</title>
+ <para>
+ New product information to go here
+ </para>
+</section>
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,50 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<section id="Overview">
+ <title>Overview</title>
+ <para>
+ JBoss Developer Studio provides an integrated development environment for developers to build rich Web and enterprise applications, and SOA services. The technologies used include:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Hibernate
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Seam
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ RichFaces
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss jBPM
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss ESB
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Portal
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Drools
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ JBoss Developer Studio includes both certified visual tooling and a runtime platform that Red Hat supports for 5 years, ensuring developers of a stable, upgradable, deployable and supportable platform.
+ </para>
+ <para>
+ JBoss Developer Studio is available for Windows, Linux and MacOS.
+ </para>
+ </section>
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.ent
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.ent (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.ent 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "JBoss Developer Studio">
+<!ENTITY BOOKID "Release_Notes">
+<!ENTITY YEAR "2009">
+<!ENTITY HOLDER "Red Hat">
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.xml (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.xml 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+
+<article>
+ <xi:include href="Article_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+ <xi:include href="Overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<!-- <xi:include href="New_Features.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> -->
+ <xi:include href="Component_Versions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+ <xi:include href="Fixed_Issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+ <xi:include href="Known_Issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+ <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+</article>
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Revision_History.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Revision_History.xml (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/Revision_History.xml 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,3 @@
+<?xml version='1.0' encoding='utf-8' ?>
+
+<appendix><title>Revision History</title><simpara><revhistory><revision><revnumber>0</revnumber><date>Mon Dec 21 2009</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix>
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/master.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/master.xml (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/en-US/master.xml 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3CR3/docbookx.dtd"
+
+[<!ENTITY Overview SYSTEM "Overview.xml">
+<!ENTITY NewFeatures SYSTEM "New_Features.xml">
+<!ENTITY ComponentVersions SYSTEM "Component_Versions.xml">
+<!ENTITY FixedIssues SYSTEM "Fixed_Issues.xml">
+<!ENTITY KnownIssues SYSTEM "Known_Issues.xml">
+]>
+
+<article>
+
+ <articleinfo>
+ <title>Release Notes</title>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata format="PNG" fileref="images/jbosstools_logo.png" />
+ </imageobject>
+ <imageobject role="html">
+ <imagedata/>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+
+ <author>
+ <firstname>Isaac</firstname>
+ <surname>Rooskov</surname>
+ <email>irooskov(a)redhat.com</email>
+ </author>
+ <copyright>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo>
+ Version: 1.0
+ </releaseinfo>
+<!--<abstract>
+ <title/>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/jboss_bpmn_convert_r...">PDF version</ulink>
+ </para>
+</abstract> -->
+
+
+ </articleinfo>
+
+ <toc/>
+ &Overview;
+ <!-- &NewFeatures; -->
+ &ComponentVersions;
+ &FixedIssues;
+<!-- &KnownIssues; -->
+
+</article>
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/pom.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/pom.xml (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/pom.xml 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,157 @@
+<project xmlns="http://maven.apache.org/POM/4.0.0"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+
+ <modelVersion>4.0.0</modelVersion>
+
+ <groupId>org.jboss.tools</groupId>
+ <artifactId>converter-ref-guide${translation}</artifactId>
+ <version>1.0-SNAPSHOT</version>
+ <packaging>jdocbook</packaging>
+ <name>Release_Notes</name>
+ <profiles>
+ <profile>
+ <id>release</id>
+ <properties>
+ <master>master_output.xml</master>
+ <xsl-single>classpath:/xslt/org/jboss/tools/xhtml-single-release.xsl</xsl-single>
+ <xsl-chunked>classpath:/xslt/org/jboss/tools/xhtml-release.xsl</xsl-chunked>
+ <xsl-pdf>classpath:/xslt/org/jboss/tools/pdf.xsl</xsl-pdf>
+ </properties>
+ </profile>
+ <profile>
+ <id>releaseJBDS</id>
+ <properties>
+ <master>master_output.xml</master>
+ <xsl-single>classpath:/xslt/com/jboss/tools/xhtml-single-release.xsl</xsl-single>
+ <xsl-chunked>classpath:/xslt/com/jboss/tools/xhtml-release.xsl</xsl-chunked>
+ <xsl-pdf>classpath:/xslt/com/jboss/tools/pdf.xsl</xsl-pdf>
+ <cssdir>../../../documentation/jbosstools-jdocbook-style/src/main/com/css/</cssdir>
+ </properties>
+ </profile>
+ <profile>
+ <id>diffmk</id>
+ <properties>
+ <master>master_output.xml</master>
+ <xsl-single>classpath:/xslt/org/jboss/tools/xhtml-single-diff.xsl</xsl-single>
+ <xsl-chunked>classpath:/xslt/org/jboss/tools/xhtml-diff.xsl</xsl-chunked>
+ <xsl-pdf>classpath:/xslt/org/jboss/tools/pdf-diff.xsl</xsl-pdf>
+ </properties>
+ </profile>
+ </profiles>
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.jboss.maven.plugins</groupId>
+ <artifactId>maven-jdocbook-plugin</artifactId>
+ <version>2.1.0-200803311251UTC-MPJDOCBOOK-8</version>
+ <extensions>true</extensions>
+ <dependencies>
+ <dependency>
+ <groupId>com.jboss</groupId>
+ <artifactId>jbossent-docbook-xslt</artifactId>
+ <version>1.0.0</version>
+ </dependency>
+ <dependency>
+ <groupId>com.jboss</groupId>
+ <artifactId>jbossent-jdocbook-style</artifactId>
+ <version>1.0.0</version>
+ <type>jdocbook-style</type>
+ </dependency>
+ <dependency>
+ <groupId>org.jboss</groupId>
+ <artifactId>jbossorg-docbook-xslt</artifactId>
+ <version>1.1.0</version>
+ </dependency>
+ <dependency>
+ <groupId>org.jboss</groupId>
+ <artifactId>jbossorg-jdocbook-style</artifactId>
+ <version>1.1.0</version>
+ <type>jdocbook-style</type>
+ </dependency>
+ <dependency>
+ <groupId>org.jboss.tools</groupId>
+ <artifactId>jbosstools-docbook-xslt</artifactId>
+ <version>1.0.0-SNAPSHOT</version>
+ </dependency>
+ <dependency>
+ <groupId>org.apache.xmlgraphics</groupId>
+ <artifactId>fop</artifactId>
+ <version>0.95</version>
+ </dependency>
+ </dependencies>
+
+ <configuration>
+ <sourceDocumentName>master.xml</sourceDocumentName>
+ <sourceDirectory>${pom.basedir}/en-US</sourceDirectory>
+ <imageResource>
+ <directory>${pom.basedir}/en-US</directory>
+ <includes>
+ <include>images/**/*</include>
+ </includes>
+ </imageResource>
+ <cssResource>
+ <directory>${pom.basedir}/${cssdir}</directory>
+ </cssResource>
+
+ <formats>
+ <format>
+ <formatName>pdf</formatName>
+ <stylesheetResource>${xsl-pdf}</stylesheetResource>
+ <finalName>${pom.name}.pdf</finalName>
+ </format>
+ <format>
+ <formatName>html</formatName>
+ <stylesheetResource>${xsl-chunked}</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+ <format>
+ <formatName>html_single</formatName>
+ <stylesheetResource>${xsl-single}</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+ <format>
+ <formatName>eclipse</formatName>
+ <stylesheetResource>file:${pom.basedir}/${stylesdir}/xslt/org/jboss/tools/eclipse.xsl</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+ </formats>
+
+ <options>
+ <xincludeSupported>true</xincludeSupported>
+ <xmlTransformerType>saxon</xmlTransformerType>
+ <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme -->
+ <!-- could also locate the docbook dependency and inspect its version... -->
+ <docbookVersion>1.72.0</docbookVersion>
+ </options>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
+
+ <distributionManagement>
+ <repository>
+ <!-- Copy the dist to the local checkout of the JBoss maven2 repo ${maven.repository.root} -->
+ <!-- It is anticipated that ${maven.repository.root} be set in user's settings.xml -->
+ <!-- todo : replace this with direct svn access once the svnkit providers are available -->
+ <id>repository.jboss.org</id>
+ <url>file://${maven.repository.root}</url>
+ </repository>
+ <snapshotRepository>
+ <id>snapshots.jboss.org</id>
+ <name>JBoss Snapshot Repository</name>
+ <url>dav:https://snapshots.jboss.org/maven2</url>
+ </snapshotRepository>
+ </distributionManagement>
+
+ <properties>
+ <stylesdir>../../../documentation/jbosstools-docbook-xslt/src/main/resources/</stylesdir>
+ <xsl-single>classpath:/xslt/org/jboss/tools/xhtml-single.xsl</xsl-single>
+ <xsl-chunked>classpath:/xslt/org/jboss/tools/xhtml.xsl</xsl-chunked>
+ <xsl-pdf>classpath:/xslt/org/jboss/tools/pdf.xsl</xsl-pdf>
+ <cssdir>../../../documentation/jbosstools-jdocbook-style/src/main/org/css/</cssdir>
+ <translation>en-US</translation>
+ </properties>
+
+
+</project>
Added: branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/publican.cfg
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/publican.cfg (rev 0)
+++ branches/jbosstools-3.1.x/documentation/guides/JBDS_Release_Notes/publican.cfg 2010-03-12 01:23:54 UTC (rev 20790)
@@ -0,0 +1,7 @@
+# Config::Simple 4.59
+# Mon Dec 21 12:14:29 2009
+
+xml_lang: en-US
+type: Article
+brand: JBoss
+
14 years, 3 months
- 1
- 0
JBoss Tools SVN: r20788 - in branches/jbosstools-3.1.x/ws/docs/reference: en-US and 4 other directories.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-11 20:08:20 -0500 (Thu, 11 Mar 2010)
New Revision: 20788
Added:
branches/jbosstools-3.1.x/ws/docs/reference/en-US/
branches/jbosstools-3.1.x/ws/docs/reference/en-US/Author_Group.xml
branches/jbosstools-3.1.x/ws/docs/reference/en-US/Book_Info.xml
branches/jbosstools-3.1.x/ws/docs/reference/en-US/JBoss_Web_Services_User_Guide.ent
branches/jbosstools-3.1.x/ws/docs/reference/en-US/JBoss_Web_Services_User_Guide.xml
branches/jbosstools-3.1.x/ws/docs/reference/en-US/Preface.xml
branches/jbosstools-3.1.x/ws/docs/reference/en-US/Revision_History.xml
branches/jbosstools-3.1.x/ws/docs/reference/en-US/client.xml
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client_1.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client_2.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client_3.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/jbosstools_logo.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/Jbossws_preference.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/Jbossws_preference_new.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/jbossws_container1.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/jbossws_container2.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/jbossws_server_runtime.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_1.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_2.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_3.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_4.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_5.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_6.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_facet.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_facet_0.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_newruntime.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_webproject_1.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_webproject_2.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_webproject_3.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_Impl_code_view.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_creation1.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_creation1_1.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_creation2.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_webxml.png
branches/jbosstools-3.1.x/ws/docs/reference/en-US/master.xml
branches/jbosstools-3.1.x/ws/docs/reference/en-US/master_output.xml
branches/jbosstools-3.1.x/ws/docs/reference/en-US/overview.xml
branches/jbosstools-3.1.x/ws/docs/reference/en-US/preference.xml
branches/jbosstools-3.1.x/ws/docs/reference/en-US/topdown.xml
branches/jbosstools-3.1.x/ws/docs/reference/publican.cfg
Removed:
branches/jbosstools-3.1.x/ws/docs/reference/en/
Modified:
branches/jbosstools-3.1.x/ws/docs/reference/pom.xml
Log:
updated to build with publican
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/Author_Group.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/Author_Group.xml (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/Author_Group.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,5 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<authorgroup><author><firstname>Denny</firstname><surname>Xu</surname><email>dxu(a)redhat.com</email></author>
+ <author><firstname>Grid</firstname><surname>Qian</surname><email>fqian(a)redhat.com</email></author></authorgroup>
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/Book_Info.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/Book_Info.xml (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/Book_Info.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<bookinfo><title>JBoss Web Services User Guide</title><subtitle>Provides information relating to the JBoss Web Services module.</subtitle><productname>JBoss Developer Studio</productname><productnumber>3.0</productnumber><edition>1.0</edition><pubsnumber>0</pubsnumber><abstract><para>The JBoss Web Services User Guide explains how to use the JBoss Web Services module to implement web services in Java.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/JBoss_Web_Services_User_Guide.ent
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/JBoss_Web_Services_User_Guide.ent (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/JBoss_Web_Services_User_Guide.ent 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "JBoss">
+<!ENTITY BOOKID "JBoss_Web_Services_User_Guide">
+<!ENTITY YEAR "2010">
+<!ENTITY HOLDER "Red Hat">
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/JBoss_Web_Services_User_Guide.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/JBoss_Web_Services_User_Guide.xml (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/JBoss_Web_Services_User_Guide.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,13 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<book>
+<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="topdown.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="client.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="preference.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<!--<xi:include href="webproject.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>-->
+<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+</book>
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/Preface.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/Preface.xml (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/Preface.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<preface><title>Preface</title><xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></xi:fallback></xi:include></preface>
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/Revision_History.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/Revision_History.xml (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/Revision_History.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<appendix><title>Revision History</title><simpara><revhistory><revision><revnumber>0</revnumber><date>Fri Nov 20 2009</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix>
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/client.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/client.xml (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/client.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="client" revisionflag="added">
+ <title>Creating a Web Service Client from a WSDL Document using JBoss WS</title>
+ <para>To create a Web Service Client from a WSDL Document using JBoss WS you need to fulfil the following steps:</para>
+ <para>Setup <link linkend="preference">JBoss WS and development environment</link>.</para>
+ <para><link linkend="createproject">Create a Dynamic Web project</link>.</para>
+ <para><link linkend="addfacet">Add JBossWS Facet to Web project</link>.</para>
+ <para>Then you can create a Web Service Client from a WSDL document: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Switch to the Java EE perspective <emphasis><property>Window > Open Perspective > Java EE</property></emphasis>.</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis><property>File > New > Other</property></emphasis>. Select Web Services in order to display the various Web service wizards. Select the Web Service Client wizard. Click on the <property>Next</property> button.</para>
+ <figure>
+ <title>New Web Service Client</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/client/jbossws_client.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>The first and the second Web Service Client wizard pages are the same as for <link linkend="topdownwebservice">Web Service from a WSDL document</link>.</para>
+ <figure>
+ <title>Set Web Service Common values</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/client/jbossws_client_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <figure>
+ <title>Set Web Service values related to WSDL file</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/client/jbossws_client_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The only difference is:</para>
+ <itemizedlist>
+ <listitem>
+ <para><property>Client Type:</property> Support of Java Proxy only.</para>
+ </listitem>
+ </itemizedlist>
+ <para>Click on the <property>Finish</property> button.</para>
+ </listitem>
+ </itemizedlist>
+ <para>After the Web Service Client has been created, the following may occur depending on the options you selected:</para>
+ <itemizedlist>
+ <listitem>
+ <para> the generated web service and client codes</para>
+ </listitem>
+ <listitem>
+ <para>a client sample class.</para>
+ <figure>
+ <title>Client Sample Class</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata scale="80" fileref="images/client/jbossws_client_3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>JBoss WS use a Java class to test Web Service. A client sample class will be generated, you may run this client as a java application to call a web service.</para>
+</chapter>
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/client/jbossws_client_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/jbosstools_logo.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/jbosstools_logo.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/Jbossws_preference.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/Jbossws_preference.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/Jbossws_preference_new.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/Jbossws_preference_new.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/jbossws_container1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/jbossws_container1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/jbossws_container2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/jbossws_container2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/jbossws_server_runtime.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/preference/jbossws_server_runtime.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_bottomup_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_facet.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_facet.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_facet_0.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_facet_0.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_newruntime.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_newruntime.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_webproject_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_webproject_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_webproject_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_webproject_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_webproject_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_webproject_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_Impl_code_view.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_Impl_code_view.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_creation1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_creation1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_creation1_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_creation1_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_creation2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_creation2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_webxml.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/ws/docs/reference/en-US/images/topdown/jbossws_ws_webxml.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/master.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/master.xml (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/master.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+[<!ENTITY overview SYSTEM "overview.xml">
+<!ENTITY topdown SYSTEM "topdown.xml">
+<!ENTITY preference SYSTEM "preference.xml">
+<!ENTITY webproject SYSTEM "webproject.xml">
+<!ENTITY client SYSTEM "client.xml">
+]>
+
+<book>
+
+ <bookinfo>
+ <title>JBoss Web Services User Guide</title>
+
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata format="PNG" fileref="images/jbosstools_logo.png" />
+ </imageobject>
+ <imageobject role="html">
+ <imagedata/>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author><firstname>Denny</firstname><surname>Xu</surname><email>dxu(a)redhat.com</email></author>
+ <author><firstname>Grid</firstname><surname>Qian</surname><email>fqian(a)redhat.com</email></author>
+
+ <copyright>
+ <year>2008</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo>
+ Version: 1.1.0.GA
+ </releaseinfo>
+<abstract>
+ <title/>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/ws_ref_guide/pdf/WS_...">PDF version</ulink>
+ </para>
+</abstract>
+
+
+ </bookinfo>
+
+ <toc/>
+ &overview;
+ &topdown;
+ &client;
+ &preference;
+</book>
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/master_output.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/master_output.xml (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/master_output.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,705 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+[<!ENTITY overview SYSTEM "modules/overview.xml">
+<!ENTITY topdown SYSTEM "modules/topdown.xml">
+<!ENTITY preference SYSTEM "modules/preference.xml">
+<!ENTITY webproject SYSTEM "modules/webproject.xml">
+<!ENTITY client SYSTEM "modules/client.xml">
+]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff">
+
+ <bookinfo>
+ <title>JBoss WS User Guide</title>
+
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
+ </imageobject>
+ <imageobject role="html">
+ <imagedata></imagedata>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author><firstname>Denny</firstname><surname>Xu</surname><email>dxu(a)redhat.com</email></author>
+ <author><firstname>Grid</firstname><surname>Qian</surname><email>fqian(a)redhat.com</email></author>
+
+ <copyright>
+ <year>2008</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo><diffmk:wrapper diffmk:change="changed">
+ Version: 1.1.0.GA
+ </diffmk:wrapper></releaseinfo>
+<abstract>
+ <title></title>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/ws_ref_guide/pdf/WS_...">PDF version</ulink>
+ </para>
+</abstract>
+
+
+ </bookinfo>
+
+ <toc></toc>
+
+<chapter id="overview" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/ws/docs/reference/en/modules/overview.xml">
+ <title>JBossWS Runtime Overview</title>
+
+ <para>JBossWS is a web service framework developed as a part of the JBoss Application Server. It implements the JAX-WS specification that defines a programming model and run-time architecture for implementing web services in Java, targeted at the Java Platform, Enterprise Edition 5 (Java EE 5).</para>
+ <para>JBossWS integrates with most current JBoss Application Server releases as well as earlier ones, that did implement the J2EE 1.4 specifications. Even though JAX-RPC, the web service specification for J2EE 1.4, is still supported JBossWS does put a clear focus on JAX-WS.</para>
+
+<section>
+ <title>Key Features of JBossWS</title>
+ <para>For a start, we propose you to look through the table of main features of JBossWS Runtime:</para>
+
+ <table>
+
+ <title>Key Functionality for JBossWS</title>
+ <tgroup cols="2">
+
+ <colspec align="left" colnum="1" colwidth="2*"></colspec>
+ <colspec colnum="2" colwidth="4*"></colspec>
+
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry><para>JAX-RPC and JAX-WS support</para></entry>
+ <entry><para>JBossWS implements both the JAX-WS and JAX-RPC specifications.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>EJB 2.1, EJB3 and JSE endpoints</para></entry>
+ <entry><para>JBossWS supports EJB 2.1, EJB3 and JSE as Web Service Endpoints.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>WS-Security 1.0 for XML Encryption/Signature of the SOAP message</para></entry>
+ <entry><para>WS-Security standardizes authorization, encryption, and digital signature processing of web services.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>JBoss AS</para></entry>
+ <entry><para>JBoss Application Server 5 (JavaEE 5 compliant) web service stack.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>Support for MTOM/XOP and SwA-Ref</para></entry>
+ <entry><para>Message Transmission Optimization Mechanism (MTOM) and XML-binary Optimized Packaging (XOP) more efficiently serialize XML Infosets that have certain types of content.</para></entry>
+
+ </row>
+
+ </tbody>
+
+ </tgroup>
+ </table>
+
+
+</section>
+<section>
+ <title>Other relevant resources on the topic</title>
+
+ <para>You can find some extra information on:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://www.jboss.org/community/wiki/JBossWS-FAQ#Tools">JBossWS Tools Wiki FAQ.</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+
+ </section>
+
+
+
+
+</chapter>
+
+<chapter id="create_ws_topdown" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/ws/docs/reference/en/modules/topdown.xml">
+ <?dbhtml filename="topdown.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Web Service</keyword>
+ <keyword>JBossWS Web Service runtime</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Creating a Web Service using JBossWS runtime</title>
+ <para>In this chapter we provide you with the necessary steps to create a Web Service using
+ JBossWS runtime. First you need to create a Dynamic Web project:</para>
+
+ <section id="createproject">
+ <title>Creating a Dynamic Web project</title>
+
+ <para>Before creating a web service, you should have a Dynamic Web Project created:</para>
+ <figure float="0">
+ <title>Dynamic Web Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_webproject_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Create a Web project by selecting <emphasis>
+ <property moreinfo="none">New > Project... > Dynamic Web project</property></emphasis>. Enter the following information: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Project Name: enter a project name</para>
+ </listitem>
+ <listitem>
+ <para>Target runtime: any server depending on your installation. If it is not listed,
+ click <property moreinfo="none">New</property> button and browse to the location where it is installed to. You may set <emphasis>
+ <property moreinfo="none">Target Runtime</property>
+ </emphasis> to <emphasis>
+ <property moreinfo="none">None</property></emphasis>, in this case, you should add <link linkend="addfacet">JBoss Web Service
+ facet to the project</link>.</para>
+ <figure float="0">
+ <title>Dynamic Web Project Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_webproject_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>Configuration: You may add <link linkend="addfacet">JBoss Web Service
+ facet to the project</link> by clicking <property moreinfo="none">Modify...</property> button. The opened page is like <property moreinfo="none">Figure 2.4</property>.</para>
+ </listitem>
+ <listitem>
+ <para>Configure Web Module values:</para>
+ <figure float="0">
+ <title>Web Module Settings Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_webproject_3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>If you added the JBoss Web Service facet to the project, now the <property moreinfo="none">Finish</property> button is disable. You must click <property moreinfo="none">Next</property> button to set more information about the JBoss Web Service facet. The page is like <property moreinfo="none">Figure 2.5</property>. Then click on the <property moreinfo="none">Finish</property> button.</para>
+ <para>If you didn't add the JBoss Web Service facet to the project, click on the <property moreinfo="none">Finish</property> button. Next you will need to add JBoss Web Service facet to the project.</para>
+ </section>
+
+ <section id="addfacet">
+ <title>Configure JBoss Web Service facet settings</title>
+ <para>If you have already created a new Dynamic Web project and not set the JBoss Web Service facet to the project, the next step is to add JBoss Web
+ Service facet to the project. Right-click on the project, select its <emphasis><property moreinfo="none">Properties</property></emphasis> and then find <emphasis>Project Facets</emphasis> in the tree-view on the left-side of the project properties dialog.
+ Tick on the check box for JBoss Web Services. You will see what like this: </para>
+ <figure float="0" id="figure_addfacet_0">
+ <title>Choose JBoss Web Service Facet</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_facet_0.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>At the bottom-left of the right-side of the project properties dialog, there is a error link: <emphasis><property moreinfo="none">Further configuration required...</property></emphasis> . You must click the link to set more information about JBoss Web Service facet.</para>
+ <para>Click on the <emphasis><property moreinfo="none">Further configuration required...</property></emphasis> link. In the opened window</para>
+ <figure float="0" id="figure_addfacet">
+ <title>Configure JBoss Web Service Facet</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_facet.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Server Supplied JBossWS Runtime: If you have already set a JBoss runtime to the
+ project's target runtime, you may choose <emphasis>
+ <property moreinfo="none">Server Supplied JBossWS Runtime</property>
+ </emphasis> and then click <emphasis>
+ <property moreinfo="none">Ok</property>
+ </emphasis> to finish the configuration of JBoss Web Service facet. </para>
+ <para>If the project has no <emphasis>
+ <property moreinfo="none">Target Runtime</property>
+ </emphasis> settings, you should check the second radio button and specify a JBossWS
+ runtime from the list. You also can create a new JBossWS runtime, click on the <emphasis>
+ <property moreinfo="none">New...</property>
+ </emphasis> button will bring you to another dialog to configure new JBossWS runtime.</para>
+ <figure float="0" id="figure_addfacet1">
+ <title>Configure JBossWS Runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_newruntime.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>See how to configure a new JBossWS runtime <link linkend="preference">here</link>.</para>
+ <para>After setting the information about JBoss Web Service facet, for saving the result, you should click the <property moreinfo="none">Apply</property> or <property moreinfo="none">OK</property> button at the bottom-right of the right-side of the project properties dialog.</para>
+ </section>
+
+
+ <section id="topdownwebservice">
+ <title>Creating a Web Service from a WSDL document using JBossWS runtime</title>
+ <para>In this chapter we provide you with the necessary steps to create a Web Service from a
+ WSDL document using JBossWS runtime.</para>
+ <para>At first, please make sure that you have already created a dynamic Web project with
+ JBoss Web Service facet installed. </para>
+ <para>See how to make it <link linkend="createproject">here</link> and <link linkend="addfacet">here</link>.</para>
+
+ <para>To create a Web Service using JBossWS runtime select<emphasis>
+ <property moreinfo="none">File > New > Other > Web Services > Web Service</property>
+ </emphasis> to run Web Service creation wizard. </para>
+ <para>Let's get through the wizard step-by-step:</para>
+ <figure float="0" id="figure_create_ws_topdown">
+ <title>New Web Service Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>First, please select <property moreinfo="none">Top down Java bean Web Service</property> from the Web
+ Service type list, and select a WSDL document from workspace, click on the Server name
+ link on the page will bring you to another dialog. Here you can specify the server to a
+ JBoss Server and Web Service runtime to JBossWS runtime:</para>
+ <figure float="0" id="figure_create_ws_topdown_setserver">
+ <title>Select Server and Web Service runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation1_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Click on the <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button to see the next wizard view opened:</para>
+
+ <figure float="0" id="figure_create_ws_topdown1">
+ <title>New Web Service Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Click on the <emphasis>
+ <property moreinfo="none">Next</property>
+ </emphasis> button to proceed:</para>
+ <figure float="0" id="figure_create_ws_topdown_codegen">
+ <title>New Web Service Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>On this page, the default package name comes from the namespace of the WSDL document,
+ you also can change it to any valid package name you want. JAX-WS specification should be
+ set to 2.0 if your JBossWS runtime in JBoss Server is JBossWS native runtime. You can
+ specify a catalog file and binding files if you have them. If you want the wizard to
+ generate empty implementation classes for the Web Service, check the <emphasis>
+ <property moreinfo="none">Generate default Web Service implementation classes</property>
+ </emphasis> check box. If you want to update the default Web.xml file with the Web Service
+ servlets configured, check the <emphasis>
+ <property moreinfo="none">Update the default Web.xml</property>
+ </emphasis> check box. Click on the <emphasis>
+ <property moreinfo="none">Next</property>
+ </emphasis> or on the <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button to generate code.</para>
+
+ <para>Once the Web Service code is generated, you can view the implementation class and add
+ business logic to each method.</para>
+ <figure float="0" id="figure_impl_code">
+ <title>The generated implementation Java code</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_Impl_code_view.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>View the Web.xml file:</para>
+ <figure float="0" id="figure_webxml">
+ <title>Web.xml</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_webxml.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+<para>In the next chapter you will find out how to create a Web service from a Java bean.</para>
+ </section>
+
+ <section id="bottomupws">
+ <title>Creating a Web service from a Java bean using JBossWS runtime</title>
+ <para>The Web Service wizard assists you in creating a new Web service, configuring it for
+ deployment, and then deploying it to the server.</para>
+ <para>To create a Web service from a bean using JBoss WS:</para>
+ <para>Setup <link linkend="preference">JBoss WS and development environment</link>.</para>
+ <para>Create <link linkend="createproject">a Dynamic Web project</link>.</para>
+ <para>Add <link linkend="addfacet">JBossWS Facet</link> to Web project.</para>
+ <para>Create a Web Service from a java bean: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Switch to the Java EE perspective <emphasis>
+ <property moreinfo="none">Window > Open Perspective > Java EE</property></emphasis>.</para>
+ </listitem>
+ <listitem>
+ <para>In the Project Explorer view, select the bean that you created or imported into
+ the source folder of your Web project.</para>
+ <figure float="0">
+ <title>Select the Bean Created</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">File > New > Other</property></emphasis>. Select Web Services in order to display various Web service wizards.
+ Select the Web Service wizard. Click on the <property moreinfo="none">Next</property> button.</para>
+ <figure float="0">
+ <title>New Web Service</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>On the first Web Service wizard page: select <property moreinfo="none">Bottom up Java bean Web
+ service</property> as your Web service type, and select the Java bean from which
+ the service will be created:</para>
+ <figure float="0">
+ <title>Set Web Service Common values</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Select the stages of Web service development that you want to complete using
+ the slider: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Develop: this will develop the WSDL definition and implementation of
+ the Web service. This includes such tasks as creating modules that will
+ contain generated code, WSDL files, deployment descriptors, and Java
+ files when appropriate.</para>
+ </listitem>
+ <listitem>
+ <para>Assemble: this ensures the project that will host the Web service or
+ client gets associated to an EAR when required by the target application
+ server.</para>
+ </listitem>
+ <listitem>
+ <para>Deploy: this will create the deployment code for the service.</para>
+ </listitem>
+ <listitem>
+ <para>Install: this will install and configure the Web module and EARs on
+ the target server.</para>
+ </listitem>
+ <listitem>
+ <para>Start: this will start the server once the service has been installed
+ on it. The server-config.wsdd file will be generated.</para>
+ </listitem>
+ <listitem>
+ <para>Test: this will provide various options for testing the service, such
+ as using the Web Service Explorer or sample JSPs.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>Select your server: the default server is displayed. If you want to deploy
+ your service to a different server click the link to specify a different server.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Select your runtime: ensure the JBoss WS runtime is selected.</para>
+ </listitem>
+ <listitem>
+ <para>Select the service project: the project selected in your workspace is
+ displayed. To select a different project click on the project link. If you are
+ deploying to JBoss Application Server you will also be asked to select the EAR
+ associated with the project. Ensure that the project selected as the Client Web
+ Project is different from the Service Web Project, or the service will be
+ overwritten by the client's generated artifacts.</para>
+ </listitem>
+ <listitem>
+ <para>If you want to create a client, select the type of proxy to be generated
+ and repeat the above steps for the client. The better way is to create a web
+ service client project separately.</para>
+ </listitem>
+ </itemizedlist>
+ <para>Click on the <property moreinfo="none">Next</property> button.</para>
+ </listitem>
+ <listitem>
+ <para>On the JBoss Web Service Code Generation Configuration page, set the following
+ values:</para>
+ <figure float="0">
+ <title>Set Web Service values for Code Generation</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Generate WSDL file: select it, you will get a generated WSDL file in your
+ project. But this wsdl's services' address location values are not a real
+ address. </para>
+ </listitem>
+ <listitem>
+ <para>After the Web service has been created, the following option can become
+ available depending on the options you selected: Update the default web.xm
+ file. If selected, you may test the web service by Explorer.</para>
+ </listitem>
+ </itemizedlist>
+ <para>Click on the <property moreinfo="none">Next</property> button.</para>
+ </listitem>
+ <listitem>
+ <para>On this page, the project is deployed to the server. You can start the server and
+ test the web service. If you want to publish the web service to a UDDI registry, you
+ may click the <property moreinfo="none">Next</property> button to publish it. If not, you may click
+ the <property moreinfo="none">Finish</property> button.</para>
+ <figure float="0">
+ <title>Start a Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>After the Web Service has been created, the following options may become available
+ depending on the options selected:</para>
+ <itemizedlist>
+ <listitem>
+ <para>the generated web services code</para>
+ </listitem>
+ <listitem>
+ <para>If you selected to generate a WSDL file, you will get the file in your project's wsdl folder.</para>
+ <figure float="0">
+ <title>The Generated HelloWorldService.wsdl File in the wsdl Folder</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_6.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>If you selected to update the default web.xml, you will test the web service in
+ the browser. Open the Explorer, input the url for the web service according to
+ web.xml plus <property moreinfo="none">?wsdl.</property>, you will get the WSDL file from Explorer. </para>
+ <figure float="0">
+ <title>The Updated web.xml file</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_5.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>In the next chapter you will be able to create a Web Service Client from a WSDL document using JBoss WS.</para>
+
+ </section>
+
+</chapter>
+
+
+<chapter id="client" revisionflag="added" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/ws/docs/reference/en/modules/client.xml">
+ <title>Creating a Web Service Client from a WSDL Document using JBoss WS</title>
+ <para>To create a Web Service Client from a WSDL Document using JBoss WS you need to fulfil the following steps:</para>
+ <para>Setup <link linkend="preference">JBoss WS and development environment</link>.</para>
+ <para><link linkend="createproject">Create a Dynamic Web project</link>.</para>
+ <para><link linkend="addfacet">Add JBossWS Facet to Web project</link>.</para>
+ <para>Then you can create a Web Service Client from a WSDL document: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Switch to the Java EE perspective <emphasis><property moreinfo="none">Window > Open Perspective > Java EE</property></emphasis>.</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis><property moreinfo="none">File > New > Other</property></emphasis>. Select Web Services in order to display the various Web service wizards. Select the Web Service Client wizard. Click on the <property moreinfo="none">Next</property> button.</para>
+ <figure float="0">
+ <title>New Web Service Client</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/client/jbossws_client.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>The first and the second Web Service Client wizard pages are the same as for <link linkend="topdownwebservice">Web Service from a WSDL document</link>.</para>
+ <figure float="0">
+ <title>Set Web Service Common values</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/client/jbossws_client_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <figure float="0">
+ <title>Set Web Service values related to WSDL file</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/client/jbossws_client_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The only difference is:</para>
+ <itemizedlist>
+ <listitem>
+ <para><property moreinfo="none">Client Type:</property> Support of Java Proxy only.</para>
+ </listitem>
+ </itemizedlist>
+ <para>Click on the <property moreinfo="none">Finish</property> button.</para>
+ </listitem>
+ </itemizedlist>
+ <para>After the Web Service Client has been created, the following may occur depending on the options you selected:</para>
+ <itemizedlist>
+ <listitem>
+ <para> the generated web service and client codes</para>
+ </listitem>
+ <listitem>
+ <para>a client sample class.</para>
+ <figure float="0">
+ <title>Client Sample Class</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/client/jbossws_client_3.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>JBoss WS use a Java class to test Web Service. A client sample class will be generated, you may run this client as a java application to call a web service.</para>
+</chapter>
+
+
+<chapter id="preference" revisionflag="added" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/ws/docs/reference/en/modules/preference.xml">
+ <title>JBoss WS and development environment</title>
+
+ <para>In this chapter you will learn how to change JBossWS preferences and how to set default server and runtime.</para>
+ <section id="jbosswspreference">
+
+
+ <title>JBossWS Preferences</title>
+
+ <para>In this section you will know how JBossWS preferences can be modified during the
+ development process.</para>
+
+ <para>JBossWS preferences can be set on the JBossWS preference page. Click on
+ <emphasis><property moreinfo="none">Window > Preferences > JBoss Tools > Web > JBossWS
+ Preferences</property>.</emphasis></para>
+
+ <para>On this page you can manage the JBossWS Runtime. Use the appropriate buttons to
+ <property moreinfo="none">Add</property> more runtimes or to <property moreinfo="none">Remove</property> those that
+ are not needed.</para>
+
+ <figure float="0">
+ <title>JBossWS Preferences Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/Jbossws_preference.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Clicking on <emphasis>
+ <property moreinfo="none">Add</property>
+ </emphasis> or <emphasis>
+ <property moreinfo="none">Edit</property>
+ </emphasis> button will open the form where you can configure a new JBossWS runtime and
+ change the path to JBossWS runtime home folder, modify the name and version of the
+ existing JBossWS runtime settings. Press <property moreinfo="none">Finish</property> to apply the
+ changes.</para>
+
+ <figure float="0">
+ <title>Edit JBossWS Runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/Jbossws_preference_new.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+
+
+ <para>WS container allows Source and JavaDoc locations to be set via the Properties dialog on each contained .jar: right-click on any .jar file in the Project Explorer view, select <emphasis><property moreinfo="none">Properties</property></emphasis>. Choose <emphasis><property moreinfo="none">Java Source Attachment</property></emphasis> and select location (folder, JAR or zip) containing new source for the chosen .jar using one of the suggested options (workspace, external folder or file) or enter the path manually:</para>
+
+ <figure float="0">
+ <title>Classpath Container: Java Source Attachment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/jbossws_container1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click on <emphasis><property moreinfo="none">Apply</property></emphasis> and then on <emphasis><property moreinfo="none">Ok</property></emphasis>.</para>
+ <para>To change JavaDoc Location choose <emphasis><property moreinfo="none">Javadoc Location</property></emphasis> and specify URL to the documentation generated by Javadoc. The Javadoc location will contain a file called <emphasis><property moreinfo="none">package-list</property></emphasis>:</para>
+
+ <figure float="0">
+ <title>Classpath Container: Javadoc Location</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/jbossws_container2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click on <emphasis><property moreinfo="none">Apply</property></emphasis> and then on <emphasis><property moreinfo="none">Ok</property></emphasis>.</para>
+
+
+
+
+
+
+ </section>
+ <section id="serverruntime">
+ <title>Default Server and Runtime</title>
+ <para>Open <emphasis>
+ <property moreinfo="none">Window > Preferences > Web Services > Server and Runtime</property></emphasis>. On this page, you can specify a default server and runtime.</para>
+ <para>For ease of use, the better way is to set runtime to JBoss WS.</para>
+ <para>After server and runtime are specified, click on the <property moreinfo="none">Apply</property> button
+ to save the values.</para>
+ <figure float="0">
+ <title>Specifing a default server and runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/jbossws_server_runtime.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>On the whole, this guide covers the fundamental concepts of work with tooling for
+ <property moreinfo="none">JBossWS</property>. It describes how to easily create a Web Service and a Web Service Client using
+ JBossWS Runtime and adjust JBossWS and development environment as well.</para>
+
+ <para>If the information on JBossWS tools in this guide isn't enough for you, ask
+ questions on our <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">forum</ulink>. Your comments and suggestions are also welcome.</para>
+ </section>
+</chapter>
+
+</book>
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/overview.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/overview.xml (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/overview.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="overview">
+ <title>JBossWS Runtime Overview</title>
+
+ <para>JBossWS is a web service framework developed as a part of the JBoss Application Server. It implements the JAX-WS specification that defines a programming model and run-time architecture for implementing web services in Java, targeted at the Java Platform, Enterprise Edition 5 (Java EE 5).</para>
+ <para>JBossWS integrates with most current JBoss Application Server releases as well as earlier ones, that did implement the J2EE 1.4 specifications. Even though JAX-RPC, the web service specification for J2EE 1.4, is still supported JBossWS does put a clear focus on JAX-WS.</para>
+
+<section>
+ <title>Key Features of JBossWS</title>
+ <para>For a start, we propose you to look through the table of main features of JBossWS Runtime:</para>
+
+ <table>
+
+ <title>Key Functionality for JBossWS</title>
+ <tgroup cols="2">
+
+ <colspec colnum="1" align="left" colwidth="2*"/>
+ <colspec colnum="2" colwidth="4*"/>
+
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry><para>JAX-RPC and JAX-WS support</para></entry>
+ <entry><para>JBossWS implements both the JAX-WS and JAX-RPC specifications.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>EJB 2.1, EJB3 and JSE endpoints</para></entry>
+ <entry><para>JBossWS supports EJB 2.1, EJB3 and JSE as Web Service Endpoints.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>WS-Security 1.0 for XML Encryption/Signature of the SOAP message</para></entry>
+ <entry><para>WS-Security standardizes authorization, encryption, and digital signature processing of web services.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>JBoss AS</para></entry>
+ <entry><para>JBoss Application Server 5 (JavaEE 5 compliant) web service stack.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>Support for MTOM/XOP and SwA-Ref</para></entry>
+ <entry><para>Message Transmission Optimization Mechanism (MTOM) and XML-binary Optimized Packaging (XOP) more efficiently serialize XML Infosets that have certain types of content.</para></entry>
+
+ </row>
+
+ </tbody>
+
+ </tgroup>
+ </table>
+
+
+</section>
+<section>
+ <title>Other relevant resources on the topic</title>
+
+ <para>You can find some extra information on:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://www.jboss.org/community/wiki/JBossWS-FAQ#Tools">JBossWS Tools Wiki FAQ.</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+
+ </section>
+
+
+
+
+</chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/preference.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/preference.xml (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/preference.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,104 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="preference" revisionflag="added">
+ <title>JBoss WS and development environment</title>
+
+ <para>In this chapter you will learn how to change JBossWS preferences and how to set default server and runtime.</para>
+ <section id="jbosswspreference">
+
+
+ <title>JBossWS Preferences</title>
+
+ <para>In this section you will know how JBossWS preferences can be modified during the
+ development process.</para>
+
+ <para>JBossWS preferences can be set on the JBossWS preference page. Click on
+ <emphasis><property>Window > Preferences > JBoss Tools > Web > JBossWS
+ Preferences</property>.</emphasis></para>
+
+ <para>On this page you can manage the JBossWS Runtime. Use the appropriate buttons to
+ <property>Add</property> more runtimes or to <property>Remove</property> those that
+ are not needed.</para>
+
+ <figure>
+ <title>JBossWS Preferences Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/Jbossws_preference.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Clicking on <emphasis>
+ <property>Add</property>
+ </emphasis> or <emphasis>
+ <property>Edit</property>
+ </emphasis> button will open the form where you can configure a new JBossWS runtime and
+ change the path to JBossWS runtime home folder, modify the name and version of the
+ existing JBossWS runtime settings. Press <property>Finish</property> to apply the
+ changes.</para>
+
+ <figure>
+ <title>Edit JBossWS Runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/Jbossws_preference_new.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+
+
+ <para>WS container allows Source and JavaDoc locations to be set via the Properties dialog on each contained .jar: right-click on any .jar file in the Project Explorer view, select <emphasis><property>Properties</property></emphasis>. Choose <emphasis><property>Java Source Attachment</property></emphasis> and select location (folder, JAR or zip) containing new source for the chosen .jar using one of the suggested options (workspace, external folder or file) or enter the path manually:</para>
+
+ <figure>
+ <title>Classpath Container: Java Source Attachment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/jbossws_container1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click on <emphasis><property>Apply</property></emphasis> and then on <emphasis><property>Ok</property></emphasis>.</para>
+ <para>To change JavaDoc Location choose <emphasis><property>Javadoc Location</property></emphasis> and specify URL to the documentation generated by Javadoc. The Javadoc location will contain a file called <emphasis><property>package-list</property></emphasis>:</para>
+
+ <figure>
+ <title>Classpath Container: Javadoc Location</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/jbossws_container2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click on <emphasis><property>Apply</property></emphasis> and then on <emphasis><property>Ok</property></emphasis>.</para>
+
+
+
+
+
+
+ </section>
+ <section id="serverruntime">
+ <title>Default Server and Runtime</title>
+ <para>Open <emphasis>
+ <property>Window > Preferences > Web Services > Server and Runtime</property></emphasis>. On this page, you can specify a default server and runtime.</para>
+ <para>For ease of use, the better way is to set runtime to JBoss WS.</para>
+ <para>After server and runtime are specified, click on the <property>Apply</property> button
+ to save the values.</para>
+ <figure>
+ <title>Specifing a default server and runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/jbossws_server_runtime.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>On the whole, this guide covers the fundamental concepts of work with tooling for
+ <property>JBossWS</property>. It describes how to easily create a Web Service and a Web Service Client using
+ JBossWS Runtime and adjust JBossWS and development environment as well.</para>
+
+ <para>If the information on JBossWS tools in this guide isn't enough for you, ask
+ questions on our <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">forum</ulink>. Your comments and suggestions are also welcome.</para>
+ </section>
+</chapter>
Added: branches/jbosstools-3.1.x/ws/docs/reference/en-US/topdown.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en-US/topdown.xml (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en-US/topdown.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,396 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="create_ws_topdown">
+ <?dbhtml filename="topdown.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Web Service</keyword>
+ <keyword>JBossWS Web Service runtime</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Creating a Web Service using JBossWS runtime</title>
+ <para>In this chapter we provide you with the necessary steps to create a Web Service using
+ JBossWS runtime. First you need to create a Dynamic Web project:</para>
+
+ <section id="createproject">
+ <title>Creating a Dynamic Web project</title>
+
+ <para>Before creating a web service, you should have a Dynamic Web Project created:</para>
+ <figure>
+ <title>Dynamic Web Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_webproject_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Create a Web project by selecting <emphasis>
+ <property>New > Project... > Dynamic Web project</property></emphasis>. Enter the following information: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Project Name: enter a project name</para>
+ </listitem>
+ <listitem>
+ <para>Target runtime: any server depending on your installation. If it is not listed,
+ click <property>New</property> button and browse to the location where it is installed to. You may set <emphasis>
+ <property>Target Runtime</property>
+ </emphasis> to <emphasis>
+ <property>None</property></emphasis>, in this case, you should add <link linkend="addfacet">JBoss Web Service
+ facet to the project</link>.</para>
+ <figure>
+ <title>Dynamic Web Project Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_webproject_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>Configuration: You may add <link linkend="addfacet">JBoss Web Service
+ facet to the project</link> by clicking <property>Modify...</property> button. The opened page is like <property>Figure 2.4</property>.</para>
+ </listitem>
+ <listitem>
+ <para>Configure Web Module values:</para>
+ <figure>
+ <title>Web Module Settings Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_webproject_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>If you added the JBoss Web Service facet to the project, now the <property>Finish</property> button is disable. You must click <property>Next</property> button to set more information about the JBoss Web Service facet. The page is like <property>Figure 2.5</property>. Then click on the <property>Finish</property> button.</para>
+ <para>If you didn't add the JBoss Web Service facet to the project, click on the <property>Finish</property> button. Next you will need to add JBoss Web Service facet to the project.</para>
+ </section>
+
+ <section id="addfacet">
+ <title>Configure JBoss Web Service facet settings</title>
+ <para>If you have already created a new Dynamic Web project and not set the JBoss Web Service facet to the project, the next step is to add JBoss Web
+ Service facet to the project. Right-click on the project, select its <emphasis><property>Properties</property></emphasis> and then find <emphasis>Project Facets</emphasis> in the tree-view on the left-side of the project properties dialog.
+ Tick on the check box for JBoss Web Services. You will see what like this: </para>
+ <figure id="figure_addfacet_0">
+ <title>Choose JBoss Web Service Facet</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_facet_0.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>At the bottom-left of the right-side of the project properties dialog, there is a error link: <emphasis><property>Further configuration required...</property></emphasis> . You must click the link to set more information about JBoss Web Service facet.</para>
+ <para>Click on the <emphasis><property>Further configuration required...</property></emphasis> link. In the opened window</para>
+ <figure id="figure_addfacet">
+ <title>Configure JBoss Web Service Facet</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_facet.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Server Supplied JBossWS Runtime: If you have already set a JBoss runtime to the
+ project's target runtime, you may choose <emphasis>
+ <property>Server Supplied JBossWS Runtime</property>
+ </emphasis> and then click <emphasis>
+ <property>Ok</property>
+ </emphasis> to finish the configuration of JBoss Web Service facet. </para>
+ <para>If the project has no <emphasis>
+ <property>Target Runtime</property>
+ </emphasis> settings, you should check the second radio button and specify a JBossWS
+ runtime from the list. You also can create a new JBossWS runtime, click on the <emphasis>
+ <property>New...</property>
+ </emphasis> button will bring you to another dialog to configure new JBossWS runtime.</para>
+ <figure id="figure_addfacet1">
+ <title>Configure JBossWS Runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_newruntime.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>See how to configure a new JBossWS runtime <link linkend="preference">here</link>.</para>
+ <para>After setting the information about JBoss Web Service facet, for saving the result, you should click the <property>Apply</property> or <property>OK</property> button at the bottom-right of the right-side of the project properties dialog.</para>
+ </section>
+
+
+ <section id="topdownwebservice">
+ <title>Creating a Web Service from a WSDL document using JBossWS runtime</title>
+ <para>In this chapter we provide you with the necessary steps to create a Web Service from a
+ WSDL document using JBossWS runtime.</para>
+ <para>At first, please make sure that you have already created a dynamic Web project with
+ JBoss Web Service facet installed. </para>
+ <para>See how to make it <link linkend="createproject">here</link> and <link
+ linkend="addfacet">here</link>.</para>
+
+ <para>To create a Web Service using JBossWS runtime select<emphasis>
+ <property>File > New > Other > Web Services > Web Service</property>
+ </emphasis> to run Web Service creation wizard. </para>
+ <para>Let's get through the wizard step-by-step:</para>
+ <figure id="figure_create_ws_topdown">
+ <title>New Web Service Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>First, please select <property>Top down Java bean Web Service</property> from the Web
+ Service type list, and select a WSDL document from workspace, click on the Server name
+ link on the page will bring you to another dialog. Here you can specify the server to a
+ JBoss Server and Web Service runtime to JBossWS runtime:</para>
+ <figure id="figure_create_ws_topdown_setserver">
+ <title>Select Server and Web Service runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation1_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Click on the <emphasis>
+ <property>Finish</property>
+ </emphasis> button to see the next wizard view opened:</para>
+
+ <figure id="figure_create_ws_topdown1">
+ <title>New Web Service Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Click on the <emphasis>
+ <property>Next</property>
+ </emphasis> button to proceed:</para>
+ <figure id="figure_create_ws_topdown_codegen">
+ <title>New Web Service Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>On this page, the default package name comes from the namespace of the WSDL document,
+ you also can change it to any valid package name you want. JAX-WS specification should be
+ set to 2.0 if your JBossWS runtime in JBoss Server is JBossWS native runtime. You can
+ specify a catalog file and binding files if you have them. If you want the wizard to
+ generate empty implementation classes for the Web Service, check the <emphasis>
+ <property>Generate default Web Service implementation classes</property>
+ </emphasis> check box. If you want to update the default Web.xml file with the Web Service
+ servlets configured, check the <emphasis>
+ <property>Update the default Web.xml</property>
+ </emphasis> check box. Click on the <emphasis>
+ <property>Next</property>
+ </emphasis> or on the <emphasis>
+ <property>Finish</property>
+ </emphasis> button to generate code.</para>
+
+ <para>Once the Web Service code is generated, you can view the implementation class and add
+ business logic to each method.</para>
+ <figure id="figure_impl_code">
+ <title>The generated implementation Java code</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_Impl_code_view.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>View the Web.xml file:</para>
+ <figure id="figure_webxml">
+ <title>Web.xml</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_webxml.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+<para>In the next chapter you will find out how to create a Web service from a Java bean.</para>
+ </section>
+
+ <section id="bottomupws">
+ <title>Creating a Web service from a Java bean using JBossWS runtime</title>
+ <para>The Web Service wizard assists you in creating a new Web service, configuring it for
+ deployment, and then deploying it to the server.</para>
+ <para>To create a Web service from a bean using JBoss WS:</para>
+ <para>Setup <link linkend="preference">JBoss WS and development environment</link>.</para>
+ <para>Create <link linkend="createproject">a Dynamic Web project</link>.</para>
+ <para>Add <link linkend="addfacet">JBossWS Facet</link> to Web project.</para>
+ <para>Create a Web Service from a java bean: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Switch to the Java EE perspective <emphasis>
+ <property>Window > Open Perspective > Java EE</property></emphasis>.</para>
+ </listitem>
+ <listitem>
+ <para>In the Project Explorer view, select the bean that you created or imported into
+ the source folder of your Web project.</para>
+ <figure>
+ <title>Select the Bean Created</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata scale="80" fileref="images/topdown/jbossws_bottomup.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property>File > New > Other</property></emphasis>. Select Web Services in order to display various Web service wizards.
+ Select the Web Service wizard. Click on the <property>Next</property> button.</para>
+ <figure>
+ <title>New Web Service</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>On the first Web Service wizard page: select <property>Bottom up Java bean Web
+ service</property> as your Web service type, and select the Java bean from which
+ the service will be created:</para>
+ <figure>
+ <title>Set Web Service Common values</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Select the stages of Web service development that you want to complete using
+ the slider: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Develop: this will develop the WSDL definition and implementation of
+ the Web service. This includes such tasks as creating modules that will
+ contain generated code, WSDL files, deployment descriptors, and Java
+ files when appropriate.</para>
+ </listitem>
+ <listitem>
+ <para>Assemble: this ensures the project that will host the Web service or
+ client gets associated to an EAR when required by the target application
+ server.</para>
+ </listitem>
+ <listitem>
+ <para>Deploy: this will create the deployment code for the service.</para>
+ </listitem>
+ <listitem>
+ <para>Install: this will install and configure the Web module and EARs on
+ the target server.</para>
+ </listitem>
+ <listitem>
+ <para>Start: this will start the server once the service has been installed
+ on it. The server-config.wsdd file will be generated.</para>
+ </listitem>
+ <listitem>
+ <para>Test: this will provide various options for testing the service, such
+ as using the Web Service Explorer or sample JSPs.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>Select your server: the default server is displayed. If you want to deploy
+ your service to a different server click the link to specify a different server.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Select your runtime: ensure the JBoss WS runtime is selected.</para>
+ </listitem>
+ <listitem>
+ <para>Select the service project: the project selected in your workspace is
+ displayed. To select a different project click on the project link. If you are
+ deploying to JBoss Application Server you will also be asked to select the EAR
+ associated with the project. Ensure that the project selected as the Client Web
+ Project is different from the Service Web Project, or the service will be
+ overwritten by the client's generated artifacts.</para>
+ </listitem>
+ <listitem>
+ <para>If you want to create a client, select the type of proxy to be generated
+ and repeat the above steps for the client. The better way is to create a web
+ service client project separately.</para>
+ </listitem>
+ </itemizedlist>
+ <para>Click on the <property>Next</property> button.</para>
+ </listitem>
+ <listitem>
+ <para>On the JBoss Web Service Code Generation Configuration page, set the following
+ values:</para>
+ <figure>
+ <title>Set Web Service values for Code Generation</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Generate WSDL file: select it, you will get a generated WSDL file in your
+ project. But this wsdl's services' address location values are not a real
+ address. </para>
+ </listitem>
+ <listitem>
+ <para>After the Web service has been created, the following option can become
+ available depending on the options you selected: Update the default web.xm
+ file. If selected, you may test the web service by Explorer.</para>
+ </listitem>
+ </itemizedlist>
+ <para>Click on the <property>Next</property> button.</para>
+ </listitem>
+ <listitem>
+ <para>On this page, the project is deployed to the server. You can start the server and
+ test the web service. If you want to publish the web service to a UDDI registry, you
+ may click the <property>Next</property> button to publish it. If not, you may click
+ the <property>Finish</property> button.</para>
+ <figure>
+ <title>Start a Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>After the Web Service has been created, the following options may become available
+ depending on the options selected:</para>
+ <itemizedlist>
+ <listitem>
+ <para>the generated web services code</para>
+ </listitem>
+ <listitem>
+ <para>If you selected to generate a WSDL file, you will get the file in your project's wsdl folder.</para>
+ <figure>
+ <title>The Generated HelloWorldService.wsdl File in the wsdl Folder</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata scale="80" fileref="images/topdown/jbossws_bottomup_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>If you selected to update the default web.xml, you will test the web service in
+ the browser. Open the Explorer, input the url for the web service according to
+ web.xml plus <property>?wsdl.</property>, you will get the WSDL file from Explorer. </para>
+ <figure>
+ <title>The Updated web.xml file</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata scale="80" fileref="images/topdown/jbossws_bottomup_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>In the next chapter you will be able to create a Web Service Client from a WSDL document using JBoss WS.</para>
+
+ </section>
+
+</chapter>
Modified: branches/jbosstools-3.1.x/ws/docs/reference/pom.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/pom.xml 2010-03-12 01:05:58 UTC (rev 20787)
+++ branches/jbosstools-3.1.x/ws/docs/reference/pom.xml 2010-03-12 01:08:20 UTC (rev 20788)
@@ -14,7 +14,7 @@
<profile>
<id>release</id>
<properties>
- <master>master_output.xml</master>
+ <!-- <master>master_output.xml</master> -->
<xsl-single>classpath:/xslt/org/jboss/tools/xhtml-single-release.xsl</xsl-single>
<xsl-chunked>classpath:/xslt/org/jboss/tools/xhtml-release.xsl</xsl-chunked>
<xsl-pdf>classpath:/xslt/org/jboss/tools/pdf.xsl</xsl-pdf>
@@ -23,7 +23,7 @@
<profile>
<id>releaseTest</id>
<properties>
- <master>master_output.xml</master>
+ <!-- <master>master_output.xml</master> -->
<xsl-single>classpath:/xslt/org/jboss/tools/xhtml-single-release-nomarker.xsl</xsl-single>
<xsl-chunked>classpath:/xslt/org/jboss/tools/xhtml-release-nomarker.xsl</xsl-chunked>
<xsl-pdf>classpath:/xslt/org/jboss/tools/pdf.xsl</xsl-pdf>
@@ -32,7 +32,7 @@
<profile>
<id>releaseJBDS</id>
<properties>
- <master>master.xml</master>
+ <!-- <master>master_output.xml</master> -->
<xsl-single>classpath:/xslt/com/jboss/tools/xhtml-single-release.xsl</xsl-single>
<xsl-chunked>classpath:/xslt/com/jboss/tools/xhtml-release.xsl</xsl-chunked>
<xsl-pdf>classpath:/xslt/com/jboss/tools/pdf.xsl</xsl-pdf>
@@ -42,7 +42,7 @@
<profile>
<id>diffmk</id>
<properties>
- <master>master_output.xml</master>
+ <!-- <master>master_output.xml</master> -->
<xsl-single>classpath:/xslt/org/jboss/tools/xhtml-single-diff.xsl</xsl-single>
<xsl-chunked>classpath:/xslt/org/jboss/tools/xhtml-diff.xsl</xsl-chunked>
<xsl-pdf>classpath:/xslt/org/jboss/tools/pdf-diff.xsl</xsl-pdf>
@@ -93,18 +93,18 @@
</dependency>
</dependencies>
- <configuration>
- <sourceDocumentName>${master}</sourceDocumentName>
- <sourceDirectory>${pom.basedir}/en</sourceDirectory>
- <imageResource>
- <directory>${pom.basedir}/en</directory>
- <includes>
- <include>images/**/*</include>
- </includes>
- </imageResource>
- <cssResource>
- <directory>${pom.basedir}/${cssdir}</directory>
- </cssResource>
+ <configuration>
+ <sourceDocumentName>master.xml</sourceDocumentName>
+ <sourceDirectory>${pom.basedir}/en-US</sourceDirectory>
+ <imageResource>
+ <directory>${pom.basedir}/en-US</directory>
+ <includes>
+ <include>images/**/*</include>
+ </includes>
+ </imageResource>
+ <cssResource>
+ <directory>${pom.basedir}/${cssdir}</directory>
+ </cssResource>
<formats>
<format>
@@ -163,7 +163,7 @@
<xsl-chunked>classpath:/xslt/org/jboss/tools/xhtml.xsl</xsl-chunked>
<xsl-pdf>classpath:/xslt/org/jboss/tools/pdf.xsl</xsl-pdf>
<cssdir>../../../documentation/jbosstools-jdocbook-style/src/main/org/css/</cssdir>
- <master>master.xml</master>
+ <master>JBoss_Web_Services_User_Guide</master>
<translation>en-US</translation>
</properties>
Added: branches/jbosstools-3.1.x/ws/docs/reference/publican.cfg
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/publican.cfg (rev 0)
+++ branches/jbosstools-3.1.x/ws/docs/reference/publican.cfg 2010-03-12 01:08:20 UTC (rev 20788)
@@ -0,0 +1,7 @@
+# Config::Simple 4.59
+# Fri Nov 20 13:19:45 2009
+
+xml_lang: en-US
+type: Book
+brand: JBoss
+
14 years, 3 months
- 1
- 0
JBoss Tools SVN: r20787 - in branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide: en-US and 3 other directories.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-11 20:05:58 -0500 (Thu, 11 Mar 2010)
New Revision: 20787
Added:
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Author_Group.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Book_Info.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Preface.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Revision_History.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Struts_Tools_Reference_Guide.ent
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Struts_Tools_Reference_Guide.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/code_generation.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/config_file_debugger.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/editors.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/favicon.ico
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/jbosstools_logo.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/Thumbs.db
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_10.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_11.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_12.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_13.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_14.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_15.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_16.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_17.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_18.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_19.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_2.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_20.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_21.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_22.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_23.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_24.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_25.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_26.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_27.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_28.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_29.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_3.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_30.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_31.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_32.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_33.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_34.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_35.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_36.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_37.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_38.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_39.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_3_1.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_4.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_40.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_41.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_42.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_43.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_44.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_45.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_46.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_47.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_48.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_49.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_5.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_50.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_51.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_6.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_7.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_8.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_9.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_10.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_11.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_12.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_13.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_14.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_8.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_9.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/introduction.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/master.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/master_output.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/modules.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/page_links_recognizer.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/project_verification.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/projects.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/rel_resources_links.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/struts_project_verification.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/publican.cfg
Removed:
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en/
Modified:
branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/pom.xml
Log:
updated to build with publican
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Author_Group.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Author_Group.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Author_Group.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,6 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<authorgroup><author><firstname>Anatoly</firstname><surname>Fedosik</surname></author>
+ <author><firstname>Olga</firstname><surname>Chikvina</surname></author>
+ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author></authorgroup>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Book_Info.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Book_Info.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Book_Info.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<bookinfo><title>Struts Tools Reference Guide</title><subtitle>Provides information relating to the BPMN Convert module.</subtitle><productname>JBoss Developer Studio</productname><productnumber>3.0</productnumber><edition>1.0</edition><pubsnumber>0</pubsnumber><abstract><para>The Struts Tools Reference Guide explains how to use the Struts Tools to create high-quality web applications.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Preface.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Preface.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Preface.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<preface><title>Preface</title><xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></xi:fallback></xi:include></preface>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Revision_History.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Revision_History.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Revision_History.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<appendix><title>Revision History</title><simpara><revhistory><revision><revnumber>0</revnumber><date>Fri Nov 20 2009</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Struts_Tools_Reference_Guide.ent
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Struts_Tools_Reference_Guide.ent (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Struts_Tools_Reference_Guide.ent 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "JBoss">
+<!ENTITY BOOKID "Struts_Tools_Reference_Guide">
+<!ENTITY YEAR "2010">
+<!ENTITY HOLDER "Red Hat">
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Struts_Tools_Reference_Guide.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Struts_Tools_Reference_Guide.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/Struts_Tools_Reference_Guide.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,18 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<book>
+<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="projects.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="editors.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="modules.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="code_generation.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="config_file_debugger.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="page_links_recognizer.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="project_verification.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="rel_resources_links.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<index></index>
+</book>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/code_generation.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/code_generation.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/code_generation.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,97 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="code_generation">
+ <?dbhtml filename="code_generation.html"?>
+
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Code Generation</title>
+
+ <para>JBoss Tools 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 that JBoss tooling provides is based on Velocity templates
+ which can be modified for your use. The templates are located at <emphasis>
+ <property> {JBossStudioHome} > 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>
+</chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/config_file_debugger.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/config_file_debugger.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/config_file_debugger.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="config_file_debugger">
+ <?dbhtml filename="config_file_debugger.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Struts Configuration File Debugger</title>
+
+ <para>JBoss Tools come 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>
+</chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/editors.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/editors.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/editors.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,479 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="editors">
+ <?dbhtml filename="editors.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Editors</title>
+ <para>In this chapter we'll introduce you to featured graphical editors for specific
+ Struts files such as Struts Configuration files, Tiles files, Struts Validation files and web.xml.</para>
+
+ <section id="webxml_editor">
+ <title>Web.xml Editor</title>
+
+ <para>The <emphasis>
+ <property>web.xml</property></emphasis> file inside the <emphasis>
+ <property>WEB-INF</property></emphasis> folder is a deployment descriptor file for a Web Application. It
+ describes the servlets and other components and deployment properties that make up your application.</para>
+
+ <para><property>JBoss Tools</property> add the <emphasis>
+ <property>web.xml</property></emphasis> file to created Struts project automatically and provides a special editor for its editing.
+ See the Visual Web Tools guide that gives a descriptive information on the web.xml editor.</para>
+ </section>
+
+ <section id="struts_config_editor">
+
+ <title>Graphical Editor for Struts Configuration Files</title>
+ <para>First, let's dwell on the Struts Configuration file editor.</para>
+ <para>This editor has three views with different representation of <emphasis>
+ <property>struts-config.xml</property>: </emphasis>Diagram, Tree and Source. The
+ views can be selected via the tabs at the bottom of the editor. Any changes made in one
+ view are immediately visible when you switch to any other view.</para>
+
+ <para>Now, we'll consider every view in more detail.</para>
+ <section id="StrutsDiagramMode453">
+
+ <title>Diagram View</title>
+
+ <para>The Diagram view graphically displays the Web flow of the application defined in
+ the Struts configuration file.</para>
+
+ <figure>
+ <title>Diagram View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_14.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The Diagram view allows to edit navigation in your Struts application. 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. </para>
+
+ <figure>
+ <title>Editor Icons</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_16.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>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>
+
+
+ </section>
+ <section id="StrutsTreeMode42">
+
+ <title>Tree View</title>
+
+ <para>The Tree view represents the different elements of the Struts application that 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_17.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can 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>
+
+ <para>Let's consider the tree on the left more closely.</para>
+
+ <itemizedlist>
+ <listitem><para>Under the <emphasis>
+ <property>data-sources</property></emphasis> node you can create a Data Source object that will be configured
+ and made available as a servlet context attribute.</para></listitem>
+
+ <listitem><para>The <emphasis>
+ <property>form-beans</property></emphasis> node is meant for creating a set of form bean descriptors for this module.
+ Every created element under this node is a JavaBean that implements the org.apache.struts.action.ActionForm class.
+ Use the Properties editor on the right to adjust properties specific to every created form-bean.</para></listitem>
+
+ <listitem><para>The <emphasis>
+ <property>global-exceptions</property></emphasis> node is intended for registering the handlers for the exceptions
+ that might be thrown by an Action object.</para></listitem>
+
+ <listitem><para>Use the <emphasis>
+ <property>global-forwards</property></emphasis> node to add, edit or delete a global forwards that represent
+ ActionForward objects available to all Action objects as a return value.</para></listitem>
+
+ <listitem><para>The <emphasis>
+ <property>controller</property></emphasis> node allows you to configure the controller properties.</para></listitem>
+
+ <listitem><para>Under the <emphasis>
+ <property>resources</property></emphasis> node you can add, delete, or edit message resources.</para></listitem>
+
+ <listitem><para>Under the <emphasis>
+ <property>plug-ins</property></emphasis> node you can define a Struts plug-in. Right-click the node, select <emphasis>
+ <property>Create Plug-in</property></emphasis>
+ and specify the plug-ib <emphasis>
+ <property>Id</property></emphasis> and <emphasis>
+ <property>ClassName</property></emphasis> by pointing to the Java class which implements the org.apache.struts.action.PlugIn interface. </para></listitem>
+
+ </itemizedlist>
+ </section>
+ <section id="StrutsSourceMode9655">
+
+ <title>Source View</title>
+
+ <para>In the Source view, you have complete editing control of the underlying XML
+ coding.</para>
+
+ <figure>
+ <title>Source View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_19.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <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>
+ <para>You can take advantage of code assist.</para>
+ <figure>
+ <title>Code Assist</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_20.png" scale="85"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The editor will also immediately flag any errors.</para>
+
+ <figure>
+ <title>Errors in Source View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_21.png" scale="85"/>
+ </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>
+
+ <para>Find more information about editor features in the editor features chapter.</para>
+ </section>
+ </section>
+
+ <section id="GraphicalEditorForTilesFiles132">
+
+ <title>Graphical Editor for Tiles Files</title>
+ <para>Here, you'll know how to make use of the special graphical editor for Tiles configuration files.</para>
+ <para>The editor has three main views: Tree, Diagram and Source.
+ The views can be selected via the tabs at the bottom of the editor. Any changes made in
+ one view are immediately visible when you switch to any other view.</para>
+
+ <para>Before we consider each view of the editor, let's look at the way of creating new Tiles files.</para>
+ <section id="CreateNewTilesFile1422">
+
+ <title>Create New Tiles File</title>
+
+ <para>To create 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">
+
+ <title>Tree View</title>
+
+ <para>The Tree view represents the different elements of the Tiles file that 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">
+
+ <title>Diagram View</title>
+
+ <para>The Diagram view allows you to create complex Tiles files in the form of a
+ diagram.</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>
+
+ <para> It contains four icons for changing the cursor state. The first one is the
+ default cursor state for selecting existing nodes. The second icon is marquee
+ selector. The third is used for creating new connections and the last one is for
+ adding definition template to the content.</para>
+ </section>
+ <section id="StrutsSource75">
+
+ <title>Source</title>
+
+ <para>The other view of the <property>Tiles editor</property> is the Source view that
+ gives you full control over the source. Any changes here will immediately appear in
+ other modes when you switch to them.</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>
+
+ <figure>
+ <title>Source View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_29.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Code
+ assist is available in the Source mode.</para>
+ <figure>
+ <title>Code Assist</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_30.png" scale="85"/>
+ </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" scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can also use the Outline view together with the editor's Source mode.
+ It provides an easier navigation through the file.</para>
+ <figure>
+ <title>Outline View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_32.png" scale="85"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ </section>
+
+ <section id="GraphicalEditorForStrutsValidationFiles86">
+
+ <title>Graphical Editor for Struts Validation Files</title>
+
+ <para>Providing full support for development Struts applications JBoss Tools comes with a
+ visual validation editor. To open the editor double-click on the validation file or if you don't have it create a new one.</para>
+
+ <para>To create a new validation file, right click any folder in
+ Project Explorer and select <emphasis>
+ <property>File > New > Other...</property>
+ </emphasis>from the context menu and then <emphasis>
+ <property>JBoss Tools Web > Struts > Validation File</property>. </emphasis></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 with five modes: Formsets, Validators, Constants and
+ standard Tree and Source that you can easily switch over using tabs at the bottom of the
+ editor.</para>
+ <para>The Formsets view shows forms and their elements on the left side and the dialogue for
+ defining their validation rules on the right side.</para>
+ <figure>
+ <title>Formsets View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_34.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The Constants view let you set constant values for your validation rules.</para>
+ <figure>
+ <title>Constansts View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_35.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The validation file can also be viewed in a Tree view.</para>
+ <figure>
+ <title>Tree View</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 view.
+ Any editing in this view will immediately be available in other views of the editor.</para>
+ <figure>
+ <title>Source View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_37.png" scale="85"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can also open your own custom or Struts-standard <emphasis>
+ <property>validation-rules.xml</property>
+ </emphasis> file.</para>
+ <para>The Validators view shows the validation rules for a selected validator. You can of
+ course add your own rules.</para>
+ <figure>
+ <title>Validators View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_38.png" scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Here are the validation rules shown in the Source mode.</para>
+ <figure>
+ <title>Validation Rules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_39.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+</chapter>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/favicon.ico
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/favicon.ico
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/jbosstools_logo.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/jbosstools_logo.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/Thumbs.db
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/Thumbs.db
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_10.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_10.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_11.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_11.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_12.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_12.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_13.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_13.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_14.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_14.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_15.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_15.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_16.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_16.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_17.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_17.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_18.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_18.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_19.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_19.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_20.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_20.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_21.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_21.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_22.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_22.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_23.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_23.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_24.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_24.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_25.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_25.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_26.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_26.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_27.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_27.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_28.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_28.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_29.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_29.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_30.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_30.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_31.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_31.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_32.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_32.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_33.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_33.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_34.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_34.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_35.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_35.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_36.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_36.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_37.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_37.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_38.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_38.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_39.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_39.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_3_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_3_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_40.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_40.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_41.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_41.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_42.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_42.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_43.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_43.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_44.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_44.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_45.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_45.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_46.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_46.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_47.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_47.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_48.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_48.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_49.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_49.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_50.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_50.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_51.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_51.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_8.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_9.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/struts/struts_9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_10.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_10.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_11.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_11.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_12.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_12.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_13.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_13.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_14.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_14.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_8.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_9.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/images/verif_valid/verif_valid_9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/introduction.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/introduction.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/introduction.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="intoduction">
+ <?dbhtml filename="introduction.html"?>
+
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Introduction</title>
+
+ <para>If you prefer to develop web applications using Struts technology JBoss Tools also meet
+ your needs. The professional developer toolset provides all necessary editors and wizards
+ for creating Struts resources that enhances the process of building high-quality web
+ applications.</para>
+ <note>
+ <title>Note:</title>
+ <para>Note that JBoss Tools support the Struts 1.1, 1.2.x versions.</para>
+ </note>
+
+ <para>In this guide you will learn how to take advantage of Struts support that <property>JBoss Tools</property>
+ provide.</para>
+
+ <section id="struts_key_features">
+ <title>Key Features of Struts Tools</title>
+
+ <para>For a start, we propose you to look through the table of main features of Struts
+ Tools:</para>
+
+ <table>
+
+ <title>Key Functionality for Struts Tools</title>
+ <tgroup cols="3">
+
+ <colspec colnum="1" align="left" colwidth="2*"/>
+ <colspec colnum="2" colwidth="4*"/>
+ <colspec colnum="3" align="left" colwidth="2*"/>
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+ <entry>Chapter</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><para>Struts Support</para></entry>
+ <entry><para>Step-by-step wizards for creating a new struts project with a number
+ of predefined templates, importing existing ones and adding struts
+ capabilities to non-struts web projects.</para></entry>
+ <entry>
+ <link linkend="projects">struts support</link>
+ </entry>
+ </row>
+
+ <row>
+ <entry><para>Support for Struts Configuration File</para></entry>
+ <entry><para>Working on file using three modes: diagram, tree and source.
+ Synchronization between the modes and full control over the code. Easy
+ moving around the diagram using the Diagram Navigator. Working with
+ struts projects that have multiple modules. Possibility to use Struts
+ configuration file debugger allowing to set break points on struts
+ diagram and then launch the server in debug mode.</para></entry>
+ <entry>
+ <link linkend="struts_config_editor">graphical editor for struts</link>
+ <link linkend="config_file_debugger">configuration file debugger</link>
+ </entry>
+ </row>
+
+ <row>
+ <entry><para>Support for Struts modules</para></entry>
+ <entry><para>A Struts module (struts-config.xml) is automatically created while
+ creating a new project. There is also possibility to add new ones or edit
+ already existing modules in your existing project or while importing Struts project.</para></entry>
+ <entry>
+ <link linkend="modules">modules</link>
+ </entry>
+ </row>
+
+ <row>
+ <entry><para>Verification and Validation</para></entry>
+ <entry><para>All occurring errors will be immediately reported by verification
+ feature, no matter in what view you are working. Constant validation and
+ errors checking allows to catch many of the errors during development
+ process that significantly reduces development time.</para></entry>
+ <entry>
+ <link linkend="project_verification">verification and validation</link>
+ </entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </section>
+
+ <section>
+ <title>Other relevant resources on the topic</title>
+
+ <para>All JBoss Developer Studio/JBoss Tools documentation you can find on<ulink url="http://docs.jboss.org/tools/">JBoss Tools project page </ulink>.</para>
+ <para>The latest documentation builds are available on<ulink url="http://download.jboss.org/jbosstools/nightly-docs/">nightly docs page</ulink>.</para>
+
+ </section>
+
+</chapter>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/master.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/master.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/master.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,80 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+[
+<!ENTITY introduction SYSTEM "introduction.xml">
+<!ENTITY projects SYSTEM "projects.xml">
+<!ENTITY editors SYSTEM "editors.xml">
+<!ENTITY modules SYSTEM "modules.xml">
+<!ENTITY code_generation SYSTEM "code_generation.xml">
+<!ENTITY config_file_debugger SYSTEM "config_file_debugger.xml">
+<!ENTITY page_links_recognizer SYSTEM "page_links_recognizer.xml">
+<!ENTITY project_verification SYSTEM "project_verification.xml">
+<!ENTITY rel_resources_links SYSTEM "rel_resources_links.xml">
+
+<!ENTITY seamlink "../../seam/html_single/index.html">
+<!ENTITY aslink "../../as/html_single/index.html">
+<!ENTITY esblink "../../esb_ref_guide/html_single/index.html">
+<!ENTITY gsglink "../../GettingStartedGuide/html_single/index.html">
+<!ENTITY hibernatelink "../../hibernatetools/html_single/index.html">
+<!ENTITY jbpmlink "../../jbpm/html_single/index.html">
+<!ENTITY jsflink "../../jsf/html_single/index.html">
+<!ENTITY jsfreflink "../../jsf_tools_ref_guide/html_single/index.html">
+<!ENTITY jsftutoriallink "../../jsf_tools_tutorial/html_single/index.html">
+<!ENTITY strutsreflink "../../struts_tools_ref_guide/html_single/index.html">
+<!ENTITY strutstutoriallink "../../struts_tools_tutorial/html_single/index.html">
+<!ENTITY migrationlink "../../Exadel-migration/html_single/index.html">
+
+]>
+<book>
+ <bookinfo>
+ <title>Struts Tools Reference Guide</title>
+
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata format="PNG" fileref="images/jbosstools_logo.png" />
+ </imageobject>
+ <imageobject role="html">
+ <imagedata/>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author><firstname>Anatoly</firstname><surname>Fedosik</surname></author>
+ <author><firstname>Olga</firstname><surname>Chikvina</surname></author>
+ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author>
+
+ <copyright>
+ <year>2007</year>
+ <year>2008</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo>
+ Version: 3.1.0.GA
+ </releaseinfo>
+
+<abstract>
+ <title/>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/struts_tools_ref_gui...">PDF version</ulink>
+ </para>
+</abstract>
+
+
+ </bookinfo>
+
+ <toc/>
+
+ &introduction;
+ &projects;
+ &editors;
+ &modules;
+ &code_generation;
+ &config_file_debugger;
+ &page_links_recognizer;
+ &project_verification;
+ &rel_resources_links;
+</book>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/master_output.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/master_output.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/master_output.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,1332 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+[
+<!ENTITY introduction SYSTEM "modules/introduction.xml">
+<!ENTITY projects SYSTEM "modules/projects.xml">
+<!ENTITY editors SYSTEM "modules/editors.xml">
+<!ENTITY modules SYSTEM "modules/modules.xml">
+<!ENTITY code_generation SYSTEM "modules/code_generation.xml">
+<!ENTITY config_file_debugger SYSTEM "modules/config_file_debugger.xml">
+<!ENTITY page_links_recognizer SYSTEM "modules/page_links_recognizer.xml">
+<!ENTITY project_verification SYSTEM "modules/project_verification.xml">
+<!ENTITY rel_resources_links SYSTEM "modules/rel_resources_links.xml">
+
+<!ENTITY seamlink "../../seam/html_single/index.html">
+<!ENTITY aslink "../../as/html_single/index.html">
+<!ENTITY esblink "../../esb_ref_guide/html_single/index.html">
+<!ENTITY gsglink "../../GettingStartedGuide/html_single/index.html">
+<!ENTITY hibernatelink "../../hibernatetools/html_single/index.html">
+<!ENTITY jbpmlink "../../jbpm/html_single/index.html">
+<!ENTITY jsflink "../../jsf/html_single/index.html">
+<!ENTITY jsfreflink "../../jsf_tools_ref_guide/html_single/index.html">
+<!ENTITY jsftutoriallink "../../jsf_tools_tutorial/html_single/index.html">
+<!ENTITY strutsreflink "../../struts_tools_ref_guide/html_single/index.html">
+<!ENTITY strutstutoriallink "../../struts_tools_tutorial/html_single/index.html">
+<!ENTITY migrationlink "../../Exadel-migration/html_single/index.html">
+
+]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff">
+ <bookinfo>
+ <title>Struts Tools Reference Guide</title>
+
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
+ </imageobject>
+ <imageobject role="html">
+ <imagedata></imagedata>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author><firstname>Anatoly</firstname><surname>Fedosik</surname></author>
+ <author><firstname>Olga</firstname><surname>Chikvina</surname></author>
+ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author>
+
+ <copyright>
+ <year>2007</year>
+ <year>2008</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo><diffmk:wrapper diffmk:change="changed">
+ Version: 3.1.0.GA
+ </diffmk:wrapper></releaseinfo>
+
+<abstract>
+ <title></title>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/struts_tools_ref_gui...">PDF version</ulink>
+ </para>
+</abstract>
+
+
+ </bookinfo>
+
+ <toc></toc>
+
+
+<chapter id="intoduction" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_ref_guide/en/modules/introduction.xml">
+ <?dbhtml filename="introduction.html"?>
+
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Introduction</title>
+
+ <para>If you prefer to develop web applications using Struts technology JBoss Tools also meet
+ your needs. The professional developer toolset provides all necessary editors and wizards
+ for creating Struts resources that enhances the process of building high-quality web
+ applications.</para>
+ <note>
+ <title>Note:</title>
+ <para>Note that JBoss Tools support the Struts 1.1, 1.2.x versions.</para>
+ </note>
+
+ <para>In this guide you will learn how to take advantage of Struts support that <property moreinfo="none">JBoss Tools</property>
+ provide.</para>
+
+ <section id="struts_key_features">
+ <title>Key Features of Struts Tools</title>
+
+ <para>For a start, we propose you to look through the table of main features of Struts
+ Tools:</para>
+
+ <table>
+
+ <title>Key Functionality for Struts Tools</title>
+ <tgroup cols="3">
+
+ <colspec align="left" colnum="1" colwidth="2*"></colspec>
+ <colspec colnum="2" colwidth="4*"></colspec>
+ <colspec align="left" colnum="3" colwidth="2*"></colspec>
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+ <entry>Chapter</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><para>Struts Support</para></entry>
+ <entry><para>Step-by-step wizards for creating a new struts project with a number
+ of predefined templates, importing existing ones and adding struts
+ capabilities to non-struts web projects.</para></entry>
+ <entry>
+ <link linkend="projects">struts support</link>
+ </entry>
+ </row>
+
+ <row>
+ <entry><para>Support for Struts Configuration File</para></entry>
+ <entry><para>Working on file using three modes: diagram, tree and source.
+ Synchronization between the modes and full control over the code. Easy
+ moving around the diagram using the Diagram Navigator. Working with
+ struts projects that have multiple modules. Possibility to use Struts
+ configuration file debugger allowing to set break points on struts
+ diagram and then launch the server in debug mode.</para></entry>
+ <entry>
+ <link linkend="struts_config_editor">graphical editor for struts</link>
+ <link linkend="config_file_debugger">configuration file debugger</link>
+ </entry>
+ </row>
+
+ <row>
+ <entry><para>Support for Struts modules</para></entry>
+ <entry><para>A Struts module (struts-config.xml) is automatically created while
+ creating a new project. There is also possibility to add new ones or edit
+ already existing modules in your existing project or while importing Struts project.</para></entry>
+ <entry>
+ <link linkend="modules">modules</link>
+ </entry>
+ </row>
+
+ <row>
+ <entry><para>Verification and Validation</para></entry>
+ <entry><para>All occurring errors will be immediately reported by verification
+ feature, no matter in what view you are working. Constant validation and
+ errors checking allows to catch many of the errors during development
+ process that significantly reduces development time.</para></entry>
+ <entry>
+ <link linkend="project_verification">verification and validation</link>
+ </entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </section>
+
+ <section>
+ <title>Other relevant resources on the topic</title>
+
+ <para>All JBoss Developer Studio/JBoss Tools documentation you can find on<ulink url="http://docs.jboss.org/tools/">JBoss Tools project page </ulink>.</para>
+ <para>The latest documentation builds are available on<ulink url="http://download.jboss.org/jbosstools/nightly-docs/">nightly docs page</ulink>.</para>
+
+ </section>
+
+</chapter>
+
+
+<chapter id="projects" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_ref_guide/en/modules/projects.xml">
+ <?dbhtml filename="projects.html"?>
+
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Projects</title>
+
+ <para>JBoss Tools provide the following functionality when working with Struts:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Create new <property moreinfo="none">Struts projects</property></para>
+ </listitem>
+ <listitem>
+ <para>Import (open) existing Struts projects. You can import any project
+ structure</para>
+ </listitem>
+ <listitem>
+ <para>Add <property moreinfo="none">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>Now, we'll focus on all these points more fully.</para>
+
+ <section id="CreatingANewStrutsProjec745t">
+
+ <title>Creating a New Struts Project</title>
+
+
+ <para>JBoss Tools provides a New Struts Project Wizard that radically simplifies the process
+ for getting started with a new Struts project. You just need to follow these steps:</para>
+ <itemizedlist>
+ <listitem>
+ <para>Select<emphasis>
+ <property moreinfo="none">File > New > Project...</property>
+ </emphasis> from the menu bar. Then, select <emphasis>
+ <property moreinfo="none">JBoss Tools Web > Struts > Struts Project</property>
+ </emphasis> in this dialog box. Click <emphasis>
+ <property moreinfo="none">Next</property>: </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <figure float="0">
+ <title>Selecting Struts Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>On this form, provide the <property moreinfo="none">Project Name</property>. You can also
+ select where to create the project or use the default path.</para>
+ <para>Next to <property moreinfo="none">Struts Environment</property> set which Struts version to
+ use.</para>
+ </listitem>
+ </itemizedlist>
+
+ <figure float="0">
+ <title>Creating Struts Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <tip>
+ <title>Tip:</title>
+ <para>Don't put spaces in project names since some OS could experience problems
+ with their processing and searching these files.</para>
+ </tip>
+
+ <para>You can select the KickStart template, then the project created will include a simple
+ Hello World type application that is ready to run.</para>
+
+ <figure float="0">
+ <title>Choosing Struts Template </title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_3_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem>
+ <para>Next, you 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 moreinfo="none">"Target Server"</property>
+ </emphasis> check box if for some reason you don't want to register
+ your application at this point.</para>
+ </listitem>
+ </itemizedlist>
+ <figure float="0">
+ <title>Registering The Project at Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>On the next form, you can select the TLD files to include in this
+ project:</para>
+ </listitem>
+ </itemizedlist>
+ <figure float="0">
+ <title>Selecting Tag Libraries</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_5.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>After the project is created, you should have the following project structure (if you
+ used the KickStart template):</para>
+
+ <figure float="0">
+ <title>Project Structure</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_6.png"></imagedata>
+ </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">
+
+ <title>Importing an Existing Struts Project with Any Structure</title>
+
+ <para>For detailed information on migration projects to JBoss Developer Studio see <ulink url="../../Exadel-migration/html_single/index.html">Migration Guide</ulink>.</para>
+
+ </section>
+ <section id="AddingStrutsCapabilityToAnExistingWebApplication532">
+
+ <title>Adding Struts Capability to an Existing Web Application</title>
+
+ <para>Here, we'll consider how to add Struts functionality (Struts libraries, tag
+ libraries and a Struts configuration file) to any existing Web application project in
+ your Eclipse workspace.</para>
+
+ <para>By adding a Struts Nature to your project, you can now edit files using JBoss Tools
+ editors, such as the <link linkend="struts_config_editor">Struts configuration
+ editor</link> and the JBoss Tools JSP editor. To take advantage of this just right-click
+ the project and select <emphasis>
+ <property moreinfo="none">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 a Web Struts project from your one.</para>
+
+ <figure float="0">
+ <title>Adding Struts Capabilities</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_7.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>In the wizard you should point to location of your deployment descriptor file web.xml
+ and name of the project.</para>
+
+ <figure float="0">
+ <title>Choosing Project Location</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_8.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>After hitting <emphasis>
+ <property moreinfo="none">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 moreinfo="none">Add Struts Support</property>
+ </emphasis> button.</para>
+ <figure float="0">
+ <title>Project Modules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_9.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Here you can select what Struts <property moreinfo="none">Version</property>, <property moreinfo="none">Servlet
+ Class</property>, <property moreinfo="none">URL Pattern</property> and <property moreinfo="none">TLD</property>s to add
+ to this project.</para>
+
+ <figure float="0">
+ <title>Selecting Struts Support Options</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_10.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>When done, you will see the default Struts module configuration information. See how
+ to Edit <link linkend="modules">Struts modules</link>.</para>
+
+ <figure float="0">
+ <title>Project Configuration Information</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_11.png"></imagedata>
+ </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. If you want the libraries (.jar
+ files) will be automatically added to your project, click on the checkbox <emphasis>
+ <property moreinfo="none">Add Libraries</property>.</emphasis></para>
+
+ <figure float="0">
+ <title>Registering the Project at Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_12.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>When done, you can open end edit the struts-config.xml file using useful Struts
+ configuration file editor provided by JBDS. (The Struts configuration is shown below in
+ the Tree viewer).</para>
+
+ <figure float="0">
+ <title>Struts-config.xml File</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_13.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section>
+ <title>Relevant Resources Links</title>
+
+ <para>You can find more in-depth explanation on how to work with special wizards, editors and views that can
+ be used in various scenarios while developing Struts applications in our <ulink url="../../jsf/html_single/index.html">Visual Web Tools guide</ulink>.</para>
+ </section>
+</chapter>
+
+
+<chapter id="editors" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_ref_guide/en/modules/editors.xml">
+ <?dbhtml filename="editors.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Editors</title>
+ <para>In this chapter we'll introduce you to featured graphical editors for specific
+ Struts files such as Struts Configuration files, Tiles files, Struts Validation files and web.xml.</para>
+
+ <section id="webxml_editor">
+ <title>Web.xml Editor</title>
+
+ <para>The <emphasis>
+ <property moreinfo="none">web.xml</property></emphasis> file inside the <emphasis>
+ <property moreinfo="none">WEB-INF</property></emphasis> folder is a deployment descriptor file for a Web Application. It
+ describes the servlets and other components and deployment properties that make up your application.</para>
+
+ <para><property moreinfo="none">JBoss Tools</property> add the <emphasis>
+ <property moreinfo="none">web.xml</property></emphasis> file to created Struts project automatically and provides a special editor for its editing.
+ See the Visual Web Tools guide that gives a descriptive information on the <ulink url="../../jsf/html_single/index.html#GraphicalWebApplicationFileEditor">web.xml editor</ulink>.</para>
+ </section>
+
+ <section id="struts_config_editor">
+
+ <title>Graphical Editor for Struts Configuration Files</title>
+ <para>First, let's dwell on the Struts Configuration file editor.</para>
+ <para>This editor has three views with different representation of <emphasis>
+ <property moreinfo="none">struts-config.xml</property>: </emphasis>Diagram, Tree and Source. The
+ views can be selected via the tabs at the bottom of the editor. Any changes made in one
+ view are immediately visible when you switch to any other view.</para>
+
+ <para>Now, we'll consider every view in more detail.</para>
+ <section id="StrutsDiagramMode453">
+
+ <title>Diagram View</title>
+
+ <para>The Diagram view graphically displays the Web flow of the application defined in
+ the Struts configuration file.</para>
+
+ <figure float="0">
+ <title>Diagram View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_14.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The Diagram view allows to edit navigation in your Struts application. 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 float="0">
+ <title>Diagram Context Menu</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_15.png"></imagedata>
+ </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. </para>
+
+ <figure float="0">
+ <title>Editor Icons</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_16.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>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 moreinfo="none">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>
+
+
+ </section>
+ <section id="StrutsTreeMode42">
+
+ <title>Tree View</title>
+
+ <para>The Tree view represents the different elements of the Struts application that 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 float="0">
+ <title>Tree View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_17.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can 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 float="0">
+ <title>Tree Context Menu</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_18.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Let's consider the tree on the left more closely.</para>
+
+ <itemizedlist>
+ <listitem><para>Under the <emphasis>
+ <property moreinfo="none">data-sources</property></emphasis> node you can create a Data Source object that will be configured
+ and made available as a servlet context attribute.</para></listitem>
+
+ <listitem><para>The <emphasis>
+ <property moreinfo="none">form-beans</property></emphasis> node is meant for creating a set of form bean descriptors for this module.
+ Every created element under this node is a JavaBean that implements the org.apache.struts.action.ActionForm class.
+ Use the Properties editor on the right to adjust properties specific to every created form-bean.</para></listitem>
+
+ <listitem><para>The <emphasis>
+ <property moreinfo="none">global-exceptions</property></emphasis> node is intended for registering the handlers for the exceptions
+ that might be thrown by an Action object.</para></listitem>
+
+ <listitem><para>Use the <emphasis>
+ <property moreinfo="none">global-forwards</property></emphasis> node to add, edit or delete a global forwards that represent
+ ActionForward objects available to all Action objects as a return value.</para></listitem>
+
+ <listitem><para>The <emphasis>
+ <property moreinfo="none">controller</property></emphasis> node allows you to configure the controller properties.</para></listitem>
+
+ <listitem><para>Under the <emphasis>
+ <property moreinfo="none">resources</property></emphasis> node you can add, delete, or edit message resources.</para></listitem>
+
+ <listitem><para>Under the <emphasis>
+ <property moreinfo="none">plug-ins</property></emphasis> node you can define a Struts plug-in. Right-click the node, select <emphasis>
+ <property moreinfo="none">Create Plug-in</property></emphasis>
+ and specify the plug-ib <emphasis>
+ <property moreinfo="none">Id</property></emphasis> and <emphasis>
+ <property moreinfo="none">ClassName</property></emphasis> by pointing to the Java class which implements the org.apache.struts.action.PlugIn interface. </para></listitem>
+
+ </itemizedlist>
+ </section>
+ <section id="StrutsSourceMode9655">
+
+ <title>Source View</title>
+
+ <para>In the Source view, you have complete editing control of the underlying XML
+ coding.</para>
+
+ <figure float="0">
+ <title>Source View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_19.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <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>
+ <para>You can take advantage of <ulink url="../../jsf/html_single/index.html#CodeAssistAndDynamicCodeAssist42BasedOnProjectData">code assist</ulink>.</para>
+ <figure float="0">
+ <title>Code Assist</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_20.png" scale="85"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The editor will also immediately flag any errors.</para>
+
+ <figure float="0">
+ <title>Errors in Source View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_21.png" scale="85"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Finally, you can use the Outline view with the editor to easily navigate through
+ the file.</para>
+
+ <figure float="0">
+ <title>Outline View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_22.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Find more information about editor features <ulink url="../../jsf/html_single/index.html#editors_features">in the editor features chapter</ulink>.</para>
+ </section>
+ </section>
+
+ <section id="GraphicalEditorForTilesFiles132">
+
+ <title>Graphical Editor for Tiles Files</title>
+ <para>Here, you'll know how to make use of the special graphical editor for Tiles configuration files.</para>
+ <para>The editor has three main views: Tree, Diagram and Source.
+ The views can be selected via the tabs at the bottom of the editor. Any changes made in
+ one view are immediately visible when you switch to any other view.</para>
+
+ <para>Before we consider each view of the editor, let's look at the way of creating new Tiles files.</para>
+ <section id="CreateNewTilesFile1422">
+
+ <title>Create New Tiles File</title>
+
+ <para>To create new Tiles files, right click any folder and select <emphasis>
+ <property moreinfo="none">New > Tiles File</property>. </emphasis></para>
+ <figure float="0">
+ <title>Creating a New Tiles File</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_23.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="StrutsTreeView896">
+
+ <title>Tree View</title>
+
+ <para>The Tree view represents the different elements of the Tiles file that 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 float="0">
+ <title>Tree View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_24.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>To edit the file, simply right click any node and select among the available
+ actions.</para>
+ <figure float="0">
+ <title>Editing in Tiles Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_25.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="StrutsDiagramView4643">
+
+ <title>Diagram View</title>
+
+ <para>The Diagram view allows you to create complex Tiles files in the form of a
+ diagram.</para>
+ <figure float="0">
+ <title>Diagram Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_26.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>To create new definitions, simply right click anywhere in the diagram.</para>
+ <figure float="0">
+ <title>Creating New Definition</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_27.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can also use the Diagram toolbar to make editing easier.</para>
+ <figure float="0">
+ <title>Diagram Toolbar</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_28.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> It contains four icons for changing the cursor state. The first one is the
+ default cursor state for selecting existing nodes. The second icon is marquee
+ selector. The third is used for creating new connections and the last one is for
+ adding definition template to the content.</para>
+ </section>
+ <section id="StrutsSource75">
+
+ <title>Source</title>
+
+ <para>The other view of the <property moreinfo="none">Tiles editor</property> is the Source view that
+ gives you full control over the source. Any changes here will immediately appear in
+ other modes when you switch to them.</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>
+
+ <figure float="0">
+ <title>Source View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_29.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para><ulink url="../../jsf/html_single/index.html#CodeAssistAndDynamicCodeAssist42BasedOnProjectData">Code
+ assist</ulink> is available in the Source mode.</para>
+ <figure float="0">
+ <title>Code Assist</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_30.png" scale="85"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Any errors are immediately reported as shown below:</para>
+ <figure float="0">
+ <title>Errors Reporting</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_31.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can also use the Outline view together with the editor's Source mode.
+ It provides an easier navigation through the file.</para>
+ <figure float="0">
+ <title>Outline View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_32.png" scale="85"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ </section>
+
+ <section id="GraphicalEditorForStrutsValidationFiles86">
+
+ <title>Graphical Editor for Struts Validation Files</title>
+
+ <para>Providing full support for development Struts applications JBoss Tools comes with a
+ visual validation editor. To open the editor double-click on the validation file or if you don't have it create a new one.</para>
+
+ <para>To create a new validation file, right click any folder in
+ Project Explorer and select <emphasis>
+ <property moreinfo="none">File > New > Other...</property>
+ </emphasis>from the context menu and then <emphasis>
+ <property moreinfo="none">JBoss Tools Web > Struts > Validation File</property>. </emphasis></para>
+ <figure float="0">
+ <title>Creating New Validation File</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_33.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The validation editor works with five modes: Formsets, Validators, Constants and
+ standard Tree and Source that you can easily switch over using tabs at the bottom of the
+ editor.</para>
+ <para>The Formsets view shows forms and their elements on the left side and the dialogue for
+ defining their validation rules on the right side.</para>
+ <figure float="0">
+ <title>Formsets View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_34.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The Constants view let you set constant values for your validation rules.</para>
+ <figure float="0">
+ <title>Constansts View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_35.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The validation file can also be viewed in a Tree view.</para>
+ <figure float="0">
+ <title>Tree View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_36.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>At any point you have full control over the source by switching to the Source view.
+ Any editing in this view will immediately be available in other views of the editor.</para>
+ <figure float="0">
+ <title>Source View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_37.png" scale="85"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can also open your own custom or Struts-standard <emphasis>
+ <property moreinfo="none">validation-rules.xml</property>
+ </emphasis> file.</para>
+ <para>The Validators view shows the validation rules for a selected validator. You can of
+ course add your own rules.</para>
+ <figure float="0">
+ <title>Validators View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_38.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Here are the validation rules shown in the Source mode.</para>
+ <figure float="0">
+ <title>Validation Rules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_39.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+</chapter>
+
+
+<chapter id="modules" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_ref_guide/en/modules/modules.xml">
+ <?dbhtml filename="modules.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Modules</title>
+
+ <para>JBoss Tools support working with Struts projects that have
+ multiple modules. 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>
+ <para>Now, let's discuss this functionality in more detail.</para>
+ <section id="WhenImportingAStrutsProject432">
+
+ <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 float="0">
+ <title>Configuring Project Modules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_40.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="EditingModulesInAnExistingProject1">
+
+ <title>Editing Modules in an Existing Project</title>
+ <para>To edit modules in an existing project, right click the project and
+ select <emphasis>
+ <property moreinfo="none">JBoss Tools > Modules Configuration</property>.
+ </emphasis></para>
+ <figure float="0">
+ <title>Choosing Modules Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_41.png"></imagedata>
+ </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 float="0">
+ <title>Modules Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_42.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="AddingNewModules1">
+
+ <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 moreinfo="none">New > Struts Config</property>. </emphasis></para>
+ <figure float="0">
+ <title>Adding New Modules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_43.png"></imagedata>
+ </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 float="0">
+ <title>Adding New Modules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_44.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+</chapter>
+
+
+<chapter id="code_generation" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_ref_guide/en/modules/code_generation.xml">
+ <?dbhtml filename="code_generation.html"?>
+
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Code Generation</title>
+
+ <para>JBoss Tools comes with a <property moreinfo="none">code generation</property>
+ feature. You can generate stub code for Struts Actions, FormBeans, Forwards
+ and Exceptions.</para>
+
+ <para>The code generation that JBoss tooling provides is based on Velocity templates
+ which can be modified for your use. The templates are located at <emphasis>
+ <property moreinfo="none"> {JBossStudioHome} > 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 moreinfo="none">Generate Java Code....</property>
+ </emphasis></para>
+
+ <figure float="0">
+ <title>Selecting Generate Java Code</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_45.png"></imagedata>
+ </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 float="0">
+ <title>Generate - Step 1</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_46.png"></imagedata>
+ </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 float="0">
+ <title>Generation Finished</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_47.png"></imagedata>
+ </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 moreinfo="none">Generate Java Code...</property>
+ </emphasis> from the context menu.</para>
+
+ <figure float="0">
+ <title>Generation For Individual Struts Artifact</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_48.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The same can be done from within the Tree viewer for the editor of the Struts
+ configuration file.</para>
+
+ <figure float="0">
+ <title>Generation in Struts Config Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_49.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+</chapter>
+
+<chapter id="config_file_debugger" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_ref_guide/en/modules/config_file_debugger.xml">
+ <?dbhtml filename="config_file_debugger.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Struts Configuration File Debugger</title>
+
+ <para>JBoss Tools come with <property moreinfo="none">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 moreinfo="none">Breakpoint</property>. </emphasis></para>
+ <figure float="0">
+ <title>Adding Breakpoint</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_50.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+</chapter>
+
+<chapter id="page_links_recognizer" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_ref_guide/en/modules/page_links_recognizer.xml">
+ <?dbhtml filename="page_links_recognizer.html"?>
+
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Customizable Page Links Recognizer</title>
+
+ <para><property moreinfo="none">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 moreinfo="none">Window > Preferences</property>
+ </emphasis> from the menu bar and then selecting <emphasis>
+ <property moreinfo="none">JBoss Tools > Web > Struts > Customization</property>
+ </emphasis> from the Preferences dialog box.</para>
+ <figure float="0">
+ <title>Customization Panel</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_51.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+</chapter>
+
+<chapter id="project_verification" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_ref_guide/en/modules/project_verification.xml">
+ <?dbhtml filename="project_verification.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Struts Project Verification</title>
+
+ <para>In this section we'll consider one more functionality that JBoss Tools provide for Struts
+ projects, namely adjusting projects verification.</para>
+
+ <para>To configure Struts project verification select <emphasis>
+ <property moreinfo="none">Window > Preferences</property>
+ </emphasis> from the menu bar, select <emphasis>
+ <property moreinfo="none">JBoss Tools > Web > Verification</property>
+ </emphasis> from the Preferences dialog box and then expand the
+ Struts Rules node.</para>
+ <figure float="0">
+ <title>Struts Rules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_8.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Suppose you are working in the Source viewer for a Struts
+ configuration file as shown below:</para>
+ <figure float="0">
+ <title>Struts Configuration File</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_9.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>While typing a class name or entering it from the graphical editor,
+ you might make a minor typo (like <emphasis role="italic">
+ <property moreinfo="none">"sample.GreetingAction1"</property>
+ </emphasis> instead of <emphasis role="italic">
+ <property moreinfo="none">"sample.GreetingAction"</property>
+ </emphasis>). After saving the file,
+ <property moreinfo="none">verification</property> checks to make sure everything is
+ correct and finds the error below:</para>
+ <figure float="0">
+ <title>Error Reporting</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_10.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Notice that the Package Explorer View shows a marked folder and a
+ marked file where the error is.</para>
+ <para>You can place the cursor over the line with the error to view a
+ detailed error message:</para>
+ <figure float="0">
+ <title>Error Message</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_11.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The verification also checks to make sure you have specified the
+ correct JSP page for the forward:</para>
+ <figure float="0">
+ <title>JSP Page Verification</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_12.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Once you place the cursor over the line, you can see the error
+ message:</para>
+ <figure float="0">
+ <title>Error Message</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_13.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>You can always invoke the verification by switching to the Diagram
+ viewer, right-clicking and selecting <emphasis>
+ <property moreinfo="none">Verify</property>
+ </emphasis> from the context menu:</para>
+ <figure float="0">
+ <title>Verify Command</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_14.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+</chapter>
+
+<chapter id="rel_resources_links" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_ref_guide/en/modules/rel_resources_links.xml">
+ <?dbhtml filename="rel_resources_links.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Relevant Resources Links</title>
+
+ <para>Find out necessary information on <ulink url="http://struts.apache.org/">Struts
+ technology</ulink> if you don't know enough.</para>
+
+ <para>In summary, this reference should help you to get familiar with those parts of
+ <property moreinfo="none">JBoss Tools</property> which are meant for development with Struts
+ technology. If you've carefully gone through the document, you should know
+ now how to create/import Struts project or enable Struts capabilities for an
+ existing web project as well as organize and edit all necessary staff for your
+ Struts application using a set of views and editors provided by <property moreinfo="none">JBoss
+ Tools</property>.</para>
+
+ <para>If you'd like to contribute your feedback is always appreciated. You can
+ leave your questions and suggestions on our
+ <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">
+ Forum</ulink>.</para>
+ <para>We hope, this guide helped you to get started with the JBoss Struts Tools.
+ Besides, for additional information you are welcome on
+ <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para>
+</chapter>
+
+</book>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/modules.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/modules.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/modules.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,99 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="modules">
+ <?dbhtml filename="modules.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Modules</title>
+
+ <para>JBoss Tools support working with Struts projects that have
+ multiple modules. 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>
+ <para>Now, let's discuss this functionality in more detail.</para>
+ <section id="WhenImportingAStrutsProject432">
+
+ <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">
+
+ <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">
+
+ <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>
+</chapter>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/page_links_recognizer.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/page_links_recognizer.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/page_links_recognizer.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="page_links_recognizer">
+ <?dbhtml filename="page_links_recognizer.html"?>
+
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <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>
+</chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/project_verification.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/project_verification.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/project_verification.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,117 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="project_verification">
+ <?dbhtml filename="project_verification.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Struts Project Verification</title>
+
+ <para>In this section we'll consider one more functionality that JBoss Tools provide for Struts
+ projects, namely adjusting projects verification.</para>
+
+ <para>To configure Struts project verification select <emphasis>
+ <property>Window > Preferences</property>
+ </emphasis> from the menu bar, select <emphasis>
+ <property>JBoss Tools > Web > Verification</property>
+ </emphasis> from the Preferences dialog box and then expand the
+ Struts Rules node.</para>
+ <figure>
+ <title>Struts Rules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_8.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Suppose you are working in the Source viewer for a Struts
+ configuration file as shown below:</para>
+ <figure>
+ <title>Struts Configuration File</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_9.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>While typing a class name or entering it from the graphical editor,
+ you might make a minor typo (like <emphasis role="italic">
+ <property>"sample.GreetingAction1"</property>
+ </emphasis> instead of <emphasis role="italic">
+ <property>"sample.GreetingAction"</property>
+ </emphasis>). After saving the file,
+ <property>verification</property> checks to make sure everything is
+ correct and finds the error below:</para>
+ <figure>
+ <title>Error Reporting</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_10.png"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Notice that the Package Explorer View shows a marked folder and a
+ marked file where the error is.</para>
+ <para>You can place the cursor over the line with the error to view a
+ detailed error message:</para>
+ <figure>
+ <title>Error Message</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_11.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The verification also checks to make sure you have specified the
+ correct JSP page for the forward:</para>
+ <figure>
+ <title>JSP Page Verification</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_12.png"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Once you place the cursor over the line, you can see the error
+ message:</para>
+ <figure>
+ <title>Error Message</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_13.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>You can always invoke the verification by switching to the Diagram
+ viewer, right-clicking and selecting <emphasis>
+ <property>Verify</property>
+ </emphasis> from the context menu:</para>
+ <figure>
+ <title>Verify Command</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_14.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+</chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/projects.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/projects.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/projects.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,275 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="projects">
+ <?dbhtml filename="projects.html"?>
+
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Projects</title>
+
+ <para>JBoss Tools provide the following functionality when working with Struts:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Create new <property>Struts projects</property></para>
+ </listitem>
+ <listitem>
+ <para>Import (open) existing Struts projects. 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>Now, we'll focus on all these points more fully.</para>
+
+ <section id="CreatingANewStrutsProjec745t">
+
+ <title>Creating a New Struts Project</title>
+
+
+ <para>JBoss Tools provides a New Struts Project Wizard that radically simplifies the process
+ for getting started with a new Struts project. You just need to follow these steps:</para>
+ <itemizedlist>
+ <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>
+ </itemizedlist>
+ <figure>
+ <title>Selecting Struts Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>On this form, provide the <property>Project Name</property>. You can also
+ select where to create the project or use the default path.</para>
+ <para>Next to <property>Struts Environment</property> set which Struts version to
+ use.</para>
+ </listitem>
+ </itemizedlist>
+
+ <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 since some OS could experience problems
+ with their processing and searching these files.</para>
+ </tip>
+
+ <para>You can select the KickStart template, then the project created will include a simple
+ Hello World type application that is ready to run.</para>
+
+ <figure>
+ <title>Choosing Struts Template </title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_3_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem>
+ <para>Next, you 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>
+ </itemizedlist>
+ <figure>
+ <title>Registering The Project at Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>On the next form, you can select the TLD files to include in this
+ project:</para>
+ </listitem>
+ </itemizedlist>
+ <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">
+
+ <title>Importing an Existing Struts Project with Any Structure</title>
+
+ <para>For detailed information on migration projects to JBoss Developer Studio see Migration Guide.</para>
+
+ </section>
+ <section id="AddingStrutsCapabilityToAnExistingWebApplication532">
+
+ <title>Adding Struts Capability to an Existing Web Application</title>
+
+ <para>Here, we'll consider how to add Struts functionality (Struts libraries, tag
+ libraries and a Struts configuration file) to any existing Web application project in
+ your Eclipse workspace.</para>
+
+ <para>By adding a Struts Nature to your project, you can now edit files using JBoss Tools
+ editors, such as the <link linkend="struts_config_editor">Struts configuration
+ editor</link> and the JBoss Tools JSP editor. To take advantage of this just 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 a Web Struts project from your one.</para>
+
+ <figure>
+ <title>Adding Struts Capabilities</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts/struts_7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>In the wizard you should point to location of your deployment descriptor file web.xml
+ and name of the project.</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 <property>Version</property>, <property>Servlet
+ Class</property>, <property>URL Pattern</property> and <property>TLD</property>s 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="modules">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. If you want the libraries (.jar
+ files) will be automatically added to your project, click on the checkbox <emphasis>
+ <property>Add Libraries</property>.</emphasis></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 end edit the struts-config.xml file using useful Struts
+ configuration file editor provided by JBDS. (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" scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section>
+ <title>Relevant Resources Links</title>
+
+ <para>You can find more in-depth explanation on how to work with special wizards, editors and views that can
+ be used in various scenarios while developing Struts applications in our Visual Web Tools guide.</para>
+ </section>
+</chapter>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/rel_resources_links.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/rel_resources_links.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/rel_resources_links.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="rel_resources_links">
+ <?dbhtml filename="rel_resources_links.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Relevant Resources Links</title>
+
+ <para>Find out necessary information on <ulink url="http://struts.apache.org/">Struts
+ technology</ulink> if you don't know enough.</para>
+
+ <para>In summary, this reference should help you to get familiar with those parts of
+ <property>JBoss Tools</property> which are meant for development with Struts
+ technology. If you've carefully gone through the document, you should know
+ now how to create/import Struts project or enable Struts capabilities for an
+ existing web project as well as organize and edit all necessary staff for your
+ Struts application using a set of views and editors provided by <property>JBoss
+ Tools</property>.</para>
+
+ <para>If you'd like to contribute your feedback is always appreciated. You can
+ leave your questions and suggestions on our <ulink
+ url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201"
+ >Forum</ulink>.</para>
+ <para>We hope, this guide helped you to get started with the JBoss Struts Tools. Besides, for additional information you are welcome on <ulink
+ url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para>
+</chapter>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/struts_project_verification.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/struts_project_verification.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/en-US/struts_project_verification.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,115 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="struts_project_verification">
+ <?dbhtml filename="struts_project_verification.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Struts Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Struts Project Verification</title>
+
+ <para>JBoss Developer Studio provides the same functionality for Struts
+ projects. To configure Struts project verification select <emphasis>
+ <property>Window > Preferences</property>
+ </emphasis> from the menu bar, select <emphasis>
+ <property>JBoss Tools > Web > Verification</property>
+ </emphasis> from the Preferences dialog box and then expand the
+ Struts Rules node.</para>
+ <figure>
+ <title>Struts Rules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_8.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Suppose you are working in the Source viewer for a Struts
+ configuration file as shown below:</para>
+ <figure>
+ <title>Struts Configuration File</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_9.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>While typing a class name or entering it from the graphical editor,
+ you might make a minor typo (like <emphasis role="italic">
+ <property>"sample.GreetingAction1"</property>
+ </emphasis> instead of <emphasis role="italic">
+ <property>"sample.GreetingAction"</property>
+ </emphasis>). After saving the file,
+ <property>verification</property> checks to make sure everything is
+ correct and finds the error below:</para>
+ <figure>
+ <title>Error Reporting</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_10.png"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Notice that the Package Explorer View shows a marked folder and a
+ marked file where the error is.</para>
+ <para>You can place the cursor over the line with the error to view a
+ detailed error message:</para>
+ <figure>
+ <title>Error Message</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_11.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The verification also checks to make sure you have specified the
+ correct JSP page for the forward:</para>
+ <figure>
+ <title>JSP Page Verification</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_12.png"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Once you place the cursor over the line, you can see the error
+ message:</para>
+ <figure>
+ <title>Error Message</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_13.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>You can always invoke the verification by switching to the Diagram
+ viewer, right-clicking and selecting <emphasis>
+ <property>Verify</property>
+ </emphasis> from the context menu:</para>
+ <figure>
+ <title>Verify Command</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/verif_valid/verif_valid_14.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+</chapter>
\ No newline at end of file
Modified: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/pom.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/pom.xml 2010-03-12 01:03:11 UTC (rev 20786)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/pom.xml 2010-03-12 01:05:58 UTC (rev 20787)
@@ -23,7 +23,7 @@
<profile>
<id>releaseJBDS</id>
<properties>
- <master>master.xml</master>
+ <master>master_output.xml</master>
<xsl-single>classpath:/xslt/com/jboss/tools/xhtml-single-release.xsl</xsl-single>
<xsl-chunked>classpath:/xslt/com/jboss/tools/xhtml-release.xsl</xsl-chunked>
<xsl-pdf>classpath:/xslt/com/jboss/tools/pdf.xsl</xsl-pdf>
@@ -85,9 +85,9 @@
<configuration>
<sourceDocumentName>${master}</sourceDocumentName>
- <sourceDirectory>${pom.basedir}/en</sourceDirectory>
+ <sourceDirectory>${pom.basedir}/en-US</sourceDirectory>
<imageResource>
- <directory>${pom.basedir}/en</directory>
+ <directory>${pom.basedir}/en-US</directory>
<includes>
<include>images/**/*</include>
</includes>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/publican.cfg
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/publican.cfg (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_ref_guide/publican.cfg 2010-03-12 01:05:58 UTC (rev 20787)
@@ -0,0 +1,7 @@
+# Config::Simple 4.59
+# Fri Nov 20 13:19:45 2009
+
+xml_lang: en-US
+type: Book
+brand: JBoss
+
14 years, 3 months
- 1
- 0
JBoss Tools SVN: r20786 - in branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial: en-US and 3 other directories.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-11 20:03:11 -0500 (Thu, 11 Mar 2010)
New Revision: 20786
Added:
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Author_Group.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Book_Info.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Preface.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Revision_History.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Struts_Tools_Tutorial.ent
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Struts_Tools_Tutorial.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/coding_files.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/compiling_and_running.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/generating_stub.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/favicon.ico
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/jbosstools_logo.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_1.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_2.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_3.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_4.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_5.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_6.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_validation/
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_validation/struts_validation.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_validation/struts_validation_1.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_validation/struts_validation_2.png
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/introduction.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/master.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/master_output.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/relevant_resources.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/struts_application.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/struts_validation.xml
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/publican.cfg
Removed:
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en/
Modified:
branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/pom.xml
Log:
now builds with publican as well
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Author_Group.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Author_Group.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Author_Group.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,6 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<authorgroup><author><firstname>Anatoly</firstname><surname>Fedosik</surname></author>
+ <author><firstname>Olga</firstname><surname>Chikvina</surname></author>
+ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author></authorgroup>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Book_Info.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Book_Info.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Book_Info.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<bookinfo><title>Struts Tools Tutorial</title><subtitle>Guides the reader through a tutorial on the Struts Tools set.</subtitle><productname>JBoss Developer Studio</productname><productnumber>3.0</productnumber><edition>1.0</edition><pubsnumber>0</pubsnumber><abstract><para>The Struts Tools Tutorial guide explains how to use the Struts Tools set and guides the reader through a tutorial.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Preface.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Preface.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Preface.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<preface><title>Preface</title><xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></xi:fallback></xi:include></preface>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Revision_History.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Revision_History.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Revision_History.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<appendix><title>Revision History</title><simpara><revhistory><revision><revnumber>0</revnumber><date>Fri Nov 20 2009</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Struts_Tools_Tutorial.ent
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Struts_Tools_Tutorial.ent (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Struts_Tools_Tutorial.ent 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "JBoss">
+<!ENTITY BOOKID "Struts_Tools_Tutorial">
+<!ENTITY YEAR "2010">
+<!ENTITY HOLDER "Red Hat">
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Struts_Tools_Tutorial.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Struts_Tools_Tutorial.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/Struts_Tools_Tutorial.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,15 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<book>
+<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="struts_application.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="generating_stub.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="coding_files.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="compiling_and_running.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="struts_validation.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="relevant_resources.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+</book>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/coding_files.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/coding_files.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/coding_files.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,433 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<chapter id="coding_files" xreflabel="coding_files">
+ <?dbhtml filename="coding_files.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Application</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Coding the Various Files</title>
+ <para>We will now code both the Java stub classes just generated, the JSP files left in as
+ placeholders from previous steps, and a new start JSP page we will have to create.</para>
+ <section id="JavaStubClasses">
+ <title>Java Stub Classes</title>
+ <itemizedlist>
+ <listitem>
+ <para>To finish the two Java classes, switch to the <emphasis>
+ <property>Package Explorer</property>
+ </emphasis> view and expand the <emphasis>
+ <property>JavaSource > sample</property>
+ </emphasis> folder</para>
+ </listitem>
+ </itemizedlist>
+ <section id="GetNameForm.java">
+ <title>GetNameForm.java</title>
+ <itemizedlist>
+ <listitem>
+ <para>Double-click <emphasis>
+ <property>GetNameForm.java</property>
+ </emphasis> for editing</para>
+ </listitem>
+
+ <listitem>
+ <para>You are looking at a Java stub class that was generated by JBoss
+ Tools. Now we are going to edit the file</para>
+ </listitem>
+
+ <listitem>
+ <para>Add the following attributes at the beginning of the class:</para>
+ </listitem>
+ </itemizedlist>
+ <programlisting role="JAVA"><![CDATA[private String name = "";
+]]></programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>Inside the reset method, delete the TO DO and throw lines and
+ add:</para>
+ </listitem>
+ </itemizedlist>
+ <programlisting role="JAVA"><![CDATA[this.name = "";
+]]></programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>Inside the validate method, delete the TO DO and throw lines and
+ add:</para>
+ </listitem>
+ </itemizedlist>
+ <programlisting role="JAVA"><![CDATA[ActionErrors errors = new ActionErrors();
+ return errors;
+]]></programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>Right-click and select <emphasis>
+ <property>Source > Generate Getters and Setters</property>
+ </emphasis>from the context menu</para>
+ </listitem>
+ <listitem>
+ <para>In the dialog box, check the check box for <emphasis>
+ <property>name</property>,</emphasis>
+ select First method for Insertion point, and click on the <emphasis>
+ <property>OK</property>
+ </emphasis> button</para>
+ </listitem>
+ </itemizedlist>
+ <para>The final <emphasis>
+ <property>GetNameForm.java</property></emphasis> file should look like this:</para>
+ <programlisting role="JAVA"><![CDATA[package sample;
+import javax.servlet.http.HttpServletRequest;
+import org.apache.struts.action.ActionErrors;
+import org.apache.struts.action.ActionMapping;
+
+public class GetNameForm extends org.apache.struts.action.ActionForm
+{
+
+ private String name = "";
+
+ public String getName()
+ {
+ return name;
+ }
+ public void setName(String name)
+ {
+ this.name = name;
+ }
+
+ public GetNameForm()
+ {
+ }
+
+ public void reset(ActionMapping actionMapping, HttpServletRequest request)
+ {
+ this.name = "";
+ }
+
+ public ActionErrors validate(ActionMapping actionMapping,
+ HttpServletRequest request)
+ {
+ ActionErrors errors = new ActionErrors();
+ return errors;
+ }
+}
+]]></programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>Save the file</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="GreetingAction.java">
+ <title>GreetingAction.java</title>
+ <itemizedlist>
+ <listitem>
+ <para>Open <emphasis>
+ <property>GreetingAction.java</property></emphasis> for editing</para>
+ </listitem>
+ <listitem>
+ <para>Inside the execute method, delete the TO DO lines and add the
+ following:</para>
+ </listitem>
+ </itemizedlist>
+
+ <programlisting role="JAVA"><![CDATA[String name = ((GetNameForm)form).getName();
+String greeting = "Hello, "+name+"!";
+((GetNameForm)form).setName(greeting);
+return mapping.findForward(FORWARD_sayHello);
+]]></programlisting>
+
+ <para>The final version of <emphasis>
+ <property>GreetingAction.java</property></emphasis> should look like this:</para>
+
+ <programlisting role="JAVA"><![CDATA[package sample;
+import javax.servlet.http.HttpServletRequest;
+import javax.servlet.http.HttpServletResponse;
+import org.apache.struts.action.ActionForm;
+import org.apache.struts.action.ActionForward;
+import org.apache.struts.action.ActionMapping;
+
+public class GreetingAction extends org.apache.struts.action.Action
+{
+
+ // Global Forwards
+ public static final String GLOBAL_FORWARD_getName = "getName";
+
+ // Local Forwards
+ public static final String FORWARD_sayHello = "sayHello";
+
+ public GreetingAction()
+ {
+ }
+ public ActionForward execute(ActionMapping mapping, ActionForm form,
+ HttpServletRequest request, HttpServletResponse response) throws Exception
+ {
+ String name = ((GetNameForm)form).getName();
+ String greeting = "Hello, "+name+"!";
+ ((GetNameForm)form).setName(greeting);
+ return mapping.findForward(FORWARD_sayHello);
+ }
+}
+]]></programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>Save the file</para>
+ </listitem>
+ <listitem>
+ <para>Close the editors for the two Java files</para>
+ </listitem>
+ </itemizedlist>
+ <para>The last thing left to do is to code the JSP files whose editors should still
+ be open from having been created as placeholders.</para>
+ </section>
+ </section>
+ <section id="JSPPages">
+ <title>JSP Pages</title>
+ <section id="inputname.jsp">
+ <title>inputname.jsp</title>
+ <para>In this page, the user will enter any name and click the <emphasis>
+ <property>submit</property>
+ </emphasis> button. Then, the greeting action will be called through the form.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>inputname.jsp</property>
+ </emphasis> tab in the Editing area to bring its editor forward</para>
+ </listitem>
+ <listitem>
+ <para>In the Web Projects view, expand <emphasis>
+ <property>StrutsHello > Configuration > default
+ > struts-config.xml > action-mappings</property>
+ </emphasis> and select <emphasis>
+ <property>/greeting</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Drag it and drop it between the quotes for the <emphasis role="italic">
+ <property>"action"</property>
+ </emphasis> attribute to the
+ <code><html:form></code>
+ element in the Source pane of the editor</para>
+ </listitem>
+ <listitem>
+ <para>Then type this text on a new line just below this line:</para>
+ <programlisting role="XML"><![CDATA[Input name:
+ ]]></programlisting>
+ </listitem>
+
+ <listitem>
+ <para>Select the <emphasis>
+ <property>Visual</property>
+ </emphasis> pane of the editor</para>
+ </listitem>
+ <listitem>
+ <para>Then, in the JBoss Tools Palette, expand the <emphasis>
+ <property>Struts Form</property>
+ </emphasis> library, select <emphasis>
+ <property>text</property>
+ </emphasis>, and drag it onto the box
+ <note>
+ <title>Note:</title>
+ <para>By default there are only four groups on the JBoss Tools
+ Palette. If you wish to make some group visible click the <emphasis>
+ <property>Show/Hide</property>
+ </emphasis> button on the top of palette and in the prompted
+ dialog check the group (or groups) you want to be shown.</para>
+ </note>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>JBoss Tools Palette</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_3.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>In the Insert Tag dialog box, type in name for property and select <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>In the StrutsForm library in the <property>JBoss Tools Palette</property>, select <emphasis>
+ <property>submit</property>
+ </emphasis>, and drag it to right after the text box in the Visual pane
+ of the editor</para>
+ </listitem>
+ <listitem>
+ <para>Right-click the <emphasis>
+ <property>submit</property>
+ </emphasis> button and select
+ <code><html:submit></code>
+ Attributes from the context menu</para>
+ </listitem>
+ <listitem>
+ <para>In the Attributes dialog box, select the <emphasis>
+ <property>value</property>
+ </emphasis> field and type in "Say Hello!" for its
+ value</para>
+ </listitem>
+ </itemizedlist>
+ <para>After tidying the page source, the Editor window for the file should look
+ something like this:</para>
+ <figure>
+ <title>Editor Window</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_4.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="greeting.jsp">
+ <title>greeting.jsp</title>
+ <para>Next, we will fill in the result page.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>greeting.jsp</property>
+ </emphasis> tab in the Editing area to bring its editor forward</para>
+ </listitem>
+ <listitem>
+ <para>Type in the following code:</para>
+ </listitem>
+ </itemizedlist>
+ <programlisting role="XML"><![CDATA[<html>
+<head>
+ <title>Greeting</title>
+</head>
+ <body>
+ <p>
+ </p>
+ </body>
+</html>
+]]></programlisting>
+
+ <para>To complete editing of this file, we will use macros from the <property>JBoss Tools
+ Palette</property>. This palette is a view that should be available to the right of the
+ editing area.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>Struts Common</property>
+ </emphasis> folder in the <property>JBoss Tools Palette</property> to open it</para>
+ </listitem>
+ <listitem>
+ <para>Position the cursor at the beginning of the <emphasis>
+ <property>greeting.jsp</property></emphasis> file in the
+ Source pane and then click on <emphasis>
+ <property>bean taglib</property></emphasis> in the <property>JBoss Tools
+ Palette</property></para>
+ </listitem>
+ </itemizedlist>
+ <para>This will insert the following line at the top of the file:</para>
+ <programlisting role="JAVA"><![CDATA[
+<%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %>
+]]></programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>Struts Bean</property>
+ </emphasis> folder in the <property>JBoss Tools Palette</property> to open it</para>
+ </listitem>
+ <listitem>
+ <para>Position the cursor inside the
+ <code><p></code>
+ element</para>
+ </listitem>
+ <listitem>
+ <para>Click on <emphasis>
+ <property>write</property></emphasis> in the <property>JBoss Tools Palette</property></para>
+ </listitem>
+ <listitem>
+ <para>Type in "GetNameForm" for the <emphasis
+ role="italic">
+ <property>name</property>
+ </emphasis> attribute and add a <emphasis role="italic">
+ <property>property</property>
+ </emphasis> attribute with "name" as its
+ value</para>
+ </listitem>
+ </itemizedlist>
+ <para>The editor should now look like this:</para>
+ <figure>
+ <title>Editor Window</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_5.png"
+ />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="index.jsp">
+ <title>index.jsp</title>
+ <para>Finally, we will need to create and edit an <emphasis>
+ <property>index.jsp</property></emphasis> page. This page will use
+ a Struts forward to simply redirect us to the getName global forward.</para>
+ <itemizedlist>
+ <listitem>
+ <para>In the Web Projects view, right-click on <emphasis>
+ <property>StrutsHello > WEB-ROOT(WebContent)</property>
+ </emphasis> node and select <emphasis>
+ <property>New > File > JSP</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Type <emphasis>
+ <property>index</property></emphasis> for Name and click on the <emphasis>
+ <property>Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>On the <property>JBoss Tools Palette</property>, select the <emphasis>
+ <property>Struts Common</property>
+ </emphasis> folder of macros by clicking on it in the palette</para>
+ </listitem>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>logic taglib</property></emphasis> icon</para>
+ </listitem>
+ <listitem>
+ <para>Press the <emphasis>
+ <property>Enter</property>
+ </emphasis> key in the editor to go to the next line</para>
+ </listitem>
+ <listitem>
+ <para>Back on the palette, select the <emphasis>
+ <property>Struts Logic</property>
+ </emphasis> folder of macros</para>
+ </listitem>
+ <listitem>
+ <para>Click on <emphasis>
+ <property>redirect</property></emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Delete the ending tag, put a forward slash in front of the closing
+ angle bracket, and type "forward=getName" in front of
+ the slash</para>
+ </listitem>
+ </itemizedlist>
+ <para>The finished code for the page is shown below:</para>
+ <programlisting role="JAVA"><![CDATA[<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
+<logic:redirect forward="getName"/>
+]]></programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>To save all the edits to files, select <emphasis>
+ <property>File>Save All</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+ </chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/compiling_and_running.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/compiling_and_running.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/compiling_and_running.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,43 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<chapter id="compiling_and_running" xreflabel="compiling_and_running">
+ <?dbhtml filename="compiling_and_running.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Application</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Compiling the Classes and Running the Application</title>
+
+ <para>As this is the Eclipse environment, no explicit compilation step is required. By
+ default, Eclipse compiles as you go.</para>
+
+ <para>Thus at this point everything is ready for running our application without having to leave JBoss
+ Developer Studio by using the JBoss Application Server engine that comes with the JBoss
+ Developer Studio. For controlling JBoss AS within JBoss Developer Studio, there is JBoss
+ Server view.</para>
+ <figure>
+ <title>JBoss Server Panel</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Start up JBoss AS by clicking on the icon in JBoss Server view. (If JBoss AS
+ is already running, stop it by clicking on the red icon and then start it again.
+ Remember, the Struts run-time requires restarting the servlet engine when any
+ changes have been made.)</para>
+ </listitem>
+ <listitem>
+ <para>After the messages in the Console tabbed view stop scrolling, JBoss AS is
+ available. At this point, right-click on the getName global forward in the
+ struts-config.xml diagram view and select Run on Server.</para>
+ </listitem>
+ </itemizedlist>
+ <para>The browser should appear with the application started.</para>
+ </chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/generating_stub.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/generating_stub.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/generating_stub.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,51 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<chapter id="generating_stub" xreflabel="generating_stub">
+ <?dbhtml filename="generating_stub.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Application</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Generating Stub Coding</title>
+ <para>We are done with designing the application through the diagram. Now we need to write
+ code for the action component. We also need to write an action class for the <emphasis>
+ <property>/greeting</property>
+ </emphasis> mapping along with a FormBean. To aid in the coding phase, JBoss Developer
+ Studio can generate Java class stubs for all of the components shown in the diagram.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Switch back to the diagram, by selecting the <emphasis>
+ <property>Diagram</property>
+ </emphasis> tab at the bottom of the editor window</para>
+ </listitem>
+ <listitem>
+ <para>Right-click a blank space in the diagram and select <emphasis>
+ <property>Generate Java Code</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Leave everything as is in the dialog box and click <emphasis>
+ <property>Generate</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <para>You should see a screen that says:</para>
+ <para>Generated classes: 2</para>
+ <para>Actions: 1</para>
+ <para>Form beans: 1</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <para>The Java files will be generated in a <emphasis>
+ <property>JavaSource > sample</property>
+ </emphasis> folder that you can see in the <property>Package Explorer view</property> under the
+ "StrutsHello" node. One Action stub and one FormBean stub will have
+ been generated.</para>
+ </chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/favicon.ico
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/favicon.ico
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/jbosstools_logo.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/jbosstools_logo.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_application/struts_application_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_validation/struts_validation.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_validation/struts_validation.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_validation/struts_validation_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_validation/struts_validation_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_validation/struts_validation_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/images/struts_validation/struts_validation_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/introduction.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/introduction.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/introduction.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="introduction" xreflabel="introduction">
+ <?dbhtml filename="introduction.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Introduction</title>
+ <para>The following chapters describe how to deal with classic/old style of Struts development. We
+ recommend users to use JBoss Seam to
+ simplify development, but until then you can read about classical Struts usage here.</para>
+
+ <para>We are going to show you how to create a simple <emphasis>
+ <property>Struts application</property>
+ </emphasis> using the JBoss Tools. The completed application will ask a user to enter
+ a name and click a button. The resulting new page will display the familiar message,
+ "Hello <name>!"</para>
+ <para>This document will show you how to create such an application from the beginning, along the
+ way demonstrating some of the powerful features of JBoss Tools. With the help of our tutorial you will design the
+ application, generate stub code for the application, fill in the stub coding, compile the
+ application, and finally run it all from inside the Eclipse.</para>
+
+ <section>
+ <title>Key Features Struts Tools</title>
+
+ <para>For a start, we propose you to look through the table of main features of Struts
+ Tools:</para>
+ <table>
+
+ <title>Key Functionality of Struts Tools</title>
+ <tgroup cols="2">
+
+ <colspec colnum="1" align="left" colwidth="2*"/>
+ <colspec colnum="2" colwidth="4*"/>
+
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><para>Struts Support</para></entry>
+ <entry><para>Step-by-step wizards for creating a new struts project with a number
+ of predefined templates, importing existing ones and adding struts
+ capabilities to non-struts web projects.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>Support for Struts Configuration File</para></entry>
+ <entry><para>Working on file using three modes: diagram, tree and source.
+ Synchronization between the modes and full control over the code. Easy
+ moving around the diagram using the Diagram Navigator. Working with
+ struts projects that have multiple modules. Possibility to use Struts
+ configuration file debugger allowing to set break points on struts
+ diagram and then launch the server in debug mode.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>Support for Struts modules</para></entry>
+ <entry><para>A Struts module (struts-config.xml) is automatically created while
+ creating a new project. There is also possibility to add new ones or edit
+ already existing modules in your existing project or while importing Struts project.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>Verification and Validation</para></entry>
+ <entry><para>All occurring errors will be immediately reported by verification
+ feature, no matter in what view you are working. Constant validation and
+ errors checking allows to catch many of the errors during development
+ process that significantly reduces development time.</para></entry>
+
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+
+
+ <section>
+ <title>Other relevant resources on the topic</title>
+
+ <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at<ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/tools</ulink> in the corresponding release directory.</para>
+ <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs</ulink>.</para>
+
+ </section>
+
+</chapter>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/master.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/master.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/master.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,77 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+[<!ENTITY introduction SYSTEM "introduction.xml">
+<!ENTITY struts_application SYSTEM "struts_application.xml">
+<!ENTITY generating_stub SYSTEM "generating_stub.xml">
+<!ENTITY coding_files SYSTEM "coding_files.xml">
+<!ENTITY compiling_and_running SYSTEM "compiling_and_running.xml">
+<!ENTITY struts_validation SYSTEM "struts_validation.xml">
+<!ENTITY relevant_resources SYSTEM "relevant_resources.xml">
+
+<!ENTITY seamlink "../../seam/html_single/index.html">
+<!ENTITY aslink "../../as/html_single/index.html">
+<!ENTITY esblink "../../esb_ref_guide/html_single/index.html">
+<!ENTITY gsglink "../../GettingStartedGuide/html_single/index.html">
+<!ENTITY hibernatelink "../../hibernatetools/html_single/index.html">
+<!ENTITY jbpmlink "../../jbpm/html_single/index.html">
+<!ENTITY jsflink "../../jsf/html_single/index.html">
+<!ENTITY jsfreflink "../../jsf_tools_ref_guide/html_single/index.html">
+<!ENTITY jsftutoriallink "../../jsf_tools_tutorial/html_single/index.html">
+<!ENTITY strutsreflink "../../struts_tools_ref_guide/html_single/index.html">
+<!ENTITY strutstutoriallink "../../struts_tools_tutorial/html_single/index.html">
+
+]>
+
+<book>
+
+ <bookinfo>
+ <title>Struts Tools Tutorial</title>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata format="PNG" fileref="images/jbosstools_logo.png" />
+ </imageobject>
+ <imageobject role="html">
+ <imagedata/>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author><firstname>Anatoly</firstname><surname>Fedosik</surname></author>
+ <author><firstname>Olga</firstname><surname>Chikvina</surname></author>
+ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author>
+
+ <copyright>
+ <year>2007</year>
+ <year>2008</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo>
+ Version: 3.1.0.GA
+ </releaseinfo>
+
+<abstract>
+ <title/>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/struts_tools_tutoria...">PDF version</ulink>
+ </para>
+</abstract>
+
+
+ </bookinfo>
+
+ <toc/>
+
+ &introduction;
+ &struts_application;
+ &generating_stub;
+ &coding_files;
+ &compiling_and_running;
+ &struts_validation;
+ &relevant_resources;
+
+
+</book>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/master_output.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/master_output.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/master_output.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,1394 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+[<!ENTITY introduction SYSTEM "modules/introduction.xml">
+<!ENTITY struts_application SYSTEM "modules/struts_application.xml">
+<!ENTITY generating_stub SYSTEM "modules/generating_stub.xml">
+<!ENTITY coding_files SYSTEM "modules/coding_files.xml">
+<!ENTITY compiling_and_running SYSTEM "modules/compiling_and_running.xml">
+<!ENTITY struts_validation SYSTEM "modules/struts_validation.xml">
+<!ENTITY relevant_resources SYSTEM "modules/relevant_resources.xml">
+
+<!ENTITY seamlink "../../seam/html_single/index.html">
+<!ENTITY aslink "../../as/html_single/index.html">
+<!ENTITY esblink "../../esb_ref_guide/html_single/index.html">
+<!ENTITY gsglink "../../GettingStartedGuide/html_single/index.html">
+<!ENTITY hibernatelink "../../hibernatetools/html_single/index.html">
+<!ENTITY jbpmlink "../../jbpm/html_single/index.html">
+<!ENTITY jsflink "../../jsf/html_single/index.html">
+<!ENTITY jsfreflink "../../jsf_tools_ref_guide/html_single/index.html">
+<!ENTITY jsftutoriallink "../../jsf_tools_tutorial/html_single/index.html">
+<!ENTITY strutsreflink "../../struts_tools_ref_guide/html_single/index.html">
+<!ENTITY strutstutoriallink "../../struts_tools_tutorial/html_single/index.html">
+
+]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff">
+
+ <bookinfo>
+ <title>Struts Tools Tutorial</title>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
+ </imageobject>
+ <imageobject role="html">
+ <imagedata></imagedata>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author><firstname>Anatoly</firstname><surname>Fedosik</surname></author>
+ <author><firstname>Olga</firstname><surname>Chikvina</surname></author>
+ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author>
+
+ <copyright>
+ <year>2007</year>
+ <year>2008</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo><diffmk:wrapper diffmk:change="changed">
+ Version: 3.1.0.GA
+ </diffmk:wrapper></releaseinfo>
+
+<abstract>
+ <title></title>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/struts_tools_tutoria...">PDF version</ulink>
+ </para>
+</abstract>
+
+
+ </bookinfo>
+
+ <toc></toc>
+
+
+<chapter id="introduction" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_tutorial/en/modules/introduction.xml" xreflabel="introduction">
+ <?dbhtml filename="introduction.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Introduction</title>
+ <para>The following chapters describe how to deal with classic/old style of Struts development. We
+ recommend users to use <ulink url="../../seam/html_single/index.html">JBoss Seam</ulink> to
+ simplify development, but until then you can read about classical Struts usage here.</para>
+
+ <para>We are going to show you how to create a simple <emphasis>
+ <property moreinfo="none">Struts application</property>
+ </emphasis> using the JBoss Tools. The completed application will ask a user to enter
+ a name and click a button. The resulting new page will display the familiar message,
+ "Hello <name>!"</para>
+ <para>This document will show you how to create such an application from the beginning, along the
+ way demonstrating some of the powerful features of JBoss Tools. With the help of our tutorial you will design the
+ application, generate stub code for the application, fill in the stub coding, compile the
+ application, and finally run it all from inside the Eclipse.</para>
+
+ <section>
+ <title>Key Features Struts Tools</title>
+
+ <para>For a start, we propose you to look through the table of main features of Struts
+ Tools:</para>
+ <table>
+
+ <title>Key Functionality of Struts Tools</title>
+ <tgroup cols="2">
+
+ <colspec align="left" colnum="1" colwidth="2*"></colspec>
+ <colspec colnum="2" colwidth="4*"></colspec>
+
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><para>Struts Support</para></entry>
+ <entry><para>Step-by-step wizards for creating a new struts project with a number
+ of predefined templates, importing existing ones and adding struts
+ capabilities to non-struts web projects.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>Support for Struts Configuration File</para></entry>
+ <entry><para>Working on file using three modes: diagram, tree and source.
+ Synchronization between the modes and full control over the code. Easy
+ moving around the diagram using the Diagram Navigator. Working with
+ struts projects that have multiple modules. Possibility to use Struts
+ configuration file debugger allowing to set break points on struts
+ diagram and then launch the server in debug mode.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>Support for Struts modules</para></entry>
+ <entry><para>A Struts module (struts-config.xml) is automatically created while
+ creating a new project. There is also possibility to add new ones or edit
+ already existing modules in your existing project or while importing Struts project.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>Verification and Validation</para></entry>
+ <entry><para>All occurring errors will be immediately reported by verification
+ feature, no matter in what view you are working. Constant validation and
+ errors checking allows to catch many of the errors during development
+ process that significantly reduces development time.</para></entry>
+
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+
+
+ <section>
+ <title>Other relevant resources on the topic</title>
+
+ <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at<ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/tools</ulink> in the corresponding release directory.</para>
+ <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs</ulink>.</para>
+
+ </section>
+
+</chapter>
+
+
+<chapter id="struts_application" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_tutorial/en/modules/struts_application.xml" xreflabel="struts_application">
+ <?dbhtml filename="struts_application.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Application</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Creating a Simple Struts Application</title>
+
+ <para>Firstly, we assume that you have already launched Eclipse with <property moreinfo="none">JBoss Tools</property> installed and
+ also that the <property moreinfo="none">Web Development perspective</property> is the current perspective. (If not, make it
+ active by selecting <emphasis>
+ <property moreinfo="none">Window > Open Perspective > Other > Web
+ Development</property>
+ </emphasis> from the menu bar.)</para>
+
+ <section id="StartingUp">
+ <title>Starting Up</title>
+ <para>We are first going to create a new project for the application.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Go to the menu bar and select <emphasis>
+ <property moreinfo="none">File > New > Struts Project</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Next enter "StrutsHello" as the project name</para>
+ </listitem>
+ <listitem>
+ <para>Leave everything else as it is, and click <emphasis>
+ <property moreinfo="none">Next</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>If you have server runtime already defined, just pass to next point. Otherwise in the <emphasis>
+ <property moreinfo="none">Runtime</property></emphasis> section click the <emphasis>
+ <property moreinfo="none">New</property></emphasis> button and target at needed server runtime environment. Click <emphasis>
+ <property moreinfo="none">Finish</property>.</emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">Next</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Make sure that <emphasis>
+ <property moreinfo="none">struts-bean.tld</property>
+ </emphasis>, <emphasis>
+ <property moreinfo="none">struts-html.tld</property>
+ </emphasis>, and <emphasis>
+ <property moreinfo="none">struts-logic.tld</property>
+ </emphasis> are checked in the list of included tag libraries and then hit <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <para>A "StrutsHello" node should appear in the <property moreinfo="none">Package
+ Explorer view</property>.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property moreinfo="none">StrutsHello</property>
+ </emphasis> to reveal the child nodes</para>
+ </listitem>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property moreinfo="none">WebContent</property>
+ </emphasis> under <emphasis>
+ <property moreinfo="none">StrutsHello</property></emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property moreinfo="none">WEB-INF</property>
+ </emphasis> under <emphasis>
+ <property moreinfo="none">WebContent</property></emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Then, double-click on the <emphasis>
+ <property moreinfo="none">struts-config.xml</property>
+ </emphasis> node to display a diagram of the Struts application configuration
+ file in the editing area</para>
+ </listitem>
+ </itemizedlist>
+ <para>At this point, its empty except for the background grid lines.</para>
+ </section>
+
+ <section id="CreatingtheApplicationComponents">
+ <?dbhtml filename="CreatingtheApplicationComponents.html"?>
+ <title>Creating the Application Components</title>
+ <para>Now, we will design the application by creating the individual components as
+ placeholders first. (We don't have to complete all of the details inside the components
+ until afterwards.)</para>
+ <section id="CreatingJSPPagePlaceholders">
+ <title>Creating JSP Page Placeholders</title>
+ <para>Next, let's create and place two JSP pages. We will not write any code
+ for the files, but only create them as placeholders so that we can create links to
+ them in the diagram. We will write the code a little bit later.</para>
+ <section id="CreatingthePagePlaceholders">
+ <title>Creating the Page Placeholders</title>
+ <itemizedlist>
+ <listitem>
+ <para>Bring the <property moreinfo="none">Web Projects view</property> to the front of the <property moreinfo="none">Package Explorer view</property>
+ by selecting the <emphasis>
+ <property moreinfo="none">Web Projects</property>
+ </emphasis> tab next to that tab.</para>
+ </listitem>
+ <listitem>
+ <para>Right-click the <emphasis>
+ <property moreinfo="none">StrutsHello > WEB-ROOT (WebContent)</property>
+ </emphasis> folder in the <property moreinfo="none">Web Projects view</property> and select <emphasis>
+ <property moreinfo="none">New > Folder...</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Enter <emphasis>
+ <property moreinfo="none">pages</property>
+ </emphasis> for a folder name and click <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ </listitem>
+
+ <listitem>
+ <para>We will keep our presentation files in this folder</para>
+ </listitem>
+
+ <listitem>
+ <para>Right-click the <emphasis>
+ <property moreinfo="none">pages</property></emphasis> folder and select <emphasis>
+ <property moreinfo="none">New > File > JSP...</property>
+ </emphasis>
+ </para>
+ </listitem>
+ <listitem>
+ <para>For Name type in <emphasis>
+ <property moreinfo="none">inputname</property>
+ </emphasis> (the JSP extension will be automatically added to the file),
+ for Template select <emphasis>
+ <property moreinfo="none">StrutsForm</property>
+ </emphasis> and then click on the <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Right-click the <emphasis>
+ <property moreinfo="none">pages</property></emphasis> folder again and select <emphasis>
+ <property moreinfo="none">New > File > JSP...</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>For Name type in <emphasis>
+ <property moreinfo="none">greeting</property>
+ </emphasis>, for Template leave as <emphasis>
+ <property moreinfo="none">Blank</property>,</emphasis> and then click on the <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ </itemizedlist>
+ <para>Just leave these files as is for now.</para>
+ </section>
+ <section id="PlacingthePagePlaceholders">
+ <title>Placing the Page Placeholders</title>
+ <para>Lets now place the two pages just created on the diagram.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">struts-config.xml</property>
+ </emphasis> tab in the editing area to bring the diagram to the
+ front</para>
+ </listitem>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">inputname.jsp</property>
+ </emphasis> page in the <property moreinfo="none">Web Projects view</property>, drag it onto the diagram, and
+ drop it</para>
+ </listitem>
+ <listitem><para>Click on the <emphasis>
+ <property moreinfo="none">greeting.jsp</property>
+ </emphasis> page in the <property moreinfo="none">Web Projects view</property>, drag it onto the diagram, and
+ drop it to the right of the <emphasis>
+ <property moreinfo="none">/pages/inputname.jsp</property>
+ </emphasis> icon with some extra space</para></listitem>
+ </itemizedlist>
+ <para>You should now have two JSP pages in the diagram.</para>
+ </section>
+ </section>
+ <section id="CreatinganActionMappings">
+ <title>Creating an Action Mappings</title>
+ <para>Using a context menu on the diagram, we are next going to create an Action
+ mapping.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Right-click between the two icons and select <emphasis>
+ <property moreinfo="none">New > Action</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Enter the following values:</para>
+ </listitem>
+ </itemizedlist>
+ <table>
+ <title>Action values</title>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>path</entry>
+ <entry>/greeting</entry>
+ </row>
+ <row>
+ <entry>name</entry>
+ <entry>GetNameForm</entry>
+ </row>
+ <row>
+ <entry>scope</entry>
+ <entry>request</entry>
+ </row>
+ <row>
+ <entry>type</entry>
+ <entry>sample.GreetingAction</entry>
+ </row>
+ <row>
+ <entry>validate</entry>
+ <entry><leave blank></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>("GetNameForm" is the name for a form bean that we will create
+ later.)</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+
+ <para>The <emphasis>
+ <property moreinfo="none">/greeting</property>
+ </emphasis> action should appear in four places, in the diagram, under the
+ <emphasis>
+ <property moreinfo="none">action-mappings</property></emphasis> node, under the <emphasis>
+ <property moreinfo="none">struts-config.xml</property></emphasis> node in Tree view, in <property moreinfo="none">Web Projects
+ view</property> and in the <property moreinfo="none">Outline view</property>. Also, note the asterisk to the right of the name,
+ <emphasis>
+ <property moreinfo="none">struts-config.xml</property>,</emphasis> in the <property moreinfo="none">Outline view</property> showing that the file has been changed, but
+ not saved to disk.</para>
+ </section>
+ <section id="CreatingaLink">
+ <title>Creating a Link</title>
+ <para>Let's now create a link from the <emphasis>
+ <property moreinfo="none">inputname.jsp</property></emphasis> page to the action.</para>
+ <itemizedlist>
+ <listitem>
+ <para>On the left-hand side of the diagram in the column of icons, click on the Create New Connection
+ icon( <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_1.png"></imagedata>
+ </imageobject>
+ </inlinemediaobject>).</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <listitem>
+ <para>In the connect-the-components mode you are in now, click on the <emphasis>
+ <property moreinfo="none">/pages/inputname.jsp</property>
+ </emphasis> icon in the diagram and then click on the <emphasis>
+ <property moreinfo="none">/greeting</property>
+ </emphasis> action</para>
+ </listitem>
+ </itemizedlist>
+ <para>A link will be created from the page to the action.</para>
+ </section>
+ <section id="CreatingaForward">
+ <title>Creating a Forward</title>
+ <para>Next, we are going to create a forward for the action.</para>
+ <itemizedlist>
+ <listitem>
+ <para>On the left-hand side of the diagram in the column of icons, click on
+ the Create New Connection
+ icon( <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_1.png"></imagedata>
+ </imageobject>
+ </inlinemediaobject>), again.</para>
+ </listitem>
+ </itemizedlist>
+
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">/greeting</property>
+ </emphasis> action icon in the diagram and then click on the <emphasis>
+ <property moreinfo="none">pages/greeting.jsp</property>
+ </emphasis> icon</para>
+ </listitem>
+ <listitem>
+ <para>That's it. A link will be drawn from the actions new greeting
+ forward to the <emphasis>
+ <property moreinfo="none">greeting.jsp</property></emphasis> JSP page. Note that the forwards name will be
+ set based on the name of the target JSP file name. If you don't
+ like it, you can easily change it</para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property moreinfo="none">Tree</property>
+ </emphasis> tab at the bottom of the editor window (between Diagram and
+ Source)</para>
+ </listitem>
+ <listitem>
+ <para>Expand the <emphasis>
+ <property moreinfo="none">struts-config.xml/action-mappings/ /greeting</property>
+ </emphasis> node and then select the greeting forward</para>
+ </listitem>
+ <listitem>
+ <para>In the Properties Editor to the right, change the text to
+ "sayHello" in the <emphasis>
+ <property moreinfo="none">Name</property></emphasis> field</para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property moreinfo="none">Diagram</property>
+ </emphasis> tab at the bottom of the editor window and see how the diagram
+ is also updated to reflect the change</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="CreatingaGlobalForward">
+ <title>Creating a Global Forward</title>
+ <para>One last component that we need to create in the diagram is a global forward.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Somewhere in the top-left corner of diagram, right-click and select <emphasis>
+ <property moreinfo="none">New > Global Forward</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Enter <emphasis>
+ <property moreinfo="none">getName</property>
+ </emphasis> in the <emphasis>
+ <property moreinfo="none">Name</property></emphasis> field</para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property moreinfo="none">Change...</property>
+ </emphasis>button for Path</para>
+ </listitem>
+ <listitem>
+ <para>In the Edit Path window, switch to the <emphasis>
+ <property moreinfo="none">Pages</property>
+ </emphasis> tab</para>
+ </listitem>
+ <listitem>
+ <para>Expand the <emphasis>
+ <property moreinfo="none">StrutsHello > WEB-ROOT (WebContent) > pages</property>
+ </emphasis> node and then select the inputname.jsp page</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">Ok</property>
+ </emphasis>.</para>
+ </listitem>
+ <listitem>
+ <para>Leave the rest of the fields blank and click <emphasis>
+ <property moreinfo="none">OK</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <para>A forward object now appears on the diagram and also in the global-forwards folder
+ in the Outline view.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Tidy up the diagram, by clicking and dragging around each icon, so that
+ the diagram looks something like this:</para>
+ </listitem>
+ </itemizedlist>
+ <figure float="0">
+ <title>Diagram View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="CreatingaFormBean">
+ <title>Creating a Form Bean</title>
+ <para>One last thing that we need to do is to create a form bean.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Switch to the Tree viewer in the editor for the <emphasis>
+ <property moreinfo="none">struts-config.xml</property></emphasis> file, by
+ selecting the <emphasis>
+ <property moreinfo="none">Tree</property>
+ </emphasis> tab at the bottom of the editor window</para>
+ </listitem>
+ <listitem>
+ <para>Right-click <emphasis>
+ <property moreinfo="none">struts-config.xml > form-beans</property>
+ </emphasis> and select Create Form Bean</para>
+ </listitem>
+ <listitem>
+ <para>Enter <emphasis>
+ <property moreinfo="none">GetNameForm</property>
+ </emphasis> in the name field and <emphasis>
+ <property moreinfo="none">sample.GetNameForm</property>
+ </emphasis> for type</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>To save your changes to struts-config.xml, select <emphasis>
+ <property moreinfo="none">File > Save</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ <para>Note the disappearance of the asterisk next to the name, <emphasis>
+ <property moreinfo="none">struts-config.xml</property>.</emphasis></para>
+ </section>
+ </section>
+</chapter>
+
+<chapter id="generating_stub" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_tutorial/en/modules/generating_stub.xml" xreflabel="generating_stub">
+ <?dbhtml filename="generating_stub.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Application</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Generating Stub Coding</title>
+ <para>We are done with designing the application through the diagram. Now we need to write
+ code for the action component. We also need to write an action class for the <emphasis>
+ <property moreinfo="none">/greeting</property>
+ </emphasis> mapping along with a FormBean. To aid in the coding phase, JBoss Developer
+ Studio can generate Java class stubs for all of the components shown in the diagram.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Switch back to the diagram, by selecting the <emphasis>
+ <property moreinfo="none">Diagram</property>
+ </emphasis> tab at the bottom of the editor window</para>
+ </listitem>
+ <listitem>
+ <para>Right-click a blank space in the diagram and select <emphasis>
+ <property moreinfo="none">Generate Java Code</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Leave everything as is in the dialog box and click <emphasis>
+ <property moreinfo="none">Generate</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <para>You should see a screen that says:</para>
+ <para>Generated classes: 2</para>
+ <para>Actions: 1</para>
+ <para>Form beans: 1</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <para>The Java files will be generated in a <emphasis>
+ <property moreinfo="none">JavaSource > sample</property>
+ </emphasis> folder that you can see in the <property moreinfo="none">Package Explorer view</property> under the
+ "StrutsHello" node. One Action stub and one FormBean stub will have
+ been generated.</para>
+ </chapter>
+
+<chapter id="coding_files" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_tutorial/en/modules/coding_files.xml" xreflabel="coding_files">
+ <?dbhtml filename="coding_files.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Application</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Coding the Various Files</title>
+ <para>We will now code both the Java stub classes just generated, the JSP files left in as
+ placeholders from previous steps, and a new start JSP page we will have to create.</para>
+ <section id="JavaStubClasses">
+ <title>Java Stub Classes</title>
+ <itemizedlist>
+ <listitem>
+ <para>To finish the two Java classes, switch to the <emphasis>
+ <property moreinfo="none">Package Explorer</property>
+ </emphasis> view and expand the <emphasis>
+ <property moreinfo="none">JavaSource > sample</property>
+ </emphasis> folder</para>
+ </listitem>
+ </itemizedlist>
+ <section id="GetNameForm.java">
+ <title>GetNameForm.java</title>
+ <itemizedlist>
+ <listitem>
+ <para>Double-click <emphasis>
+ <property moreinfo="none">GetNameForm.java</property>
+ </emphasis> for editing</para>
+ </listitem>
+
+ <listitem>
+ <para>You are looking at a Java stub class that was generated by JBoss
+ Tools. Now we are going to edit the file</para>
+ </listitem>
+
+ <listitem>
+ <para>Add the following attributes at the beginning of the class:</para>
+ </listitem>
+ </itemizedlist>
+ <programlisting format="linespecific" role="JAVA"><![CDATA[private String name = "";
+]]></programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>Inside the reset method, delete the TO DO and throw lines and
+ add:</para>
+ </listitem>
+ </itemizedlist>
+ <programlisting format="linespecific" role="JAVA"><![CDATA[this.name = "";
+]]></programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>Inside the validate method, delete the TO DO and throw lines and
+ add:</para>
+ </listitem>
+ </itemizedlist>
+ <programlisting format="linespecific" role="JAVA"><![CDATA[ActionErrors errors = new ActionErrors();
+ return errors;
+]]></programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>Right-click and select <emphasis>
+ <property moreinfo="none">Source > Generate Getters and Setters</property>
+ </emphasis>from the context menu</para>
+ </listitem>
+ <listitem>
+ <para>In the dialog box, check the check box for <emphasis>
+ <property moreinfo="none">name</property>,</emphasis>
+ select First method for Insertion point, and click on the <emphasis>
+ <property moreinfo="none">OK</property>
+ </emphasis> button</para>
+ </listitem>
+ </itemizedlist>
+ <para>The final <emphasis>
+ <property moreinfo="none">GetNameForm.java</property></emphasis> file should look like this:</para>
+ <programlisting format="linespecific" role="JAVA"><![CDATA[package sample;
+import javax.servlet.http.HttpServletRequest;
+import org.apache.struts.action.ActionErrors;
+import org.apache.struts.action.ActionMapping;
+
+public class GetNameForm extends org.apache.struts.action.ActionForm
+{
+
+ private String name = "";
+
+ public String getName()
+ {
+ return name;
+ }
+ public void setName(String name)
+ {
+ this.name = name;
+ }
+
+ public GetNameForm()
+ {
+ }
+
+ public void reset(ActionMapping actionMapping, HttpServletRequest request)
+ {
+ this.name = "";
+ }
+
+ public ActionErrors validate(ActionMapping actionMapping,
+ HttpServletRequest request)
+ {
+ ActionErrors errors = new ActionErrors();
+ return errors;
+ }
+}
+]]></programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>Save the file</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="GreetingAction.java">
+ <title>GreetingAction.java</title>
+ <itemizedlist>
+ <listitem>
+ <para>Open <emphasis>
+ <property moreinfo="none">GreetingAction.java</property></emphasis> for editing</para>
+ </listitem>
+ <listitem>
+ <para>Inside the execute method, delete the TO DO lines and add the
+ following:</para>
+ </listitem>
+ </itemizedlist>
+
+ <programlisting format="linespecific" role="JAVA"><![CDATA[String name = ((GetNameForm)form).getName();
+String greeting = "Hello, "+name+"!";
+((GetNameForm)form).setName(greeting);
+return mapping.findForward(FORWARD_sayHello);
+]]></programlisting>
+
+ <para>The final version of <emphasis>
+ <property moreinfo="none">GreetingAction.java</property></emphasis> should look like this:</para>
+
+ <programlisting format="linespecific" role="JAVA"><![CDATA[package sample;
+import javax.servlet.http.HttpServletRequest;
+import javax.servlet.http.HttpServletResponse;
+import org.apache.struts.action.ActionForm;
+import org.apache.struts.action.ActionForward;
+import org.apache.struts.action.ActionMapping;
+
+public class GreetingAction extends org.apache.struts.action.Action
+{
+
+ // Global Forwards
+ public static final String GLOBAL_FORWARD_getName = "getName";
+
+ // Local Forwards
+ public static final String FORWARD_sayHello = "sayHello";
+
+ public GreetingAction()
+ {
+ }
+ public ActionForward execute(ActionMapping mapping, ActionForm form,
+ HttpServletRequest request, HttpServletResponse response) throws Exception
+ {
+ String name = ((GetNameForm)form).getName();
+ String greeting = "Hello, "+name+"!";
+ ((GetNameForm)form).setName(greeting);
+ return mapping.findForward(FORWARD_sayHello);
+ }
+}
+]]></programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>Save the file</para>
+ </listitem>
+ <listitem>
+ <para>Close the editors for the two Java files</para>
+ </listitem>
+ </itemizedlist>
+ <para>The last thing left to do is to code the JSP files whose editors should still
+ be open from having been created as placeholders.</para>
+ </section>
+ </section>
+ <section id="JSPPages">
+ <title>JSP Pages</title>
+ <section id="inputname.jsp">
+ <title>inputname.jsp</title>
+ <para>In this page, the user will enter any name and click the <emphasis>
+ <property moreinfo="none">submit</property>
+ </emphasis> button. Then, the greeting action will be called through the form.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">inputname.jsp</property>
+ </emphasis> tab in the Editing area to bring its editor forward</para>
+ </listitem>
+ <listitem>
+ <para>In the Web Projects view, expand <emphasis>
+ <property moreinfo="none">StrutsHello > Configuration > default
+ > struts-config.xml > action-mappings</property>
+ </emphasis> and select <emphasis>
+ <property moreinfo="none">/greeting</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Drag it and drop it between the quotes for the <emphasis role="italic">
+ <property moreinfo="none">"action"</property>
+ </emphasis> attribute to the
+ <code><html:form></code>
+ element in the Source pane of the editor</para>
+ </listitem>
+ <listitem>
+ <para>Then type this text on a new line just below this line:</para>
+ <programlisting format="linespecific" role="XML"><![CDATA[Input name:
+ ]]></programlisting>
+ </listitem>
+
+ <listitem>
+ <para>Select the <emphasis>
+ <property moreinfo="none">Visual</property>
+ </emphasis> pane of the editor</para>
+ </listitem>
+ <listitem>
+ <para>Then, in the JBoss Tools Palette, expand the <emphasis>
+ <property moreinfo="none">Struts Form</property>
+ </emphasis> library, select <emphasis>
+ <property moreinfo="none">text</property>
+ </emphasis>, and drag it onto the box
+ <note>
+ <title>Note:</title>
+ <para>By default there are only four groups on the JBoss Tools
+ Palette. If you wish to make some group visible click the <emphasis>
+ <property moreinfo="none">Show/Hide</property>
+ </emphasis> button on the top of palette and in the prompted
+ dialog check the group (or groups) you want to be shown.</para>
+ </note>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <figure float="0">
+ <title>JBoss Tools Palette</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>In the Insert Tag dialog box, type in name for property and select <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>In the StrutsForm library in the <property moreinfo="none">JBoss Tools Palette</property>, select <emphasis>
+ <property moreinfo="none">submit</property>
+ </emphasis>, and drag it to right after the text box in the Visual pane
+ of the editor</para>
+ </listitem>
+ <listitem>
+ <para>Right-click the <emphasis>
+ <property moreinfo="none">submit</property>
+ </emphasis> button and select
+ <code><html:submit></code>
+ Attributes from the context menu</para>
+ </listitem>
+ <listitem>
+ <para>In the Attributes dialog box, select the <emphasis>
+ <property moreinfo="none">value</property>
+ </emphasis> field and type in "Say Hello!" for its
+ value</para>
+ </listitem>
+ </itemizedlist>
+ <para>After tidying the page source, the Editor window for the file should look
+ something like this:</para>
+ <figure float="0">
+ <title>Editor Window</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="greeting.jsp">
+ <title>greeting.jsp</title>
+ <para>Next, we will fill in the result page.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">greeting.jsp</property>
+ </emphasis> tab in the Editing area to bring its editor forward</para>
+ </listitem>
+ <listitem>
+ <para>Type in the following code:</para>
+ </listitem>
+ </itemizedlist>
+ <programlisting format="linespecific" role="XML"><![CDATA[<html>
+<head>
+ <title>Greeting</title>
+</head>
+ <body>
+ <p>
+ </p>
+ </body>
+</html>
+]]></programlisting>
+
+ <para>To complete editing of this file, we will use macros from the <property moreinfo="none">JBoss Tools
+ Palette</property>. This palette is a view that should be available to the right of the
+ editing area.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">Struts Common</property>
+ </emphasis> folder in the <property moreinfo="none">JBoss Tools Palette</property> to open it</para>
+ </listitem>
+ <listitem>
+ <para>Position the cursor at the beginning of the <emphasis>
+ <property moreinfo="none">greeting.jsp</property></emphasis> file in the
+ Source pane and then click on <emphasis>
+ <property moreinfo="none">bean taglib</property></emphasis> in the <property moreinfo="none">JBoss Tools
+ Palette</property></para>
+ </listitem>
+ </itemizedlist>
+ <para>This will insert the following line at the top of the file:</para>
+ <programlisting format="linespecific" role="JAVA"><![CDATA[
+<%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %>
+]]></programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">Struts Bean</property>
+ </emphasis> folder in the <property moreinfo="none">JBoss Tools Palette</property> to open it</para>
+ </listitem>
+ <listitem>
+ <para>Position the cursor inside the
+ <code><p></code>
+ element</para>
+ </listitem>
+ <listitem>
+ <para>Click on <emphasis>
+ <property moreinfo="none">write</property></emphasis> in the <property moreinfo="none">JBoss Tools Palette</property></para>
+ </listitem>
+ <listitem>
+ <para>Type in "GetNameForm" for the <emphasis role="italic">
+ <property moreinfo="none">name</property>
+ </emphasis> attribute and add a <emphasis role="italic">
+ <property moreinfo="none">property</property>
+ </emphasis> attribute with "name" as its
+ value</para>
+ </listitem>
+ </itemizedlist>
+ <para>The editor should now look like this:</para>
+ <figure float="0">
+ <title>Editor Window</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_5.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="index.jsp">
+ <title>index.jsp</title>
+ <para>Finally, we will need to create and edit an <emphasis>
+ <property moreinfo="none">index.jsp</property></emphasis> page. This page will use
+ a Struts forward to simply redirect us to the getName global forward.</para>
+ <itemizedlist>
+ <listitem>
+ <para>In the Web Projects view, right-click on <emphasis>
+ <property moreinfo="none">StrutsHello > WEB-ROOT(WebContent)</property>
+ </emphasis> node and select <emphasis>
+ <property moreinfo="none">New > File > JSP</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Type <emphasis>
+ <property moreinfo="none">index</property></emphasis> for Name and click on the <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>On the <property moreinfo="none">JBoss Tools Palette</property>, select the <emphasis>
+ <property moreinfo="none">Struts Common</property>
+ </emphasis> folder of macros by clicking on it in the palette</para>
+ </listitem>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">logic taglib</property></emphasis> icon</para>
+ </listitem>
+ <listitem>
+ <para>Press the <emphasis>
+ <property moreinfo="none">Enter</property>
+ </emphasis> key in the editor to go to the next line</para>
+ </listitem>
+ <listitem>
+ <para>Back on the palette, select the <emphasis>
+ <property moreinfo="none">Struts Logic</property>
+ </emphasis> folder of macros</para>
+ </listitem>
+ <listitem>
+ <para>Click on <emphasis>
+ <property moreinfo="none">redirect</property></emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Delete the ending tag, put a forward slash in front of the closing
+ angle bracket, and type "forward=getName" in front of
+ the slash</para>
+ </listitem>
+ </itemizedlist>
+ <para>The finished code for the page is shown below:</para>
+ <programlisting format="linespecific" role="JAVA"><![CDATA[<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
+<logic:redirect forward="getName"/>
+]]></programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>To save all the edits to files, select <emphasis>
+ <property moreinfo="none">File>Save All</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+ </chapter>
+
+<chapter id="compiling_and_running" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_tutorial/en/modules/compiling_and_running.xml" xreflabel="compiling_and_running">
+ <?dbhtml filename="compiling_and_running.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Application</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Compiling the Classes and Running the Application</title>
+
+ <para>As this is the Eclipse environment, no explicit compilation step is required. By
+ default, Eclipse compiles as you go.</para>
+
+ <para>Thus at this point everything is ready for running our application without having to leave JBoss
+ Developer Studio by using the JBoss Application Server engine that comes with the JBoss
+ Developer Studio. For controlling JBoss AS within JBoss Developer Studio, there is JBoss
+ Server view.</para>
+ <figure float="0">
+ <title>JBoss Server Panel</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_6.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Start up JBoss AS by clicking on the icon in JBoss Server view. (If JBoss AS
+ is already running, stop it by clicking on the red icon and then start it again.
+ Remember, the Struts run-time requires restarting the servlet engine when any
+ changes have been made.)</para>
+ </listitem>
+ <listitem>
+ <para>After the messages in the Console tabbed view stop scrolling, JBoss AS is
+ available. At this point, right-click on the getName global forward in the
+ struts-config.xml diagram view and select Run on Server.</para>
+ </listitem>
+ </itemizedlist>
+ <para>The browser should appear with the application started.</para>
+ </chapter>
+
+<chapter id="struts_validation" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_tutorial/en/modules/struts_validation.xml" xreflabel="struts_validation">
+ <?dbhtml filename="struts_validation.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Validation</keyword>
+ </keywordset>
+ </chapterinfo>
+<title>Struts Validation Examples</title>
+
+<para><property moreinfo="none">Validation</property> of input is an important part of any Web application. All Apache Jakarta frameworks,
+including Struts, can use a common Jakarta Validation Framework for streamlining this aspect of Web
+application development. The Validation Framework allows you to define validation rules and then apply these rules on the client-side or the server-side.</para>
+
+ <para>JBoss Developer Studio makes using the <property moreinfo="none">Validation Framework</property> in Struts even easier with the help of a specialized editor for the XML files that controls validation in a project. In this document, we'll show you how this all works by creating some simple client-side validation and server-side validation examples.</para>
+
+<section id="StartingPoint">
+<?dbhtml filename="StartingPoint.html"?>
+<title>Starting Point</title>
+<para>The example assumes that you have already created our sample "StrutsHello" application from the
+Getting Started Guide for Creating a Struts Application. You should have the JBoss Developer Studio perspective
+ open on this StrutsHello project.</para>
+</section>
+
+<section id="DefiningTheValidationRule">
+<?dbhtml filename="DefiningTheValidationRule.html"?>
+<title>Defining the Validation Rule</title>
+<para>In these steps you will set up the validation that can be used for either client-side or
+server side validation. You need to enable validation as a part of the project, define an error message, and tie it into an appropriate part of the application.</para>
+
+<itemizedlist>
+<listitem><para>Right-click on a "plug-ins" node under the <emphasis><property moreinfo="none">StrutsHello > Configuration > default > struts-config.xml</property></emphasis> node in the Web Projects view and select <emphasis><property moreinfo="none">Create Special Plugin > Validators</property></emphasis> from the context menu</para></listitem>
+<listitem><para>Further down in the Web Projects view, right-click on the
+<emphasis><property moreinfo="none">StrutsHello > ResourceBundles</property></emphasis> node and select <emphasis><property moreinfo="none"> New > Properties File...</property></emphasis>from the context menu</para></listitem>
+<listitem><para>In the dialog box, click on the <emphasis><property moreinfo="none">Browse...</property></emphasis>button next to the Folder field, expand the
+ JavaSource folder in this next dialog box, select the sample subfolder, and click on the <emphasis><property moreinfo="none">OK</property></emphasis> button</para></listitem>
+ <listitem><para>Back in the first dialog box, type in "applResources" for the Name field and click on the <emphasis><property moreinfo="none">Finish</property></emphasis> button</para></listitem>
+<listitem><para>Right-click on a newly created file and select <emphasis><property moreinfo="none">Add > Default Error Messages</property></emphasis>
+ from the context menu</para></listitem>
+
+<listitem><para>Drag up the sample.applResources icon until you can drop it on the resources folder under struts-config.xml</para></listitem>
+<listitem><para>Select<emphasis><property moreinfo="none"> File > Save </property></emphasis>All from the menu bar</para></listitem>
+<listitem><para>Select validation.xml under the <emphasis><property moreinfo="none">StrutsHello > Validation</property></emphasis> node and double-click it to open it with the JBoss Tools XML Editor</para></listitem>
+<listitem><para>Here you must create a Formset.</para></listitem>
+<listitem><para>In the validation.xml file editor click the button <emphasis><property moreinfo="none">Create Formset</property></emphasis> on the panel <emphasis><property moreinfo="none">Formsets</property></emphasis></para></listitem>
+<listitem><para>In the dialog <emphasis><property moreinfo="none">Add Formset</property></emphasis> fill the fields <emphasis><property moreinfo="none">Language</property></emphasis> and <emphasis><property moreinfo="none">Country</property></emphasis> or just leave them empty to create a default formset. Click <emphasis><property moreinfo="none">OK</property></emphasis></para></listitem>
+</itemizedlist>
+<figure float="0">
+ <title>Create Formset</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_validation/struts_validation.png"></imagedata>
+ </imageobject>
+</mediaobject>
+</figure>
+<itemizedlist>
+<listitem><para>Expand the "form-beans" node under the <emphasis><property moreinfo="none">StrutsHello > Configuration > default > struts-config.xml node.</property></emphasis> Then, drag the form bean "GetNameForm" and drop it onto a formset in the <property moreinfo="none">XML</property> Editor</para></listitem>
+<listitem><para>In the Validation Editor, expand the formset node, right-click GetNameForm, and select <emphasis><property moreinfo="none">Create Field...</property></emphasis> from the context menu</para></listitem>
+<listitem><para>Enter a name for Property in the dialog box. A new property will be created:</para></listitem>
+</itemizedlist>
+<figure float="0">
+ <title>New Property Is Added</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_validation/struts_validation_2.png"></imagedata>
+ </imageobject>
+</mediaobject>
+</figure>
+<itemizedlist>
+<listitem><para>In the Properties view for the name field to the right of the "tree" for the validation.xml file, click on the <emphasis><property moreinfo="none">Change...</property></emphasis>button next to the Depends entry field</para></listitem>
+<listitem><para>In the displayed double list, select <emphasis><property moreinfo="none">required</property></emphasis> from the left list and then click <emphasis><property moreinfo="none">Add</property></emphasis></para></listitem>
+ <listitem><para>Click <emphasis><property moreinfo="none">Ok</property></emphasis></para></listitem>
+<listitem><para>Right-click name and select <emphasis><property moreinfo="none">Add Arg...</property></emphasis> from the context menu</para></listitem>
+<listitem><para>In the Add Arg dialog box, click on the <emphasis><property moreinfo="none">Change...</property></emphasis>button next to the <emphasis><property moreinfo="none">Key</property></emphasis> field</para></listitem>
+ <listitem><para>In the Key dialog box that appears now, click on the <emphasis><property moreinfo="none">Add</property></emphasis> button</para></listitem>
+ <listitem><para>Enter "name.required" in the Name field, and enter a person's name in the Value field</para></listitem>
+ <listitem><para>Click <emphasis><property moreinfo="none">Finish</property></emphasis>, then <emphasis><property moreinfo="none">Ok</property></emphasis>, and then <emphasis><property moreinfo="none">Ok</property></emphasis> again</para></listitem>
+<listitem><para>Select <emphasis><property moreinfo="none">File > Save All</property></emphasis> from the menu bar</para></listitem>
+</itemizedlist>
+</section>
+
+<section id="Client-SideValidation">
+<?dbhtml filename="Client-SideValidation.html"?>
+<title>Client-Side Validation</title>
+<para>Client-side <property moreinfo="none">validation</property> uses a scripting language (like JavaScript) running in the client browser to actually do the <property moreinfo="none">validation</property>. In a Struts application using the <property moreinfo="none">Validation</property> Framework, however, you don't actually have to do any of the script coding. The <property moreinfo="none">Validation</property> Framework handles this.</para>
+<para>To see how this works in our application, you'll just need to make a couple of modifications to one of the JSP files.</para>
+<itemizedlist>
+<listitem><para>Double-click inputname.jsp under <emphasis><property moreinfo="none">StrutsHello > WEB-ROOT(WebContent) > pages</property></emphasis> to open it for editing</para></listitem>
+<listitem><para>Find the tag near the top and hit Return to make a new line under it</para></listitem>
+ <listitem><para>In the JBoss Tools Palette view to the right, open the Struts HTML folder and click on the javascript tag</para></listitem>
+<listitem><para>Back in the editor, just in front of the closing slash for this inserted tag, hit Ctrl+Space and select "formName" from the prompting menu</para></listitem>
+<listitem><para>Over in the Web Projects view, select GetNameForm under the <emphasis><property moreinfo="none">StrutsHello > Configuration > default > struts-config.xml > form-beans</property></emphasis> node, drag it, and drop it between the quotes in the editor</para></listitem>
+<listitem><para>Modify the <code><html:form></code> tag by inserting this attribute:</para></listitem>
+</itemizedlist>
+<programlisting format="linespecific" role="XML"><![CDATA[onsubmit="return validateGetNameForm(this)"
+]]></programlisting>
+<para></para>
+<para>The file should now look like this:</para>
+<programlisting format="linespecific" role="XML"><![CDATA[
+<%@ taglib uri="/WEB-INF/struts-html" prefix="html" %>
+
+<html:html >
+ <head>
+ <html:javascript formName="GetNameForm"/>
+ <title></title>
+ </head>
+ <body>
+ <html:form action="/greeting.do" onsubmit="return validateGetNameForm(this)">
+ Input name:<html:text property="name"/><html:submit value="Say Hello!"/>
+ </html:form>
+ </body>
+</html:html>
+]]></programlisting>
+<itemizedlist>
+<listitem><para>Select<emphasis><property moreinfo="none"> File > Save </property></emphasis>from the menu bar</para></listitem>
+<listitem><para>Start JBoss Application Server by clicking on its icon (a right-pointing arrow) in the toolbar</para></listitem>
+ <listitem><para>Click the Run icon(<inlinemediaobject> <imageobject>
+ <imagedata fileref="images/struts_validation/struts_validation_1.png"></imagedata>
+ </imageobject></inlinemediaobject>) or right click your project folder and select <emphasis><property moreinfo="none">Run As > Run on Server</property></emphasis></para></listitem>
+</itemizedlist>
+
+<itemizedlist><listitem><para>In the browser window, click on the "Say Hello!" button without having entered any name in the form</para></listitem></itemizedlist>
+<para>A JavaScript error message should be displayed in an alert box.</para>
+</section>
+<section id="Server-SideValidation">
+<?dbhtml filename="Server-SideValidation.html"?>
+<title>Server Side Validation</title>
+<para>Server side validation does the validation inside the application on the server. In a Struts application using the Validation Framework, you still don't have to do any of the actual validation coding. The Validation Framework handles this. You will though have to make a few changes to the JSP file you modified for client-side validation along with a change to an action and a few changes to the form bean class.</para>
+</section>
+
+<section id="EditingTheJSPFile">
+<?dbhtml filename="EditingTheJSPFile.html"?>
+<title>Editing the JSP File</title>
+<itemizedlist>
+<listitem><para>Reopen inputname.jsp for editing</para></listitem>
+<listitem><para>Delete the <emphasis role="italic"><property moreinfo="none">"onsubmit"</property></emphasis> attribute in the <code><html:form></code> element that you put in for client-side validation</para></listitem>
+
+<listitem><para>Add an <code><html:errors/></code> tag after the
+ <code><html:form></code>
+ tag</para></listitem>
+</itemizedlist>
+<para>The JSP file should now look like this:</para>
+
+ <programlisting format="linespecific" role="XML"><![CDATA[<%@ taglib uri="/WEB-INF/struts-html" prefix="html" %>
+<html:html >
+<head>
+ <html:javascript formName="GetNameForm"/>
+ <title></title>
+ </head>
+ <body>
+ <html:form action="/greeting.do" >Input name:<html:text property="name"/>
+ <html:submit value="Say Hello!"/>
+ </html:form>
+ <html:errors/>
+ </body>
+</html:html>
+]]></programlisting>
+
+</section>
+
+<section id="EditingTheAction">
+<?dbhtml filename="EditingTheAction.html"?>
+<title>Editing the Action</title>
+<itemizedlist>
+<listitem><para>In the Web Projects view, expand the node under the <emphasis><property moreinfo="none">StrutsHello > Configuration > default > struts-config.xml > action-mappings</property></emphasis> node, right-click the <emphasis><property moreinfo="none">/greeting</property></emphasis> action, and then select <emphasis><property moreinfo="none">Properties...</property></emphasis>from the context menu</para></listitem>
+
+ <listitem><para>In the Edit Properties window, insert the cursor into the value column for the input property and click on the <property moreinfo="none">...</property> button</para></listitem>
+
+ <listitem><para>In the dialog box, make sure the Pages tab is selected, select <emphasis><property moreinfo="none">StrutsHello > WEB-ROOT(WebContent) > pages > inputname.jsp</property></emphasis>, click the <emphasis><property moreinfo="none">Ok</property></emphasis> button, and then click on the <emphasis><property moreinfo="none">Close</property></emphasis> button</para></listitem>
+</itemizedlist>
+</section>
+<section id="EditingTheFormBean">
+<?dbhtml filename="EditingTheFormBean.html"?>
+
+<title>Editing the Form Bean</title>
+<itemizedlist>
+<listitem><para>Right-click the <emphasis><property moreinfo="none">/greeting</property></emphasis> action again and select Open Form-bean Source to open the GetNameForm.java file for editing</para></listitem>
+<listitem><para>Change the class that it extends from: <emphasis><property moreinfo="none">org.apache.struts.action.ActionForm</property></emphasis> to <emphasis><property moreinfo="none">org.apache.struts.validator.ValidatorForm</property></emphasis></para></listitem>
+<listitem><para>Comment out a validate method</para></listitem>
+</itemizedlist>
+<para>The file should now look like this:</para>
+<programlisting format="linespecific" role="JAVA"><![CDATA[package sample;
+import javax.servlet.http.HttpServletRequest;
+import org.apache.struts.action.ActionErrors;
+import org.apache.struts.action.ActionMapping;
+public class GetNameForm extends
+
+org.apache.struts.validator.ValidatorForm
+{
+
+ private String name = "";
+
+ /**
+ * @return Returns the name.
+ */
+ public String getName()
+ {
+ return name;
+ }
+
+ /**
+ * @param name The name to set.
+ */
+ public void setName(String name)
+ {
+ this.name = name;
+ }
+
+ public GetNameForm ()
+ {
+ }
+
+ public void reset(ActionMapping actionMapping,
+ HttpServletRequest request)
+ {
+ this.name = "";
+ }
+
+ // public ActionErrors validate(ActionMapping actionMapping,
+ // HttpServletRequest request)
+ //{
+ // ActionErrors errors = new ActionErrors();
+ // return errors;
+ // }
+ }
+]]></programlisting>
+
+<itemizedlist>
+<listitem><para>Select <emphasis><property moreinfo="none">File > Save All </property></emphasis>from the menu bar</para></listitem>
+<listitem><para>Reload the application into JBoss AS by clicking on the "Change Time Stamp" icon (a finger pointing with a little star) in the toolbar</para></listitem>
+<listitem><para>Run the application</para></listitem>
+<listitem><para>In the browser window, click on the "Say Hello!" button without having entered any name in the form</para></listitem>
+</itemizedlist>
+<para>The error message should appear in a refreshed version of the form.</para>
+</section>
+
+</chapter>
+
+<chapter id="relevant_resources" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/struts/docs/struts_tools_tutorial/en/modules/relevant_resources.xml" xreflabel="relevant_resources">
+ <?dbhtml filename="relevant_resources.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Application</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Other Relevant Resources on the topic</title>
+
+ <para>Our reference: <ulink url="../../struts_tools_ref_guide/html_single/index.html">Struts Tools Reference Guide</ulink></para>
+ <para>Apache Struts: <ulink url="http://struts.apache.org/">Struts Technology</ulink></para>
+ <para>Struts 2: <ulink url="http://struts.apache.org/2.x/">Apache Struts 2</ulink></para>
+ <para>Get Started: <ulink url="http://struts.apache.org/2.x/docs/home.html">Struts Getting
+ Started</ulink></para>
+ <para>Struts on IBM: <ulink url="http://www.ibm.com/developerworks/library/j-struts/">Struts -
+ An open-source MVC implementation</ulink></para>
+ <para>FAQ: <ulink url="http://struts.apache.org/2.x/docs/faqs.html">Struts FAQ</ulink></para>
+ <para>Download: <ulink url="http://struts.apache.org/download.cgi#struts206">Release of Apache
+ Struts</ulink></para>
+
+ <para>Thus, this tutorial should help you to execute the hole development circle for building a
+ sample Struts-based Web application using <property moreinfo="none">JBoss Tools</property> bundle of Eclipse
+ plugins starting from organizing a new Struts project and ending with the running and
+ deploying it onto the <property moreinfo="none">JBoss Server</property>.</para>
+
+ <para>To find out all the features of <property moreinfo="none">JBoss Tools</property> for working with Struts
+ refer to our <ulink url="../../struts_tools_ref_guide/html_single/index.html">Struts Tools Reference Guide</ulink>. If you
+ still have questions you are always welcome on
+ <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss
+ Tools Forum</ulink>.</para>
+</chapter>
+
+
+
+</book>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/relevant_resources.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/relevant_resources.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/relevant_resources.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,35 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<chapter id="relevant_resources" xreflabel="relevant_resources">
+ <?dbhtml filename="relevant_resources.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Application</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Other Relevant Resources on the topic</title>
+
+ <para>Our reference: Struts Tools Reference Guide</para>
+ <para>Apache Struts: <ulink url="http://struts.apache.org/">Struts Technology</ulink></para>
+ <para>Struts 2: <ulink url="http://struts.apache.org/2.x/">Apache Struts 2</ulink></para>
+ <para>Get Started: <ulink url="http://struts.apache.org/2.x/docs/home.html">Struts Getting
+ Started</ulink></para>
+ <para>Struts on IBM: <ulink url="http://www.ibm.com/developerworks/library/j-struts/">Struts -
+ An open-source MVC implementation</ulink></para>
+ <para>FAQ: <ulink url="http://struts.apache.org/2.x/docs/faqs.html">Struts FAQ</ulink></para>
+ <para>Download: <ulink url="http://struts.apache.org/download.cgi#struts206">Release of Apache
+ Struts</ulink></para>
+
+ <para>Thus, this tutorial should help you to execute the hole development circle for building a
+ sample Struts-based Web application using <property>JBoss Tools</property> bundle of Eclipse
+ plugins starting from organizing a new Struts project and ending with the running and
+ deploying it onto the <property>JBoss Server</property>.</para>
+
+ <para>To find out all the features of <property>JBoss Tools</property> for working with Struts
+ refer to our Struts Tools Reference Guide. If you
+ still have questions you are always welcome on <ulink
+ url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss
+ Tools Forum</ulink>.</para>
+</chapter>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/struts_application.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/struts_application.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/struts_application.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,427 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<chapter id="struts_application" xreflabel="struts_application">
+ <?dbhtml filename="struts_application.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Application</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Creating a Simple Struts Application</title>
+
+ <para>Firstly, we assume that you have already launched Eclipse with <property>JBoss Tools</property> installed and
+ also that the <property>Web Development perspective</property> is the current perspective. (If not, make it
+ active by selecting <emphasis>
+ <property>Window > Open Perspective > Other > Web
+ Development</property>
+ </emphasis> from the menu bar.)</para>
+
+ <section id="StartingUp">
+ <title>Starting Up</title>
+ <para>We are first going to create a new project for the application.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Go to the menu bar and select <emphasis>
+ <property>File > New > Struts Project</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Next enter "StrutsHello" as the project name</para>
+ </listitem>
+ <listitem>
+ <para>Leave everything else as it is, and click <emphasis>
+ <property>Next</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>If you have server runtime already defined, just pass to next point. Otherwise in the <emphasis>
+ <property>Runtime</property></emphasis> section click the <emphasis>
+ <property>New</property></emphasis> button and target at needed server runtime environment. Click <emphasis>
+ <property>Finish</property>.</emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property>Next</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Make sure that <emphasis>
+ <property>struts-bean.tld</property>
+ </emphasis>, <emphasis>
+ <property>struts-html.tld</property>
+ </emphasis>, and <emphasis>
+ <property>struts-logic.tld</property>
+ </emphasis> are checked in the list of included tag libraries and then hit <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <para>A "StrutsHello" node should appear in the <property>Package
+ Explorer view</property>.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property>StrutsHello</property>
+ </emphasis> to reveal the child nodes</para>
+ </listitem>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property>WebContent</property>
+ </emphasis> under <emphasis>
+ <property>StrutsHello</property></emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property>WEB-INF</property>
+ </emphasis> under <emphasis>
+ <property>WebContent</property></emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Then, double-click on the <emphasis>
+ <property>struts-config.xml</property>
+ </emphasis> node to display a diagram of the Struts application configuration
+ file in the editing area</para>
+ </listitem>
+ </itemizedlist>
+ <para>At this point, its empty except for the background grid lines.</para>
+ </section>
+
+ <section id="CreatingtheApplicationComponents">
+ <?dbhtml filename="CreatingtheApplicationComponents.html"?>
+ <title>Creating the Application Components</title>
+ <para>Now, we will design the application by creating the individual components as
+ placeholders first. (We don't have to complete all of the details inside the components
+ until afterwards.)</para>
+ <section id="CreatingJSPPagePlaceholders">
+ <title>Creating JSP Page Placeholders</title>
+ <para>Next, let's create and place two JSP pages. We will not write any code
+ for the files, but only create them as placeholders so that we can create links to
+ them in the diagram. We will write the code a little bit later.</para>
+ <section id="CreatingthePagePlaceholders">
+ <title>Creating the Page Placeholders</title>
+ <itemizedlist>
+ <listitem>
+ <para>Bring the <property>Web Projects view</property> to the front of the <property>Package Explorer view</property>
+ by selecting the <emphasis>
+ <property>Web Projects</property>
+ </emphasis> tab next to that tab.</para>
+ </listitem>
+ <listitem>
+ <para>Right-click the <emphasis>
+ <property>StrutsHello > WEB-ROOT (WebContent)</property>
+ </emphasis> folder in the <property>Web Projects view</property> and select <emphasis>
+ <property>New > Folder...</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Enter <emphasis>
+ <property>pages</property>
+ </emphasis> for a folder name and click <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ </listitem>
+
+ <listitem>
+ <para>We will keep our presentation files in this folder</para>
+ </listitem>
+
+ <listitem>
+ <para>Right-click the <emphasis>
+ <property>pages</property></emphasis> folder and select <emphasis>
+ <property>New > File > JSP...</property>
+ </emphasis>
+ </para>
+ </listitem>
+ <listitem>
+ <para>For Name type in <emphasis>
+ <property>inputname</property>
+ </emphasis> (the JSP extension will be automatically added to the file),
+ for Template select <emphasis>
+ <property>StrutsForm</property>
+ </emphasis> and then click on the <emphasis>
+ <property>Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Right-click the <emphasis>
+ <property>pages</property></emphasis> folder again and select <emphasis>
+ <property>New > File > JSP...</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>For Name type in <emphasis>
+ <property>greeting</property>
+ </emphasis>, for Template leave as <emphasis>
+ <property>Blank</property>,</emphasis> and then click on the <emphasis>
+ <property>Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ </itemizedlist>
+ <para>Just leave these files as is for now.</para>
+ </section>
+ <section id="PlacingthePagePlaceholders">
+ <title>Placing the Page Placeholders</title>
+ <para>Lets now place the two pages just created on the diagram.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>struts-config.xml</property>
+ </emphasis> tab in the editing area to bring the diagram to the
+ front</para>
+ </listitem>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>inputname.jsp</property>
+ </emphasis> page in the <property>Web Projects view</property>, drag it onto the diagram, and
+ drop it</para>
+ </listitem>
+ <listitem><para>Click on the <emphasis>
+ <property>greeting.jsp</property>
+ </emphasis> page in the <property>Web Projects view</property>, drag it onto the diagram, and
+ drop it to the right of the <emphasis>
+ <property>/pages/inputname.jsp</property>
+ </emphasis> icon with some extra space</para></listitem>
+ </itemizedlist>
+ <para>You should now have two JSP pages in the diagram.</para>
+ </section>
+ </section>
+ <section id="CreatinganActionMappings">
+ <title>Creating an Action Mappings</title>
+ <para>Using a context menu on the diagram, we are next going to create an Action
+ mapping.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Right-click between the two icons and select <emphasis>
+ <property>New > Action</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Enter the following values:</para>
+ </listitem>
+ </itemizedlist>
+ <table>
+ <title>Action values</title>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>path</entry>
+ <entry>/greeting</entry>
+ </row>
+ <row>
+ <entry>name</entry>
+ <entry>GetNameForm</entry>
+ </row>
+ <row>
+ <entry>scope</entry>
+ <entry>request</entry>
+ </row>
+ <row>
+ <entry>type</entry>
+ <entry>sample.GreetingAction</entry>
+ </row>
+ <row>
+ <entry>validate</entry>
+ <entry><leave blank></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>("GetNameForm" is the name for a form bean that we will create
+ later.)</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+
+ <para>The <emphasis>
+ <property>/greeting</property>
+ </emphasis> action should appear in four places, in the diagram, under the
+ <emphasis>
+ <property>action-mappings</property></emphasis> node, under the <emphasis>
+ <property>struts-config.xml</property></emphasis> node in Tree view, in <property>Web Projects
+ view</property> and in the <property>Outline view</property>. Also, note the asterisk to the right of the name,
+ <emphasis>
+ <property>struts-config.xml</property>,</emphasis> in the <property>Outline view</property> showing that the file has been changed, but
+ not saved to disk.</para>
+ </section>
+ <section id="CreatingaLink">
+ <title>Creating a Link</title>
+ <para>Let's now create a link from the <emphasis>
+ <property>inputname.jsp</property></emphasis> page to the action.</para>
+ <itemizedlist>
+ <listitem>
+ <para>On the left-hand side of the diagram in the column of icons, click on the Create New Connection
+ icon( <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_1.png"/>
+ </imageobject>
+ </inlinemediaobject>).</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <listitem>
+ <para>In the connect-the-components mode you are in now, click on the <emphasis>
+ <property>/pages/inputname.jsp</property>
+ </emphasis> icon in the diagram and then click on the <emphasis>
+ <property>/greeting</property>
+ </emphasis> action</para>
+ </listitem>
+ </itemizedlist>
+ <para>A link will be created from the page to the action.</para>
+ </section>
+ <section id="CreatingaForward">
+ <title>Creating a Forward</title>
+ <para>Next, we are going to create a forward for the action.</para>
+ <itemizedlist>
+ <listitem>
+ <para>On the left-hand side of the diagram in the column of icons, click on
+ the Create New Connection
+ icon( <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_1.png"/>
+ </imageobject>
+ </inlinemediaobject>), again.</para>
+ </listitem>
+ </itemizedlist>
+
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>/greeting</property>
+ </emphasis> action icon in the diagram and then click on the <emphasis>
+ <property>pages/greeting.jsp</property>
+ </emphasis> icon</para>
+ </listitem>
+ <listitem>
+ <para>That's it. A link will be drawn from the actions new greeting
+ forward to the <emphasis>
+ <property>greeting.jsp</property></emphasis> JSP page. Note that the forwards name will be
+ set based on the name of the target JSP file name. If you don't
+ like it, you can easily change it</para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property>Tree</property>
+ </emphasis> tab at the bottom of the editor window (between Diagram and
+ Source)</para>
+ </listitem>
+ <listitem>
+ <para>Expand the <emphasis>
+ <property>struts-config.xml/action-mappings/ /greeting</property>
+ </emphasis> node and then select the greeting forward</para>
+ </listitem>
+ <listitem>
+ <para>In the Properties Editor to the right, change the text to
+ "sayHello" in the <emphasis>
+ <property>Name</property></emphasis> field</para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property>Diagram</property>
+ </emphasis> tab at the bottom of the editor window and see how the diagram
+ is also updated to reflect the change</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="CreatingaGlobalForward">
+ <title>Creating a Global Forward</title>
+ <para>One last component that we need to create in the diagram is a global forward.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Somewhere in the top-left corner of diagram, right-click and select <emphasis>
+ <property>New > Global Forward</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Enter <emphasis>
+ <property>getName</property>
+ </emphasis> in the <emphasis>
+ <property>Name</property></emphasis> field</para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property>Change...</property>
+ </emphasis>button for Path</para>
+ </listitem>
+ <listitem>
+ <para>In the Edit Path window, switch to the <emphasis>
+ <property>Pages</property>
+ </emphasis> tab</para>
+ </listitem>
+ <listitem>
+ <para>Expand the <emphasis>
+ <property>StrutsHello > WEB-ROOT (WebContent) > pages</property>
+ </emphasis> node and then select the inputname.jsp page</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property>Ok</property>
+ </emphasis>.</para>
+ </listitem>
+ <listitem>
+ <para>Leave the rest of the fields blank and click <emphasis>
+ <property>OK</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <para>A forward object now appears on the diagram and also in the global-forwards folder
+ in the Outline view.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Tidy up the diagram, by clicking and dragging around each icon, so that
+ the diagram looks something like this:</para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Diagram View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_application/struts_application_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="CreatingaFormBean">
+ <title>Creating a Form Bean</title>
+ <para>One last thing that we need to do is to create a form bean.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Switch to the Tree viewer in the editor for the <emphasis>
+ <property>struts-config.xml</property></emphasis> file, by
+ selecting the <emphasis>
+ <property>Tree</property>
+ </emphasis> tab at the bottom of the editor window</para>
+ </listitem>
+ <listitem>
+ <para>Right-click <emphasis>
+ <property>struts-config.xml > form-beans</property>
+ </emphasis> and select Create Form Bean</para>
+ </listitem>
+ <listitem>
+ <para>Enter <emphasis>
+ <property>GetNameForm</property>
+ </emphasis> in the name field and <emphasis>
+ <property>sample.GetNameForm</property>
+ </emphasis> for type</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>To save your changes to struts-config.xml, select <emphasis>
+ <property>File > Save</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ <para>Note the disappearance of the asterisk next to the name, <emphasis>
+ <property>struts-config.xml</property>.</emphasis></para>
+ </section>
+ </section>
+</chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/struts_validation.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/struts_validation.xml (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/en-US/struts_validation.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,239 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<chapter id="struts_validation" xreflabel="struts_validation">
+ <?dbhtml filename="struts_validation.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Struts</keyword>
+ <keyword>Struts Validation</keyword>
+ </keywordset>
+ </chapterinfo>
+<title>Struts Validation Examples</title>
+
+<para><property>Validation</property> of input is an important part of any Web application. All Apache Jakarta frameworks,
+including Struts, can use a common Jakarta Validation Framework for streamlining this aspect of Web
+application development. The Validation Framework allows you to define validation rules and then apply these rules on the client-side or the server-side.</para>
+
+ <para>JBoss Developer Studio makes using the <property>Validation Framework</property> in Struts even easier with the help of a specialized editor for the XML files that controls validation in a project. In this document, we'll show you how this all works by creating some simple client-side validation and server-side validation examples.</para>
+
+<section id="StartingPoint">
+<?dbhtml filename="StartingPoint.html"?>
+<title>Starting Point</title>
+<para>The example assumes that you have already created our sample "StrutsHello" application from the
+Getting Started Guide for Creating a Struts Application. You should have the JBoss Developer Studio perspective
+ open on this StrutsHello project.</para>
+</section>
+
+<section id="DefiningTheValidationRule">
+<?dbhtml filename="DefiningTheValidationRule.html"?>
+<title>Defining the Validation Rule</title>
+<para>In these steps you will set up the validation that can be used for either client-side or
+server side validation. You need to enable validation as a part of the project, define an error message, and tie it into an appropriate part of the application.</para>
+
+<itemizedlist>
+<listitem><para>Right-click on a "plug-ins" node under the <emphasis><property>StrutsHello > Configuration > default > struts-config.xml</property></emphasis> node in the Web Projects view and select <emphasis><property>Create Special Plugin > Validators</property></emphasis> from the context menu</para></listitem>
+<listitem><para>Further down in the Web Projects view, right-click on the
+<emphasis><property>StrutsHello > ResourceBundles</property></emphasis> node and select <emphasis><property> New > Properties File...</property></emphasis>from the context menu</para></listitem>
+<listitem><para>In the dialog box, click on the <emphasis><property>Browse...</property></emphasis>button next to the Folder field, expand the
+ JavaSource folder in this next dialog box, select the sample subfolder, and click on the <emphasis><property>OK</property></emphasis> button</para></listitem>
+ <listitem><para>Back in the first dialog box, type in "applResources" for the Name field and click on the <emphasis><property>Finish</property></emphasis> button</para></listitem>
+<listitem><para>Right-click on a newly created file and select <emphasis><property>Add > Default Error Messages</property></emphasis>
+ from the context menu</para></listitem>
+
+<listitem><para>Drag up the sample.applResources icon until you can drop it on the resources folder under struts-config.xml</para></listitem>
+<listitem><para>Select<emphasis><property> File > Save </property></emphasis>All from the menu bar</para></listitem>
+<listitem><para>Select validation.xml under the <emphasis><property>StrutsHello > Validation</property></emphasis> node and double-click it to open it with the JBoss Tools XML Editor</para></listitem>
+<listitem><para>Here you must create a Formset.</para></listitem>
+<listitem><para>In the validation.xml file editor click the button <emphasis><property>Create Formset</property></emphasis> on the panel <emphasis><property>Formsets</property></emphasis></para></listitem>
+<listitem><para>In the dialog <emphasis><property>Add Formset</property></emphasis> fill the fields <emphasis><property>Language</property></emphasis> and <emphasis><property>Country</property></emphasis> or just leave them empty to create a default formset. Click <emphasis><property>OK</property></emphasis></para></listitem>
+</itemizedlist>
+<figure>
+ <title>Create Formset</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_validation/struts_validation.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<itemizedlist>
+<listitem><para>Expand the "form-beans" node under the <emphasis><property>StrutsHello > Configuration > default > struts-config.xml node.</property></emphasis> Then, drag the form bean "GetNameForm" and drop it onto a formset in the <property>XML</property> Editor</para></listitem>
+<listitem><para>In the Validation Editor, expand the formset node, right-click GetNameForm, and select <emphasis><property>Create Field...</property></emphasis> from the context menu</para></listitem>
+<listitem><para>Enter a name for Property in the dialog box. A new property will be created:</para></listitem>
+</itemizedlist>
+<figure>
+ <title>New Property Is Added</title>
+<mediaobject>
+ <imageobject>
+ <imagedata fileref="images/struts_validation/struts_validation_2.png"/>
+ </imageobject>
+</mediaobject>
+</figure>
+<itemizedlist>
+<listitem><para>In the Properties view for the name field to the right of the "tree" for the validation.xml file, click on the <emphasis><property>Change...</property></emphasis>button next to the Depends entry field</para></listitem>
+<listitem><para>In the displayed double list, select <emphasis><property>required</property></emphasis> from the left list and then click <emphasis><property>Add</property></emphasis></para></listitem>
+ <listitem><para>Click <emphasis><property>Ok</property></emphasis></para></listitem>
+<listitem><para>Right-click name and select <emphasis><property>Add Arg...</property></emphasis> from the context menu</para></listitem>
+<listitem><para>In the Add Arg dialog box, click on the <emphasis><property>Change...</property></emphasis>button next to the <emphasis><property>Key</property></emphasis> field</para></listitem>
+ <listitem><para>In the Key dialog box that appears now, click on the <emphasis><property>Add</property></emphasis> button</para></listitem>
+ <listitem><para>Enter "name.required" in the Name field, and enter a person's name in the Value field</para></listitem>
+ <listitem><para>Click <emphasis><property>Finish</property></emphasis>, then <emphasis><property>Ok</property></emphasis>, and then <emphasis><property>Ok</property></emphasis> again</para></listitem>
+<listitem><para>Select <emphasis><property>File > Save All</property></emphasis> from the menu bar</para></listitem>
+</itemizedlist>
+</section>
+
+<section id="Client-SideValidation">
+<?dbhtml filename="Client-SideValidation.html"?>
+<title>Client-Side Validation</title>
+<para>Client-side <property>validation</property> uses a scripting language (like JavaScript) running in the client browser to actually do the <property>validation</property>. In a Struts application using the <property>Validation</property> Framework, however, you don't actually have to do any of the script coding. The <property>Validation</property> Framework handles this.</para>
+<para>To see how this works in our application, you'll just need to make a couple of modifications to one of the JSP files.</para>
+<itemizedlist>
+<listitem><para>Double-click inputname.jsp under <emphasis><property>StrutsHello > WEB-ROOT(WebContent) > pages</property></emphasis> to open it for editing</para></listitem>
+<listitem><para>Find the tag near the top and hit Return to make a new line under it</para></listitem>
+ <listitem><para>In the JBoss Tools Palette view to the right, open the Struts HTML folder and click on the javascript tag</para></listitem>
+<listitem><para>Back in the editor, just in front of the closing slash for this inserted tag, hit Ctrl+Space and select "formName" from the prompting menu</para></listitem>
+<listitem><para>Over in the Web Projects view, select GetNameForm under the <emphasis><property>StrutsHello > Configuration > default > struts-config.xml > form-beans</property></emphasis> node, drag it, and drop it between the quotes in the editor</para></listitem>
+<listitem><para>Modify the <code><html:form></code> tag by inserting this attribute:</para></listitem>
+</itemizedlist>
+<programlisting role="XML"><![CDATA[onsubmit="return validateGetNameForm(this)"
+]]></programlisting>
+<para></para>
+<para>The file should now look like this:</para>
+<programlisting role="XML"><![CDATA[
+<%@ taglib uri="/WEB-INF/struts-html" prefix="html" %>
+
+<html:html >
+ <head>
+ <html:javascript formName="GetNameForm"/>
+ <title></title>
+ </head>
+ <body>
+ <html:form action="/greeting.do" onsubmit="return validateGetNameForm(this)">
+ Input name:<html:text property="name"/><html:submit value="Say Hello!"/>
+ </html:form>
+ </body>
+</html:html>
+]]></programlisting>
+<itemizedlist>
+<listitem><para>Select<emphasis><property> File > Save </property></emphasis>from the menu bar</para></listitem>
+<listitem><para>Start JBoss Application Server by clicking on its icon (a right-pointing arrow) in the toolbar</para></listitem>
+ <listitem><para>Click the Run icon(<inlinemediaobject> <imageobject>
+ <imagedata fileref="images/struts_validation/struts_validation_1.png"/>
+ </imageobject></inlinemediaobject>) or right click your project folder and select <emphasis><property>Run As > Run on Server</property></emphasis></para></listitem>
+</itemizedlist>
+
+<itemizedlist><listitem><para>In the browser window, click on the "Say Hello!" button without having entered any name in the form</para></listitem></itemizedlist>
+<para>A JavaScript error message should be displayed in an alert box.</para>
+</section>
+<section id="Server-SideValidation">
+<?dbhtml filename="Server-SideValidation.html"?>
+<title>Server Side Validation</title>
+<para>Server side validation does the validation inside the application on the server. In a Struts application using the Validation Framework, you still don't have to do any of the actual validation coding. The Validation Framework handles this. You will though have to make a few changes to the JSP file you modified for client-side validation along with a change to an action and a few changes to the form bean class.</para>
+</section>
+
+<section id="EditingTheJSPFile">
+<?dbhtml filename="EditingTheJSPFile.html"?>
+<title>Editing the JSP File</title>
+<itemizedlist>
+<listitem><para>Reopen inputname.jsp for editing</para></listitem>
+<listitem><para>Delete the <emphasis role="italic"><property>"onsubmit"</property></emphasis> attribute in the <code><html:form></code> element that you put in for client-side validation</para></listitem>
+
+<listitem><para>Add an <code><html:errors/></code> tag after the
+ <code><html:form></code>
+ tag</para></listitem>
+</itemizedlist>
+<para>The JSP file should now look like this:</para>
+
+ <programlisting role="XML"><![CDATA[<%@ taglib uri="/WEB-INF/struts-html" prefix="html" %>
+<html:html >
+<head>
+ <html:javascript formName="GetNameForm"/>
+ <title></title>
+ </head>
+ <body>
+ <html:form action="/greeting.do" >Input name:<html:text property="name"/>
+ <html:submit value="Say Hello!"/>
+ </html:form>
+ <html:errors/>
+ </body>
+</html:html>
+]]></programlisting>
+
+</section>
+
+<section id="EditingTheAction">
+<?dbhtml filename="EditingTheAction.html"?>
+<title>Editing the Action</title>
+<itemizedlist>
+<listitem><para>In the Web Projects view, expand the node under the <emphasis><property>StrutsHello > Configuration > default > struts-config.xml > action-mappings</property></emphasis> node, right-click the <emphasis><property>/greeting</property></emphasis> action, and then select <emphasis><property>Properties...</property></emphasis>from the context menu</para></listitem>
+
+ <listitem><para>In the Edit Properties window, insert the cursor into the value column for the input property and click on the <property>...</property> button</para></listitem>
+
+ <listitem><para>In the dialog box, make sure the Pages tab is selected, select <emphasis><property>StrutsHello > WEB-ROOT(WebContent) > pages > inputname.jsp</property></emphasis>, click the <emphasis><property>Ok</property></emphasis> button, and then click on the <emphasis><property>Close</property></emphasis> button</para></listitem>
+</itemizedlist>
+</section>
+<section id="EditingTheFormBean">
+<?dbhtml filename="EditingTheFormBean.html"?>
+
+<title>Editing the Form Bean</title>
+<itemizedlist>
+<listitem><para>Right-click the <emphasis><property>/greeting</property></emphasis> action again and select Open Form-bean Source to open the GetNameForm.java file for editing</para></listitem>
+<listitem><para>Change the class that it extends from: <emphasis><property>org.apache.struts.action.ActionForm</property></emphasis> to <emphasis><property>org.apache.struts.validator.ValidatorForm</property></emphasis></para></listitem>
+<listitem><para>Comment out a validate method</para></listitem>
+</itemizedlist>
+<para>The file should now look like this:</para>
+<programlisting role="JAVA"><![CDATA[package sample;
+import javax.servlet.http.HttpServletRequest;
+import org.apache.struts.action.ActionErrors;
+import org.apache.struts.action.ActionMapping;
+public class GetNameForm extends
+
+org.apache.struts.validator.ValidatorForm
+{
+
+ private String name = "";
+
+ /**
+ * @return Returns the name.
+ */
+ public String getName()
+ {
+ return name;
+ }
+
+ /**
+ * @param name The name to set.
+ */
+ public void setName(String name)
+ {
+ this.name = name;
+ }
+
+ public GetNameForm ()
+ {
+ }
+
+ public void reset(ActionMapping actionMapping,
+ HttpServletRequest request)
+ {
+ this.name = "";
+ }
+
+ // public ActionErrors validate(ActionMapping actionMapping,
+ // HttpServletRequest request)
+ //{
+ // ActionErrors errors = new ActionErrors();
+ // return errors;
+ // }
+ }
+]]></programlisting>
+
+<itemizedlist>
+<listitem><para>Select <emphasis><property>File > Save All </property></emphasis>from the menu bar</para></listitem>
+<listitem><para>Reload the application into JBoss AS by clicking on the "Change Time Stamp" icon (a finger pointing with a little star) in the toolbar</para></listitem>
+<listitem><para>Run the application</para></listitem>
+<listitem><para>In the browser window, click on the "Say Hello!" button without having entered any name in the form</para></listitem>
+</itemizedlist>
+<para>The error message should appear in a refreshed version of the form.</para>
+</section>
+
+</chapter>
\ No newline at end of file
Modified: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/pom.xml
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/pom.xml 2010-03-12 01:02:00 UTC (rev 20785)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/pom.xml 2010-03-12 01:03:11 UTC (rev 20786)
@@ -32,7 +32,7 @@
<profile>
<id>releaseJBDS</id>
<properties>
- <master>master.xml</master>
+ <master>master_output.xml</master>
<xsl-single>classpath:/xslt/com/jboss/tools/xhtml-single-release.xsl</xsl-single>
<xsl-chunked>classpath:/xslt/com/jboss/tools/xhtml-release.xsl</xsl-chunked>
<xsl-pdf>classpath:/xslt/com/jboss/tools/pdf.xsl</xsl-pdf>
@@ -96,9 +96,9 @@
<configuration>
<sourceDocumentName>${master}</sourceDocumentName>
- <sourceDirectory>${pom.basedir}/en</sourceDirectory>
+ <sourceDirectory>${pom.basedir}/en-US</sourceDirectory>
<imageResource>
- <directory>${pom.basedir}/en</directory>
+ <directory>${pom.basedir}/en-US</directory>
<includes>
<include>images/**/*</include>
</includes>
Added: branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/publican.cfg
===================================================================
--- branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/publican.cfg (rev 0)
+++ branches/jbosstools-3.1.x/struts/docs/struts_tools_tutorial/publican.cfg 2010-03-12 01:03:11 UTC (rev 20786)
@@ -0,0 +1,7 @@
+# Config::Simple 4.59
+# Fri Nov 20 13:19:45 2009
+
+xml_lang: en-US
+type: Book
+brand: JBoss
+
14 years, 3 months
- 1
- 0
JBoss Tools SVN: r20785 - in branches/jbosstools-3.1.x/smooks/docs/reference: en-US and 8 other directories.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-11 20:02:00 -0500 (Thu, 11 Mar 2010)
New Revision: 20785
Added:
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Author_Group.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Book_Info.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Preface.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Revision_History.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.ent
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page1.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page2.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page2a.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page2b.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page3.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page3a.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page6.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page7.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page8.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page9.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/favicon.ico
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor1.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor1a.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor2.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor3.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor4.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor5.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor6.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor7.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/introduction/
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/introduction/introduction1.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/introduction/introduction2.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/jbosstools_logo.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process1.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process2.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process3.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process4.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process5.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process6.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process7.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start1.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start10.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start11.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start12.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start13a.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start2.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start6.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start7.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start8.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9a.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9b.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9c.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start_6a.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/sourcemodel_structured.jpg
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/targetmodel_structured.jpg
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_1.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_10.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_11.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_2.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_3.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_4.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_5.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_6.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_7.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_7a.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_8.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_9.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator_settings.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/source_editor1.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/source_editor2.png
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/introduction.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/master.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/master_output.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/options_page.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/process_page.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/quick_start.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/references.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_configurationpage.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_graphicalpage.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_sourcepage.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/summary.xml
branches/jbosstools-3.1.x/smooks/docs/reference/en-US/tasks.xml
branches/jbosstools-3.1.x/smooks/docs/reference/publican.cfg
Removed:
branches/jbosstools-3.1.x/smooks/docs/reference/en/
Modified:
branches/jbosstools-3.1.x/smooks/docs/reference/pom.xml
Log:
updated to build with publican
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Author_Group.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Author_Group.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Author_Group.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,7 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<authorgroup><author>
+ <firstname>Xue(Dart)</firstname>
+ <surname>Peng</surname>
+ </author></authorgroup>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Book_Info.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Book_Info.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Book_Info.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<bookinfo><title>Smooks Developer Tools Reference Guide</title><subtitle>Provides information relating to the Smooks Tools module.</subtitle><productname>JBoss Developer Studio</productname><productnumber>3.0</productnumber><edition>1.0</edition><pubsnumber>0</pubsnumber><abstract><para>The Smooks Developer Tools Reference Guide explains how to use Smooks Tools to graphically edit Smooks configuration files.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Preface.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Preface.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Preface.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<preface><title>Preface</title><xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></xi:fallback></xi:include></preface>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Revision_History.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Revision_History.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Revision_History.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<appendix><title>Revision History</title><simpara><revhistory><revision><revnumber>0</revnumber><date>Fri Nov 20 2009</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.ent
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.ent (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.ent 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "JBoss">
+<!ENTITY BOOKID "Smooks_Developer_Tools_Reference_Guide">
+<!ENTITY YEAR "2010">
+<!ENTITY HOLDER "Red Hat">
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/Smooks_Developer_Tools_Reference_Guide.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,12 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<book>
+<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="tasks.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="references.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="summary.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+</book>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page2a.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page2a.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page2b.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page2b.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page3a.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page3a.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page8.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page9.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/config_page/config_page9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/favicon.ico
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/favicon.ico
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor1a.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor1a.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/graph_editor/graph_editor7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/introduction/introduction1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/introduction/introduction1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/introduction/introduction2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/introduction/introduction2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/jbosstools_logo.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/jbosstools_logo.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/process_page/process7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start10.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start10.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start11.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start11.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start12.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start12.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start13a.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start13a.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start8.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9a.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9a.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9b.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9b.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9c.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start9c.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start_6a.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/quick_start_6a.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/sourcemodel_structured.jpg
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/sourcemodel_structured.jpg
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/targetmodel_structured.jpg
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/quick_start/targetmodel_structured.jpg
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_10.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_10.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_11.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_11.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_7a.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_7a.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_8.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_9.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/reference/reference_9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator_settings.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/smooks_conf_validator_settings.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/source_editor1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/source_editor1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/source_editor2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/images/source_editor/source_editor2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/introduction.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/introduction.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/introduction.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,195 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="introduction">
+ <?dbhtml filename="introduction.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Introduction</title>
+ <para>This chapter gives you a short introduction to Smooks, Smooks tools and its installation.</para>
+ <para>First, have a look at the key features of Smooks tools:</para>
+ <section>
+ <title>Key Features of Smooks Tools</title>
+ <para>Here, we provide you with a key functionality which is integrated in Smooks tools.</para>
+ <table>
+
+ <title>Key Functionality for Smooks Tools</title>
+ <tgroup cols="3">
+
+ <colspec colnum="1" align="left" colwidth="2*"/>
+ <colspec colnum="2" colwidth="4*"/>
+ <colspec colnum="3" align="left" colwidth="2*"/>
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+ <entry>Chapter</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry><para>Smooks Configuration File Wizard</para></entry>
+ <entry><para>Smooks tools allows to create/edit the Smooks configuration file for Java2Java data transformation.</para></entry>
+ <entry>
+ <link linkend="config_file_wizzard">Smooks Configuration File Wizard</link>
+ </entry>
+ </row>
+
+ <row>
+ <entry><para>Smooks Editor</para></entry>
+ <entry><para>Smooks Editor helps configure the created Smooks configuration file.</para></entry>
+ <entry>
+ <link linkend="process_tab">Smooks Editor</link>
+ </entry>
+ </row>
+
+ </tbody>
+
+ </tgroup>
+ </table>
+
+
+
+ </section>
+
+
+
+ <section>
+ <title>What is Smooks?</title>
+
+ <para><property>Smooks</property> is a Java Framework/Engine for processing XML and non XML
+ data (CSV, EDI, Java, JSON etc).It provides: </para>
+ <para/>
+ <para>
+ <orderedlist numeration="upperroman" inheritnum="inherit">
+ <listitem>
+ <para><emphasis role="bold">Transformation</emphasis>: Perform a wide range of
+ Data Transforms. Supports many different Source and Result types
+ -XML/CSV/EDI/Java/JSON to XML/CSV/EDI/Java/JSON.</para>
+ </listitem>
+ <listitem>
+ <para><emphasis role="bold">Java Binding</emphasis>: Bind into a Java Object
+ Model from any data source (CSV, EDI, XML, Java, JSON etc). </para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis role="bold">Huge Message Processing</emphasis>: Process huge
+ messages (GBs) - Split, Transform and Route message fragments to JMS, File,
+ Database etc destinations. Route multiple message formats to multiple
+ destinations in a single pass over a message. </para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis role="bold">Message Enrichment</emphasis>: Enrich a message with
+ data from a Database, or other Datasources. </para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis role="bold">Combine</emphasis>: Combine the above features in
+ different ways e.g. add Message Enrichment as part of a Splitting and
+ Routing process. </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ <figure>
+ <title>Smooks</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/introduction/introduction1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> For more informations about <property>Smooks</property>, please visit <ulink
+ url="http://www.smooks.org">Smooks official site</ulink>.</para>
+ </section>
+ <section>
+ <title>What is Smooks Tools?</title>
+
+ <para>Smooks tools is a set of graphical tools for editing Smooks configuration file
+ based on Eclipse.</para>
+ <figure>
+ <title>Smooks Form editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/introduction/introduction2.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <!-- <para>The easiest way to use the Smooks Configuration Editor is to create a project
+ (Java project, an ESB project, etc.), right-click on it and select <property>New -> Other</property>
+ to open the New wizard. Drill into <property>Smooks -> Smooks Configuration File</property>
+ and continue through the wizard.
+ Once the file is created, it will open in the Smooks Configuration Editor.</para> -->
+ </section>
+ <section>
+ <title>Adding Smooks jars</title>
+
+ <para>During your development, you probably will be faced with the
+ necessity to include some additional Smooks jars to your project.
+ This problem can be solved in such a way:</para>
+ <itemizedlist>
+ <listitem><para>Create the folder named "lib" inside your project,if it doesn't exist yet.
+ Copy all the Smooks jars you need to include into the <emphasis><property>lib</property></emphasis> directory.
+ </para></listitem>
+ <listitem><para>Right-click on the project and select Properties.</para></listitem>
+ <listitem><para>Select the "Java Build Path" item in the Properties list, then the Libraries tab, and click "Add JARs".
+ </para></listitem>
+ <listitem><para>In the Jar Selection dialog, select all the jars in the "lib" directory you want to include and click OK.</para></listitem>
+ <listitem><para>
+ Now you should see all the jars
+ included to your project hierarchy. </para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Smooks Form editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/introduction/introduction2.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <!-- <para>The easiest way to use the Smooks Configuration Editor is to create a project
+ (Java project, an ESB project, etc.), right-click on it and select <property>New -> Other</property>
+ to open the New wizard. Drill into <property>Smooks -> Smooks Configuration File</property>
+ and continue through the wizard.
+ Once the file is created, it will open in the Smooks Configuration Editor.</para> -->
+ </section>
+ <!-- <section>
+ <title>How to install Smooks dev tools?</title>
+
+ <para> The Smooks tools was included by the <property>JBoss Tools</property> since 3.0.0
+ Beta1 version. You can download the <property>JBoss Tools</property> from <ulink
+ url="http://jboss.org/tools/download.html">JBoss download site</ulink>.</para>
+ <para> Smooks tools (<property>JBoss Tools</property>) run with the latest Eclipse and
+ other required plug-ins (GEF, EMF, etc.).</para>
+ <para> You should download the latest IDE for Java EE developers from <ulink
+ url="http://www.eclipse.org/downloads/"> Eclipse site</ulink>. It contains many plug-ins (
+ GEF, EMF, etc. ) required by Smooks dev tools. </para>
+ <para>The Smooks Configuration depends on having all of the appropriate Smooks runtime jars in the path of the Eclipse Plug-in or Java Project in the Eclipse workspace.
+
+ The easiest solution is to do the following:
+ <itemizedlist>
+ <listitem><para>1) Download the Smooks distribution from here: http://www.smooks.org/mediawiki/index.php?title=Downloads .
+ Grab the latest "ALL" distribution (as of today, it is the Smooks v.1.2.2 "ALL" distribution) and it will include binaries, examples, etc.</para></listitem>
+ <listitem><para>2) Extract files from the archive somewhere on your machine.</para></listitem>
+ <listitem><para>3) In your Eclipse workspace, copy the Smooks jars into a directory of your Eclipse plug-in or Java project named "lib".</para></listitem>
+ <listitem><para>4) For your Eclipse Plug-in or Java Project, right-click on the project and select Properties.</para></listitem>
+ <listitem><para>5) Select the "Java Build Path" item in the Properties list, select the Libraries tab, and click "Add JARs"
+ </para></listitem>
+ <listitem><para>6) In the Jar Selection dialog, select all the jars in the "lib" directory mentioned in step 3 and click <property>OK</property>.
+ </para></listitem>
+ <listitem><para>7) Click <property>OK</property> to close the Properties dialog. Now you should see a "Referenced Libraries" node that appeared in your project hierarchy in Eclipse.
+ </para></listitem>
+ </itemizedlist>
+
+ </para>
+ <para>Now let's progress to more advanced topics.</para>
+ </section>
+ -->
+</chapter>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/master.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/master.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/master.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+[
+<!ENTITY introduction SYSTEM "introduction.xml">
+<!ENTITY tasks SYSTEM "tasks.xml">
+<!ENTITY references SYSTEM "references.xml">
+<!ENTITY summary SYSTEM "summary.xml">
+]>
+<book>
+
+ <bookinfo>
+
+ <title>Smooks Developer Tools Reference Guide</title>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata format="PNG" fileref="images/jbosstools_logo.png" />
+ </imageobject>
+ <imageobject role="html">
+ <imagedata/>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author>
+ <firstname>Xue(Dart)</firstname>
+ <surname>Peng</surname>
+ </author>
+ <copyright>
+ <year>2009,2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo>
+ Version: 1.1.0.GA
+ </releaseinfo>
+
+ <abstract>
+ <title/>
+ <para>
+ <ulink
+ url="http://download.jboss.org/jbosstools/nightly-docs/en/smooks/pdf/Smooks_Re...">PDF version</ulink>
+ </para>
+ </abstract>
+
+
+ </bookinfo>
+ <toc/>
+ &introduction;
+ &tasks;
+ &references;
+ &summary;
+</book>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/master_output.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/master_output.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/master_output.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,1132 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+[
+<!ENTITY introduction SYSTEM "modules/introduction.xml">
+<!ENTITY quickstart SYSTEM "modules/quick_start.xml">
+<!ENTITY smooksformeditor_graphicaltab SYSTEM "modules/smooksformeditor_graphicalpage.xml">
+<!ENTITY smooksformeditor_configurationtab SYSTEM "modules/smooksformeditor_configurationpage.xml">
+<!ENTITY smooksformeditor_sourcetab SYSTEM "modules/smooksformeditor_sourcepage.xml">
+]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff">
+
+ <bookinfo>
+
+ <title>Smooks Dev Tools Reference Guide</title>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
+ </imageobject>
+ <imageobject role="html">
+ <imagedata></imagedata>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author>
+ <firstname>Xue(Dart)</firstname>
+ <surname>Peng</surname>
+ </author>
+
+ <pubdate>November 2008</pubdate>
+ <copyright>
+ <year>2009</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo><diffmk:wrapper diffmk:change="changed">
+ Version: 1.1.0.CR1
+ </diffmk:wrapper></releaseinfo>
+
+ <abstract>
+ <title></title>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/smooks/pdf/Smooks_Re...">PDF version</ulink>
+ </para>
+ </abstract>
+
+
+ </bookinfo>
+ <toc></toc>
+
+<chapter id="introduction" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/smooks/docs/reference/en/modules/introduction.xml">
+ <?dbhtml filename="introduction.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Introduction</title>
+ <para>This chapter gives you a short introduction to Smooks, Smooks tools and its installation.</para>
+ <para>First, have a look at the key features of Smooks tools:</para>
+ <section>
+ <title>Key Features of Smooks Tools</title>
+ <para>Here, we provide you with a key functionality which is integrated in Smooks tools.</para>
+ <table>
+
+ <title>Key Functionality for Smooks Tools</title>
+ <tgroup cols="3">
+
+ <colspec align="left" colnum="1" colwidth="2*"></colspec>
+ <colspec colnum="2" colwidth="4*"></colspec>
+ <colspec align="left" colnum="3" colwidth="2*"></colspec>
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+ <entry>Chapter</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry><para>Smooks Configuration File Wizard</para></entry>
+ <entry><para>Smooks tools allows to create/edit the Smooks configuration file for Java2Java data transformation.</para></entry>
+ <entry>
+ <link linkend="config_file_wizzard">Smooks Configuration File Wizard</link>
+ </entry>
+ </row>
+
+ <row>
+ <entry><para>Smooks Editor</para></entry>
+ <entry><para>Smooks Editor helps configure the created Smooks configuration file.</para></entry>
+ <entry>
+ <link linkend="quickstart_formeditor">Smooks Editor</link>
+ </entry>
+ </row>
+
+ </tbody>
+
+ </tgroup>
+ </table>
+
+
+
+ </section>
+
+
+
+ <section>
+ <title>What is Smooks?</title>
+
+ <para><property moreinfo="none">Smooks</property> is a Java Framework/Engine for processing XML and non XML
+ data (CSV, EDI, Java, JSON etc).</para>
+ <para></para>
+ <para>
+ <orderedlist continuation="restarts" inheritnum="inherit" numeration="upperroman">
+ <listitem>
+ <para><emphasis role="bold">Transformation</emphasis>: Perform a wide range of
+ Data Transforms. Supports many different Source and Result types
+ -XML/CSV/EDI/Java/JSON to XML/CSV/EDI/Java/JSON.</para>
+ </listitem>
+ <listitem>
+ <para><emphasis role="bold">Java Binding</emphasis>: Bind into a Java Object
+ Model from any data source (CSV, EDI, XML, Java, JSON etc). </para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis role="bold">Huge Message Processing</emphasis>: Process huge
+ messages (GBs) - Split, Transform and Route message fragments to JMS, File,
+ Database etc destinations. Route multiple message formats to multiple
+ destinations in a single pass over a message. </para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis role="bold">Message Enrichment</emphasis>: Enrich a message with
+ data from a Database, or other Datasources. </para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis role="bold">Combine</emphasis>: Combine the above features in
+ different ways e.g. add Message Enrichment as part of a Splitting and
+ Routing process. </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ <figure float="0">
+ <title>Smooks</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/introduction/introduction1.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> For More informations about <property moreinfo="none">Smooks</property>, please visit <ulink url="http://www.smooks.org">Smooks official site</ulink>.</para>
+ </section>
+ <section>
+ <title>What is Smooks Tools?</title>
+
+ <para>Smooks tools is a set of graphical tools for editing Smooks configuration file
+ based on Eclipse.</para>
+ <figure float="0">
+ <title>Smooks Form editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/introduction/introduction2.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section>
+ <title>How to install Smooks dev tools?</title>
+
+ <para> The Smooks tools was included by the <property moreinfo="none">JBoss Tools</property> since 3.0.0
+ Beta1 version. You can download the <property moreinfo="none">JBoss Tools</property> from <ulink url="http://jboss.org/tools/download.html">JBoss download site</ulink>.</para>
+ <para> Smooks tools (<property moreinfo="none">JBoss Tools</property>) run with the latest Eclipse and
+ other required plug-ins (GEF, EMF, etc.).</para>
+ <para> You should download the latest IDE for Java EE developers from <ulink url="http://www.eclipse.org/downloads/"> Eclipse site</ulink>. It contains many plug-ins (
+ GEF, EMF, etc. ) required by Smooks dev tools. </para>
+
+ <para>Now let's progress to more advanced topics.</para>
+ </section>
+
+</chapter>
+
+
+<chapter id="quickstart" role="updated" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/smooks/docs/reference/en/modules/quick_start.xml" xreflabel="Quick Start">
+ <?dbhtml filename="quick_start.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ <keyword>java</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Quick Start</title>
+ <para> This "Quick Start" will show how to use the <property moreinfo="none">Smooks tools</property> to create/edit the Smooks
+ configuration file for Java2Java data transformation.</para>
+ <para> This chapter gives you a brief understanding of the <property moreinfo="none">Smooks tools</property>.</para>
+ <section>
+ <title>Download Smooks Java-to-Java Example</title>
+ <para> Visit <ulink url="http://www.blogjava.net/Files/reloadcn/smooks_java_java.zip">smooks examples page</ulink> to download the "java-to-java" example project. </para>
+ <tip>
+ <title>Tip:</title>
+
+ <para> The example project is based on Maven, we suggest you to create a new eclipse
+ Java project, copy the example code and .jar files from the example project and paste
+ them into the eclipse Java project. </para>
+ </tip>
+ </section>
+ <section>
+ <title>Mapping rules</title>
+ <para>At the begining of working with Smooks tools,
+ we need to understand the Java-to-Java mapping rules of this example.
+ The transform input Java class is <emphasis><property moreinfo="none">example.sourcemodel.Order</property></emphasis> , its structure looks like this :
+ </para>
+ <figure float="0">
+ <title>Order class</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/sourcemodel_structured.jpg"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Let's describe the structure of <emphasis><property moreinfo="none">example.sourcemodel.Order</property></emphasis> in short:</para>
+ <itemizedlist>
+ <listitem><para>Order class contains a <property moreinfo="none">Header</property> class and a <property moreinfo="none">List</property> class.</para></listitem>
+ <listitem><para>The <property moreinfo="none">Header</property> class has <property moreinfo="none">customerName</property>,<property moreinfo="none">customerNumber</property>,<property moreinfo="none">priority</property> as properties.</para></listitem>
+ <listitem><para>In Order class the objects of the OrderItem class are stored in the List.</para></listitem>
+ <listitem><para>OrderItem has <property moreinfo="none">price</property>,<property moreinfo="none">productId</property>,<property moreinfo="none">quantity</property> as its properties.</para></listitem>
+ </itemizedlist>
+ <para>Let's look at the transform target Java class : <emphasis><property moreinfo="none">LineOrder</property></emphasis>.</para>
+ <para>On the screen below you can see its structure:</para>
+ <figure float="0">
+ <title>LineOrder class</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/targetmodel_structured.jpg"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem><para><property moreinfo="none">LineOrder</property> class contains 3 properties:<property moreinfo="none">customerId</property>,<property moreinfo="none">customerName</property>,<property moreinfo="none">priority</property> and an array of lineItems.</para></listitem>
+ <listitem><para>The <property moreinfo="none">Header</property> class has <property moreinfo="none">customerName</property>,<property moreinfo="none">customerNumber</property>,<property moreinfo="none">priority</property> as its properties.</para></listitem>
+ <listitem><para>OrderItem objects are stored in a List.</para></listitem>
+ </itemizedlist>
+ <para>Now it's the time to define the mapping rules to transform the input source java class to the target java class:</para>
+ <itemizedlist>
+ <listitem><para>Each instance of the Order class should be mapped with an instance of the LineOrder class.</para></listitem>
+ <listitem><para>The value of <property moreinfo="none">customerName</property> of the Header class should be assigned to the <property moreinfo="none">customerName</property> property of a LineOrder instance.</para></listitem>
+ <listitem><para>The value of <property moreinfo="none">customerNumber</property> of the Header class should be assigned to the <property moreinfo="none">customerId</property> property of a LineOrder instance.</para></listitem>
+ <listitem><para>The value of <property moreinfo="none">priority</property> of the Header class should be assigned to the <property moreinfo="none">priority</property> property of LineOrder instance.</para></listitem>
+ <listitem><para>For the <property moreinfo="none">orderitems</property> List of the Order instance, it's necessary to map a new lineItems array instance of LineOrder ,
+ and each OrderItem instance in the orderItems List should be transformed to a LineItem instance,
+ those instances will be put into the lineItems array.</para></listitem>
+ <listitem><para>The value of <property moreinfo="none">productId</property> of the OrderItem instance should be assigned to the 'productCode' of LineItem.</para></listitem>
+ <listitem><para>The value of <property moreinfo="none">price</property> of OrderItem should be assigned to the <property moreinfo="none">unitPrice</property> of LineItem.</para></listitem>
+
+ </itemizedlist>
+ </section>
+
+ <section id="config_file_wizzard">
+ <title>Smooks Configuration File Wizard</title>
+ <para>Select the Smooks Java-to-Java example project that you created and right-click,
+ select the menu <emphasis><property moreinfo="none">New > Other</property>,</emphasis> then find
+ <emphasis><property moreinfo="none">Smooks > Smooks Configuration File</property>.</emphasis>
+ Click the <emphasis>
+ <property moreinfo="none">Next</property>
+ </emphasis> button. </para>
+ <figure float="0">
+ <title>Selecting Smooks Configuration File Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start1.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The first wizard page is a file path creation page. Select the <emphasis>
+ <property moreinfo="none">src</property>
+ </emphasis> folder to be the files container, and input the name
+ <emphasis><property moreinfo="none">smooks-config.xml</property>.</emphasis> Click
+ <emphasis><property moreinfo="none">Next</property>.</emphasis></para>
+ <figure float="0">
+ <title>Choosing the configuration file container and the file name</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start2.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para><diffmk:wrapper diffmk:change="changed">The second wizard page is allows you to select Smooks configuration file version. Select the appropriate one and click </diffmk:wrapper><emphasis><property moreinfo="none">Finish</property></emphasis><diffmk:wrapper diffmk:change="changed"> to complete the wizard.</diffmk:wrapper></para>
+
+
+
+ <!--<para> As the quick start introduces how to create/edit the Java-to-Java Smooks
+ configuration file, let's select the<emphasis>
+ <property>Java-to-Java</property>
+ </emphasis> type as the source/target transform data type. </para>
+
+ <figure>
+ <title>Selecting Data Type</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start3.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>On the next page you are prompted to choose the source data for transformation.
+ Let's select the <property>Order</property> class from the example project as
+ the source JavaBean class.</para>
+
+ <figure>
+ <title>Selecting the Source Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start4.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Then the wizard page asks you to choose the target data for transformation. We select
+ the <property>ListOrder</property> class as the target JavaBean class.</para>
+ <figure>
+ <title>Selecting the Target Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start5.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para/>
+
+ <tip>
+ <title>Tip:</title>
+ <para>You can omit two these steps and just press
+ <emphasis><property>Finish</property>.</emphasis> This will open the empty
+ Smooks Configuration file. It's possible to <link
+ linkend="graphicaleditor_datalink">select source/target data</link> afterwards
+ in the Smooks Graph editor.</para>
+ </tip>-->
+ </section>
+ <section id="quickstart_formeditor">
+ <title>Smooks Editor</title>
+
+ <para>When all the wizard steps are passed, a new Smooks Configuration file is created and
+ the <property moreinfo="none">Smooks Configuration Editor</property> will be opened automatically:</para>
+ <figure float="0">
+ <title>Smooks Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start6.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>On the bottom of this editor there are 5 tabs, they are :
+
+ Overview, Reader, Message Filter, Graph, Source.</para>
+ <section id="graphicaleditor_datalink">
+ <title>Adding the input data</title>
+ <para>At first, we need to add the Order class as the input data.
+ To do this, click the Reader tab, swich to the Reader/Input editor page</para>
+
+ <!--<para> This editor contains several parts: <table>
+ <title>The Smooks Editor Parts</title>
+ <tgroup cols="2">
+
+ <colspec colnum="1" align="left" colwidth="1*"/>
+ <colspec colnum="2" colwidth="5*"/>
+
+ <thead>
+ <row>
+ <entry>Editor feature</entry>
+ <entry>Functionality</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>
+ <para>Problems area</para>
+ </entry>
+ <entry>
+ <para>If there are any errors when you are editing the file, the
+ Problems area displays them</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Source data tree</para>
+ </entry>
+ <entry>
+ <para>The tree displays a structure of the transformed source
+ data</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Target data tree</para>
+ </entry>
+ <entry>
+ <para>The tree displays a structure of the transformed target
+ data</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Mapping graphical area</para>
+ </entry>
+ <entry>
+ <para>Show the data mapping connection lines</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Source/Target data selection links</para>
+ </entry>
+ <entry>
+ <para>Click the link, and <link linkend="graphicaleditor_datalink"
+ >Data Selection wizard</link> is opened helping you to
+ choose the source/target data</para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>-->
+
+
+ <para>To choose the transform data you should open <emphasis>
+ <property moreinfo="none">Reader</property></emphasis> tab and click <emphasis>
+ <property moreinfo="none">Add</property></emphasis> button in the Input Data section.</para>
+ <figure float="0">
+ <title>Input Data section</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start_6a.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>After clicking the button the <property moreinfo="none">Data Type Selection wizard</property> is
+ opened, and there are many data types in the list: Java, XML etc.</para>
+ <note>
+ <title>Note</title>
+ <para> There will become more and more data types on the list as the development goes on.
+ </para>
+ </note>
+
+ <figure float="0">
+ <title>Data Type Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start7.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Select the <emphasis>
+ <property moreinfo="none">Java</property>
+ </emphasis> data type and click <emphasis><property moreinfo="none">Next</property>,</emphasis> you will
+ see the JavaBean class selection page:</para>
+
+ <figure float="0">
+ <title>JavaBean Data Selection</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start8.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> Let's select the Order class from the example project as the source JavaBean class.After that click <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> and you should see the just added java class, being displayed in the Input Data Section.
+ </para>
+ <figure float="0">
+ <title>Displaying the Structure of the Transformed Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start9.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section>
+ <title>Adding the target Bean</title>
+ <para>After adding the input data, let's switch to the Message Filter page:</para>
+ <figure float="0">
+ <title>Displaying the Structure of the Transformed Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start9a.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click the <property moreinfo="none">Add</property> button, the <property moreinfo="none">Add Child</property> wizard page will be shown, let's select the <property moreinfo="none">Java Binding v1.2 -> Bean v1.2</property> and click <emphasis><property moreinfo="none">OK</property></emphasis> to add the Bean :
+ </para>
+ <figure float="0">
+ <title>Add Child wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start9b.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Then we can find on the Message Filter page the <property moreinfo="none">Bean v1.2</property> item added, click on it ,a Bean v1.2 section should appear to the right of the page.
+ The section represents a GUI for editing <property moreinfo="none">Bean v1.2</property> properties:</para>
+ <figure float="0">
+ <title>Bean v1.2 section</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start9c.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>You should input <property moreinfo="none">
+ lineOrder</property> as the Bean's id in the "Bean Id" field.Then you should click <property moreinfo="none">Browse</property> button
+ near the <property moreinfo="none">Class</property> textfield and select LineOrder as the Bean's class.</para>
+ <note>
+ <para>
+ When you enter a value for the <property moreinfo="none">Class</property> text field,
+ you can type 'Alt + /' and the content assist pop dialog will be shown,
+ so it's will increase the efficiency. If 'Alt + /' doesn't work,
+ try to use the 'Ctrl + space'('Key Assist' of Eclipse).
+ </para>
+ </note>
+ <para>Let's click the <property moreinfo="none">Add Binding</property> link at the bottom of this page,
+ it will show a dialog to ask the binding of what Bean properties you will prefer to add.
+ Select all and click OK, you will see a list of Binding elements added under the Bean item.</para>
+ <para>Then you should add an array of beans called <property moreinfo="none">lineItems</property> and a Bean LineItem.These two classes and Id values are:</para>
+ <para>Array Bean:</para>
+ <itemizedlist>
+ <listitem><para>BeanId : lineItems;</para></listitem>
+ <listitem><para>Class : example.trgmodel.LineItem[]</para></listitem>
+ </itemizedlist>
+ <para>LineItem Bean :</para>
+ <itemizedlist>
+ <listitem><para>BeanId : lineItem;</para></listitem>
+ <listitem><para>Class : example.trgmodel.LineItem</para></listitem>
+ </itemizedlist>
+ <note>
+ <para>
+ In Smooks , to be an array of Beans , the class value should end with '[]'. This means that this bean is an array type.
+
+ </para>
+ </note>
+ <para>To finish this work, use the <property moreinfo="none">Add Binding</property> link to add all the bindings for the Bean.</para>
+ </section>
+
+
+ </section>
+ <section id="quickstart_mapping">
+ <title>Mapping</title>
+
+
+ <para>How to map the java class just added?</para>
+
+ <para>First, you should know what to transform:</para>
+
+ <orderedlist continuation="restarts" inheritnum="inherit" numeration="loweralpha">
+ <listitem>
+ <para>Bind the <emphasis>
+ <property moreinfo="none">"customerName"</property>
+ </emphasis> property of the <property moreinfo="none">Order#header</property> to the <emphasis>
+ <property moreinfo="none">"customerName"</property>
+ </emphasis> property of <property moreinfo="none">LineOrder</property>.</para>
+ </listitem>
+ <listitem>
+ <para>Bind the <emphasis>
+ <property moreinfo="none">"customerNumber"</property>
+ </emphasis> property of the <property moreinfo="none">Order#header</property> to the <emphasis>
+ <property moreinfo="none">"customerId"</property>
+ </emphasis> property of <property moreinfo="none">LineOrder</property>.</para>
+ </listitem>
+ <listitem>
+ <para>Bind the <emphasis>
+ <property moreinfo="none">"price"</property>
+ </emphasis> property of the <property moreinfo="none">OrderItem</property> to the <emphasis>
+ <property moreinfo="none">"unitPrice"</property>
+ </emphasis> property of <property moreinfo="none">LineItem</property>.</para>
+ </listitem>
+ <listitem>
+ <para>Bind the <emphasis>
+ <property moreinfo="none">"productId"</property>
+ </emphasis> property of the <property moreinfo="none">OrderItem</property> to the <emphasis>
+ <property moreinfo="none">"productCode"</property>
+ </emphasis> property of <property moreinfo="none">LineItem</property>.</para>
+ </listitem>
+ <listitem>
+ <para>Bind the <emphasis>
+ <property moreinfo="none">"quantity"</property>
+ </emphasis> property of the <property moreinfo="none">OrderItem</property> to the <emphasis>
+ <property moreinfo="none">"unitQuantity"</property>
+ </emphasis> property of <property moreinfo="none">LineItem</property>.</para>
+ </listitem>
+ </orderedlist>
+
+ <para> Make sense?
+ You should open Design tab and click Add button. In opened Add Child Wizard,please, select <emphasis>
+ <property moreinfo="none">Add Smooks Resource>Java Binding>Bindings</property></emphasis>.
+ </para>
+ <para>First of all, you should bind <emphasis>
+ <property moreinfo="none">Order</property></emphasis> to <emphasis>
+ <property moreinfo="none">LineOrder</property></emphasis>. To do this one <emphasis>
+ <property moreinfo="none">Bindings</property></emphasis> Item should be added to the Resource List.</para>
+ <figure float="0">
+ <title>Mapping</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start10.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure><para>Click on it and you should see <emphasis>
+ <property moreinfo="none">Bindings</property></emphasis> Section to the right of <emphasis>
+ <property moreinfo="none">Message Filtering Resources</property></emphasis>.Write <emphasis> <property moreinfo="none">lineOrder</property></emphasis> in the <emphasis>
+ <property moreinfo="none">Bean id</property></emphasis> field.</para>
+ <para>Select <emphasis>
+ <property moreinfo="none">example.trgmodel.LineOrder</property></emphasis> in the <emphasis>
+ <property moreinfo="none">Class</property></emphasis> field and <emphasis>
+ <property moreinfo="none">example.srcmodel.Order</property></emphasis> in the <emphasis>
+ <property moreinfo="none">Name</property></emphasis> field.Your <emphasis> <property moreinfo="none">Smooks Configuration Editor</property></emphasis> should look like this: </para>
+ <figure float="0">
+ <title>Mapping</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start11.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Now you should bind two values <emphasis> <property moreinfo="none">"customerNumber"</property>
+ </emphasis> property of the <property moreinfo="none">Order#header</property> to the <emphasis>
+ <property moreinfo="none">"customerId"</property>
+ </emphasis> property of <property moreinfo="none">LineOrder</property>.To do this right click your just created <emphasis>
+ <property moreinfo="none">Bindings Item >Add Smooks Resource>Value</property></emphasis>
+ .</para>
+
+ <figure float="0">
+ <title> Mapping Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start12.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure><note>
+ <title>Note:</title>
+ <para>Please, remember that the root nodes of the source data and target data *MUST* be
+ connected.</para>
+ <para>This rule is not only for Java-to-Java, but also is relevant for
+ XML-to-Java </para>
+ </note>
+ <para> Do the same operation with the
+ other properties in this and other classes.</para>
+ <para>It's also necessary to bind <emphasis>
+ <property moreinfo="none">orderItems</property></emphasis> property of the <emphasis>
+ <property moreinfo="none">Order</property></emphasis> to <emphasis>
+ <property moreinfo="none">lineItems</property></emphasis> property of <emphasis>
+ <property moreinfo="none">LineOrder</property></emphasis>.The difference from the previous steps is that the <emphasis>
+ <property moreinfo="none">orderItems</property></emphasis> is presented by the list of <emphasis>
+ <property moreinfo="none">Order</property></emphasis> and <emphasis>
+ <property moreinfo="none">lineItems</property></emphasis> is the massive of <emphasis>
+ <property moreinfo="none">LineItem</property></emphasis> .To do the binding,you should use <emphasis>
+ <property moreinfo="none">Wiring Item</property></emphasis>.First you should create a new Binding item. This is a configuration that allows you to construct an object graph .Select <emphasis>
+ <property moreinfo="none">example.trgmodel.LineItem[]</property></emphasis> in the Class field and orderItems in the Name field,in bean Id write lineItems.
+ Your Smooks Configuration Editor should look like this:
+ </para>
+ <figure float="0">
+ <title> Creating Wiring Item</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start13a.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> Then you should right click <emphasis>
+ <property moreinfo="none">lineOrder</property></emphasis> binding item<emphasis>
+ <property moreinfo="none">>Add Smooks Resource>Wiring</property></emphasis>.Select <emphasis>
+ <property moreinfo="none">lineItem</property></emphasis> in <emphasis>
+ <property moreinfo="none">Bean id Ref</property></emphasis>.
+ </para>
+ <para>The final step is to add new Wiring item to lineOrder <property moreinfo="none">Binding</property>.In the <property moreinfo="none">Bean id Ref</property> select <emphasis>
+ <property moreinfo="none">lineItems</property></emphasis> and in <emphasis>
+ <property moreinfo="none">Property</property></emphasis> select <emphasis>
+ <property moreinfo="none">lineItems</property></emphasis>.</para>
+<!--
+ <para>Next, you are going to bind the properties of the <property>OrderItem</property> to
+ the properties of the <property>LineItem</property>.</paa>
+ <para>Select the <emphasis>
+ <property>"price"</property>
+ </emphasis> and drag it onto the <emphasis>
+ <property>"unitPrice"</property>
+ </emphasis> of the other side tree viewer. The Problems area shows an
+ error:</para>
+ <figure>
+ <title>Connection Error 1</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start12.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>How to deal with the error?</para>
+ <para>Please click the <emphasis>
+ <property>Fix it</property></emphasis> link, a menu is popped-up with several
+ resolve methods on it.</para>
+ <figure>
+ <title>Fixing the Connection Error</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start13.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> Select the first resolve method: <emphasis>
+ 'Connect the "OrderItem" to the
+ "LineItem" '.</emphasis> As the result the <emphasis>
+ <property>"OrderItem"</property></emphasis> is connected with
+ the <emphasis>
+ <property>"LineItem"</property>.</emphasis></para>
+ <para>But the notify message area still shows some other errors:</para>
+ <figure>
+ <title>Connection Error 2</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start14.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>OK, let's deal with the fire error. Click the <emphasis>
+ <property>Fix it</property></emphasis> link and
+ select the first resolve method. The <emphasis>
+ <property>"orderItems"</property></emphasis> is connected with
+ the <emphasis>
+ <property>"lineItems"</property>.</emphasis></para>
+
+ <tip>
+ <title>Tip:</title>
+ <para> Why does the error occur?</para>
+ <para> You will find that, if you only connect the property node without connecting the
+ parent node of the property, the "connection error" occurs.</para>
+ <para>The connection of the "price-to-unitPrice" is the
+ "Binding Connection", but it needs an "Instance Creation
+ Connection" - the connection of the
+ "OrderItem-to-LineItem".</para>
+ </tip>
+ <para> After that, connect <emphasis>
+ <property>"quantity"</property></emphasis> to the <emphasis>
+ <property>"unitQuantity"</property></emphasis> and <emphasis>
+ <property>"productId"</property></emphasis> to the
+ <emphasis>
+ <property>"productCode"</property>:</emphasis></para>
+ <figure>
+ <title>Complete Mapping</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start15.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>-->
+ <para>Now, you should save the file and the <property moreinfo="none">Smooks tools</property> generate the correct
+ configuration file content.</para>
+ <para>OK, let run the test class: <property moreinfo="none">example.Main</property>. (Please, make sure that the Smooks engine
+ loads the correct configuration file).</para>
+ <para>Success!</para>
+ </section>
+</chapter>
+
+ <!--&smooksformeditor_graphicaltab;-->
+
+<chapter id="smooksformeditor_configurationtab" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/smooks/docs/reference/en/modules/smooksformeditor_configurationpage.xml" xreflabel="Smooks Configuration Editor Page">
+ <?dbhtml filename="smooks_form_editor_configurationtab.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Smooks Design Page</title>
+ <para>In this section you will explore the details of Smooks Design Page usage.</para>
+ <para><property moreinfo="none">Smooks Design Page</property> is one tab of the <property moreinfo="none">Smooks Editor</property>. </para>
+ <figure float="0">
+ <title>Design Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page1.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>This page consists of 3 sections: Message Filtering Resources, Input Data and the section devoted to the configurations of a selected in a Message Filtering Resources section Item.</para>
+ <para> You can bind classes <link linkend="quickstart_mapping">using Bindings item
+ </link> on the Design page of the <property moreinfo="none">Smooks Editor</property>. </para>
+ <para><emphasis>
+ <property moreinfo="none">Resource list</property></emphasis> item in <emphasis>
+ <property moreinfo="none">Message Filtering Resources</property></emphasis> corresponds to the root element of the <emphasis>
+ <property moreinfo="none">smooks-config.xml</property></emphasis> file.You can configurate the next four properties using corresponding fields:</para>
+ <itemizedlist>
+ <listitem><para><emphasis>
+ <property moreinfo="none">default-selector</property></emphasis>:Defines the selector that will be applied to all resource-config elements in the <emphasis>
+ <property moreinfo="none">smooks-config.xml</property></emphasis>, where a selector is not defined. </para></listitem>
+ <listitem><para><emphasis>
+ <property moreinfo="none">default-selector-namespace</property></emphasis>:Defines the default selector namespace. </para></listitem>
+ <listitem><para><emphasis>
+ <property moreinfo="none">default-target-profile</property></emphasis>: Defines the default target profile that will be applied to all resources in the smooks-config.xml. </para></listitem>
+ <listitem><para><emphasis>
+ <property moreinfo="none">default-condition-ref</property></emphasis>:The condition is applied to resources where an empty "condition" element (i.e. <code><condition/></code>)is defined.The condition element does not reference a globally defined condition. </para></listitem>
+ </itemizedlist>
+ <para> The configuration editor also edits the <link linkend="configurationpage_parsetype">Smooks parse
+ type</link> and manages the <link linkend="configurationpage_importfile">Import
+ Files</link>.</para>
+ <section id="selector-dialog">
+ <title>Selector generate dialog</title>
+ <para>Using <emphasis>
+ <property moreinfo="none">Selector generate dialog</property></emphasis> you can allow the user to select a node for generation <property moreinfo="none">"selector"</property> for smooks-config file.
+ To open the dialog you should left click <property moreinfo="none">Browse</property> button in <emphasis>
+ <property moreinfo="none">Default Selector</property></emphasis> section.
+ </para>
+ <figure float="0">
+ <title>Selector generate dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page2a.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> When the dialog is opened you should click <property moreinfo="none">"Click to add input data"</property>to set the selector.
+ In the opened <emphasis>
+ <property moreinfo="none">Data Type Selection</property></emphasis> Wizard you should choose the type of the file and the file itself you want to load to the <emphasis>
+ <property moreinfo="none">Selector generate dialog</property></emphasis>.After that your dialog should look nearly like that:</para>
+ <figure float="0">
+ <title>Selector generate dialog after adding Input Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page2b.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The final step is to choose the node you want to make a selector for <emphasis>
+ <property moreinfo="none">smooks-config.xml</property></emphasis>.</para>
+ </section>
+ <section id="configurationpage_parsetype">
+
+ <title>Smooks Parse Type</title>
+ <para>If your config file doesn't contain <emphasis>
+ <property moreinfo="none">Global Parametres</property></emphasis> item yet, you should add it by right click <emphasis>
+ <property moreinfo="none">Resource List>Add Smooks Resource>Global Parametres</property></emphasis>.After this step you should add <emphasis>
+ <property moreinfo="none">Param</property></emphasis> to just created <emphasis>
+ <property moreinfo="none">Global Parametres</property></emphasis>. </para>
+ <figure float="0">
+ <title>Adding Param to created Global Parametres</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page2.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Then left click <emphasis>
+ <property moreinfo="none">Param</property>
+ </emphasis>and in the Param section, you will see a set of text fields: <emphasis>
+ <property moreinfo="none">Name</property></emphasis>,<emphasis>
+ <property moreinfo="none">Type</property></emphasis> and <emphasis>
+ <property moreinfo="none">Text</property></emphasis>.<emphasis>
+ <property moreinfo="none">Name</property></emphasis> value is required. To set a parse type you should write SAX/DOM to the
+ <emphasis>
+ <property moreinfo="none">Text</property></emphasis> field.</para>
+
+ <figure float="0">
+ <title>Filling Param section field Name and Text Value for set a Parse Type</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page3.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>To apply changes to the <emphasis>
+ <property moreinfo="none">smooks-config.xml</property></emphasis> click <emphasis>
+ <property moreinfo="none">Save</property></emphasis> button (<emphasis>
+ <property moreinfo="none">Ctrl+S</property></emphasis>). </para>
+ </section>
+ <section id="configurationpage_importfile">
+
+ <title>Import Smooks Configuration page</title>
+ <para> Right click <emphasis>
+ <property moreinfo="none">Resource List>Add Smooks Resource>Import Smooks Configuration</property>
+ </emphasis>, then you should see a new <emphasis>
+ <property moreinfo="none">Import Smooks Configuration</property>
+ </emphasis>item in the list (see the figure below).</para>
+
+ <figure float="0">
+ <title>Import Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page3a.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Left click the added item and to the left of <emphasis>
+ <property moreinfo="none">Message Filtering Resources Import Smooks Configuration </property></emphasis> section should appear. Click the <emphasis>
+ <property moreinfo="none">Browse</property>
+ </emphasis> button and select the file you want to import(see <link linkend="file_selection">File selection</link> section). </para>
+ <para>Click <emphasis>
+ <property moreinfo="none">Save</property></emphasis> and the <code><import></code> tag with the corresponding file path as a <emphasis>
+ <property moreinfo="none">file</property></emphasis> property will be added to the <emphasis>
+ <property moreinfo="none">smooks-config.xml</property></emphasis>.</para>
+ </section>
+ <section id="file_selection">
+ <title>File selection</title>
+ <para>Some attributes in Smooks elements should store path to a file as a value
+ (e.g. attribute <emphasis><property moreinfo="none">"mappingModel"</property></emphasis> of the element <emphasis><property moreinfo="none">"edi:reader"</property></emphasis>).
+ You can see a Browse button near the fields, that set such a value to the attribute
+ (e.g. <emphasis><property moreinfo="none">"Mapping Model"</property></emphasis> field set a value to the <emphasis><property moreinfo="none">"mappingModel"</property></emphasis> attribute).
+ </para>
+ <figure float="0">
+ <title>EDI:Reader element</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page6.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ When you click <emphasis><property moreinfo="none">Browse</property></emphasis>, the dialog prompts you click one of two buttons:
+ <emphasis><property moreinfo="none">Browse File System</property></emphasis> and <emphasis><property moreinfo="none">Browse WorkSpace</property></emphasis>.
+ </para>
+ <figure float="0">
+ <title>Browse dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page7.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Using the buttons you can locate the file you need. If you click <emphasis>
+ <property moreinfo="none">Browse File System</property></emphasis> button you specify the path of, or browse to, a file system directory.
+ </para>
+ <figure float="0">
+ <title>Browse file system</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page8.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ If you click <emphasis><property moreinfo="none">Browse WorkSpace</property></emphasis> button, you specify the path of, or browse to, a workspace relative working directory.
+ </para>
+ <figure float="0">
+ <title>Browse Workspace</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page9.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <!--<section id="configurationpage_datedecoder">
+ <title>Date Decoder Detail Page</title>
+
+ <para>Date Decoder is a resourceConfig element in the Smooks configuration file. It
+ describes how to transform the "Date" type.</para>
+ <para> Click the <emphasis>
+ <property>New</property>
+ </emphasis> button to open the <property>New Resource Type wizard</property>
+ dialog.</para>
+ <figure>
+ <title>Resource Type Selection Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page4.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>There are several resource type on the list. Select the <emphasis>
+ <property>Date Decoder</property>
+ </emphasis> and click the <emphasis>
+ <property>Finish</property>
+ </emphasis> button, a new <emphasis>
+ <property>Date Decoder</property>
+ </emphasis> item was added and shown on the resource type list.</para>
+ <para> There are several parameters in the <emphasis>
+ <property>Date Decoder</property>
+ </emphasis> resourceConfig element:</para>
+
+ <para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Format</para>
+ </listitem>
+
+ <listitem>
+ <para>Locale-Language</para>
+
+ </listitem>
+
+ <listitem>
+ <para>Locale-Country</para>
+
+ </listitem>
+ </itemizedlist>
+ </para>
+
+ <para> You can modify the parameters of the <emphasis>
+ <property>Date Decoder</property></emphasis> item with the left detail page.</para>
+
+ <figure>
+ <title>Date Decoder Detail Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> When you defined a new <emphasis>
+ <property>Date Decoder</property></emphasis>, then you can use the <link
+ linkend="graphicalpage_propertiesview">JavaBean Properties</link> GUI to set
+ it to be the "Java type".</para>
+ <para>Now when we've learnt Smooks Configuration Editor Page, let's have a look at one more Smooks Editor Page - Smooks Source Editor Page and investigate its functionality</para>
+
+
+ <para> The XML fragment generated by Smooks tools for the "Date
+ Decoder": </para> <para> <programlisting> <![CDATA[<resource-config
+ selector="decoder:DateLong">
+ <resource>org.milyn.javabean.decoders.DateDecoder</resource> <param
+ name="locale-language">en</param> <param name="format">yyy-MM-dd
+ HH:mm:ss</param> <param name="locale-country">IE</param>
+ </resource-config>]]> </programlisting> </para>
+
+ </section>
+
+ <section id="configurationpage_documenttype"> <title>Document Type
+ Detail Page</title> <para> </para> </section> <section
+ id="configurationpage_unhandleresourceconfig"> <title>Unhandle
+ ResourceConfig</title> </section>
+ -->
+</chapter>
+
+
+<chapter id="smooksformeditor_sourcetab" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/smooks/docs/reference/en/modules/smooksformeditor_sourcepage.xml" xreflabel="Smooks Source Editor Page">
+ <?dbhtml filename="smooks_form_editor_sourcetab.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Smooks Source Editor Page</title>
+ <para>This section provides information about Smooks Source Editor Page.</para>
+ <section>
+ <title>XML Source Editor</title>
+ <para>You can use this editor to edit the Smooks Configuration file directly. </para>
+ <figure float="0">
+ <title>Graphical Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/source_editor/source_editor1.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section>
+ <title>Error underlining in Graphical Editor</title>
+ <para>If the <property moreinfo="none">Smooks tools</property> can't understand the configuration
+ file or the configuration file is illegal (XML structure isn't right for Smooks
+ Configuration file, etc.), the error is underlined.</para>
+ <figure float="0">
+ <title>Graphical Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/source_editor/source_editor2.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <!--note>
+ <title>Tip:</title>
+ <para> When the error message panel is displayed, other editors ( Graphical Editor,
+ Configuration Editor ) are disabled. </para>
+ <para> You can't edit the configuration file with other editors until file becomes
+ valid. </para>
+ </note-->
+
+
+
+ </section>
+
+ <section>
+ <title>Smooks Configuration File Validator</title>
+ <para>Smooks configuration file validator will validate your Smooks configuration file. Just right-click on the file and then click on the <property moreinfo="none">Validate</property> button. The validator can be enabled/disabled in <emphasis><property moreinfo="none">Window -> Preferences -> Validation</property></emphasis>:</para>
+
+ <figure float="0">
+ <title>Validation: Smooks Configuration File Validator</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/source_editor/smooks_conf_validator.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can set up your Smooks validator to include, exclude groups to validate and specify rules for validation. Just click on the <property moreinfo="none">Settings</property> button and use the options provided:</para>
+
+ <figure float="0">
+ <title>Smooks Configuration File Validator Settings</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/source_editor/smooks_conf_validator_settings.png" scale="90"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ <para>We hope, our guide will help you to get started with JBoss Smooks Tools. Besides, for additional information you are welcome on <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para>
+
+ </section>
+
+
+
+
+</chapter>
+
+</book>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/options_page.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/options_page.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/options_page.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,97 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="options_page">
+ <?dbhtml filename="options_page.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Options Tab</title>
+ <para>This chapter describes Options tab of the Smooks Configuration File editor, gives short recommendations how this tab can be used during the project configuring.</para>
+ <figure>
+ <title> Options tab of the Smooks Configuration File editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_10.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <section>
+ <title>Smooks Configuration section</title>
+ <para>
+ In the <property>Smooks Configuration</property> section of <property>Options Tab</property>
+ only one element is availible:Smooks Platform Version
+ </para>
+ <figure>
+ <title>Smooks Configuration section of Options tab</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_9.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>This parameter is not rechangable,
+ and is set according to the vesion of the Smooks libraries that are added to the project.
+ </para>
+ </section>
+ <section>
+ <title>Filter Settings Filter section</title>
+ <para>
+ In Filter Settings section you can set
+ the following global options responsible for Smooks filtering configuring:</para>
+ <figure>
+ <title>Filter Settings section of Options tab</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>This behavior can be turned off using this global configuration parameter and can be overriden on a per fragment basis by targetting a Visitor implementation at that fragment that takes ownership of the Result writer (in the case of SAX filtering), or simply modifies the DOM (in the case of DOM filtering). As an example of this, see the FreeMarkerTemplateProcessor.
+ </para>
+ <table>
+ <title>Options Tab. Filter Settings section.</title>
+ <tgroup cols="3">
+ <colspec colnum="1" align="left" colwidth="1*"/>
+ <colspec colnum="2" align="left" colwidth="3*"/>
+ <colspec colnum="3" align="left" colwidth="1*"/>
+
+ <thead>
+ <row>
+ <entry>Option</entry>
+ <entry>Description</entry>
+ <entry>Default</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Stream Filter Type</entry>
+ <entry>Determines the type of processing model that will be used.
+ Please refer to <ulink url="http://www.smooks.org/mediawiki/index.php?title=V1.2:Smooks_v1.2_User_Gui...">
+ Filtering Process Selection section</ulink>
+ of the official Smooks User Guide for more information about these models:
+ <itemizedlist>
+ <listitem><para><emphasis>SAX</emphasis></para></listitem>
+ <listitem><para><emphasis>DOM</emphasis></para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>DOM</entry>
+ </row>
+
+ <row>
+ <entry>Default Serialization is On</entry>
+ <entry>Defines whether default serialization should be switched on.
+ Default serialization being turned on leads to locating StreamResult/DOMResult
+ to the Result objects provided to the Smooks.filterSource method and to
+ serialization all the events to that Result.</entry>
+ <entry>true</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+</chapter>
+
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/options_page.xml
___________________________________________________________________
Name: svn:executable
+ *
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/process_page.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/process_page.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/process_page.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="process_page">
+ <?dbhtml filename="process_page.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Process Page</title>
+ <para>This chapter describes Process tab of the Smooks Configuration File editor, gives short recommendations how this tab can be used during the project configuring.</para>
+
+ <section>
+ <title>Input Task Configuring</title>
+ <para>
+ <property>Input task configuring</property> is an obligatory step for your smooks project creation.
+ You can do this on the Process page of the editor: look for the "Input Task" in the Process Map at the top of the page.
+ </para>
+ <figure>
+ <title>Input Task Configuring</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Select it and you will see all the properties to set for the Input reader of your Smooks configuration.
+ "Input type" corresponds to the type of data that you will be working with.
+ For example, to work with incoming CSV (Comma-separated Values) data, you would specify "CSV" in the drop-down list.
+ Each reader type has slightly different configuration details that must be set in the "Input configuration" area.
+ For instance, the CSV reader requires you to specify details such as the encoding, quote character, separator character, and the list of incoming fields.
+ The EDI reader requires the encoding and the path to the Mapping Model describing the incoming data.
+ In the "Input data" section, you specify some sample data that conforms to your reader configuration.
+ </para>
+
+ <para>
+ Once you've specified your reader configuration and sample data, you can see the input model rendered in a tree form in the "Input model" section.
+ On the picture below you can see the correct configuration of some XML input task.
+ </para>
+ <figure>
+ <title>Input Task Configuring</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process2.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+
+
+ <section>
+ <title>"Java Mapping" or "Apply Template"?</title>
+
+ <para>Though there are many options in Smooks as far as what you can do with input
+ data such as transformation, routing, and persistence, the first release
+ of the Smooks Configuration Editor focuses on just a couple of areas:
+ mapping to java and applying templates to create different output formats.
+ If you have a set of Java classes you want to use the incoming data for,
+ you can use the "Java Mapping" task to specify those classes and use drag and
+ drop to map between the input model generated by the reader and elements in the output model.
+ Or if you simply want to transform your output to one or more formats, you can use the "Apply Template"
+ task to map it to a CSV file, XML or XSD file (and other formats in the future).
+ </para>
+ </section>
+ <section id="mapping">
+ <title>Java Mapping</title>
+
+ <para>
+ If you decide to do Java Mapping, you need to make sure that your Input reader has been set up and you have some sample data specified.
+ Then you should select the "Input Task" in the Process tab and click the plus (+) sign to the right of the icon.
+ Select "Java Mapping" from the popup menu and it will appear to the right, connected to the "Input Task". Then select the "Java Mapping" task.
+ </para>
+ <figure>
+ <title>Java Mapping configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Another method of adding "Java Mapping" element to the canvas in the Processing Tasks section is to right click Input Task element and select in the popup menu </para>
+ <figure>
+ <title>Java Mapping configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ Right-click on the canvas in an empty space and select "Add ->Java Class".
+ </para>
+ <figure>
+ <title>Java Mapping configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ The "Java Bean Creation" wizard appears.
+ Specify a unique identifier for the new class, the class path, whether it's an array or not, and if it is a collection, also specify the collection class.
+ If the Java class is specified, you'll see a list of the properties in the box below.
+ Click Finish when you're done.
+ Now with the input and output models on the canvas, you can click and drag from the various input elements to corresponding output elements. Make sure to connect collection elements to corresponding collection elements.
+ Finally your mapping should look nearly like the one on the picture below.
+ </para>
+ <figure>
+ <title>Final Mapping schema</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section>
+ <title>"Apply Template" task</title>
+
+ <para>The "Apply Template" task works very similarly to the <link linkend="mapping">"Java Mapping" task</link>, where you map between an input model and an output model.
+ Select the "Input Task" or "Java Mapping" task you want to use as the input model in the Process Map pane and click the plus (+) sign to the right of the icon.
+ </para>
+ <figure>
+ <title>"Apply Template" task opening</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ Select "Apply Template" from the popup menu and it will appear to the right, connected to the task you created it from. Then select the "Apply Template" task.
+ Once you've defined your template model, you can click and drag from the various input elements to corresponding output elements in the template. Make sure to connect collection elements to corresponding collection elements
+ </para>
+ </section>
+</chapter>
+
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/quick_start.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/quick_start.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/quick_start.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,590 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="quickstart" xreflabel="Quick Start" role="updated">
+ <?dbhtml filename="quick_start.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ <keyword>java</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Quick Start</title>
+ <para> This "Quick Start" will show how to use the <property>Smooks tools</property> to create/edit the Smooks
+ configuration file for Java2Java data transformation.</para>
+ <para> This chapter gives you a brief understanding of the <property>Smooks tools</property>.</para>
+ <section>
+ <title>Download Smooks Java-to-Java Example</title>
+ <para> Visit <ulink
+ url="http://www.blogjava.net/Files/reloadcn/smooks_java_java.zip"
+ >smooks examples page</ulink> to download the "java-to-java" example project. </para>
+ <tip>
+ <title>Tip:</title>
+
+ <para> The example project is based on Maven, we suggest you to create a new eclipse
+ Java project, copy the example code and .jar files from the example project and paste
+ them into the eclipse Java project. </para>
+ </tip>
+ </section>
+ <section>
+ <title>Mapping rules</title>
+ <para>At the begining of working with Smooks tools,
+ we need to understand the Java-to-Java mapping rules of this example.
+ The transform input Java class is <emphasis><property>example.sourcemodel.Order</property></emphasis> , its structure looks like this :
+ </para>
+ <figure>
+ <title>Order class</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/sourcemodel_structured.jpg" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Let's describe the structure of <emphasis><property>example.sourcemodel.Order</property></emphasis> in short:</para>
+ <itemizedlist>
+ <listitem><para>Order class contains a <property>Header</property> class and a <property>List</property> class.</para></listitem>
+ <listitem><para>The <property>Header</property> class has <property>customerName</property>,<property>customerNumber</property>,<property>priority</property> as properties.</para></listitem>
+ <listitem><para>In Order class the objects of the OrderItem class are stored in the List.</para></listitem>
+ <listitem><para>OrderItem has <property>price</property>,<property>productId</property>,<property>quantity</property> as its properties.</para></listitem>
+ </itemizedlist>
+ <para>Let's look at the transform target Java class : <emphasis><property>LineOrder</property></emphasis>.</para>
+ <para>On the screen below you can see its structure:</para>
+ <figure>
+ <title>LineOrder class</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/targetmodel_structured.jpg" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem><para><property>LineOrder</property> class contains 3 properties:<property>customerId</property>,<property>customerName</property>,<property>priority</property> and an array of lineItems.</para></listitem>
+ <listitem><para>The <property>Header</property> class has <property>customerName</property>,<property>customerNumber</property>,<property>priority</property> as its properties.</para></listitem>
+ <listitem><para>OrderItem objects are stored in a List.</para></listitem>
+ </itemizedlist>
+ <para>Now it's the time to define the mapping rules to transform the input source java class to the target java class:</para>
+ <itemizedlist>
+ <listitem><para>Each instance of the Order class should be mapped with an instance of the LineOrder class.</para></listitem>
+ <listitem><para>The value of <property>customerName</property> of the Header class should be assigned to the <property>customerName</property> property of a LineOrder instance.</para></listitem>
+ <listitem><para>The value of <property>customerNumber</property> of the Header class should be assigned to the <property>customerId</property> property of a LineOrder instance.</para></listitem>
+ <listitem><para>The value of <property>priority</property> of the Header class should be assigned to the <property>priority</property> property of LineOrder instance.</para></listitem>
+ <listitem><para>For the <property>orderitems</property> List of the Order instance, it's necessary to map a new lineItems array instance of LineOrder ,
+ and each OrderItem instance in the orderItems List should be transformed to a LineItem instance,
+ those instances will be put into the lineItems array.</para></listitem>
+ <listitem><para>The value of <property>productId</property> of the OrderItem instance should be assigned to the 'productCode' of LineItem.</para></listitem>
+ <listitem><para>The value of <property>price</property> of OrderItem should be assigned to the <property>unitPrice</property> of LineItem.</para></listitem>
+
+ </itemizedlist>
+ </section>
+
+ <section id="config_file_wizzard">
+ <title>Smooks Configuration File Wizard</title>
+ <para>Select the Smooks Java-to-Java example project that you created and right-click,
+ select the menu <emphasis><property>New > Other</property>,</emphasis> then find
+ <emphasis><property>Smooks > Smooks Configuration File</property>.</emphasis>
+ Click the <emphasis>
+ <property>Next</property>
+ </emphasis> button. </para>
+ <figure>
+ <title>Selecting Smooks Configuration File Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The first wizard page is a file path creation page. Select the <emphasis>
+ <property>src</property>
+ </emphasis> folder to be the files container, and input the name
+ <emphasis><property>smooks-config.xml</property>.</emphasis> Click
+ <emphasis><property>Next</property>.</emphasis></para>
+ <figure>
+ <title>Choosing the configuration file container and the file name</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start2.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The second wizard page is allows you to select Smooks configuration file version. Select the appropriate one and click <emphasis><property>Finish</property></emphasis> to complete the wizard.</para>
+
+
+
+ <!--<para> As the quick start introduces how to create/edit the Java-to-Java Smooks
+ configuration file, let's select the<emphasis>
+ <property>Java-to-Java</property>
+ </emphasis> type as the source/target transform data type. </para>
+
+ <figure>
+ <title>Selecting Data Type</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start3.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>On the next page you are prompted to choose the source data for transformation.
+ Let's select the <property>Order</property> class from the example project as
+ the source JavaBean class.</para>
+
+ <figure>
+ <title>Selecting the Source Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start4.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Then the wizard page asks you to choose the target data for transformation. We select
+ the <property>ListOrder</property> class as the target JavaBean class.</para>
+ <figure>
+ <title>Selecting the Target Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start5.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para/>
+
+ <tip>
+ <title>Tip:</title>
+ <para>You can omit two these steps and just press
+ <emphasis><property>Finish</property>.</emphasis> This will open the empty
+ Smooks Configuration file. It's possible to <link
+ linkend="graphicaleditor_datalink">select source/target data</link> afterwards
+ in the Smooks Graph editor.</para>
+ </tip>-->
+ </section>
+ <section id="quickstart_formeditor">
+ <title>Smooks Editor</title>
+
+ <para>When all the wizard steps are passed, a new Smooks Configuration file is created and
+ the <property>Smooks Configuration Editor</property> will be opened automatically:</para>
+ <figure>
+ <title>Smooks Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start6.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>On the bottom of this editor there are 5 tabs, they are :
+
+ Overview, Reader, Message Filter, Graph, Source.</para>
+ <section id="graphicaleditor_datalink">
+ <title>Adding the input data</title>
+ <para>At first, we need to add the Order class as the input data.
+ To do this, click the Reader tab, swich to the Reader/Input editor page</para>
+
+ <!--<para> This editor contains several parts: <table>
+ <title>The Smooks Editor Parts</title>
+ <tgroup cols="2">
+
+ <colspec colnum="1" align="left" colwidth="1*"/>
+ <colspec colnum="2" colwidth="5*"/>
+
+ <thead>
+ <row>
+ <entry>Editor feature</entry>
+ <entry>Functionality</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>
+ <para>Problems area</para>
+ </entry>
+ <entry>
+ <para>If there are any errors when you are editing the file, the
+ Problems area displays them</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Source data tree</para>
+ </entry>
+ <entry>
+ <para>The tree displays a structure of the transformed source
+ data</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Target data tree</para>
+ </entry>
+ <entry>
+ <para>The tree displays a structure of the transformed target
+ data</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Mapping graphical area</para>
+ </entry>
+ <entry>
+ <para>Show the data mapping connection lines</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Source/Target data selection links</para>
+ </entry>
+ <entry>
+ <para>Click the link, and <link linkend="graphicaleditor_datalink"
+ >Data Selection wizard</link> is opened helping you to
+ choose the source/target data</para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>-->
+
+
+ <para>To choose the transform data you should open <emphasis>
+ <property>Reader</property></emphasis> tab and click <emphasis>
+ <property>Add</property></emphasis> button in the Input Data section.</para>
+ <figure>
+ <title>Input Data section</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start_6a.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>After clicking the button the <property>Data Type Selection wizard</property> is
+ opened, and there are many data types in the list: Java, XML etc.</para>
+ <note>
+ <title>Note</title>
+ <para> There will become more and more data types on the list as the development goes on.
+ </para>
+ </note>
+
+ <figure>
+ <title>Data Type Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start7.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Select the <emphasis>
+ <property>Java</property>
+ </emphasis> data type and click <emphasis><property>Next</property>,</emphasis> you will
+ see the JavaBean class selection page:</para>
+
+ <figure>
+ <title>JavaBean Data Selection</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start8.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> Let's select the Order class from the example project as the source JavaBean class.After that click <emphasis>
+ <property>Finish</property>
+ </emphasis> and you should see the just added java class, being displayed in the Input Data Section.
+ </para>
+ <figure>
+ <title>Displaying the Structure of the Transformed Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start9.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section>
+ <title>Adding the target Bean</title>
+ <para>After adding the input data, let's switch to the Message Filter page:</para>
+ <figure>
+ <title>Displaying the Structure of the Transformed Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start9a.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click the <property>Add</property> button, the <property>Add Child</property> wizard page will be shown, let's select the <property>Java Binding v1.2 -> Bean v1.2</property> and click <emphasis><property>OK</property></emphasis> to add the Bean :
+ </para>
+ <figure>
+ <title>Add Child wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start9b.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Then we can find on the Message Filter page the <property>Bean v1.2</property> item added, click on it ,a Bean v1.2 section should appear to the right of the page.
+ The section represents a GUI for editing <property>Bean v1.2</property> properties:</para>
+ <figure>
+ <title>Bean v1.2 section</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start9c.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>You should input <property>
+ lineOrder</property> as the Bean's id in the "Bean Id" field.Then you should click <property>Browse</property> button
+ near the <property>Class</property> textfield and select LineOrder as the Bean's class.</para>
+ <note>
+ <para>
+ When you enter a value for the <property>Class</property> text field,
+ you can type 'Alt + /' and the content assist pop dialog will be shown,
+ so it's will increase the efficiency. If 'Alt + /' doesn't work,
+ try to use the 'Ctrl + space'('Key Assist' of Eclipse).
+ </para>
+ </note>
+ <para>Let's click the <property>Add Binding</property> link at the bottom of this page,
+ it will show a dialog to ask the binding of what Bean properties you will prefer to add.
+ Select all and click OK, you will see a list of Binding elements added under the Bean item.</para>
+ <para>Then you should add an array of beans called <property>lineItems</property> and a Bean LineItem.These two classes and Id values are:</para>
+ <para>Array Bean:</para>
+ <itemizedlist>
+ <listitem><para>BeanId : lineItems;</para></listitem>
+ <listitem><para>Class : example.trgmodel.LineItem[]</para></listitem>
+ </itemizedlist>
+ <para>LineItem Bean :</para>
+ <itemizedlist>
+ <listitem><para>BeanId : lineItem;</para></listitem>
+ <listitem><para>Class : example.trgmodel.LineItem</para></listitem>
+ </itemizedlist>
+ <note>
+ <para>
+ In Smooks , to be an array of Beans , the class value should end with '[]'. This means that this bean is an array type.
+
+ </para>
+ </note>
+ <para>To finish this work, use the <property>Add Binding</property> link to add all the bindings for the Bean.</para>
+ </section>
+
+
+ </section>
+ <section id="quickstart_mapping">
+ <title>Mapping</title>
+
+
+ <para>How to map the java class just added?</para>
+
+ <para>First, you should know what to transform:</para>
+
+ <orderedlist numeration="loweralpha" inheritnum="inherit">
+ <listitem>
+ <para>Bind the <emphasis>
+ <property>"customerName"</property>
+ </emphasis> property of the <property>Order#header</property> to the <emphasis>
+ <property>"customerName"</property>
+ </emphasis> property of <property>LineOrder</property>.</para>
+ </listitem>
+ <listitem>
+ <para>Bind the <emphasis>
+ <property>"customerNumber"</property>
+ </emphasis> property of the <property>Order#header</property> to the <emphasis>
+ <property>"customerId"</property>
+ </emphasis> property of <property>LineOrder</property>.</para>
+ </listitem>
+ <listitem>
+ <para>Bind the <emphasis>
+ <property>"price"</property>
+ </emphasis> property of the <property>OrderItem</property> to the <emphasis>
+ <property>"unitPrice"</property>
+ </emphasis> property of <property>LineItem</property>.</para>
+ </listitem>
+ <listitem>
+ <para>Bind the <emphasis>
+ <property>"productId"</property>
+ </emphasis> property of the <property>OrderItem</property> to the <emphasis>
+ <property>"productCode"</property>
+ </emphasis> property of <property>LineItem</property>.</para>
+ </listitem>
+ <listitem>
+ <para>Bind the <emphasis>
+ <property>"quantity"</property>
+ </emphasis> property of the <property>OrderItem</property> to the <emphasis>
+ <property>"unitQuantity"</property>
+ </emphasis> property of <property>LineItem</property>.</para>
+ </listitem>
+ </orderedlist>
+
+ <para> Make sense?
+ You should open Design tab and click Add button. In opened Add Child Wizard,please, select <emphasis>
+ <property>Add Smooks Resource>Java Binding>Bindings</property></emphasis>.
+ </para>
+ <para>First of all, you should bind <emphasis>
+ <property>Order</property></emphasis> to <emphasis>
+ <property>LineOrder</property></emphasis>. To do this one <emphasis>
+ <property>Bindings</property></emphasis> Item should be added to the Resource List.</para>
+ <figure>
+ <title>Mapping</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start10.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure><para>Click on it and you should see <emphasis>
+ <property>Bindings</property></emphasis> Section to the right of <emphasis>
+ <property>Message Filtering Resources</property></emphasis>.Write <emphasis> <property>lineOrder</property></emphasis> in the <emphasis>
+ <property>Bean id</property></emphasis> field.</para>
+ <para>Select <emphasis>
+ <property>example.trgmodel.LineOrder</property></emphasis> in the <emphasis>
+ <property>Class</property></emphasis> field and <emphasis>
+ <property>example.srcmodel.Order</property></emphasis> in the <emphasis>
+ <property>Name</property></emphasis> field.Your <emphasis> <property>Smooks Configuration Editor</property></emphasis> should look like this: </para>
+ <figure>
+ <title>Mapping</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start11.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Now you should bind two values <emphasis> <property>"customerNumber"</property>
+ </emphasis> property of the <property>Order#header</property> to the <emphasis>
+ <property>"customerId"</property>
+ </emphasis> property of <property>LineOrder</property>.To do this right click your just created <emphasis>
+ <property>Bindings Item >Add Smooks Resource>Value</property></emphasis>
+ .</para>
+
+ <figure>
+ <title> Mapping Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start12.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure><note>
+ <title>Note:</title>
+ <para>Please, remember that the root nodes of the source data and target data *MUST* be
+ connected.</para>
+ <para>This rule is not only for Java-to-Java, but also is relevant for
+ XML-to-Java </para>
+ </note>
+ <para> Do the same operation with the
+ other properties in this and other classes.</para>
+ <para>It's also necessary to bind <emphasis>
+ <property>orderItems</property></emphasis> property of the <emphasis>
+ <property>Order</property></emphasis> to <emphasis>
+ <property>lineItems</property></emphasis> property of <emphasis>
+ <property>LineOrder</property></emphasis>.The difference from the previous steps is that the <emphasis>
+ <property>orderItems</property></emphasis> is presented by the list of <emphasis>
+ <property>Order</property></emphasis> and <emphasis>
+ <property>lineItems</property></emphasis> is the massive of <emphasis>
+ <property>LineItem</property></emphasis> .To do the binding,you should use <emphasis>
+ <property>Wiring Item</property></emphasis>.First you should create a new Binding item. This is a configuration that allows you to construct an object graph .Select <emphasis>
+ <property>example.trgmodel.LineItem[]</property></emphasis> in the Class field and orderItems in the Name field,in bean Id write lineItems.
+ Your Smooks Configuration Editor should look like this:
+ </para>
+ <figure>
+ <title> Creating Wiring Item</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start13a.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> Then you should right click <emphasis>
+ <property>lineOrder</property></emphasis> binding item<emphasis>
+ <property>>Add Smooks Resource>Wiring</property></emphasis>.Select <emphasis>
+ <property>lineItem</property></emphasis> in <emphasis>
+ <property>Bean id Ref</property></emphasis>.
+ </para>
+ <para>The final step is to add new Wiring item to lineOrder <property>Binding</property>.In the <property>Bean id Ref</property> select <emphasis>
+ <property>lineItems</property></emphasis> and in <emphasis>
+ <property>Property</property></emphasis> select <emphasis>
+ <property>lineItems</property></emphasis>.</para>
+<!--
+ <para>Next, you are going to bind the properties of the <property>OrderItem</property> to
+ the properties of the <property>LineItem</property>.</paa>
+ <para>Select the <emphasis>
+ <property>"price"</property>
+ </emphasis> and drag it onto the <emphasis>
+ <property>"unitPrice"</property>
+ </emphasis> of the other side tree viewer. The Problems area shows an
+ error:</para>
+ <figure>
+ <title>Connection Error 1</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start12.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>How to deal with the error?</para>
+ <para>Please click the <emphasis>
+ <property>Fix it</property></emphasis> link, a menu is popped-up with several
+ resolve methods on it.</para>
+ <figure>
+ <title>Fixing the Connection Error</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start13.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> Select the first resolve method: <emphasis>
+ 'Connect the "OrderItem" to the
+ "LineItem" '.</emphasis> As the result the <emphasis>
+ <property>"OrderItem"</property></emphasis> is connected with
+ the <emphasis>
+ <property>"LineItem"</property>.</emphasis></para>
+ <para>But the notify message area still shows some other errors:</para>
+ <figure>
+ <title>Connection Error 2</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start14.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>OK, let's deal with the fire error. Click the <emphasis>
+ <property>Fix it</property></emphasis> link and
+ select the first resolve method. The <emphasis>
+ <property>"orderItems"</property></emphasis> is connected with
+ the <emphasis>
+ <property>"lineItems"</property>.</emphasis></para>
+
+ <tip>
+ <title>Tip:</title>
+ <para> Why does the error occur?</para>
+ <para> You will find that, if you only connect the property node without connecting the
+ parent node of the property, the "connection error" occurs.</para>
+ <para>The connection of the "price-to-unitPrice" is the
+ "Binding Connection", but it needs an "Instance Creation
+ Connection" - the connection of the
+ "OrderItem-to-LineItem".</para>
+ </tip>
+ <para> After that, connect <emphasis>
+ <property>"quantity"</property></emphasis> to the <emphasis>
+ <property>"unitQuantity"</property></emphasis> and <emphasis>
+ <property>"productId"</property></emphasis> to the
+ <emphasis>
+ <property>"productCode"</property>:</emphasis></para>
+ <figure>
+ <title>Complete Mapping</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start15.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>-->
+ <para>Now, you should save the file and the <property>Smooks tools</property> generate the correct
+ configuration file content.</para>
+ <para>OK, let run the test class: <property>example.Main</property>. (Please, make sure that the Smooks engine
+ loads the correct configuration file).</para>
+ <para>Success!</para>
+ </section>
+</chapter>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/references.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/references.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/references.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,524 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="reference">
+ <?dbhtml filename="reference.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Reference</title>
+ <para>This chapter includes detailed reference information about Smooks Tools.</para>
+ <section>
+ <title>Smooks Configuration Editor</title>
+ <para>This chapter describes the following tabs of the Smooks Configuration Editor:</para>
+
+ <itemizedlist>
+ <listitem><para><link linkend="process_tab">Process tab</link></para></listitem>
+ <listitem><para><link linkend="options_tab">Options tab</link></para></listitem>
+ <listitem><para><link linkend="smooksformeditor_sourcetab">Source tab</link></para></listitem>
+ </itemizedlist>
+ <section id="process_tab">
+ <title>Process tab</title>
+ <para>The Process tab of the Smooks Configuration Editor helps to configure different types of transformations.
+ By default smooks configuration file is opened in this editor.If you have another default settings for editor opening
+ you should left click smooks configuration file and select:<emphasis>Open With->Smooks Configuration Editor</emphasis>.</para>
+ <para>The Process tab has two sections:</para>
+ <itemizedlist>
+ <listitem><para><link linkend="processing_task_section">Processing Task section</link></para></listitem>
+ <listitem><para><link linkend="selected_task_details">Selected Task Details section</link></para></listitem>
+ </itemizedlist>
+ <para>You can see them on the picture below.</para>
+ <figure>
+ <title>Two Sections of the Process tab.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <section id="processing_task_section">
+ <title>Processing Task section</title>
+ <para>Using the popup menu in the Processing Task section you
+ can select which types of technologies(templating or mapping ones) you will use for transofmation: </para>
+ <para>The descriptions of the popup menu options are in the following table.</para>
+ <table>
+ <title>Process Tab. Processing Task section.</title>
+ <tgroup cols="3">
+ <colspec colnum="1" align="left" colwidth="1*"/>
+ <colspec colnum="2" align="left" colwidth="3*"/>
+ <colspec colnum="3" align="left" colwidth="1*"/>
+
+ <thead>
+ <row>
+ <entry>Option</entry>
+ <entry>Description</entry>
+ <entry>Default</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Add Task</entry>
+ <entry>Select one of the following tasks according to the necessary type of Source and Result types of the files:
+ <itemizedlist>
+ <listitem><para><emphasis>Input</emphasis> -this task is required and
+ appears automatically when Smooks config file is created.
+ You should just configure it properly.</para></listitem>
+ <listitem><para><emphasis>Java Mapping</emphasis></para></listitem>
+ <listitem><para><emphasis>Apply Template</emphasis></para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry></entry>
+ </row>
+
+ <row>
+ <entry>Delete</entry>
+ <entry>Click this option if you want to delete some task from the section.
+ Note:you can't delete input task because it's required.</entry>
+ <entry></entry>
+
+ </row>
+
+ <row>
+ <entry>Input Methods</entry>
+ <entry>Choose one of the following methods:
+ <itemizedlist>
+ <listitem><para>System</para></listitem>
+ <listitem><para>Simple</para></listitem>
+ <listitem><para>Amharic(EZ+)</para></listitem>
+ <listitem><para>Cedilla</para></listitem>
+ <listitem><para>Cyrillic</para></listitem>
+ <listitem><para>Inuktitut</para></listitem>
+ <listitem><para>IPA</para></listitem>
+ <listitem><para>Multipress</para></listitem>
+ <listitem><para>SCIM Bridge Input Method</para></listitem>
+ <listitem><para>SCIM Input Method</para></listitem>
+ <listitem><para>Thai-Lio</para></listitem>
+ <listitem><para>Tigrigna-Eritrean(EZ+)</para></listitem>
+ <listitem><para>Tigrigna-Ethiopian(EZ+)</para></listitem>
+ <listitem><para>Vietnamese</para></listitem>
+ <listitem><para>X input Method</para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>System</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section id="selected_task_details">
+ <title>Selected Task Details Section</title>
+ <para>The options of this section depends on the selected task in the Processing Task section.
+ Because there are 3 types of tasks there are 3 different sets of its options in the Selected Task Details Section.
+ They will be described one by one. </para>
+ <section>
+ <title>Selected Task Details Section for Input Task.</title>
+ <para>On the picture below you can find an example of Selected Task Details Section view
+ if XML is selected as input type.</para>
+
+ <figure>
+ <title>Selected Task Details Section for Input XML Task.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_2.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>As you can see on the picture above Input Configuration section is empty for XML input file.
+ But this section has special configuration options for CSV,EDI,JSON,Custom input files.</para>
+
+ <para>Here are the screens of these configuration options:</para>
+ <itemizedlist>
+ <listitem><para>CSV:</para>
+ <figure>
+ <title>Selected Task Details Section for Input CSV Task.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_3.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem><para>EDI:</para>
+ <figure>
+ <title>Selected Task Details Section for Input EDI Task.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem><para>JSON:</para>
+ <figure>
+ <title>Selected Task Details Section for Input JSON Task.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem><para>Custom:</para>
+ <figure>
+ <title>Selected Task Details Section for Input Custom Task.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>All the input task configuration positions can be found in the table below:</para>
+ <table>
+ <title>Selected Task Details Section. Options for Input Task.</title>
+ <tgroup cols="3">
+ <colspec colnum="1" align="left" colwidth="1*"/>
+ <colspec colnum="2" align="left" colwidth="3*"/>
+ <colspec colnum="3" align="left" colwidth="1*"/>
+ <thead>
+ <row>
+ <entry>Option</entry>
+ <entry>Description</entry>
+ <entry>Default</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Input type</entry>
+ <entry>Select your type of input file.
+ If don't find your type in the list,you should use Custom type:
+ <itemizedlist>
+ <listitem><para>No Input</para></listitem>
+ <listitem><para>XML</para></listitem>
+ <listitem><para>Java</para></listitem>
+ <listitem><para>XSD/WSDL</para></listitem>
+ <listitem><para>CSV</para></listitem>
+ <listitem><para>EDI</para></listitem>
+ <listitem><para>JSON</para></listitem>
+ <listitem><para>Custom</para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>XML</entry>
+ </row>
+
+ <row>
+ <entry>Input configuration
+
+ </entry>
+ <entry>
+ <itemizedlist>
+ <listitem><para><emphasis>No Input</emphasis> -no info required</para></listitem>
+ <listitem><para><emphasis>XML</emphasis> -no info required</para></listitem>
+ <listitem><para><emphasis>Java</emphasis> -no info required</para></listitem>
+ <listitem><para><emphasis>XSD/WSDL</emphasis> -no info required</para></listitem>
+ <listitem><para><emphasis>CSV</emphasis></para><itemizedlist>
+ <listitem><para><emphasis>Fields</emphasis> -Comma separated list of CSV record field names
+ </para></listitem>
+ <listitem><para><emphasis>Separator Character</emphasis> -Field separator character. Default of ','.
+ </para></listitem>
+ <listitem><para><emphasis>Quote Character</emphasis> -Quote character. Default of '"'.
+ </para></listitem>
+ <listitem><para><emphasis>Record Name</emphasis> -Name of csv record element.Default:csv-record</para></listitem>
+ <listitem><para><emphasis>Root Name</emphasis> -Name of csv root element.Default:csv-set</para></listitem>
+ <listitem><para><emphasis>indent</emphasis> -Add indentation character data to the generated event stream. This simply makes
+ the generated event stream easier to read in its serialized form. Useful for
+ testing etc.Default:true
+ </para></listitem>
+ <listitem><para><emphasis>Skip Lines</emphasis> -Number of lines to skip before processing starts. Default of 0.
+
+ </para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para><emphasis>EDI</emphasis></para>
+ <itemizedlist>
+ <listitem><para><emphasis>Target Profile</emphasis> -Defines the target profile
+ </para></listitem>
+ <listitem><para><emphasis>Encoding</emphasis> -The character encoding. Default "UTF-8"</para></listitem>
+ <listitem><para><emphasis>Mapping Model</emphasis> -Defines the EDI Mapping Model configuration for processing the
+ EDI message stream to a stream of SAX events that can be processed by Smooks.</para></listitem>
+ <listitem><para><emphasis>Validate</emphasis> -This attribute turns on/off datatype validation in the EDI Parser.
+ Validation is on by default.
+ It makes sense to turn datatype validation off on the EDI Reader
+ if the EDI data is being bound into a Java Object model.
+ </para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para><emphasis>JSON</emphasis></para>
+ <itemizedlist>
+ <listitem><para><emphasis>Target Profile</emphasis> -Defines the target profile</para></listitem>
+ <listitem><para><emphasis>Array Element Name</emphasis> -The element name of a array element. Default of 'element'.
+ </para></listitem>
+ <listitem><para><emphasis>Encoding</emphasis> -encoding: The default encoding of any JSON message
+ InputStream processed by this Reader. Default of 'UTF-8'.</para></listitem>
+ <listitem><para><emphasis>Illegal Element Name Char Replacement</emphasis> -If illegal characters are encountered in a JSON element name then they are replaced with this value.
+ By default this is not defined, so that the reader doesn't doesn't search for illegal characters.
+ </para></listitem>
+ <listitem><para><emphasis>Indent</emphasis> -Add indentation character data to the generated event stream. This simply makes
+ the generated event stream easier to read in its serialized form. Useful for
+ testing etc.Default:false.
+ </para></listitem>
+ <listitem><para><emphasis>Key Prefix on Numeric</emphasis> -The prefix character to add if the JSON node name starts with a number.
+ By default this is not defined, so that the reader doesn't search for element names that start with a number.
+ </para></listitem>
+ <listitem><para><emphasis>Key Whitespace Replacement</emphasis> -The replacement character for whitespaces in a JSON map key.
+ By default this not defined, so that the reader doesn't search for whitespaces.
+ </para></listitem>
+ <listitem><para><emphasis>Null Value Replacement</emphasis> -The replacement string for JSON NULL values. Default is ""(an empty string). </para></listitem>
+ <listitem><para><emphasis>Root Name</emphasis> -The element name of the document root. Default of 'json'.
+ </para></listitem>
+ <listitem><para><emphasis>Key Maps</emphasis> -Defines a JSON element name mapping
+ The "from" key will be replaced with the "to" key or the contents of the element.
+ </para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para><emphasis>Custom</emphasis></para>
+ <itemizedlist>
+ <listitem><para><emphasis>Target Profile</emphasis> -</para></listitem>
+ <listitem><para><emphasis>Class</emphasis> -Custom reader class.</para></listitem>
+ <listitem><para><emphasis>Handlers</emphasis> -Set a handler on the reader instance e.g. an EntityResolver, ErrorHandler etc.
+ </para></listitem>
+ <listitem><para><emphasis>Features</emphasis> -Reader Features List</para></listitem>
+ <listitem><para><emphasis>Parametres</emphasis> -Resource Parameters</para></listitem>
+
+ </itemizedlist>
+ </listitem>
+ </itemizedlist></entry>
+ <entry><itemizedlist>
+ <listitem><para><emphasis>CSV</emphasis></para><itemizedlist>
+ <listitem><para>not defined</para></listitem>
+ <listitem><para>','</para></listitem>
+ <listitem><para>'"'</para></listitem>
+ <listitem><para>csv-record</para></listitem>
+ <listitem><para>csv-set</para></listitem>
+ <listitem><para>true</para></listitem>
+ <listitem><para>0</para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para><emphasis>EDI</emphasis></para>
+ <itemizedlist>
+ <listitem><para>not defined</para></listitem>
+ <listitem><para>UTF-8</para></listitem>
+ <listitem><para>not defined</para></listitem>
+ <listitem><para>true</para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para><emphasis>JSON</emphasis></para>
+ <itemizedlist>
+ <listitem><para>not defined</para></listitem>
+ <listitem><para>element</para></listitem>
+ <listitem><para>UTF-8</para></listitem>
+ <listitem><para>not defined</para></listitem>
+ <listitem><para>false</para></listitem>
+ <listitem><para>not defined</para></listitem>
+ <listitem><para>not defined</para></listitem>
+ <listitem><para>""(an empty string)</para></listitem>
+ <listitem><para>'json'</para></listitem>
+ <listitem><para>not defined</para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para><emphasis>Custom</emphasis></para>
+ <itemizedlist>
+ <listitem><para>no defaults</para></listitem>
+
+ </itemizedlist>
+ </listitem>
+ </itemizedlist></entry>
+ </row>
+ <row>
+ <entry>Input Data</entry>
+ <entry>You should select a data file using <emphasis>Add</emphasis> and <emphasis>Delete</emphasis> buttons</entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>Input Model View</entry>
+ <entry>Using this view you can see the structure of your input file.If the file has been changed, to see the changes
+ click <emphasis>Refresh</emphasis>link.</entry>
+ <entry></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section id="mapping_task"><title>Selected Task Details section for Java Mapping Task.</title>
+ <para>Selected Task Details section for this task is presented by the graf,
+ that lighten the process of java mapping. </para>
+ <figure>
+ <title>Selected Task Details Section for Mapping Task.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_7.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> This graphical editor allow you to perform drug/drop operations with the nodes of transform data to map the source data to target data.
+ When you save the changes in the graphical editor the correct Smooks configuration file content will be generated. </para>
+
+ </section>
+ <section><title>Selected Task Details section for Template Task.</title>
+ <para>Selected Task Details section for this task is presented by the graf,
+ that is similar to the one in the <link linkend="mapping_task">previous section</link>.
+ </para>
+ <figure>
+ <title>Selected Task Details Section for Template Task.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_7a.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ </section>
+
+ </section>
+ <section id="options_tab">
+ <title>Options Tab</title>
+ <para>This section describes Options tab of the Smooks Configuration File editor, gives short recommendations how this tab can be used during the project configuring.</para>
+ <figure>
+ <title> Options tab of the Smooks Configuration File editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_8.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <section>
+ <title>Smooks Configuration section</title>
+ <para>
+ In the <property>Smooks Configuration</property> section of <property>Options Tab</property>
+ only one element is availible:Smooks Platform Version
+ </para>
+ <figure>
+ <title>Smooks Configuration section of Options tab</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_9.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>This parameter is not rechangable,
+ and is set according to the vesion of the Smooks libraries that are added to the project.
+ </para>
+ </section>
+
+ <section>
+ <title>Filter Settings Filter section</title>
+ <para>
+ In Filter Settings section you can set
+ the following global options responsible for Smooks filtering configuring:</para>
+ <figure>
+ <title>Filter Settings section of Options tab</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_10.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>This behavior can be turned off using this global configuration parameter and can be overriden on a per fragment basis by targetting a Visitor implementation at that fragment that takes ownership of the Result writer (in the case of SAX filtering), or simply modifies the DOM (in the case of DOM filtering). As an example of this, see the FreeMarkerTemplateProcessor.
+ </para>
+ <table>
+ <title>Options Tab. Filter Settings section.</title>
+ <tgroup cols="3">
+ <colspec colnum="1" align="left" colwidth="1*"/>
+ <colspec colnum="2" align="left" colwidth="3*"/>
+ <colspec colnum="3" align="left" colwidth="1*"/>
+
+ <thead>
+ <row>
+ <entry>Option</entry>
+ <entry>Description</entry>
+ <entry>Default</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Stream Filter Type</entry>
+ <entry>Determines the type of processing model that will be used.
+ Please refer to <ulink url="http://www.smooks.org/mediawiki/index.php?title=V1.2:Smooks_v1.2_User_Gui...">
+ Filtering Process Selection section</ulink>
+ of the official Smooks User Guide for more information about these models:
+ <itemizedlist>
+ <listitem><para><emphasis>SAX</emphasis></para></listitem>
+ <listitem><para><emphasis>DOM</emphasis></para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>DOM</entry>
+ </row>
+
+ <row>
+ <entry>Default Serialization is On</entry>
+ <entry>Defines whether default serialization should be switched on.
+ Default serialization being turned on leads to locating StreamResult/DOMResult
+ to the Result objects provided to the Smooks.filterSource method and to
+ serialization all the events to that Result.</entry>
+ <entry>true</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ </section>
+ <section id="smooksformeditor_sourcetab" xreflabel="Smooks Source Tab">
+
+ <title>Source Tab</title>
+ <para>This section provides information about Smooks Source Editor Page.</para>
+ <section>
+ <title>XML Source Editor</title>
+ <para>You can use this editor to edit the Smooks Configuration file directly. </para>
+ <figure>
+ <title>Graphical Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/source_editor/source_editor1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section>
+ <title>Error underlining in Graphical Editor</title>
+ <para>If the <property>Smooks tools</property> can't understand the configuration
+ file or the configuration file is illegal (XML structure isn't right for Smooks
+ Configuration file, etc.), the error is underlined.</para>
+ <figure>
+ <title>Graphical Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/reference_11.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+
+ <section>
+ <title>Smooks Configuration File Validator</title>
+ <para>Smooks configuration file validator will validate your Smooks configuration file. Just right-click on the file and then click on the <property>Validate</property> button. The validator can be enabled/disabled in <emphasis><property>Window -> Preferences -> Validation</property></emphasis>:</para>
+
+ <figure>
+ <title>Validation: Smooks Configuration File Validator</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/source_editor/smooks_conf_validator.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can set up your Smooks validator to include, exclude groups to validate and specify rules for validation. Just click on the <property>Settings</property> button and use the options provided:</para>
+
+ <figure>
+ <title>Smooks Configuration File Validator Settings</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/source_editor/smooks_conf_validator_settings.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ </section>
+ </section>
+ </section>
+</chapter>
Property changes on: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/references.xml
___________________________________________________________________
Name: svn:executable
+ *
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_configurationpage.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_configurationpage.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_configurationpage.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,270 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="smooksformeditor_configurationtab" xreflabel="Smooks Configuration Editor Page">
+ <?dbhtml filename="smooks_form_editor_configurationtab.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Smooks Design Page</title>
+ <para>In this section you will explore the details of Smooks Design Page usage.</para>
+ <para><property>Smooks Design Page</property> is one tab of the <property>Smooks Editor</property>. </para>
+ <figure>
+ <title>Design Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>This page consists of 3 sections: Message Filtering Resources, Input Data and the section devoted to the configurations of a selected in a Message Filtering Resources section Item.</para>
+ <para> You can bind classes <link linkend="quickstart_mapping">using Bindings item
+ </link> on the Design page of the <property>Smooks Editor</property>. </para>
+ <para><emphasis>
+ <property>Resource list</property></emphasis> item in <emphasis>
+ <property>Message Filtering Resources</property></emphasis> corresponds to the root element of the <emphasis>
+ <property>smooks-config.xml</property></emphasis> file.You can configurate the next four properties using corresponding fields:</para>
+ <itemizedlist>
+ <listitem><para><emphasis>
+ <property>default-selector</property></emphasis>:Defines the selector that will be applied to all resource-config elements in the <emphasis>
+ <property>smooks-config.xml</property></emphasis>, where a selector is not defined. </para></listitem>
+ <listitem><para><emphasis>
+ <property>default-selector-namespace</property></emphasis>:Defines the default selector namespace. </para></listitem>
+ <listitem><para><emphasis>
+ <property>default-target-profile</property></emphasis>: Defines the default target profile that will be applied to all resources in the smooks-config.xml. </para></listitem>
+ <listitem><para><emphasis>
+ <property>default-condition-ref</property></emphasis>:The condition is applied to resources where an empty "condition" element (i.e. <code><condition/></code>)is defined.The condition element does not reference a globally defined condition. </para></listitem>
+ </itemizedlist>
+ <para> The configuration editor also edits the <link linkend="configurationpage_parsetype">Smooks parse
+ type</link> and manages the <link linkend="configurationpage_importfile">Import
+ Files</link>.</para>
+ <section id="selector-dialog">
+ <title>Selector generate dialog</title>
+ <para>Using <emphasis>
+ <property>Selector generate dialog</property></emphasis> you can allow the user to select a node for generation <property>"selector"</property> for smooks-config file.
+ To open the dialog you should left click <property>Browse</property> button in <emphasis>
+ <property>Default Selector</property></emphasis> section.
+ </para>
+ <figure>
+ <title>Selector generate dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page2a.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> When the dialog is opened you should click <property>"Click to add input data"</property>to set the selector.
+ In the opened <emphasis>
+ <property>Data Type Selection</property></emphasis> Wizard you should choose the type of the file and the file itself you want to load to the <emphasis>
+ <property>Selector generate dialog</property></emphasis>.After that your dialog should look nearly like that:</para>
+ <figure>
+ <title>Selector generate dialog after adding Input Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page2b.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The final step is to choose the node you want to make a selector for <emphasis>
+ <property>smooks-config.xml</property></emphasis>.</para>
+ </section>
+ <section id="configurationpage_parsetype">
+
+ <title>Smooks Parse Type</title>
+ <para>If your config file doesn't contain <emphasis>
+ <property>Global Parametres</property></emphasis> item yet, you should add it by right click <emphasis>
+ <property>Resource List>Add Smooks Resource>Global Parametres</property></emphasis>.After this step you should add <emphasis>
+ <property>Param</property></emphasis> to just created <emphasis>
+ <property>Global Parametres</property></emphasis>. </para>
+ <figure>
+ <title>Adding Param to created Global Parametres</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page2.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Then left click <emphasis>
+ <property>Param</property>
+ </emphasis>and in the Param section, you will see a set of text fields: <emphasis>
+ <property>Name</property></emphasis>,<emphasis>
+ <property>Type</property></emphasis> and <emphasis>
+ <property>Text</property></emphasis>.<emphasis>
+ <property>Name</property></emphasis> value is required. To set a parse type you should write SAX/DOM to the
+ <emphasis>
+ <property>Text</property></emphasis> field.</para>
+
+ <figure>
+ <title>Filling Param section field Name and Text Value for set a Parse Type</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page3.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>To apply changes to the <emphasis>
+ <property>smooks-config.xml</property></emphasis> click <emphasis>
+ <property>Save</property></emphasis> button (<emphasis>
+ <property>Ctrl+S</property></emphasis>). </para>
+ </section>
+ <section id="configurationpage_importfile">
+
+ <title>Import Smooks Configuration page</title>
+ <para> Right click <emphasis>
+ <property>Resource List>Add Smooks Resource>Import Smooks Configuration</property>
+ </emphasis>, then you should see a new <emphasis>
+ <property>Import Smooks Configuration</property>
+ </emphasis>item in the list (see the figure below).</para>
+
+ <figure>
+ <title>Import Data</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page3a.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Left click the added item and to the left of <emphasis>
+ <property>Message Filtering Resources Import Smooks Configuration </property></emphasis> section should appear. Click the <emphasis>
+ <property>Browse</property>
+ </emphasis> button and select the file you want to import(see <link linkend="file_selection">File selection</link> section). </para>
+ <para>Click <emphasis>
+ <property>Save</property></emphasis> and the <code><import></code> tag with the corresponding file path as a <emphasis>
+ <property>file</property></emphasis> property will be added to the <emphasis>
+ <property>smooks-config.xml</property></emphasis>.</para>
+ </section >
+ <section id="file_selection">
+ <title>File selection</title>
+ <para>Some attributes in Smooks elements should store path to a file as a value
+ (e.g. attribute <emphasis><property>"mappingModel"</property></emphasis> of the element <emphasis><property>"edi:reader"</property></emphasis>).
+ You can see a Browse button near the fields, that set such a value to the attribute
+ (e.g. <emphasis><property>"Mapping Model"</property></emphasis> field set a value to the <emphasis><property>"mappingModel"</property></emphasis> attribute).
+ </para>
+ <figure>
+ <title>EDI:Reader element</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page6.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ When you click <emphasis><property>Browse</property></emphasis>, the dialog prompts you click one of two buttons:
+ <emphasis><property>Browse File System</property></emphasis> and <emphasis><property>Browse WorkSpace</property></emphasis>.
+ </para>
+ <figure>
+ <title>Browse dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page7.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Using the buttons you can locate the file you need. If you click <emphasis>
+ <property>Browse File System</property></emphasis> button you specify the path of, or browse to, a file system directory.
+ </para>
+ <figure>
+ <title>Browse file system</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page8.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ If you click <emphasis><property>Browse WorkSpace</property></emphasis> button, you specify the path of, or browse to, a workspace relative working directory.
+ </para>
+ <figure>
+ <title>Browse Workspace</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page9.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <!--<section id="configurationpage_datedecoder">
+ <title>Date Decoder Detail Page</title>
+
+ <para>Date Decoder is a resourceConfig element in the Smooks configuration file. It
+ describes how to transform the "Date" type.</para>
+ <para> Click the <emphasis>
+ <property>New</property>
+ </emphasis> button to open the <property>New Resource Type wizard</property>
+ dialog.</para>
+ <figure>
+ <title>Resource Type Selection Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page4.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>There are several resource type on the list. Select the <emphasis>
+ <property>Date Decoder</property>
+ </emphasis> and click the <emphasis>
+ <property>Finish</property>
+ </emphasis> button, a new <emphasis>
+ <property>Date Decoder</property>
+ </emphasis> item was added and shown on the resource type list.</para>
+ <para> There are several parameters in the <emphasis>
+ <property>Date Decoder</property>
+ </emphasis> resourceConfig element:</para>
+
+ <para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Format</para>
+ </listitem>
+
+ <listitem>
+ <para>Locale-Language</para>
+
+ </listitem>
+
+ <listitem>
+ <para>Locale-Country</para>
+
+ </listitem>
+ </itemizedlist>
+ </para>
+
+ <para> You can modify the parameters of the <emphasis>
+ <property>Date Decoder</property></emphasis> item with the left detail page.</para>
+
+ <figure>
+ <title>Date Decoder Detail Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/config_page/config_page1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> When you defined a new <emphasis>
+ <property>Date Decoder</property></emphasis>, then you can use the <link
+ linkend="graphicalpage_propertiesview">JavaBean Properties</link> GUI to set
+ it to be the "Java type".</para>
+ <para>Now when we've learnt Smooks Configuration Editor Page, let's have a look at one more Smooks Editor Page - Smooks Source Editor Page and investigate its functionality</para>
+
+
+ <para> The XML fragment generated by Smooks tools for the "Date
+ Decoder": </para> <para> <programlisting> <![CDATA[<resource-config
+ selector="decoder:DateLong">
+ <resource>org.milyn.javabean.decoders.DateDecoder</resource> <param
+ name="locale-language">en</param> <param name="format">yyy-MM-dd
+ HH:mm:ss</param> <param name="locale-country">IE</param>
+ </resource-config>]]> </programlisting> </para>
+
+ </section>
+
+ <section id="configurationpage_documenttype"> <title>Document Type
+ Detail Page</title> <para> </para> </section> <section
+ id="configurationpage_unhandleresourceconfig"> <title>Unhandle
+ ResourceConfig</title> </section>
+ -->
+</chapter>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_graphicalpage.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_graphicalpage.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_graphicalpage.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,172 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="smooksformeditor_graphicaltab" xreflabel="Smooks Graphical Editor Page" role="updated">
+ <?dbhtml filename="smooks_form_editor_graphicaltab.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Smooks Graphical Editor Page</title>
+ <para>This chapter is packed with useful information about Smooks Graphical Editor Page usage</para>
+ <para>Smooks Graphical Editor page is one tab of the <property>Smooks Editor</property>.</para>
+ <figure>
+ <title>Graphical Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/graph_editor/graph_editor1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> This <property>Graphical editor</property> allows you to perform drug/drop operations
+ with the nodes of transform data to map the source data to target data. </para>
+ <para> When you save the changes in the <property>Graphical editor</property> the correct Smooks
+ Configuration file content is generated. </para>
+
+ <para>To adjust the properties of the connection lines in the editor, you should use the <link
+ linkend="graphicalpage_propertiesview">Properties view</link> (activate it by following
+ to <emphasis>
+ <property>Window > Show View > Other > General > Properties</property>).</emphasis></para>
+
+ <para>For example, if you defined a date decoder in the <link
+ linkend="configurationpage_datedecoder">Smooks Configuration Editor</link>, in the <property>Properties view</property> you can
+ select it as a Mapping type for the "Date" type element.</para>
+
+ <figure>
+ <title>Browsing Custom Type for the Date Type Element</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/graph_editor/graph_editor1a.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <section>
+
+ <title>Introducing the areas of graphical editor</title>
+ <para>Information on the topic could be found in the <link linkend="quickstart_formeditor"
+ >Quick Start/Smooks Editor</link> section.</para>
+ </section>
+ <section>
+
+ <title>Load Source/Target Data</title>
+ <para> Click the links under the data view, the <property>Data Type Selection
+ wizard</property> page will be shown.</para>
+ <figure>
+ <title>Data Type Selection Wizard Page</title>
+ <mediaobject>
+ <imageobject>
+
+ <imagedata fileref="images/graph_editor/graph_editor2.png" scale="90"/>
+
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> There are sets of transform data type on the wizard page, select one type and click
+ <emphasis><property>Next</property>,</emphasis> the data source selection wizard
+ page will be shown.</para>
+
+ <tip>
+ <title>Note:</title>
+ <para>For different data type, the Data source selection wizard are different too.
+ </para>
+ </tip>
+ <figure>
+ <title>Java Data Source Selection Wizard Page</title>
+ <mediaobject>
+ <imageobject>
+
+ <imagedata fileref="images/graph_editor/graph_editor3.png" scale="90"/>
+
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <figure>
+ <title>XML File Path Selection Wizard Page</title>
+ <mediaobject>
+ <imageobject>
+
+ <imagedata fileref="images/graph_editor/graph_editor4.png" scale="90"/>
+
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> When you finish the data selection (file path selection), click
+ <emphasis><property>Finish</property>,</emphasis> the data view displays the
+ selected data structure.</para>
+ </section>
+ <section>
+
+ <title>Using Graphical Editor for Mapping</title>
+ <para>To get information on the topic please, read the <link linkend="quickstart_mapping"
+ >Quick Start/Mapping</link> section. </para>
+ </section>
+ <section>
+
+ <title>Error Messages</title>
+ <para>When you do any mapping operations, the <property>Smooks tools</property> validate the
+ file content with "Mapping Logic". If there are any errors of the configuration file
+ content, error messages are shown in the <link linkend="quickstart_formeditor">Problems
+ area</link>.</para>
+ <para> Please, read the <link linkend="quickstart_mapping">Quick Start/Mapping</link>
+ section to find how to fix the errors.</para>
+ </section>
+ <section id="graphicalpage_propertiesview">
+ <title>Properties View</title>
+
+ <para> You can edit the properties of the connection lines with the <property>Properties
+ view</property>.</para>
+ <para>Navigate to <emphasis><property>Window > Show View > Other >
+ Properties</property>,</emphasis> to open the <property>Properties
+ view</property>.</para>
+ <para> When you select the connection line, the <property>Properties view</property> will
+ show a set of section GUI for editing its properties.</para>
+ <tip>
+
+ <title>Tip:</title>
+ <para>This GUI on the <property>Properties view</property> is displayed when the Smooks
+ Graphical editor is active, if not, the <property>Properties view</property>
+ displays empty GUI.</para>
+ <para>If the source data type of the selected connection line is
+ "XML", the <property>Properties view</property> shows an XML
+ Properties section GUI.</para>
+ <para>But if the source data type of the selected connection line is
+ "Java", the XML Properties section GUI isn't
+ displayed.</para>
+ <para>It means that if the source/target data type of the selected connection line is
+ different, the <property>Properties view</property> shows a different GUI.</para>
+ </tip>
+ <figure>
+ <title>JavaBean Properties Section</title>
+ <mediaobject>
+ <imageobject>
+
+ <imagedata fileref="images/graph_editor/graph_editor5.png" scale="90"/>
+
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <figure>
+ <title>XML Properties Section</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/graph_editor/graph_editor6.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <figure>
+ <title>Mapping Properties Section</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/graph_editor/graph_editor7.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>To discover about other Editor pages, read the next chapters</para>
+ </section>
+</chapter>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_sourcepage.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_sourcepage.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/smooksformeditor_sourcepage.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,83 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="smooksformeditor_sourcetab" xreflabel="Smooks Source Editor Page">
+ <?dbhtml filename="smooks_form_editor_sourcetab.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Smooks Source Editor Page</title>
+ <para>This section provides information about Smooks Source Editor Page.</para>
+ <section>
+ <title>XML Source Editor</title>
+ <para>You can use this editor to edit the Smooks Configuration file directly. </para>
+ <figure>
+ <title>Graphical Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/source_editor/source_editor1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section>
+ <title>Error underlining in Graphical Editor</title>
+ <para>If the <property>Smooks tools</property> can't understand the configuration
+ file or the configuration file is illegal (XML structure isn't right for Smooks
+ Configuration file, etc.), the error is underlined.</para>
+ <figure>
+ <title>Graphical Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/source_editor/source_editor2.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <!--note>
+ <title>Tip:</title>
+ <para> When the error message panel is displayed, other editors ( Graphical Editor,
+ Configuration Editor ) are disabled. </para>
+ <para> You can't edit the configuration file with other editors until file becomes
+ valid. </para>
+ </note-->
+
+
+
+ </section>
+
+ <section>
+ <title>Smooks Configuration File Validator</title>
+ <para>Smooks configuration file validator will validate your Smooks configuration file. Just right-click on the file and then click on the <property>Validate</property> button. The validator can be enabled/disabled in <emphasis><property>Window -> Preferences -> Validation</property></emphasis>:</para>
+
+ <figure>
+ <title>Validation: Smooks Configuration File Validator</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/source_editor/smooks_conf_validator.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can set up your Smooks validator to include, exclude groups to validate and specify rules for validation. Just click on the <property>Settings</property> button and use the options provided:</para>
+
+ <figure>
+ <title>Smooks Configuration File Validator Settings</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/source_editor/smooks_conf_validator_settings.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ <para>We hope, our guide will help you to get started with JBoss Smooks Tools. Besides, for additional information you are welcome on <ulink
+ url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para>
+
+ </section>
+
+
+
+
+</chapter>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/summary.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/summary.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/summary.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter>
+ <?dbhtml filename="summary.html"?>
+ <title>Summary</title>
+ <para>In conclusion, with this document you know all the capabilities of Smooks Tools and could easily start with them.
+ The chapters above walked you through the steps on how to create and configure some XML to JAVA mapping project.
+ If you have questions or suggestions concerned both the documentation and tools behavior,
+ you are welcome to JBoss Tools Users forum.
+ Please, use Jira to report bugs and requests on documentation.</para>
+
+ <section>
+ <title>Other relevant resources on the topic</title>
+ <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at
+ <ulink url="http://docs.jboss.org/tools">http://docs.jboss.org/tools</ulink> in the corresponding release directory.
+ </para>
+ <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs">http://download.jboss.org/jbosstools/nightly-docs</ulink>. </para>
+<para>For more information about Smooks technology please visit
+ <ulink url="http://www.smooks.org/mediawiki/index.php?title=Main_Page">
+ Smooks Technology Home Page</ulink></para>
+
+ </section>
+</chapter>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/en-US/tasks.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/en-US/tasks.xml (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/en-US/tasks.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,183 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="process_page">
+ <?dbhtml filename="tasks.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Smooks</keyword>
+ <keyword>JBDS</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Tasks</title>
+ <para>This chapter describes the main tasks a user can be faced during Smooks tools usage.</para>
+ <section id="config_file_wizzard">
+ <title>New Smooks Configuration File Creation</title>
+ <para>Select the project where you want to create new Smooks Configuration File and right-click on it,
+ select in the menu <emphasis><property>New > Other</property>,</emphasis> then find
+ <emphasis><property>Smooks > Smooks Configuration File</property>.</emphasis>
+ Click the <emphasis>
+ <property>Next</property>
+ </emphasis> button. </para>
+ <figure>
+ <title>Selecting Smooks Configuration File Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The first wizard page is a file path creation page. Select the <emphasis>
+ <property>src</property>
+ </emphasis> folder to be the files container, and input the name
+ <emphasis><property>smooks-config.xml</property>.</emphasis> Click
+ <emphasis><property>Next</property>.</emphasis></para>
+ <figure>
+ <title>Choosing the configuration file container and the file name</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/quick_start/quick_start2.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The second wizard page allow you to select Smooks configuration file version. Select the appropriate one and click <emphasis><property>Finish</property></emphasis> to complete the wizard.</para>
+ </section>
+ <section>
+ <title>Input Task Configuring</title>
+ <para>
+ <property>Input task configuring</property> is an obligatory step for your smooks project creation.
+ You can configure it on the Process page of the editor: look for the "Input Task" in the Process Map at the top of the page.
+ </para>
+ <figure>
+ <title>Input Task Configuring</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process1.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Select it and you will see all the properties to set for the Input reader of your Smooks configuration.
+ "Input type" corresponds to the type of data that you will be working with.
+ For example, to work with incoming CSV (Comma-separated Values) data, you would specify "CSV" in the drop-down list.
+ Each reader type has slightly different configuration details that must be set in the "Input configuration" area.
+ For instance, the CSV reader requires you to specify details such as the encoding, quote character, separator character, and the list of incoming fields.
+ The EDI reader requires the encoding and the path to the Mapping Model describing the incoming data.
+ In the <emphasis>Input data</emphasis> section, you specify some sample data that conforms to your reader configuration.
+ </para>
+
+ <para>
+ Once you've specified your reader configuration and sample data, you can see the input model rendered in a tree form in the <emphasis>Input model</emphasis> section.
+ On the picture below you can see the correct configuration of some XML input task.
+ </para>
+ <figure>
+ <title>Input Task Configuring</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process2.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section>
+ <title>"Java Mapping" or "Apply Template"?</title>
+
+ <para>Though there are many options in Smooks as far as what you can do with input
+ data such as transformation, routing, and persistence, this version
+ of the Smooks Configuration Editor focuses only on these areas:
+ mapping to java and applying templates to create different output formats.
+ If you have a set of Java classes you want to use the incoming data for,
+ you can use the "Java Mapping" task to specify those classes and use drag and
+ drop to map between the input model generated by the reader and elements in the output model.
+ Or if you simply want to transform your output to one or more formats, you can use the "Apply Template"
+ task to map it to a CSV file, XML or XSD file (and other formats in the future).
+ <note><title>Note</title>
+ <para>Now you can't transform your output directly,
+ using only Input and Template tasks.
+ You should use Mapping as an interagent between these tasks.</para>
+ </note>
+ </para>
+ </section>
+ <section id="mapping">
+ <title>Java Mapping Task</title>
+
+ <para>
+ If you decide to do Java Mapping, you need to make sure that your Input reader has been set up and you have some sample data specified.
+ Then you should select <emphasis>Input Task</emphasis> in the Process tab and click the plus (+) sign to the right of the icon.
+ Select <emphasis>Java Mapping</emphasis> from the popup menu and it will appear to the right, connected to <emphasis>Input Task</emphasis>. Then select <emphasis>Java Mapping</emphasis> task.
+ </para>
+ <figure>
+ <title>Java Mapping configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Another method of adding <emphasis>Java Mapping</emphasis> element
+ to the canvas in the Processing Tasks section is to right click Input Task
+ element and select <emphasis>Java Mapping</emphasis> in the popup menu </para>
+ <figure>
+ <title>Java Mapping configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ Right-click on the canvas in an empty space and select "Add ->Java Class".
+ </para>
+ <figure>
+ <title>Java Mapping configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ <emphasis>Java Bean Creation</emphasis> wizard appears.
+ Specify a unique identifier for the new class, the class path,
+ whether it's an array or not, and if it is a collection, also specify the collection class.
+ If the Java class is specified, you'll see a list of the properties in the box below.
+ Click <emphasis>Finish</emphasis> when you're done.
+ Now with the input and output models on the canvas, you can click and drag
+ from the various input elements to corresponding output elements.
+ Make sure to connect collection elements to corresponding collection elements.
+ Finally your mapping should look nearly like the one on the picture below.
+ </para>
+ <figure>
+ <title>Final Mapping schema</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section>
+ <title>Apply Template Task</title>
+
+ <para>The "Apply Template" task works very similarly to the <link linkend="mapping">"Java Mapping" task</link>, where you map between an input model and an output model.
+ Select the <emphasis>Java Mapping</emphasis> task you want to use as the input model in the Process Map pane and click the plus (+) sign to the right of the icon.
+ </para>
+ <figure>
+ <title>Apply Template configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/process_page/process7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ Select "Apply Template" from the popup menu and it will appear to the right, connected to the task you created it from. Then select the "Apply Template" task.
+ Once you've defined your template model, you can click and drag from the various input elements to corresponding output elements in the template. Make sure to connect collection elements to corresponding collection elements
+ </para>
+ </section>
+ <section>
+ <title>Smooks Configuration testing using Smooks Run Configuration</title>
+
+ <para>This option is intended to view the results of Smooks transforming procedure.
+ For more detailed information about this option please go <ulink url="http://community.jboss.org/wiki/UsingtheSmooksRunConfigurationtotestSmook...">here</ulink>.</para>
+ </section>
+</chapter>
+
Modified: branches/jbosstools-3.1.x/smooks/docs/reference/pom.xml
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/pom.xml 2010-03-12 00:58:21 UTC (rev 20784)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/pom.xml 2010-03-12 01:02:00 UTC (rev 20785)
@@ -95,9 +95,9 @@
<configuration>
<sourceDocumentName>${master}</sourceDocumentName>
- <sourceDirectory>${pom.basedir}/en</sourceDirectory>
+ <sourceDirectory>${pom.basedir}/en-US</sourceDirectory>
<imageResource>
- <directory>${pom.basedir}/en</directory>
+ <directory>${pom.basedir}/en-US</directory>
<includes>
<include>images/**/*</include>
</includes>
Added: branches/jbosstools-3.1.x/smooks/docs/reference/publican.cfg
===================================================================
--- branches/jbosstools-3.1.x/smooks/docs/reference/publican.cfg (rev 0)
+++ branches/jbosstools-3.1.x/smooks/docs/reference/publican.cfg 2010-03-12 01:02:00 UTC (rev 20785)
@@ -0,0 +1,7 @@
+# Config::Simple 4.59
+# Fri Nov 20 13:19:45 2009
+
+xml_lang: en-US
+type: Book
+brand: JBoss
+
14 years, 3 months
- 1
- 0
JBoss Tools SVN: r20783 - in branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial: en-US and 2 other directories.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-11 19:39:49 -0500 (Thu, 11 Mar 2010)
New Revision: 20783
Added:
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Author_Group.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Book_Info.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/JSF_Tools_Tutorial.ent
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/JSF_Tools_Tutorial.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Preface.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Revision_History.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/adding_managed_bean.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/adding_navigation.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/favicon.ico
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jbosstools_logo.png
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_1.png
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_10.png
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_2.png
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_3.png
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_4.png
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_5.png
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_6.png
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_7.png
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_8.png
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_9.png
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/introduction.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/jsf_application.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/jsp_view_files.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/master.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/master_output.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/relevant_resources.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/running_application.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/start_page.xml
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/publican.cfg
Removed:
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en/
Modified:
branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/pom.xml
Log:
builds with publican
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Author_Group.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Author_Group.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Author_Group.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,6 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<authorgroup><author><firstname>Anatoly</firstname><surname>Fedosik</surname></author>
+ <author><firstname>Olga</firstname><surname>Chikvina</surname></author>
+ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author></authorgroup>
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Book_Info.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Book_Info.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Book_Info.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<bookinfo><title>JSF Tools Tutorial</title><subtitle>Provides information relating to the JSF Tools module.</subtitle><productname>JBoss Developer Studio</productname><productnumber>3.0</productnumber><edition>1.0</edition><pubsnumber>0</pubsnumber><abstract><para>The JSF Tools Tutorial explains how to use the JSF Tools module to create a simple JSF application.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/JSF_Tools_Tutorial.ent
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/JSF_Tools_Tutorial.ent (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/JSF_Tools_Tutorial.ent 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "JBoss">
+<!ENTITY BOOKID "JSF_Tools_Tutorial">
+<!ENTITY YEAR "2010">
+<!ENTITY HOLDER "Red Hat">
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/JSF_Tools_Tutorial.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/JSF_Tools_Tutorial.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/JSF_Tools_Tutorial.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,16 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<book>
+<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="jsf_application.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="adding_navigation.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="adding_managed_bean.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="jsp_view_files.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="start_page.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="running_application.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="relevant_resources.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+</book>
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Preface.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Preface.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Preface.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<preface><title>Preface</title><xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></xi:fallback></xi:include></preface>
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Revision_History.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Revision_History.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/Revision_History.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<appendix><title>Revision History</title><simpara><revhistory><revision><revnumber>0</revnumber><date>Fri Nov 20 2009</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix>
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/adding_managed_bean.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/adding_managed_bean.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/adding_managed_bean.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="adding_managed_bean" xreflabel="adding_managed_bean">
+ <?dbhtml filename="adding_managed_bean.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Adding a Managed Bean to the Application</title>
+ <para>To store data in the application, we will use a managed bean.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>Tree</property>
+ </emphasis> tab at the bottom of the editing window</para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property>Managed Beans</property>
+ </emphasis> node and then click the <emphasis>
+ <property>Add...</property>
+ </emphasis> button displayed along the right side of the editor window</para>
+ </listitem>
+ <listitem>
+ <para>Type in <emphasis>
+ <property>jsfHello.PersonBean</property>
+ </emphasis> for Class and <emphasis>
+ <property>personBean</property>
+ </emphasis> for Name. Leave Scope as is and Generate Source Code as is
+ (checked)</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>personBean will now be selected and three sections of information: <emphasis>
+ <property>Managed Bean</property>
+ </emphasis>, <emphasis>
+ <property>Properties</property>
+ </emphasis>, and <emphasis>
+ <property>Advanced</property>
+ </emphasis>, will be displayed about it. Under the Properties section, click the <emphasis>
+ <property>Add...</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Type in <emphasis>
+ <property>name</property>
+ </emphasis> for Property-Name. Leave everything else as is. (When Property-
+ Class is not filled in, String is the assumed type)</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property>personBean</property>
+ </emphasis> node in the tree</para>
+ </listitem>
+ </itemizedlist>
+ <para>You should see this now:</para>
+ <figure>
+ <title>Tree View in Config Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Select <emphasis>
+ <property>File > Save</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ <para>You have now registered the <emphasis>
+ <property>managed bean</property>
+ </emphasis> and created a <emphasis>
+ <property>stub-coded class</property>
+ </emphasis> file for it.</para>
+
+ </chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/adding_navigation.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/adding_navigation.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/adding_navigation.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,108 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="adding_navigation" xreflabel="adding_navigation">
+ <?dbhtml filename="adding_navigation.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Adding Navigation to the Application</title>
+
+ <para>In our simple application, the flow is defined as a single navigation rule connecting
+ two views (presentation files). At this point, we will create the placeholders for the
+ two JSP presentation files and then the navigation rule to connect them as views. Later,
+ we will complete the coding for the JSP presentation files. We can do all of this in the
+ Diagram mode of the configuration file editor.</para>
+ <section id="AddingTwoViewsJSPPages">
+ <?dbhtml filename="AddingTwoViewsJSPPages.html"?>
+ <title>Adding Two Views (JSP Pages)</title>
+ <itemizedlist>
+ <listitem>
+ <para>Right-click anywhere on the diagram and select <emphasis>
+ <property>New View...</property>
+ </emphasis> from the pop-up menu</para>
+ </listitem>
+ <listitem>
+ <para>In the dialog box, type <emphasis>
+ <property>pages/inputname</property>
+ </emphasis> as the value for From-view-id</para>
+ </listitem>
+ <listitem>
+ <para>Leave everything else as is</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ <para>If you look in the Package Explorer view you should see a <emphasis>
+ <property>pages</property>
+ </emphasis> folder under WebContent. Opening it will reveal the JSP file you
+ just created</para>
+ </listitem>
+ <listitem>
+ <para>Back on the diagram, right-click anywhere and select <emphasis>
+ <property>New View...</property>
+ </emphasis> from the pop-up menu</para>
+ </listitem>
+ <listitem>
+ <para>In the dialog box, type <emphasis>
+ <property>pages/greeting</property>
+ </emphasis> as the value for From-view-id</para>
+ </listitem>
+ <listitem>
+ <para>Leave everything else as is</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+ <section id="CreatingTheTransitionNavigationRule">
+ <?dbhtml filename="CreatingTheTransitionNavigationRule.html"?>
+ <title>Creating the Transition (Navigation Rule)</title>
+ <itemizedlist>
+ <listitem>
+ <para>In the diagram, select the connection icon third from the top along
+ the upper left side of the diagram (<inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_3.png"/>
+ </imageobject>
+ </inlinemediaobject>) to get an arrow cursor with a two-pronged plug at the arrow's bottom.</para>
+ </listitem>
+ </itemizedlist>
+
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>pages/inputname</property>
+ </emphasis> page icon and then click on the <emphasis>
+ <property>pages/greeting</property>
+ </emphasis> page icon</para>
+ </listitem>
+
+ </itemizedlist>
+ <para>A transition should appear between the two icons.</para>
+ <figure>
+ <title>Transition Between Two Icons</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Select <emphasis>
+ <property>File > Save</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+</chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/favicon.ico
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/favicon.ico
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jbosstools_logo.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jbosstools_logo.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_10.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_10.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_8.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_9.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/images/jsf_application/jsf_application_9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/introduction.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/introduction.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/introduction.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="introduction" xreflabel="introduction">
+ <?dbhtml filename="introduction.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Introduction</title>
+ <para>The following chapters describe how to deal with classic/old style of JSF development. We
+ recommend users to use JBoss
+ Seam to simplify development, but until then you can read about classical JSF
+ usage here.</para>
+
+ <para>Thus, in this document we are going to show you how to create a simple <property>JSF application
+ </property>using <property>JBoss Tools</property> plugins for Eclipse. The completed
+ application will ask a user to enter a name and click a button. The resulting new page
+ will display the familiar message, "Hello <name>!" This
+ tutorial will show you how to create and run such an application from the beginning along the
+ way demonstrating some of the powerful features of <property>JBoss Tools</property>.</para>
+ <section><title>Key Features of JSF Tools</title>
+ <para>Here, we provide you with a key functionality which is integrated in JSF tooling.</para>
+
+ <table>
+ <title>Key Functionality for JSF Tools</title>
+ <tgroup cols="2">
+
+ <colspec colnum="1" align="left" colwidth="2*"/>
+ <colspec colnum="2" colwidth="4*"/>
+
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+
+ </row>
+ </thead>
+ <tbody>
+
+ <row>
+ <entry>JSF and Facelets support</entry>
+ <entry>Step-by-step wizards for creating new JSF and Facelets projects with a number of predefined templates, importing existing ones and adding JSF capabilities to non-jsf web projects.</entry>
+
+ </row>
+
+ <row>
+ <entry>Flexible and customizable project template management</entry>
+ <entry>Jump-start development with out-of-the-box templates or easily
+ customized templates for re-use.</entry>
+
+ </row>
+
+ <row>
+ <entry>Support for JSF Configuration File</entry>
+ <entry>Working on file using three modes: diagram, tree and source.
+ Synchronization between the modes and full control over the code. Easy
+ moving around the diagram using the Diagram Navigator.</entry>
+
+ </row>
+
+ <row>
+ <entry>Support for Managed Beans</entry>
+ <entry>Adding new managed beans, generating code for attributes, properties
+ and getter/setter methods.</entry>
+
+ </row>
+
+ <row>
+ <entry>Support for Custom Converters and Validators</entry>
+ <entry>Fast creating of custom converters and validators with tree view of
+ faces-config.xml file.</entry>
+
+ </row>
+
+ <row>
+ <entry>Verification and Validation</entry>
+ <entry>All occuring errors will be immediately reported by verification
+ feature, no matter in what view you are working. Constant validation and
+ errors checking allows to catch many of the errors during development
+ process that significantly reduces development time.</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </section>
+
+
+ <section>
+ <title>Other relevant resources on the topic</title>
+ <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at <ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/tools</ulink> in the corresponding release directory.</para>
+ <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs</ulink>.</para>
+ </section>
+
+</chapter>
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/jsf_application.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/jsf_application.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/jsf_application.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="jsf_application" xreflabel="jsf_application">
+ <?dbhtml filename="jsf_application.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Creating a Simple JSF Application</title>
+
+ <para>Firstly, we assume that you have already launched Eclipse with <property>JBoss Tools</property>
+ plug-ins installed and also that the <property>Web Development perspective</property> is the current
+ one. (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 <emphasis>
+ <property>Web Development</property>
+ </emphasis> from the Select Perspective dialog box.)</para>
+
+ <section id="setting_up_the_project">
+ <?dbhtml filename="SettingUpTheProject.html"?>
+ <title>Setting Up the Project</title>
+ <para>Now we are going to create a new project for the application.</para>
+ <itemizedlist>
+ <listitem>
+ <para>For that go to the menu bar and select <emphasis>
+ <property>File > New > Project...</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Select <emphasis>
+ <property>JBoss Tools Web > JSF > JSF Project</property>
+ </emphasis> in the New Project dialog box</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property>Next</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Enter "jsfHello" as the project name.</para>
+ </listitem>
+ <listitem>
+ <para>Leave everything else as is, and click <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ </listitem>
+
+ </itemizedlist>
+ </section>
+
+ <section id="TheJSFApplicationConfigurationFile">
+ <?dbhtml filename="TheJSFApplicationConfigurationFile.html"?>
+ <title>JSF Configuration File</title>
+ <para>A jsfHello node should appear in the upper-left Package Explorer view.</para>
+ <figure>
+ <title>Package Explorer View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property>jsfHello</property>
+ </emphasis> to reveal the child nodes</para>
+ </listitem>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property>WebContent</property>
+ </emphasis> under jsfHello</para>
+ </listitem>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property>WEB-INF</property>
+ </emphasis> under WebContent</para>
+ </listitem>
+
+ <listitem>
+ <para>Then double-click on the <property>faces-config.xml</property> node to display
+ the JSF application configuration file editor</para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Configuration File Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+</chapter>
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/jsp_view_files.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/jsp_view_files.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/jsp_view_files.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,255 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="jsp_view_files" xreflabel="jsp_view_files">
+ <?dbhtml filename="jsp_view_files.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Editing the JSP View Files</title>
+
+ <para>Now we will finish editing the JSP files for our two "views" using
+ JSP Visual Page.</para>
+ <section id="Inputname.jsp">
+ <title>inputname.jsp</title>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>Diagram</property>
+ </emphasis> tab for the configuration file editor</para>
+ </listitem>
+ <listitem>
+ <para>Open the editor for this first JSP file by double-clicking on the <emphasis>
+ <property>/pages/inputname. 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:</para>
+ <figure>
+ <title>Visual Page Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Some JSF code is already in the file, because we have chosen a template to create
+ a page.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Select the <emphasis>
+ <property>Visual</property>
+ </emphasis> tab, so we can work with the editor completely in its WYSIWYG
+ mode</para>
+ </listitem>
+ <listitem>
+ <para>To the right of the editor, in the JBoss Tools Palette, expand the <emphasis>
+ <property>JSF HTML</property>
+ </emphasis> palette folder by selecting it</para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>JBoss Tools Palette</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Click on <emphasis>
+ <property>form</property>
+ </emphasis> within this folder, drag the cursor over to the editor, and drop
+ it inside the red box in the editor</para>
+ </listitem>
+ <listitem>
+ <para>Another red box will appear inside the first red box</para>
+ </listitem>
+ <listitem>
+ <para>Right-click on the innermost box and select <emphasis role="bold">
+ <property><h:form></property>
+ </emphasis> Attributes from the menu</para>
+ </listitem>
+ <listitem>
+ <para>In the value field next to id, type <emphasis>
+ <property>greeting</property>
+ </emphasis> and click on the <emphasis>
+ <property>Close</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Type "Please enter name:" inside the boxes</para>
+ </listitem>
+ <listitem>
+ <para>Select <emphasis>
+ <property>inputText</property>
+ </emphasis> within the JSF HTML palette folder and drag it into the
+ innermost box in the editor after "Please enter
+ name:"</para>
+ </listitem>
+ <listitem>
+ <para>In the attributes dialog, click in the <emphasis>
+ <property>value</property>
+ </emphasis> field next to the value attribute and click on the <property>...
+ </property>button</para>
+ </listitem>
+ <listitem>
+ <para>Then, select the <emphasis>
+ <property>Managed Beans > personBean > name</property>
+ </emphasis> node and click on the <emphasis>
+ <property>Ok</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Back in the attributes dialog, select the <emphasis>
+ <property>Advanced</property>
+ </emphasis> tab, type in <emphasis>
+ <property>name</property>
+ </emphasis> as the value for the <emphasis role="italic">
+ <property>"id"</property>
+ </emphasis> attribute, and then click on the <emphasis>
+ <property>Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Select <emphasis>
+ <property>commandButton</property>
+ </emphasis> within the JSF HTML palette folder and drag it into the
+ innermost box in the editor after the input box</para>
+ </listitem>
+ <listitem>
+ <para>In the attributes dialog, click in the value field next to the <emphasis
+ role="italic">
+ <property>"action"</property>
+ </emphasis> attribute and click on the <property>...
+ </property>button</para>
+ </listitem>
+ <listitem>
+ <para>Then, select the <emphasis>
+ <property>View Actions > greeting</property>
+ </emphasis> node and click on the <emphasis>
+ <property>OK</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Back in the attributes dialog box, type in "Say Hello"
+ as the value for the value attribute ("Say Hello") and
+ then click on the <emphasis>
+ <property>Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ </itemizedlist>
+ <para>The source coding should be something like this now:</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" %>
+<html>
+<head>
+<title></title>
+</head>
+<body>
+<f:view>
+<h:form id="greeting">
+Please enter name:
+<h:inputText id="name" value="#{personBean.name}"/>
+<h:commandButton value=" Say Hello " action="greeting"/>
+</h:form>
+</f:view>
+</body>
+</html>
+]]></programlisting>
+ <para>The editor should look like this:</para>
+ <figure>
+ <title>Visual Page Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_8.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Save the file by selecting <emphasis>
+ <property>File > Save</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="Greeting.jsp">
+ <title>greeting.jsp</title>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property>faces-config.xml</property>
+ </emphasis> tab to bring the diagram back</para>
+ </listitem>
+ <listitem>
+ <para>Open the editor for the second file by double-clicking on the <emphasis>
+ <property>/pages/greeting.jsp</property>
+ </emphasis> icon</para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property>Visual</property>
+ </emphasis> tab, so we can work with the editor completely in its WYSIWYG
+ mode</para>
+ </listitem>
+ <listitem>
+ <para>Type "Hello "(note space after Hello) into the
+ box</para>
+ </listitem>
+ <listitem>
+ <para>Select <emphasis>
+ <property>outputText</property>
+ </emphasis> within the JSF HTML palette folder and drag it into the
+ innermost box in the editor after "Hello"</para>
+ </listitem>
+ <listitem>
+ <para>In the attributes dialog, click in <emphasis>
+ <property>value</property>
+ </emphasis> field next to the value attribute and click on the
+ <property>...</property> (Browse) button</para>
+ </listitem>
+ <listitem>
+ <para>Then, select the <emphasis>
+ <property>Managed Beans > personBean > name</property>
+ </emphasis> node, click on the <emphasis>
+ <property>Ok</property>
+ </emphasis> button, and then click on the <emphasis>
+ <property>Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Right after the output field, type an <emphasis>
+ <property>exclamation point</property>
+ </emphasis> (<emphasis>
+ <property>!</property>
+ </emphasis>)</para>
+ </listitem>
+ </itemizedlist>
+ <para>The source coding should be something like this now:</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" %>
+<html>
+<head>
+<title></title>
+</head>
+<body>
+<f:view>
+Hello <h:outputText value="#{personBean.name}"/>!
+</f:view>
+</body>
+</html>
+]]></programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>Save the file</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/master.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/master.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/master.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,80 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+[<!ENTITY introduction SYSTEM "introduction.xml">
+<!ENTITY jsf_application SYSTEM "jsf_application.xml">
+<!ENTITY adding_navigation SYSTEM "adding_navigation.xml">
+<!ENTITY adding_managed_bean SYSTEM "adding_managed_bean.xml">
+<!ENTITY jsp_view_files SYSTEM "jsp_view_files.xml">
+<!ENTITY start_page SYSTEM "start_page.xml">
+<!ENTITY running_application SYSTEM "running_application.xml">
+<!ENTITY relevant_resources SYSTEM "relevant_resources.xml">
+
+<!ENTITY seamlink "../../seam/html_single/index.html">
+<!ENTITY aslink "../../as/html_single/index.html">
+<!ENTITY esblink "../../esb_ref_guide/html_single/index.html">
+<!ENTITY gsglink "../../GettingStartedGuide/html_single/index.html">
+<!ENTITY hibernatelink "../../hibernatetools/html_single/index.html">
+<!ENTITY jbpmlink "../../jbpm/html_single/index.html">
+<!ENTITY jsflink "../../jsf/html_single/index.html">
+<!ENTITY jsfreflink "../../jsf_tools_ref_guide/html_single/index.html">
+<!ENTITY jsftutoriallink "../../jsf_tools_tutorial/html_single/index.html">
+<!ENTITY strutsreflink "../../struts_tools_ref_guide/html_single/index.html">
+<!ENTITY strutstutoriallink "../../struts_tools_tutorial/html_single/index.html">
+
+]>
+
+<book>
+
+ <bookinfo>
+ <title>JSF Tools Tutorial</title>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata format="PNG" fileref="images/jbosstools_logo.png" />
+ </imageobject>
+ <imageobject role="html">
+ <imagedata/>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author><firstname>Anatoly</firstname><surname>Fedosik</surname></author>
+ <author><firstname>Olga</firstname><surname>Chikvina</surname></author>
+ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author>
+
+ <copyright>
+ <year>2007</year>
+ <year>2008</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+
+ <releaseinfo>
+ Version: 3.1.0.GA
+ </releaseinfo>
+
+
+<abstract>
+ <title/>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/jsf_tools_tutorial/p...">PDF version</ulink>
+ </para>
+</abstract>
+
+
+ </bookinfo>
+
+ <toc/>
+
+
+ &introduction;
+ &jsf_application;
+ &adding_navigation;
+ &adding_managed_bean;
+ &jsp_view_files;
+ &start_page;
+ &running_application;
+ &relevant_resources;
+</book>
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/master_output.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/master_output.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/master_output.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,872 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+[<!ENTITY introduction SYSTEM "modules/introduction.xml">
+<!ENTITY jsf_application SYSTEM "modules/jsf_application.xml">
+<!ENTITY adding_navigation SYSTEM "modules/adding_navigation.xml">
+<!ENTITY adding_managed_bean SYSTEM "modules/adding_managed_bean.xml">
+<!ENTITY jsp_view_files SYSTEM "modules/jsp_view_files.xml">
+<!ENTITY start_page SYSTEM "modules/start_page.xml">
+<!ENTITY running_application SYSTEM "modules/running_application.xml">
+<!ENTITY relevant_resources SYSTEM "modules/relevant_resources.xml">
+
+<!ENTITY seamlink "../../seam/html_single/index.html">
+<!ENTITY aslink "../../as/html_single/index.html">
+<!ENTITY esblink "../../esb_ref_guide/html_single/index.html">
+<!ENTITY gsglink "../../GettingStartedGuide/html_single/index.html">
+<!ENTITY hibernatelink "../../hibernatetools/html_single/index.html">
+<!ENTITY jbpmlink "../../jbpm/html_single/index.html">
+<!ENTITY jsflink "../../jsf/html_single/index.html">
+<!ENTITY jsfreflink "../../jsf_tools_ref_guide/html_single/index.html">
+<!ENTITY jsftutoriallink "../../jsf_tools_tutorial/html_single/index.html">
+<!ENTITY strutsreflink "../../struts_tools_ref_guide/html_single/index.html">
+<!ENTITY strutstutoriallink "../../struts_tools_tutorial/html_single/index.html">
+
+]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff">
+
+ <bookinfo>
+ <title>JSF Tools Tutorial</title>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
+ </imageobject>
+ <imageobject role="html">
+ <imagedata></imagedata>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author><firstname>Anatoly</firstname><surname>Fedosik</surname></author>
+ <author><firstname>Olga</firstname><surname>Chikvina</surname></author>
+ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author>
+
+ <copyright>
+ <year>2007</year>
+ <year>2008</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+
+ <releaseinfo><diffmk:wrapper diffmk:change="changed">
+ Version: 3.1.0.GA
+ </diffmk:wrapper></releaseinfo>
+
+
+<abstract>
+ <title></title>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/jsf_tools_tutorial/p...">PDF version</ulink>
+ </para>
+</abstract>
+
+
+ </bookinfo>
+
+ <toc></toc>
+
+
+
+<chapter id="introduction" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jsf/docs/jsf_tools_tutorial/en/modules/introduction.xml" xreflabel="introduction">
+ <?dbhtml filename="introduction.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Introduction</title>
+ <para>The following chapters describe how to deal with classic/old style of JSF development. We
+ recommend users to use <ulink url="../../seam/html_single/index.html">JBoss
+ Seam</ulink> to simplify development, but until then you can read about classical JSF
+ usage here.</para>
+
+ <para>Thus, in this document we are going to show you how to create a simple <property moreinfo="none">JSF application
+ </property>using <property moreinfo="none">JBoss Tools</property> plugins for Eclipse. The completed
+ application will ask a user to enter a name and click a button. The resulting new page
+ will display the familiar message, "Hello <name>!" This
+ tutorial will show you how to create and run such an application from the beginning along the
+ way demonstrating some of the powerful features of <property moreinfo="none">JBoss Tools</property>.</para>
+ <section><title>Key Features of JSF Tools</title>
+ <para>Here, we provide you with a key functionality which is integrated in JSF tooling.</para>
+
+ <table>
+ <title>Key Functionality for JSF Tools</title>
+ <tgroup cols="2">
+
+ <colspec align="left" colnum="1" colwidth="2*"></colspec>
+ <colspec colnum="2" colwidth="4*"></colspec>
+
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+
+ </row>
+ </thead>
+ <tbody>
+
+ <row>
+ <entry>JSF and Facelets support</entry>
+ <entry>Step-by-step wizards for creating new JSF and Facelets projects with a number of predefined templates, importing existing ones and adding JSF capabilities to non-jsf web projects.</entry>
+
+ </row>
+
+ <row>
+ <entry>Flexible and customizable project template management</entry>
+ <entry>Jump-start development with out-of-the-box templates or easily
+ customized templates for re-use.</entry>
+
+ </row>
+
+ <row>
+ <entry>Support for JSF Configuration File</entry>
+ <entry>Working on file using three modes: diagram, tree and source.
+ Synchronization between the modes and full control over the code. Easy
+ moving around the diagram using the Diagram Navigator.</entry>
+
+ </row>
+
+ <row>
+ <entry>Support for Managed Beans</entry>
+ <entry>Adding new managed beans, generating code for attributes, properties
+ and getter/setter methods.</entry>
+
+ </row>
+
+ <row>
+ <entry>Support for Custom Converters and Validators</entry>
+ <entry>Fast creating of custom converters and validators with tree view of
+ faces-config.xml file.</entry>
+
+ </row>
+
+ <row>
+ <entry>Verification and Validation</entry>
+ <entry>All occuring errors will be immediately reported by verification
+ feature, no matter in what view you are working. Constant validation and
+ errors checking allows to catch many of the errors during development
+ process that significantly reduces development time.</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </section>
+
+
+ <section>
+ <title>Other relevant resources on the topic</title>
+ <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at <ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/tools</ulink> in the corresponding release directory.</para>
+ <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs</ulink>.</para>
+ </section>
+
+</chapter>
+
+
+<chapter id="jsf_application" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jsf/docs/jsf_tools_tutorial/en/modules/jsf_application.xml" xreflabel="jsf_application">
+ <?dbhtml filename="jsf_application.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Creating a Simple JSF Application</title>
+
+ <para>Firstly, we assume that you have already launched Eclipse with <property moreinfo="none">JBoss Tools</property>
+ plug-ins installed and also that the <property moreinfo="none">Web Development perspective</property> is the current
+ one. (If not, make it active by selecting <emphasis>
+ <property moreinfo="none">Window > Open Perspective > Web Development</property>
+ </emphasis> from the menu bar or by selecting <emphasis>
+ <property moreinfo="none">Window > Open Perspective > Other...</property>
+ </emphasis> from the menu bar and then selecting <emphasis>
+ <property moreinfo="none">Web Development</property>
+ </emphasis> from the Select Perspective dialog box.)</para>
+
+ <section id="setting_up_the_project">
+ <?dbhtml filename="SettingUpTheProject.html"?>
+ <title>Setting Up the Project</title>
+ <para>Now we are going to create a new project for the application.</para>
+ <itemizedlist>
+ <listitem>
+ <para>For that go to the menu bar and select <emphasis>
+ <property moreinfo="none">File > New > Project...</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Select <emphasis>
+ <property moreinfo="none">JBoss Tools Web > JSF > JSF Project</property>
+ </emphasis> in the New Project dialog box</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">Next</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Enter "jsfHello" as the project name.</para>
+ </listitem>
+ <listitem>
+ <para>Leave everything else as is, and click <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ </listitem>
+
+ </itemizedlist>
+ </section>
+
+ <section id="TheJSFApplicationConfigurationFile">
+ <?dbhtml filename="TheJSFApplicationConfigurationFile.html"?>
+ <title>JSF Configuration File</title>
+ <para>A jsfHello node should appear in the upper-left Package Explorer view.</para>
+ <figure float="0">
+ <title>Package Explorer View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property moreinfo="none">jsfHello</property>
+ </emphasis> to reveal the child nodes</para>
+ </listitem>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property moreinfo="none">WebContent</property>
+ </emphasis> under jsfHello</para>
+ </listitem>
+ <listitem>
+ <para>Click the plus sign next to <emphasis>
+ <property moreinfo="none">WEB-INF</property>
+ </emphasis> under WebContent</para>
+ </listitem>
+
+ <listitem>
+ <para>Then double-click on the <property moreinfo="none">faces-config.xml</property> node to display
+ the JSF application configuration file editor</para>
+ </listitem>
+ </itemizedlist>
+ <figure float="0">
+ <title>Configuration File Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+</chapter>
+
+
+<chapter id="adding_navigation" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jsf/docs/jsf_tools_tutorial/en/modules/adding_navigation.xml" xreflabel="adding_navigation">
+ <?dbhtml filename="adding_navigation.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Adding Navigation to the Application</title>
+
+ <para>In our simple application, the flow is defined as a single navigation rule connecting
+ two views (presentation files). At this point, we will create the placeholders for the
+ two JSP presentation files and then the navigation rule to connect them as views. Later,
+ we will complete the coding for the JSP presentation files. We can do all of this in the
+ Diagram mode of the configuration file editor.</para>
+ <section id="AddingTwoViewsJSPPages">
+ <?dbhtml filename="AddingTwoViewsJSPPages.html"?>
+ <title>Adding Two Views (JSP Pages)</title>
+ <itemizedlist>
+ <listitem>
+ <para>Right-click anywhere on the diagram and select <emphasis>
+ <property moreinfo="none">New View...</property>
+ </emphasis> from the pop-up menu</para>
+ </listitem>
+ <listitem>
+ <para>In the dialog box, type <emphasis>
+ <property moreinfo="none">pages/inputname</property>
+ </emphasis> as the value for From-view-id</para>
+ </listitem>
+ <listitem>
+ <para>Leave everything else as is</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ <para>If you look in the Package Explorer view you should see a <emphasis>
+ <property moreinfo="none">pages</property>
+ </emphasis> folder under WebContent. Opening it will reveal the JSP file you
+ just created</para>
+ </listitem>
+ <listitem>
+ <para>Back on the diagram, right-click anywhere and select <emphasis>
+ <property moreinfo="none">New View...</property>
+ </emphasis> from the pop-up menu</para>
+ </listitem>
+ <listitem>
+ <para>In the dialog box, type <emphasis>
+ <property moreinfo="none">pages/greeting</property>
+ </emphasis> as the value for From-view-id</para>
+ </listitem>
+ <listitem>
+ <para>Leave everything else as is</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+ <section id="CreatingTheTransitionNavigationRule">
+ <?dbhtml filename="CreatingTheTransitionNavigationRule.html"?>
+ <title>Creating the Transition (Navigation Rule)</title>
+ <itemizedlist>
+ <listitem>
+ <para>In the diagram, select the connection icon third from the top along
+ the upper left side of the diagram (<inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_3.png"></imagedata>
+ </imageobject>
+ </inlinemediaobject>) to get an arrow cursor with a two-pronged plug at the arrow's bottom.</para>
+ </listitem>
+ </itemizedlist>
+
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">pages/inputname</property>
+ </emphasis> page icon and then click on the <emphasis>
+ <property moreinfo="none">pages/greeting</property>
+ </emphasis> page icon</para>
+ </listitem>
+
+ </itemizedlist>
+ <para>A transition should appear between the two icons.</para>
+ <figure float="0">
+ <title>Transition Between Two Icons</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Select <emphasis>
+ <property moreinfo="none">File > Save</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+</chapter>
+
+<chapter id="adding_managed_bean" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jsf/docs/jsf_tools_tutorial/en/modules/adding_managed_bean.xml" xreflabel="adding_managed_bean">
+ <?dbhtml filename="adding_managed_bean.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Adding a Managed Bean to the Application</title>
+ <para>To store data in the application, we will use a managed bean.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">Tree</property>
+ </emphasis> tab at the bottom of the editing window</para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property moreinfo="none">Managed Beans</property>
+ </emphasis> node and then click the <emphasis>
+ <property moreinfo="none">Add...</property>
+ </emphasis> button displayed along the right side of the editor window</para>
+ </listitem>
+ <listitem>
+ <para>Type in <emphasis>
+ <property moreinfo="none">jsfHello.PersonBean</property>
+ </emphasis> for Class and <emphasis>
+ <property moreinfo="none">personBean</property>
+ </emphasis> for Name. Leave Scope as is and Generate Source Code as is
+ (checked)</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>personBean will now be selected and three sections of information: <emphasis>
+ <property moreinfo="none">Managed Bean</property>
+ </emphasis>, <emphasis>
+ <property moreinfo="none">Properties</property>
+ </emphasis>, and <emphasis>
+ <property moreinfo="none">Advanced</property>
+ </emphasis>, will be displayed about it. Under the Properties section, click the <emphasis>
+ <property moreinfo="none">Add...</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Type in <emphasis>
+ <property moreinfo="none">name</property>
+ </emphasis> for Property-Name. Leave everything else as is. (When Property-
+ Class is not filled in, String is the assumed type)</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property moreinfo="none">personBean</property>
+ </emphasis> node in the tree</para>
+ </listitem>
+ </itemizedlist>
+ <para>You should see this now:</para>
+ <figure float="0">
+ <title>Tree View in Config Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_5.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Select <emphasis>
+ <property moreinfo="none">File > Save</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ <para>You have now registered the <emphasis>
+ <property moreinfo="none">managed bean</property>
+ </emphasis> and created a <emphasis>
+ <property moreinfo="none">stub-coded class</property>
+ </emphasis> file for it.</para>
+
+ </chapter>
+
+<chapter id="jsp_view_files" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jsf/docs/jsf_tools_tutorial/en/modules/jsp_view_files.xml" xreflabel="jsp_view_files">
+ <?dbhtml filename="jsp_view_files.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Editing the JSP View Files</title>
+
+ <para>Now we will finish editing the JSP files for our two "views" using
+ JSP Visual Page.</para>
+ <section id="Inputname.jsp">
+ <title>inputname.jsp</title>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">Diagram</property>
+ </emphasis> tab for the configuration file editor</para>
+ </listitem>
+ <listitem>
+ <para>Open the editor for this first JSP file by double-clicking on the <emphasis>
+ <property moreinfo="none">/pages/inputname. 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:</para>
+ <figure float="0">
+ <title>Visual Page Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_6.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Some JSF code is already in the file, because we have chosen a template to create
+ a page.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Select the <emphasis>
+ <property moreinfo="none">Visual</property>
+ </emphasis> tab, so we can work with the editor completely in its WYSIWYG
+ mode</para>
+ </listitem>
+ <listitem>
+ <para>To the right of the editor, in the JBoss Tools Palette, expand the <emphasis>
+ <property moreinfo="none">JSF HTML</property>
+ </emphasis> palette folder by selecting it</para>
+ </listitem>
+ </itemizedlist>
+ <figure float="0">
+ <title>JBoss Tools Palette</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_7.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Click on <emphasis>
+ <property moreinfo="none">form</property>
+ </emphasis> within this folder, drag the cursor over to the editor, and drop
+ it inside the red box in the editor</para>
+ </listitem>
+ <listitem>
+ <para>Another red box will appear inside the first red box</para>
+ </listitem>
+ <listitem>
+ <para>Right-click on the innermost box and select <emphasis role="bold">
+ <property moreinfo="none"><h:form></property>
+ </emphasis> Attributes from the menu</para>
+ </listitem>
+ <listitem>
+ <para>In the value field next to id, type <emphasis>
+ <property moreinfo="none">greeting</property>
+ </emphasis> and click on the <emphasis>
+ <property moreinfo="none">Close</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Type "Please enter name:" inside the boxes</para>
+ </listitem>
+ <listitem>
+ <para>Select <emphasis>
+ <property moreinfo="none">inputText</property>
+ </emphasis> within the JSF HTML palette folder and drag it into the
+ innermost box in the editor after "Please enter
+ name:"</para>
+ </listitem>
+ <listitem>
+ <para>In the attributes dialog, click in the <emphasis>
+ <property moreinfo="none">value</property>
+ </emphasis> field next to the value attribute and click on the <property moreinfo="none">...
+ </property>button</para>
+ </listitem>
+ <listitem>
+ <para>Then, select the <emphasis>
+ <property moreinfo="none">Managed Beans > personBean > name</property>
+ </emphasis> node and click on the <emphasis>
+ <property moreinfo="none">Ok</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Back in the attributes dialog, select the <emphasis>
+ <property moreinfo="none">Advanced</property>
+ </emphasis> tab, type in <emphasis>
+ <property moreinfo="none">name</property>
+ </emphasis> as the value for the <emphasis role="italic">
+ <property moreinfo="none">"id"</property>
+ </emphasis> attribute, and then click on the <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Select <emphasis>
+ <property moreinfo="none">commandButton</property>
+ </emphasis> within the JSF HTML palette folder and drag it into the
+ innermost box in the editor after the input box</para>
+ </listitem>
+ <listitem>
+ <para>In the attributes dialog, click in the value field next to the <emphasis role="italic">
+ <property moreinfo="none">"action"</property>
+ </emphasis> attribute and click on the <property moreinfo="none">...
+ </property>button</para>
+ </listitem>
+ <listitem>
+ <para>Then, select the <emphasis>
+ <property moreinfo="none">View Actions > greeting</property>
+ </emphasis> node and click on the <emphasis>
+ <property moreinfo="none">OK</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Back in the attributes dialog box, type in "Say Hello"
+ as the value for the value attribute ("Say Hello") and
+ then click on the <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ </itemizedlist>
+ <para>The source coding should be something like this now:</para>
+ <programlisting format="linespecific" role="XML"><![CDATA[<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
+<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
+<html>
+<head>
+<title></title>
+</head>
+<body>
+<f:view>
+<h:form id="greeting">
+Please enter name:
+<h:inputText id="name" value="#{personBean.name}"/>
+<h:commandButton value=" Say Hello " action="greeting"/>
+</h:form>
+</f:view>
+</body>
+</html>
+]]></programlisting>
+ <para>The editor should look like this:</para>
+ <figure float="0">
+ <title>Visual Page Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_8.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Save the file by selecting <emphasis>
+ <property moreinfo="none">File > Save</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="Greeting.jsp">
+ <title>greeting.jsp</title>
+ <itemizedlist>
+ <listitem>
+ <para>Click on the <emphasis>
+ <property moreinfo="none">faces-config.xml</property>
+ </emphasis> tab to bring the diagram back</para>
+ </listitem>
+ <listitem>
+ <para>Open the editor for the second file by double-clicking on the <emphasis>
+ <property moreinfo="none">/pages/greeting.jsp</property>
+ </emphasis> icon</para>
+ </listitem>
+ <listitem>
+ <para>Select the <emphasis>
+ <property moreinfo="none">Visual</property>
+ </emphasis> tab, so we can work with the editor completely in its WYSIWYG
+ mode</para>
+ </listitem>
+ <listitem>
+ <para>Type "Hello "(note space after Hello) into the
+ box</para>
+ </listitem>
+ <listitem>
+ <para>Select <emphasis>
+ <property moreinfo="none">outputText</property>
+ </emphasis> within the JSF HTML palette folder and drag it into the
+ innermost box in the editor after "Hello"</para>
+ </listitem>
+ <listitem>
+ <para>In the attributes dialog, click in <emphasis>
+ <property moreinfo="none">value</property>
+ </emphasis> field next to the value attribute and click on the
+ <property moreinfo="none">...</property> (Browse) button</para>
+ </listitem>
+ <listitem>
+ <para>Then, select the <emphasis>
+ <property moreinfo="none">Managed Beans > personBean > name</property>
+ </emphasis> node, click on the <emphasis>
+ <property moreinfo="none">Ok</property>
+ </emphasis> button, and then click on the <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button</para>
+ </listitem>
+ <listitem>
+ <para>Right after the output field, type an <emphasis>
+ <property moreinfo="none">exclamation point</property>
+ </emphasis> (<emphasis>
+ <property moreinfo="none">!</property>
+ </emphasis>)</para>
+ </listitem>
+ </itemizedlist>
+ <para>The source coding should be something like this now:</para>
+ <programlisting format="linespecific" role="XML"><![CDATA[<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
+<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
+<html>
+<head>
+<title></title>
+</head>
+<body>
+<f:view>
+Hello <h:outputText value="#{personBean.name}"/>!
+</f:view>
+</body>
+</html>
+]]></programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>Save the file</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </chapter>
+
+<chapter id="start_page" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jsf/docs/jsf_tools_tutorial/en/modules/start_page.xml" xreflabel="start_page">
+ <?dbhtml filename="start_page.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Creating the Start Page</title>
+ <para>You also need to create a start page as an entry point into the application.</para>
+ <itemizedlist>
+ <listitem>
+ <para>In the Package Explorer view to the left, right-click <emphasis>
+ <property moreinfo="none">jsfHello > WebContent</property>
+ </emphasis> and select <emphasis>
+ <property moreinfo="none">New > JSP File</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>For Name type in <emphasis>
+ <property moreinfo="none">index</property>
+ </emphasis>, for Template select <emphasis>
+ <property moreinfo="none">JSPRedirect</property>
+ </emphasis> and click <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <para>A JSP editor will open up on the newly created file.</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>In the Source part of the split screen, type <emphasis>
+ <property moreinfo="none">/pages/inputname.jsf</property>
+ </emphasis> in between the quotes for the page attribute</para>
+ </listitem>
+ </itemizedlist>
+ <para>The source coding should look like this now:</para>
+ <programlisting format="linespecific" role="XML"><![CDATA[<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+<html>
+<head></head>
+<body>
+<jsp:forward page="/pages/inputname.jsf" />
+</body>
+</html>
+]]></programlisting>
+
+ <para>Note the <emphasis>
+ <property moreinfo="none">.jsf</property>
+ </emphasis> extension for the file name. This is a mapping defined in the web.xml file
+ for the project for invoking <property moreinfo="none">JavaServer Faces</property> when you run the
+ application.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Select<emphasis>
+ <property moreinfo="none"> File > Save</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ </chapter>
+
+<chapter id="running_application" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jsf/docs/jsf_tools_tutorial/en/modules/running_application.xml" xreflabel="running_application">
+ <?dbhtml filename="running_application.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Running the Application</title>
+ <para>Everything is now ready for running our application by using the JBoss engine. For
+ controlling JBoss server there is JBoss Server view:</para>
+ <figure float="0">
+ <title>JBoss Server View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_9.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <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 the Run icon(<inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_10.png"></imagedata>
+ </imageobject>
+ </inlinemediaobject>) or right click your project folder and select <emphasis>
+ <property moreinfo="none">Run As > Run on Server</property>
+ </emphasis>:</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>This is the equivalent of launching the browser and typing <emphasis>
+ <property moreinfo="none">http://localhost:8080/jsfHello</property>
+ </emphasis> into your browser. Our <property moreinfo="none">JSF application</property> should now
+ appear.</para>
+ </chapter>
+
+<chapter id="relevant_resources" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jsf/docs/jsf_tools_tutorial/en/modules/relevant_resources.xml" xreflabel="relevant_resources">
+ <?dbhtml filename="relevant_resources.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Other Relevant Resources on the topic</title>
+ <para>JSF on Sun: <ulink url="http://java.sun.com/javaee/javaserverfaces/">JavaServer Faces
+ Technology</ulink></para>
+ <para>Core JSF: <ulink url="http://www.horstmann.com/corejsf/">Core JavaServer Faces</ulink></para>
+ <para>API: <ulink url="http://java.sun.com/javaee/javaserverfaces/1.1/docs/api/index.html">JSF
+ API</ulink></para>
+ <para>JSF Tags: <ulink url="http://www.horstmann.com/corejsf/jsf-tags.html">JSF Core
+ Tags</ulink></para>
+ <para>HTML Tags Reference: <ulink url="http://www.exadel.com/tutorial/jsf/jsftags-guide.html">JSF HTML Tags Reference</ulink></para>
+ <para>JSF Central: <ulink url="http://www.jsfcentral.com/">JSF Central - Your JavaServer Faces
+ Community</ulink></para>
+ <para>FAQ: <ulink url="http://wiki.java.net/bin/view/Projects/JavaServerFacesSpecFaq">JSF
+ FAQ</ulink></para>
+ <para>Download: <ulink url="http://java.sun.com/javaee/javaserverfaces/download.html">JavaServer
+ Faces Technology - Download</ulink></para>
+
+ <para>In summary, with this tutorial you should now know how to organize JSF sample application
+ using the wizards provided by <property moreinfo="none">JBoss Tools</property>, configure its stuff and
+ finally run it on the <property moreinfo="none">JBoss Server</property>.</para>
+
+ <para>Find out more features on JSF tooling in our <ulink url="../../jsf_tools_ref_guide/html_single/index.html">JSF Tools
+ Reference Guide</ulink>.
+ If you have questions and suggestions, please refer to
+ <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss
+ Tools Forum</ulink>.</para>
+</chapter>
+
+</book>
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/relevant_resources.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/relevant_resources.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/relevant_resources.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="relevant_resources" xreflabel="relevant_resources">
+ <?dbhtml filename="relevant_resources.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Other Relevant Resources on the topic</title>
+ <para>JSF on Sun: <ulink url="http://java.sun.com/javaee/javaserverfaces/">JavaServer Faces
+ Technology</ulink></para>
+ <para>Core JSF: <ulink url="http://www.horstmann.com/corejsf/">Core JavaServer Faces</ulink></para>
+ <para>API: <ulink url="http://java.sun.com/javaee/javaserverfaces/1.1/docs/api/index.html">JSF
+ API</ulink></para>
+ <para>JSF Tags: <ulink url="http://www.horstmann.com/corejsf/jsf-tags.html">JSF Core
+ Tags</ulink></para>
+ <para>HTML Tags Reference: <ulink url="http://www.exadel.com/tutorial/jsf/jsftags-guide.html"
+ >JSF HTML Tags Reference</ulink></para>
+ <para>JSF Central: <ulink url="http://www.jsfcentral.com/">JSF Central - Your JavaServer Faces
+ Community</ulink></para>
+ <para>FAQ: <ulink url="http://wiki.java.net/bin/view/Projects/JavaServerFacesSpecFaq">JSF
+ FAQ</ulink></para>
+ <para>Download: <ulink url="http://java.sun.com/javaee/javaserverfaces/download.html">JavaServer
+ Faces Technology - Download</ulink></para>
+
+ <para>In summary, with this tutorial you should now know how to organize JSF sample application
+ using the wizards provided by <property>JBoss Tools</property>, configure its stuff and
+ finally run it on the <property>JBoss Server</property>.</para>
+
+ <para>Find out more features on JSF tooling in our JSF Tools
+ Reference Guide. If you have questions and suggestions, please refer to <ulink
+ url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss
+ Tools Forum</ulink>.</para>
+</chapter>
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/running_application.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/running_application.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/running_application.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="running_application" xreflabel="running_application">
+ <?dbhtml filename="running_application.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Running the Application</title>
+ <para>Everything is now ready for running our application by using the JBoss engine. For
+ controlling JBoss server there is JBoss Server view:</para>
+ <figure>
+ <title>JBoss Server View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_9.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <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 the Run icon(<inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_application/jsf_application_10.png"/>
+ </imageobject>
+ </inlinemediaobject>) or right click your project folder and select <emphasis>
+ <property>Run As > Run on Server</property>
+ </emphasis>:</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>This is the equivalent of launching the browser and typing <emphasis>
+ <property>http://localhost:8080/jsfHello</property>
+ </emphasis> into your browser. Our <property>JSF application</property> should now
+ appear.</para>
+ </chapter>
\ No newline at end of file
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/start_page.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/start_page.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/en-US/start_page.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="start_page" xreflabel="start_page">
+ <?dbhtml filename="start_page.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>JSF application</keyword>
+ <keyword>Java</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Creating the Start Page</title>
+ <para>You also need to create a start page as an entry point into the application.</para>
+ <itemizedlist>
+ <listitem>
+ <para>In the Package Explorer view to the left, right-click <emphasis>
+ <property>jsfHello > WebContent</property>
+ </emphasis> and select <emphasis>
+ <property>New > JSP File</property>
+ </emphasis></para>
+ </listitem>
+ <listitem>
+ <para>For Name type in <emphasis>
+ <property>index</property>
+ </emphasis>, for Template select <emphasis>
+ <property>JSPRedirect</property>
+ </emphasis> and click <emphasis>
+ <property>Finish</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <para>A JSP editor will open up on the newly created file.</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>In the Source part of the split screen, type <emphasis>
+ <property>/pages/inputname.jsf</property>
+ </emphasis> in between the quotes for the page attribute</para>
+ </listitem>
+ </itemizedlist>
+ <para>The source coding should look like this now:</para>
+ <programlisting role="XML"><![CDATA[<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+<html>
+<head></head>
+<body>
+<jsp:forward page="/pages/inputname.jsf" />
+</body>
+</html>
+]]></programlisting>
+
+ <para>Note the <emphasis>
+ <property>.jsf</property>
+ </emphasis> extension for the file name. This is a mapping defined in the web.xml file
+ for the project for invoking <property>JavaServer Faces</property> when you run the
+ application.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Select<emphasis>
+ <property> File > Save</property>
+ </emphasis> from the menu bar</para>
+ </listitem>
+ </itemizedlist>
+ </chapter>
\ No newline at end of file
Modified: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/pom.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/pom.xml 2010-03-12 00:38:36 UTC (rev 20782)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/pom.xml 2010-03-12 00:39:49 UTC (rev 20783)
@@ -23,7 +23,7 @@
<profile>
<id>releaseJBDS</id>
<properties>
- <master>master.xml</master>
+ <master>master_output.xml</master>
<xsl-single>classpath:/xslt/com/jboss/tools/xhtml-single-release.xsl</xsl-single>
<xsl-chunked>classpath:/xslt/com/jboss/tools/xhtml-release.xsl</xsl-chunked>
<xsl-pdf>classpath:/xslt/com/jboss/tools/pdf.xsl</xsl-pdf>
@@ -86,9 +86,9 @@
<configuration>
<sourceDocumentName>${master}</sourceDocumentName>
- <sourceDirectory>${pom.basedir}/en</sourceDirectory>
+ <sourceDirectory>${pom.basedir}/en-US</sourceDirectory>
<imageResource>
- <directory>${pom.basedir}/en</directory>
+ <directory>${pom.basedir}/en-US</directory>
<includes>
<include>images/**/*</include>
</includes>
Added: branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/publican.cfg
===================================================================
--- branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/publican.cfg (rev 0)
+++ branches/jbosstools-3.1.x/jsf/docs/jsf_tools_tutorial/publican.cfg 2010-03-12 00:39:49 UTC (rev 20783)
@@ -0,0 +1,7 @@
+# Config::Simple 4.59
+# Fri Nov 20 13:19:45 2009
+
+xml_lang: en-US
+type: Book
+brand: JBoss
+
14 years, 3 months
- 1
- 0