JBoss Tools SVN: r13199 - trunk/jsf/docs/userguide/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2009-01-22 10:19:18 -0500 (Thu, 22 Jan 2009)
New Revision: 13199
Modified:
trunk/jsf/docs/userguide/en/modules/editors.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-571 - deleting the old markers;
Modified: trunk/jsf/docs/userguide/en/modules/editors.xml
===================================================================
--- trunk/jsf/docs/userguide/en/modules/editors.xml 2009-01-22 14:57:18 UTC (rev 13198)
+++ trunk/jsf/docs/userguide/en/modules/editors.xml 2009-01-22 15:19:18 UTC (rev 13199)
@@ -655,8 +655,8 @@
<para>Follow these steps to set what is available for code assist:</para>
<itemizedlist>
<listitem>
- <para>Adds code assist for JSF pre-defined objects, such as
- <![CDATA[value=]]><emphasis role="italic">
+ <para>Adds code assist for JSF pre-defined objects, such as <![CDATA[value=]]><emphasis
+ role="italic">
<property>"#{param}"</property>
</emphasis>:</para>
</listitem>
@@ -933,16 +933,15 @@
<title>Support for Taglib versions</title>
<para>VPE templates now support various versions of tag libraries. It means that the
- <property>VPE</property> takes control under those components which have
- different parameters or preview according to the framework version (like seam
- 1.2 and seam 2.0, or JSF 1.1 and JSF 1.2).</para>
+ <property>VPE</property> takes control under those components which have different parameters or
+ preview according to the framework version (like seam 1.2 and seam 2.0, or JSF
+ 1.1 and JSF 1.2).</para>
<para>For example, <emphasis>
- <property><s:decorate></property>
- </emphasis> element in seam has different parameters in versions 1.2 and 2.0 as
- well as <emphasis>
- <property><h:outputLink></property>
- </emphasis> JSF element has different preview in versions 1.1 and 1.2.</para>
+ <property><s:decorate></property></emphasis> element in seam has different
+ parameters in versions 1.2 and 2.0 as well as <emphasis>
+ <property><h:outputLink></property></emphasis> JSF
+ element has different preview in versions 1.1 and 1.2.</para>
</section>
</section>
@@ -1610,101 +1609,46 @@
<title>Graphical Web Application File (web.xml) Editor</title>
- <para>The Web Application File editor is provided for work with a deployment descriptor
- file: <emphasis>
- <property>web.xml</property>.</emphasis></para>
+ <para>The Web Application File editor comes with the same features you will find in all
+ other JBoss Developer Studio editors:</para>
-
- <para>The editor comes with the same features you will find in all other <property>JBoss
- Developer Studio</property> editors:</para>
-
<itemizedlist>
<listitem>
- <para>graphical and source edit modes: Tree view and Source view</para>
+ <para>Graphical and source edit modes</para>
</listitem>
<listitem>
- <para>validation and error checking</para>
+ <para>Validation and error checking</para>
</listitem>
</itemizedlist>
-
<section id="TreeView1">
<title>Tree View</title>
- <para>In the Tree view all elements of the <emphasis>
- <property>web.xml</property>
- </emphasis> file are organized as a list of extendable nodes on the left. You
- can configure all nodes and their properties with the help of the right-hand
- area. You can add any new elements right in the Tree
- view:</para>
-
- <figure>
- <title>Adding a New Element</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/more_editors/more_editors_11.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Let's examine the editor nodes more closely:</para>
-
- <itemizedlist>
- <listitem>
- <para>Select the <emphasis>
- <property>Context Params</property>
- </emphasis> node to see all registered in <emphasis>
- <property>web.xml</property>
- </emphasis> parameters. To create a new one, click <emphasis>
- <property>Add</property></emphasis> on the right-hand
- area or right-click the node and go to <emphasis>
- <property>New > Context Param...</property>.</emphasis></para>
- </listitem>
- </itemizedlist>
-
<figure>
- <title>Context Params</title>
+ <title>Tree View</title>
<mediaobject>
<imageobject>
- <imagedata fileref="images/more_editors/more_editors_10a.png"/>
+ <imagedata fileref="images/more_editors/more_editors_10.png"/>
</imageobject>
</mediaobject>
</figure>
-
- <para>The appeared wizard asks to set the parameter name and point to its value.</para>
-
+
+ <para>You can add any new elements right in the <property>Tree
+ viewer</property>:</para>
+
<figure>
- <title>New Context Param Wizard</title>
+ <title>Adding New Elements</title>
<mediaobject>
<imageobject>
- <imagedata fileref="images/more_editors/more_editors_10b.png"/>
+ <imagedata fileref="images/more_editors/more_editors_11.png"/>
</imageobject>
</mediaobject>
</figure>
-
- <itemizedlist>
- <listitem>
- <para>Click <emphasis>
- <property>Filters</property></emphasis> if you need to set a Filter and Filter mappings for your web application.</para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>Filters</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/more_editors/more_editors_10c.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para></para>
-
</section>
<section id="SourceView2">
<title>Source View</title>
- <para>Switch to the <property>Source view</property>to edit the web.xml file by
+ <para>Switch to the <property>Source viewer </property>to edit the web.xml file by
hand at any time:</para>
<figure>
15 years, 11 months
- 1
- 0
JBoss Tools SVN: r13198 - trunk/struts/docs/struts_tools_tutorial/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2009-01-22 09:57:18 -0500 (Thu, 22 Jan 2009)
New Revision: 13198
Modified:
trunk/struts/docs/struts_tools_tutorial/en/modules/relevant_resources.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-571 - deleting the old marker;
Modified: trunk/struts/docs/struts_tools_tutorial/en/modules/relevant_resources.xml
===================================================================
--- trunk/struts/docs/struts_tools_tutorial/en/modules/relevant_resources.xml 2009-01-22 14:53:07 UTC (rev 13197)
+++ trunk/struts/docs/struts_tools_tutorial/en/modules/relevant_resources.xml 2009-01-22 14:57:18 UTC (rev 13198)
@@ -1,35 +1,35 @@
<?xml version='1.0' encoding='UTF-8'?>
-<chapter id="relevant_resources" xreflabel="relevant_resources" role="updated">
- <?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="&strutsreflink;">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>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 <ulink url="&strutsreflink;">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>
+<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: <ulink url="&strutsreflink;">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>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 <ulink url="&strutsreflink;">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>
15 years, 11 months
- 1
- 0
JBoss Tools SVN: r13197 - trunk/seam/docs/reference/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2009-01-22 09:53:07 -0500 (Thu, 22 Jan 2009)
New Revision: 13197
Modified:
trunk/seam/docs/reference/en/modules/crud_application_walkthrough.xml
trunk/seam/docs/reference/en/modules/crud_database_application.xml
trunk/seam/docs/reference/en/modules/seam_preferences.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-571 - deleting the old markers;
Modified: trunk/seam/docs/reference/en/modules/crud_application_walkthrough.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/crud_application_walkthrough.xml 2009-01-22 14:48:35 UTC (rev 13196)
+++ trunk/seam/docs/reference/en/modules/crud_application_walkthrough.xml 2009-01-22 14:53:07 UTC (rev 13197)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="crud_application_walkthrough" xreflabel="crud_application_walkthrough" role="updated">
+<chapter id="crud_application_walkthrough" xreflabel="crud_application_walkthrough">
<?dbhtml filename="crud_application_walkthrough.html"?>
<chapterinfo>
<keywordset>
@@ -13,7 +13,7 @@
<title>The CRUD Application Walkthrough</title>
<para>After you familiarized oneself with example of creating the CRUD Database Application with
Seam, you can read this charter.</para>
- <section role="updated">
+ <section>
<title>Using CRUD Application</title>
<para>To run your CRUD Application you should do the following steps:</para>
Modified: trunk/seam/docs/reference/en/modules/crud_database_application.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/crud_database_application.xml 2009-01-22 14:48:35 UTC (rev 13196)
+++ trunk/seam/docs/reference/en/modules/crud_database_application.xml 2009-01-22 14:53:07 UTC (rev 13197)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="crud_database_application" xreflabel="crud_database_application" role="updated">
+<chapter id="crud_database_application" xreflabel="crud_database_application">
<?dbhtml filename="crud_database_application.html"?>
<chapterinfo>
<keywordset>
@@ -31,7 +31,7 @@
<property>CRUD</property> support. </para>
</section>
- <section role="updated">
+ <section>
<title>How to create the CRUD Database Application with Seam</title>
<itemizedlist>
Modified: trunk/seam/docs/reference/en/modules/seam_preferences.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/seam_preferences.xml 2009-01-22 14:48:35 UTC (rev 13196)
+++ trunk/seam/docs/reference/en/modules/seam_preferences.xml 2009-01-22 14:53:07 UTC (rev 13197)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="seam_preferences" xreflabel="seam_preferences" role="updated">
+<chapter id="seam_preferences" xreflabel="seam_preferences">
<!-- mark as new -->
<?dbhtml filename="seam_preferences.html"?>
<chapterinfo>
@@ -111,7 +111,7 @@
</section>
</section>
- <section id="project_pref" role="updated">
+ <section id="project_pref">
<title>Project Preferences</title>
<para>Once Seam project is created you can modify its settings. Right click on Seam project
15 years, 11 months
- 1
- 0
JBoss Tools SVN: r13196 - trunk/portlet/docs/reference/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2009-01-22 09:48:35 -0500 (Thu, 22 Jan 2009)
New Revision: 13196
Modified:
trunk/portlet/docs/reference/en/modules/jsf_portlet.xml
trunk/portlet/docs/reference/en/modules/portlets_to_nonWTP_projects.xml
trunk/portlet/docs/reference/en/modules/seam_portlet.xml
trunk/portlet/docs/reference/en/modules/starting_project.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-571 - deleting the old markers;
Modified: trunk/portlet/docs/reference/en/modules/jsf_portlet.xml
===================================================================
--- trunk/portlet/docs/reference/en/modules/jsf_portlet.xml 2009-01-22 14:39:01 UTC (rev 13195)
+++ trunk/portlet/docs/reference/en/modules/jsf_portlet.xml 2009-01-22 14:48:35 UTC (rev 13196)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="jsf_portlet" xreflabel="jsf_portlet" role="new">
+<chapter id="jsf_portlet" xreflabel="jsf_portlet">
<?dbhtml filename="jsf_portlet.html"?>
<title>Creating JSF Portlet</title>
Modified: trunk/portlet/docs/reference/en/modules/portlets_to_nonWTP_projects.xml
===================================================================
--- trunk/portlet/docs/reference/en/modules/portlets_to_nonWTP_projects.xml 2009-01-22 14:39:01 UTC (rev 13195)
+++ trunk/portlet/docs/reference/en/modules/portlets_to_nonWTP_projects.xml 2009-01-22 14:48:35 UTC (rev 13196)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="portlets_to_nonWTP_projects" xreflabel="portlets_to_nonWTP_projects" role="new">
+<chapter id="portlets_to_nonWTP_projects" xreflabel="portlets_to_nonWTP_projects">
<?dbhtml filename="portlets_to_nonWTP_projects.html"?>
<title>Adding Portlets to non-WTP Projects</title>
Modified: trunk/portlet/docs/reference/en/modules/seam_portlet.xml
===================================================================
--- trunk/portlet/docs/reference/en/modules/seam_portlet.xml 2009-01-22 14:39:01 UTC (rev 13195)
+++ trunk/portlet/docs/reference/en/modules/seam_portlet.xml 2009-01-22 14:48:35 UTC (rev 13196)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="seam_portlet" xreflabel="seam_portlet" role="new">
+<chapter id="seam_portlet" xreflabel="seam_portlet">
<?dbhtml filename="seam_portlet.html"?>
<title>Creating Seam Portlet</title>
Modified: trunk/portlet/docs/reference/en/modules/starting_project.xml
===================================================================
--- trunk/portlet/docs/reference/en/modules/starting_project.xml 2009-01-22 14:39:01 UTC (rev 13195)
+++ trunk/portlet/docs/reference/en/modules/starting_project.xml 2009-01-22 14:48:35 UTC (rev 13196)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="starting_project" xreflabel="starting_project" role="updated">
+<chapter id="starting_project" xreflabel="starting_project">
<?dbhtml filename="starting_project.html"?>
<title>Starting the Project with JBoss Portal</title>
15 years, 11 months
- 1
- 0
JBoss Tools SVN: r13195 - trunk/jsf/docs/userguide/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2009-01-22 09:39:01 -0500 (Thu, 22 Jan 2009)
New Revision: 13195
Modified:
trunk/jsf/docs/userguide/en/modules/editors.xml
trunk/jsf/docs/userguide/en/modules/preferences.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-571 - deleting the old markers;
Modified: trunk/jsf/docs/userguide/en/modules/editors.xml
===================================================================
--- trunk/jsf/docs/userguide/en/modules/editors.xml 2009-01-22 14:35:38 UTC (rev 13194)
+++ trunk/jsf/docs/userguide/en/modules/editors.xml 2009-01-22 14:39:01 UTC (rev 13195)
@@ -35,7 +35,7 @@
within your application and make use of content and code assist no matter what project
file (jsp, xhtml, xml, css, etc...) you are working on.</para>
- <section id="OpenOnSelection4Hyperlinknavigation" role="updated">
+ <section id="OpenOnSelection4Hyperlinknavigation">
<title>OpenOn</title>
@@ -181,7 +181,7 @@
</section>
</section>
- <section id="CodeAssistAndDynamicCodeAssist42BasedOnProjectData" role="updated">
+ <section id="CodeAssistAndDynamicCodeAssist42BasedOnProjectData">
<title>Content Assist</title>
<para><property>Content assist</property> is available when working with</para>
@@ -655,8 +655,8 @@
<para>Follow these steps to set what is available for code assist:</para>
<itemizedlist>
<listitem>
- <para>Adds code assist for JSF pre-defined objects, such as <![CDATA[value=]]><emphasis
- role="italic">
+ <para>Adds code assist for JSF pre-defined objects, such as
+ <![CDATA[value=]]><emphasis role="italic">
<property>"#{param}"</property>
</emphasis>:</para>
</listitem>
@@ -933,15 +933,16 @@
<title>Support for Taglib versions</title>
<para>VPE templates now support various versions of tag libraries. It means that the
- <property>VPE</property> takes control under those components which have different parameters or
- preview according to the framework version (like seam 1.2 and seam 2.0, or JSF
- 1.1 and JSF 1.2).</para>
+ <property>VPE</property> takes control under those components which have
+ different parameters or preview according to the framework version (like seam
+ 1.2 and seam 2.0, or JSF 1.1 and JSF 1.2).</para>
<para>For example, <emphasis>
- <property><s:decorate></property></emphasis> element in seam has different
- parameters in versions 1.2 and 2.0 as well as <emphasis>
- <property><h:outputLink></property></emphasis> JSF
- element has different preview in versions 1.1 and 1.2.</para>
+ <property><s:decorate></property>
+ </emphasis> element in seam has different parameters in versions 1.2 and 2.0 as
+ well as <emphasis>
+ <property><h:outputLink></property>
+ </emphasis> JSF element has different preview in versions 1.1 and 1.2.</para>
</section>
</section>
@@ -1609,46 +1610,101 @@
<title>Graphical Web Application File (web.xml) Editor</title>
- <para>The Web Application File editor comes with the same features you will find in all
- other JBoss Developer Studio editors:</para>
+ <para>The Web Application File editor is provided for work with a deployment descriptor
+ file: <emphasis>
+ <property>web.xml</property>.</emphasis></para>
+
+ <para>The editor comes with the same features you will find in all other <property>JBoss
+ Developer Studio</property> editors:</para>
+
<itemizedlist>
<listitem>
- <para>Graphical and source edit modes</para>
+ <para>graphical and source edit modes: Tree view and Source view</para>
</listitem>
<listitem>
- <para>Validation and error checking</para>
+ <para>validation and error checking</para>
</listitem>
</itemizedlist>
+
<section id="TreeView1">
<title>Tree View</title>
+ <para>In the Tree view all elements of the <emphasis>
+ <property>web.xml</property>
+ </emphasis> file are organized as a list of extendable nodes on the left. You
+ can configure all nodes and their properties with the help of the right-hand
+ area. You can add any new elements right in the Tree
+ view:</para>
+
+ <figure>
+ <title>Adding a New Element</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/more_editors/more_editors_11.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Let's examine the editor nodes more closely:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Select the <emphasis>
+ <property>Context Params</property>
+ </emphasis> node to see all registered in <emphasis>
+ <property>web.xml</property>
+ </emphasis> parameters. To create a new one, click <emphasis>
+ <property>Add</property></emphasis> on the right-hand
+ area or right-click the node and go to <emphasis>
+ <property>New > Context Param...</property>.</emphasis></para>
+ </listitem>
+ </itemizedlist>
+
<figure>
- <title>Tree View</title>
+ <title>Context Params</title>
<mediaobject>
<imageobject>
- <imagedata fileref="images/more_editors/more_editors_10.png"/>
+ <imagedata fileref="images/more_editors/more_editors_10a.png"/>
</imageobject>
</mediaobject>
</figure>
-
- <para>You can add any new elements right in the <property>Tree
- viewer</property>:</para>
-
+
+ <para>The appeared wizard asks to set the parameter name and point to its value.</para>
+
<figure>
- <title>Adding New Elements</title>
+ <title>New Context Param Wizard</title>
<mediaobject>
<imageobject>
- <imagedata fileref="images/more_editors/more_editors_11.png"/>
+ <imagedata fileref="images/more_editors/more_editors_10b.png"/>
</imageobject>
</mediaobject>
</figure>
+
+ <itemizedlist>
+ <listitem>
+ <para>Click <emphasis>
+ <property>Filters</property></emphasis> if you need to set a Filter and Filter mappings for your web application.</para>
+ </listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Filters</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/more_editors/more_editors_10c.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para></para>
+
</section>
<section id="SourceView2">
<title>Source View</title>
- <para>Switch to the <property>Source viewer </property>to edit the web.xml file by
+ <para>Switch to the <property>Source view</property>to edit the web.xml file by
hand at any time:</para>
<figure>
Modified: trunk/jsf/docs/userguide/en/modules/preferences.xml
===================================================================
--- trunk/jsf/docs/userguide/en/modules/preferences.xml 2009-01-22 14:35:38 UTC (rev 13194)
+++ trunk/jsf/docs/userguide/en/modules/preferences.xml 2009-01-22 14:39:01 UTC (rev 13195)
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding='UTF-8'?>
-<chapter id="preferences" xreflabel="preferences" role="updated">
+<chapter id="preferences" xreflabel="preferences">
<?dbhtml filename="preferences.html"?>
<title>JBoss Tools Preferences</title>
@@ -344,7 +344,7 @@
</section>
- <section id="VisualPageEditor2" role="updated">
+ <section id="VisualPageEditor2">
<?dbhtml filename="VisualPageEditor.html"?>
<title>Visual Page Editor</title>
<para><emphasis>
@@ -459,7 +459,7 @@
dialog</link> where you can adjust new settings.</para>
</section>
- <section id="el_variables" role="updated">
+ <section id="el_variables">
<?dbhtml filename="el_variables.html"?>
<title>El Variables</title>
<para>To specify necessary EL variables globally, i. e. for all projects and resources in
@@ -978,7 +978,7 @@
</section>
- <section id="JBossServerPreferences" role="updated">
+ <section id="JBossServerPreferences">
<?dbhtml filename="View.html"?>
<title>Server Preferences</title>
<para>Preferences for <property>JBoss Server</property> and other servers can be changed on
@@ -1036,7 +1036,7 @@
</figure>
</section>
- <section id="XDoclet" role="updated">
+ <section id="XDoclet">
<?dbhtml filename="XDoclet.html"?>
<title>XDoclet</title>
<para>The preferences for XDoclet can be changed if you click <emphasis>
15 years, 11 months
- 1
- 0
JBoss Tools SVN: r13194 - trunk/jsf/docs/jsf_tools_tutorial/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2009-01-22 09:35:38 -0500 (Thu, 22 Jan 2009)
New Revision: 13194
Modified:
trunk/jsf/docs/jsf_tools_tutorial/en/modules/relevant_resources.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-571 - deleting the old marker;
Modified: trunk/jsf/docs/jsf_tools_tutorial/en/modules/relevant_resources.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_tutorial/en/modules/relevant_resources.xml 2009-01-22 14:34:31 UTC (rev 13193)
+++ trunk/jsf/docs/jsf_tools_tutorial/en/modules/relevant_resources.xml 2009-01-22 14:35:38 UTC (rev 13194)
@@ -1,37 +1,37 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="relevant_resources" xreflabel="relevant_resources" role="updated">
- <?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 <ulink url="&jsfreflink;">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>
+<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 <ulink url="&jsfreflink;">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>
15 years, 11 months
- 1
- 0
JBoss Tools SVN: r13193 - trunk/jsf/docs/jsf_tools_ref_guide/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2009-01-22 09:34:31 -0500 (Thu, 22 Jan 2009)
New Revision: 13193
Modified:
trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_project_verification.xml
trunk/jsf/docs/jsf_tools_ref_guide/en/modules/managed_beans.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-571 - deleting the old markers;
Modified: trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_project_verification.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_project_verification.xml 2009-01-22 14:32:07 UTC (rev 13192)
+++ trunk/jsf/docs/jsf_tools_ref_guide/en/modules/jsf_project_verification.xml 2009-01-22 14:34:31 UTC (rev 13193)
@@ -1,107 +1,107 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="jsf_project_verification" role="updated">
- <?dbhtml filename="struts_project_verification.html"?>
-
- <chapterinfo>
- <keywordset>
- <keyword>JBoss Developer Studio</keyword>
- <keyword>Eclipse</keyword>
- <keyword>JSF Tools</keyword>
- <keyword>Java</keyword>
- <keyword>JBoss</keyword>
- </keywordset>
- </chapterinfo>
-
- <title>JSF Project Verification</title>
-
- <para>In this chapter we'll discuss a possible verification that you can take advantage
- of.</para>
- <!-- JBoss Developer Studio checks for many different rules for a JSF project -->
- <para>Many different rules are checked for a JSF project that can be configured by selecting <emphasis>
- <property>Window > Preferences</property>
- </emphasis> from the menu bar, selecting <emphasis>
- <property>JBoss Tools > Web > Verification</property>
- </emphasis> from the Preferences dialog box and then expanding the JSF Rules node.</para>
- <figure>
- <title>JSF Rules</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/verif_valid/verif_valid_1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Suppose you are working in the Source viewer for a JSF configuration file as shown below:</para>
- <figure>
- <title>Faces-config.xml File</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/verif_valid/verif_valid_2.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>While typing a class name, you might make a minor typo (like <emphasis role="italic">
- <property>"jsfHello.PersonBean9"</property>
- </emphasis> instead of <emphasis role="italic">
- <property>"jsfHello.PersonBean"</property>
- </emphasis>). After saving the file, verification checks to make sure everything is correct
- and finds the error below:</para>
- <figure>
- <title>Error in Source View</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/verif_valid/verif_valid_3.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 an error message and get a detailed error
- message:</para>
- <figure>
- <title>Error Message</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/verif_valid/verif_valid_4.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Verification also checks navigation rules:</para>
- <figure>
- <title>Checking Navigation Rules</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/verif_valid/verif_valid_5.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>If you provide a page name that does not exist, verification will let you know about that:</para>
- <figure>
- <title>Page Name Verification</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/verif_valid/verif_valid_6.png" scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>You can always call up verification explicitly by right-clicking any element in the tree
- and selecting Verify from the context menu. This works from both the Tree and Diagram
- viewers for the JSF configuration file editor. You can also invoke verification from the Web
- Projects view. Below we are checking all of the elements in the configuration file.</para>
- <figure>
- <title>Verify Command</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/verif_valid/verif_valid_7.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>In summary, this document highlights all the JSF-specific features of <property>JBoss Tools</property>
- meant for enhancing the development of rich Web applications based on JSF technology. The
- reference introduces you to wizards for creating and importing JSF projects, JSF
- Configuration File editor features, functionality for enabling JSF capabilities and etc.</para>
-
- <para>If you have questions or good suggestions, please refer to <ulink
- url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss
- Tools Forum</ulink>.</para>
-</chapter>
+<chapter id="jsf_project_verification">
+ <?dbhtml filename="struts_project_verification.html"?>
+
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>JSF Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>JSF Project Verification</title>
+
+ <para>In this chapter we'll discuss a possible verification that you can take advantage
+ of.</para>
+ <!-- JBoss Developer Studio checks for many different rules for a JSF project -->
+ <para>Many different rules are checked for a JSF project that can be configured by selecting <emphasis>
+ <property>Window > Preferences</property>
+ </emphasis> from the menu bar, selecting <emphasis>
+ <property>JBoss Tools > Web > Verification</property>
+ </emphasis> from the Preferences dialog box and then expanding the JSF Rules node.</para>
+ <figure>
+ <title>JSF Rules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Suppose you are working in the Source viewer for a JSF configuration file as shown below:</para>
+ <figure>
+ <title>Faces-config.xml File</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>While typing a class name, you might make a minor typo (like <emphasis role="italic">
+ <property>"jsfHello.PersonBean9"</property>
+ </emphasis> instead of <emphasis role="italic">
+ <property>"jsfHello.PersonBean"</property>
+ </emphasis>). After saving the file, verification checks to make sure everything is correct
+ and finds the error below:</para>
+ <figure>
+ <title>Error in Source View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_3.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 an error message and get a detailed error
+ message:</para>
+ <figure>
+ <title>Error Message</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Verification also checks navigation rules:</para>
+ <figure>
+ <title>Checking Navigation Rules</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>If you provide a page name that does not exist, verification will let you know about that:</para>
+ <figure>
+ <title>Page Name Verification</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_6.png" scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>You can always call up verification explicitly by right-clicking any element in the tree
+ and selecting Verify from the context menu. This works from both the Tree and Diagram
+ viewers for the JSF configuration file editor. You can also invoke verification from the Web
+ Projects view. Below we are checking all of the elements in the configuration file.</para>
+ <figure>
+ <title>Verify Command</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/verif_valid/verif_valid_7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>In summary, this document highlights all the JSF-specific features of <property>JBoss Tools</property>
+ meant for enhancing the development of rich Web applications based on JSF technology. The
+ reference introduces you to wizards for creating and importing JSF projects, JSF
+ Configuration File editor features, functionality for enabling JSF capabilities and etc.</para>
+
+ <para>If you have questions or good suggestions, please refer to <ulink
+ url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss
+ Tools Forum</ulink>.</para>
+</chapter>
Modified: trunk/jsf/docs/jsf_tools_ref_guide/en/modules/managed_beans.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_ref_guide/en/modules/managed_beans.xml 2009-01-22 14:32:07 UTC (rev 13192)
+++ trunk/jsf/docs/jsf_tools_ref_guide/en/modules/managed_beans.xml 2009-01-22 14:34:31 UTC (rev 13193)
@@ -1,208 +1,208 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="managed_beans" role="updated">
- <?dbhtml filename="managed_beans.html"?>
- <chapterinfo>
- <keywordset>
- <keyword>JBoss Developer Studio</keyword>
- <keyword>Eclipse</keyword>
- <keyword>JSF Tools</keyword>
- <keyword>Java</keyword>
- <keyword>JBoss</keyword>
- </keywordset>
- </chapterinfo>
-
- <title>Managed Beans</title>
-
- <para>There is lots of power to work with <property>managed beans</property>.</para>
- <itemizedlist>
- <listitem>
- <para>Add and generate code for new managed beans</para>
- <itemizedlist>
- <listitem>
- <para>Generate code for attributes and getter/setter methods</para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>Add existing managed beans to JSF configuration file</para>
- </listitem>
- </itemizedlist>
-
- <para>Thus, in this section we will guides you through all this possibilities.</para>
-
- <section id="CodeGenerationForManagedBeans421" role="updated">
-
- <title>Code Generation for Managed Beans</title>
-
- <para>To start, create a new managed bean in JSF configuration file editor, in the Tree
- view.</para>
- <figure>
- <title>Creation of New Managed Bean</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_support/jsf_support_34.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <note>
- <title>Note:</title>
- <para>When you define a new managed bean, make sure that <emphasis>
- <property>Generate Source Code</property>
- </emphasis> is checked as shown in the figure below.</para>
- </note>
- <figure>
- <title>New Managed Bean</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_support/jsf_support_35.png" scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>After the <emphasis role="italic">
- <property>"Java"</property>
- </emphasis> class has been generated you can open it for additional editing. There are
- two ways to open the <emphasis role="italic">
- <property>"Java"</property>
- </emphasis> class:</para>
-
- <itemizedlist>
- <listitem>
- <para>click on <emphasis>
- <property>Managed-Bean-Class</property>
- </emphasis> link in the editor</para>
- </listitem>
- </itemizedlist>
- <para>or</para>
- <itemizedlist>
- <listitem>
- <para>right click the <emphasis>
- <property>managed bean</property>
- </emphasis> and select <emphasis>
- <property>Open Source</property>
- </emphasis></para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>Opening of Created Managed Bean</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_support/jsf_support_36.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The generated Java source should look as follows:</para>
-
- <figure>
- <title>Java Source Code</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_support/jsf_support_37.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>You can also generate source code for properties, also includes <emphasis
- role="italic">
- <property>"getter"</property>
- </emphasis> and <emphasis role="italic">
- <property>"setter"</property>
- </emphasis> methods. Right click on the bean and select <emphasis>
- <property>New > Property</property>
- </emphasis>. You will see <property>Add Property</property> dialog.</para>
- <figure>
- <title>Generation of Source Code for Properties</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_support/jsf_support_38.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>When the form is open make sure that all the check boxes are selected:</para>
- <itemizedlist>
- <listitem>
- <para>Add Java property</para>
- </listitem>
- <listitem>
- <para>Generate Getter</para>
- </listitem>
- <listitem>
- <para>Generate Setter</para>
- </listitem>
- </itemizedlist>
- <para/>
- <figure>
- <title>"Add Property" Form</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_support/jsf_support_39.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Once the generation is complete, you can open the file and see the added property with
- <emphasis role="italic">
- <property>"get"</property>
- </emphasis> and <emphasis role="italic">
- <property>"set"</property>
- </emphasis> methods:</para>
- <figure>
- <title>Generated Java Source Code for Property</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_support/jsf_support_40.png" scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Thus, we've discussed everything which comes to creating a new Managed Bean.
- The next section will show you how to add an existing Bean into a JSF configuration
- file.</para>
- </section>
- <section id="AddExistingJavaBeansToAJSFConfigurationFile74332" role="updated">
-
- <title>Add Existing Java Beans to a JSF Configuration File</title>
- <para>If you already have a Java bean you can easily add it to a <property>JSF configuration
- file</property>.</para>
- <para>You should start the same way you create a new managed bean. Use the <emphasis>
- <property>Browse...</property>
- </emphasis> button to add your existing Java class.</para>
- <figure>
- <title>New Managed Bean Form</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_support/jsf_support_42.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Once the class is set, its <emphasis>
- <property>Name</property>
- </emphasis> will be set as well. But you can easily substitute it for the other one.
- Notice that <emphasis>
- <property>Generate Source Code</property>
- </emphasis> option is not available as the <emphasis role="italic">
- <property>"Java"</property>
- </emphasis> class already exists. </para>
- <para>After adding your class <emphasis>
- <property>Next</property>
- </emphasis> button will be activated. Pressing it you'll get <emphasis>
- <property>Managed Properties</property>
- </emphasis> dialog where all corresponding properties are displayed. Check the necessary
- ones to add them into your <property>JSF Configuration File</property>.</para>
-
- <figure>
- <title>Selection of Bean's Properties.</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_support/jsf_support_43.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>If you don't want to add any, just click <emphasis>
- <property>Finish</property>. </emphasis></para>
- <para>Above-listed steps have demonstrated how you can specify an existing Bean in the JSF
- configuration file, i.e. <emphasis>
- <property>faces-config.xml</property>. </emphasis> In the next chapter
- you'll know how to organize and register another kind of artifacts.</para>
- </section>
-</chapter>
+<chapter id="managed_beans">
+ <?dbhtml filename="managed_beans.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>JSF Tools</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Managed Beans</title>
+
+ <para>There is lots of power to work with <property>managed beans</property>.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Add and generate code for new managed beans</para>
+ <itemizedlist>
+ <listitem>
+ <para>Generate code for attributes and getter/setter methods</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>Add existing managed beans to JSF configuration file</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>Thus, in this section we will guides you through all this possibilities.</para>
+
+ <section id="CodeGenerationForManagedBeans421">
+
+ <title>Code Generation for Managed Beans</title>
+
+ <para>To start, create a new managed bean in JSF configuration file editor, in the Tree
+ view.</para>
+ <figure>
+ <title>Creation of New Managed Bean</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_support/jsf_support_34.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <note>
+ <title>Note:</title>
+ <para>When you define a new managed bean, make sure that <emphasis>
+ <property>Generate Source Code</property>
+ </emphasis> is checked as shown in the figure below.</para>
+ </note>
+ <figure>
+ <title>New Managed Bean</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_support/jsf_support_35.png" scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>After the <emphasis role="italic">
+ <property>"Java"</property>
+ </emphasis> class has been generated you can open it for additional editing. There are
+ two ways to open the <emphasis role="italic">
+ <property>"Java"</property>
+ </emphasis> class:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>click on <emphasis>
+ <property>Managed-Bean-Class</property>
+ </emphasis> link in the editor</para>
+ </listitem>
+ </itemizedlist>
+ <para>or</para>
+ <itemizedlist>
+ <listitem>
+ <para>right click the <emphasis>
+ <property>managed bean</property>
+ </emphasis> and select <emphasis>
+ <property>Open Source</property>
+ </emphasis></para>
+ </listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Opening of Created Managed Bean</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_support/jsf_support_36.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The generated Java source should look as follows:</para>
+
+ <figure>
+ <title>Java Source Code</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_support/jsf_support_37.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You can also generate source code for properties, also includes <emphasis
+ role="italic">
+ <property>"getter"</property>
+ </emphasis> and <emphasis role="italic">
+ <property>"setter"</property>
+ </emphasis> methods. Right click on the bean and select <emphasis>
+ <property>New > Property</property>
+ </emphasis>. You will see <property>Add Property</property> dialog.</para>
+ <figure>
+ <title>Generation of Source Code for Properties</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_support/jsf_support_38.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>When the form is open make sure that all the check boxes are selected:</para>
+ <itemizedlist>
+ <listitem>
+ <para>Add Java property</para>
+ </listitem>
+ <listitem>
+ <para>Generate Getter</para>
+ </listitem>
+ <listitem>
+ <para>Generate Setter</para>
+ </listitem>
+ </itemizedlist>
+ <para/>
+ <figure>
+ <title>"Add Property" Form</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_support/jsf_support_39.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Once the generation is complete, you can open the file and see the added property with
+ <emphasis role="italic">
+ <property>"get"</property>
+ </emphasis> and <emphasis role="italic">
+ <property>"set"</property>
+ </emphasis> methods:</para>
+ <figure>
+ <title>Generated Java Source Code for Property</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_support/jsf_support_40.png" scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Thus, we've discussed everything which comes to creating a new Managed Bean.
+ The next section will show you how to add an existing Bean into a JSF configuration
+ file.</para>
+ </section>
+ <section id="AddExistingJavaBeansToAJSFConfigurationFile74332">
+
+ <title>Add Existing Java Beans to a JSF Configuration File</title>
+ <para>If you already have a Java bean you can easily add it to a <property>JSF configuration
+ file</property>.</para>
+ <para>You should start the same way you create a new managed bean. Use the <emphasis>
+ <property>Browse...</property>
+ </emphasis> button to add your existing Java class.</para>
+ <figure>
+ <title>New Managed Bean Form</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_support/jsf_support_42.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Once the class is set, its <emphasis>
+ <property>Name</property>
+ </emphasis> will be set as well. But you can easily substitute it for the other one.
+ Notice that <emphasis>
+ <property>Generate Source Code</property>
+ </emphasis> option is not available as the <emphasis role="italic">
+ <property>"Java"</property>
+ </emphasis> class already exists. </para>
+ <para>After adding your class <emphasis>
+ <property>Next</property>
+ </emphasis> button will be activated. Pressing it you'll get <emphasis>
+ <property>Managed Properties</property>
+ </emphasis> dialog where all corresponding properties are displayed. Check the necessary
+ ones to add them into your <property>JSF Configuration File</property>.</para>
+
+ <figure>
+ <title>Selection of Bean's Properties.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_support/jsf_support_43.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>If you don't want to add any, just click <emphasis>
+ <property>Finish</property>. </emphasis></para>
+ <para>Above-listed steps have demonstrated how you can specify an existing Bean in the JSF
+ configuration file, i.e. <emphasis>
+ <property>faces-config.xml</property>. </emphasis> In the next chapter
+ you'll know how to organize and register another kind of artifacts.</para>
+ </section>
+</chapter>
15 years, 11 months
- 1
- 0
JBoss Tools SVN: r13192 - trunk/jbpm/docs/reference/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2009-01-22 09:32:07 -0500 (Thu, 22 Jan 2009)
New Revision: 13192
Modified:
trunk/jbpm/docs/reference/en/modules/the_views.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-571 - deleting the old markers;
Modified: trunk/jbpm/docs/reference/en/modules/the_views.xml
===================================================================
--- trunk/jbpm/docs/reference/en/modules/the_views.xml 2009-01-22 14:30:47 UTC (rev 13191)
+++ trunk/jbpm/docs/reference/en/modules/the_views.xml 2009-01-22 14:32:07 UTC (rev 13192)
@@ -1,230 +1,230 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="the_views" xreflabel="the_views" role="updated">
- <?dbhtml filename="the_views.html"?>
- <chapterinfo>
- <keywordset>
- <keyword>jBPM</keyword>
- </keywordset>
- </chapterinfo>
-
- <title>The views</title>
-
- <para>Here, it will be explained how to work with views and editors provided by JBDS.</para>
- <para>The views are used for representation and navigation the resources you are working on at
- the moment. One of the advantages of all the views is that all modifications made in the
- currant-active file are immediately displayed in them. Let’s get acquainted more closely
- with those that the <property>jPDL perspective</property> provides. </para>
-
- <figure>
- <title>The jPDL Perspective Views and Editors</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/the_views/the_views_0.png" scale="80"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>As you can see in the picture above, the <property>jPDL perspective</property> contains a
- complete set of functionality that's necessary for working on the jBPM project.</para>
-
- <section id="the_outline_view">
- <?dbhtml filename="the_outline_view.html"?>
- <title>The Outline View</title>
- <para>To have a way to quickly see an outline of the process use the <emphasis>
- <property>Outline view</property>
- </emphasis> that is presented as the classical tree. If it is not visible select <emphasis>
- <property>Window > Show view > Outline</property>. </emphasis></para>
-
- <figure>
- <title>The Overview View</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/the_views/the_views_1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- <section id="the_overview">
- <?dbhtml filename="the_outline_view.html"?>
- <title>The Overview</title>
- <para>The main advantage of this view is that it gives visual representation of the whole
- currant-developing process. Besides, the <emphasis>
- <property>Overview</property>
- </emphasis> comes as a scrollable thumbnail which enables a better navigation of the
- process structure if it's too large.</para>
-
- <figure>
- <title>The Overview</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/the_views/the_views_2.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- <section id="the_properties_view" role="updated">
- <?dbhtml filename="the_properties_view.html"?>
- <title>The Properties View</title>
- <para> Here, we dwell on the JBDS <property>Properties view</property>.</para>
- <para>Notice if it's not visible you can access it by navigating <emphasis>
- <property>Window > Show view > Properties</property>. </emphasis></para>
- <para>The view shows the relevant properties of the selected item in the tabbed form. Every
- item has its own set of properties, which can be directly editable in the Properties
- view or by brining up the context menu.</para>
-
- <figure>
- <title>The Properties View of selected Transition</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/the_views/the_views_3.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>For example, on the picture above the Properties view displays all the properties for
- a selected transition. Its name has been changed to <emphasis>
- <property>to_auction</property>. </emphasis> We've done it directly in
- active General tab of the view. The same way let's change the name for the
- second transition to <emphasis>
- <property>to_end</property>. </emphasis></para>
- <para>If no one item is selected, the view represents the properties of the whole process
- definition. </para>
-
- <figure>
- <title>The Properties View of Process Definition</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/the_views/the_views_4.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>In this case, it contains six tabs. The first one is the <emphasis>
- <property>General</property>.</emphasis> It allows to specify a process name and add
- necessary description. To illustrate let's change the process definition name
- to <emphasis>
- <property>jbay</property>. </emphasis></para>
- </section>
-
- <section id="jbpm_gpd_editor" role="updated">
- <?dbhtml filename="direct_editing.html"?>
- <title>The jBPM Graphical Process Designer editor.</title>
- <para>The <property>jBPM GPD editor</property> includes four modes: Diagram, Deployment,
- Design and Source, which are available as switchable tabs at the bottom of the editor.
- Let's dwell on each of them.</para>
-
- <section id="the_diagram_mode">
- <title>The Diagram mode</title>
- <para> In this mode we define the process in the form of a diagram by means of tools
- provided on the left-hand side of the jBPM GPD. </para>
-
- <figure>
- <title>The Diagram mode</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/the_views/the_views_5.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Besides, some properties can be directly edited in the <property>Diagram
- mode</property> of the graphical editor. One example of this is the <emphasis>
- <property>name</property>
- </emphasis> property of nodes. You can edit this directly by selecting the node of
- which you want to change the name and then click once inside this node. This enables
- an editor in the node. We change the name of the node to <emphasis>
- <property>auction</property>. </emphasis></para>
- </section>
-
- <section id="source_mode">
- <?dbhtml filename="the_source_view.html"?>
- <title>The Source Mode</title>
- <para>Now, that we have defined a simple process definition, we can have a look at the
- XML that is being generated under the covers. To see this XML click on the Source
- tab of the graphical process designer editor.</para>
-
- <figure>
- <title>The Source Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/the_views/the_views_6.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>The <property>Source mode</property> enables to easily manipulate our XML. That is
- manually inserting and editing necessary elements or attributes. In addition, here
- you can take advantage of content assist.</para>
- </section>
-
- <section id="design_mode">
- <?dbhtml filename="the_design_view.html"?>
- <title>The Design Mode</title>
- <para>One more way to edit your file is to use <property>Design mode</property>. You can
- see it in the next picture:</para>
- <figure>
- <title>The Design Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/the_views/the_views_7.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>As you can see above, this mode looks like a table in the first column of which
- the process structure is performed. Here, you can also insert, remove and edit
- elements or attributes, moreover add comments and instructions. Their values can be
- directly edited in the second column of the Design mode table.</para>
- <para>For instance, let’s add a comment on the second transition. For that, you should
- bring up the context menu for it and choose <emphasis>
- <property>Add Before > Comment</property>. </emphasis></para>
-
- <figure>
- <title>Adding a Comment</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/the_views/the_views_8.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Then, we can put the text <emphasis>This transition leads to the end
- state</emphasis> in the right column as its value.</para>
-
- <figure>
- <title>Comment is added</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/the_views/the_views_9.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- </section>
-
- <section id="deployment_mode">
- <?dbhtml filename="the_deployment_view.html"?>
- <title>The Deployment Mode</title>
- <para>Finally, to adjust the deployment settings of the project you should switch on to
- the tab that opens the <property>Deployment mode</property>. On the picture below
- the <property>Deployment mode</property> is performed with default settings. Here,
- you can easily modify them or, if the settings won't match your needs, to
- reset defaults. </para>
- <figure>
- <title>The Deployment Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/the_views/the_views_10.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The button <emphasis>
- <property>Test Connections</property>
- </emphasis> is necessary to make sure whether all your settings are valid before
- deploying the process.</para>
- <para>Now that we've seen how to work with <property>jPDL
- perspective</property>, let's pass on to the project testing.</para>
- </section>
- </section>
-</chapter>
+<chapter id="the_views" xreflabel="the_views">
+ <?dbhtml filename="the_views.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>The views</title>
+
+ <para>Here, it will be explained how to work with views and editors provided by JBDS.</para>
+ <para>The views are used for representation and navigation the resources you are working on at
+ the moment. One of the advantages of all the views is that all modifications made in the
+ currant-active file are immediately displayed in them. Let’s get acquainted more closely
+ with those that the <property>jPDL perspective</property> provides. </para>
+
+ <figure>
+ <title>The jPDL Perspective Views and Editors</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_0.png" scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>As you can see in the picture above, the <property>jPDL perspective</property> contains a
+ complete set of functionality that's necessary for working on the jBPM project.</para>
+
+ <section id="the_outline_view">
+ <?dbhtml filename="the_outline_view.html"?>
+ <title>The Outline View</title>
+ <para>To have a way to quickly see an outline of the process use the <emphasis>
+ <property>Outline view</property>
+ </emphasis> that is presented as the classical tree. If it is not visible select <emphasis>
+ <property>Window > Show view > Outline</property>. </emphasis></para>
+
+ <figure>
+ <title>The Overview View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section id="the_overview">
+ <?dbhtml filename="the_outline_view.html"?>
+ <title>The Overview</title>
+ <para>The main advantage of this view is that it gives visual representation of the whole
+ currant-developing process. Besides, the <emphasis>
+ <property>Overview</property>
+ </emphasis> comes as a scrollable thumbnail which enables a better navigation of the
+ process structure if it's too large.</para>
+
+ <figure>
+ <title>The Overview</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section id="the_properties_view">
+ <?dbhtml filename="the_properties_view.html"?>
+ <title>The Properties View</title>
+ <para> Here, we dwell on the JBDS <property>Properties view</property>.</para>
+ <para>Notice if it's not visible you can access it by navigating <emphasis>
+ <property>Window > Show view > Properties</property>. </emphasis></para>
+ <para>The view shows the relevant properties of the selected item in the tabbed form. Every
+ item has its own set of properties, which can be directly editable in the Properties
+ view or by brining up the context menu.</para>
+
+ <figure>
+ <title>The Properties View of selected Transition</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>For example, on the picture above the Properties view displays all the properties for
+ a selected transition. Its name has been changed to <emphasis>
+ <property>to_auction</property>. </emphasis> We've done it directly in
+ active General tab of the view. The same way let's change the name for the
+ second transition to <emphasis>
+ <property>to_end</property>. </emphasis></para>
+ <para>If no one item is selected, the view represents the properties of the whole process
+ definition. </para>
+
+ <figure>
+ <title>The Properties View of Process Definition</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>In this case, it contains six tabs. The first one is the <emphasis>
+ <property>General</property>.</emphasis> It allows to specify a process name and add
+ necessary description. To illustrate let's change the process definition name
+ to <emphasis>
+ <property>jbay</property>. </emphasis></para>
+ </section>
+
+ <section id="jbpm_gpd_editor">
+ <?dbhtml filename="direct_editing.html"?>
+ <title>The jBPM Graphical Process Designer editor.</title>
+ <para>The <property>jBPM GPD editor</property> includes four modes: Diagram, Deployment,
+ Design and Source, which are available as switchable tabs at the bottom of the editor.
+ Let's dwell on each of them.</para>
+
+ <section id="the_diagram_mode">
+ <title>The Diagram mode</title>
+ <para> In this mode we define the process in the form of a diagram by means of tools
+ provided on the left-hand side of the jBPM GPD. </para>
+
+ <figure>
+ <title>The Diagram mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Besides, some properties can be directly edited in the <property>Diagram
+ mode</property> of the graphical editor. One example of this is the <emphasis>
+ <property>name</property>
+ </emphasis> property of nodes. You can edit this directly by selecting the node of
+ which you want to change the name and then click once inside this node. This enables
+ an editor in the node. We change the name of the node to <emphasis>
+ <property>auction</property>. </emphasis></para>
+ </section>
+
+ <section id="source_mode">
+ <?dbhtml filename="the_source_view.html"?>
+ <title>The Source Mode</title>
+ <para>Now, that we have defined a simple process definition, we can have a look at the
+ XML that is being generated under the covers. To see this XML click on the Source
+ tab of the graphical process designer editor.</para>
+
+ <figure>
+ <title>The Source Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The <property>Source mode</property> enables to easily manipulate our XML. That is
+ manually inserting and editing necessary elements or attributes. In addition, here
+ you can take advantage of content assist.</para>
+ </section>
+
+ <section id="design_mode">
+ <?dbhtml filename="the_design_view.html"?>
+ <title>The Design Mode</title>
+ <para>One more way to edit your file is to use <property>Design mode</property>. You can
+ see it in the next picture:</para>
+ <figure>
+ <title>The Design Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>As you can see above, this mode looks like a table in the first column of which
+ the process structure is performed. Here, you can also insert, remove and edit
+ elements or attributes, moreover add comments and instructions. Their values can be
+ directly edited in the second column of the Design mode table.</para>
+ <para>For instance, let’s add a comment on the second transition. For that, you should
+ bring up the context menu for it and choose <emphasis>
+ <property>Add Before > Comment</property>. </emphasis></para>
+
+ <figure>
+ <title>Adding a Comment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_8.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Then, we can put the text <emphasis>This transition leads to the end
+ state</emphasis> in the right column as its value.</para>
+
+ <figure>
+ <title>Comment is added</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_9.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+
+ <section id="deployment_mode">
+ <?dbhtml filename="the_deployment_view.html"?>
+ <title>The Deployment Mode</title>
+ <para>Finally, to adjust the deployment settings of the project you should switch on to
+ the tab that opens the <property>Deployment mode</property>. On the picture below
+ the <property>Deployment mode</property> is performed with default settings. Here,
+ you can easily modify them or, if the settings won't match your needs, to
+ reset defaults. </para>
+ <figure>
+ <title>The Deployment Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_10.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The button <emphasis>
+ <property>Test Connections</property>
+ </emphasis> is necessary to make sure whether all your settings are valid before
+ deploying the process.</para>
+ <para>Now that we've seen how to work with <property>jPDL
+ perspective</property>, let's pass on to the project testing.</para>
+ </section>
+ </section>
+</chapter>
15 years, 11 months
- 1
- 0
JBoss Tools SVN: r13191 - trunk/jbpm/docs/converter_ref/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2009-01-22 09:30:47 -0500 (Thu, 22 Jan 2009)
New Revision: 13191
Modified:
trunk/jbpm/docs/converter_ref/en/modules/overview.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-571 - making the chapter valid;
Modified: trunk/jbpm/docs/converter_ref/en/modules/overview.xml
===================================================================
--- trunk/jbpm/docs/converter_ref/en/modules/overview.xml 2009-01-22 14:29:59 UTC (rev 13190)
+++ trunk/jbpm/docs/converter_ref/en/modules/overview.xml 2009-01-22 14:30:47 UTC (rev 13191)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
-<chapter id="overview" revisionflag="overview">
+<chapter id="overview">
<title>BPMN Convert Overview</title>
<para>JBoss BPMN Convert module is a tool. Users can use it to translate a BPMN file to something else.</para>
15 years, 11 months
- 1
- 0
JBoss Tools SVN: r13190 - trunk/hibernatetools/docs/reference/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2009-01-22 09:29:59 -0500 (Thu, 22 Jan 2009)
New Revision: 13190
Modified:
trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-571 - deleting old marker;
Modified: trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml
===================================================================
--- trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml 2009-01-22 14:26:15 UTC (rev 13189)
+++ trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml 2009-01-22 14:29:59 UTC (rev 13190)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
-<chapter id="reverseengineering" role="updated">
+<chapter id="reverseengineering">
<title>Controlling reverse engineering</title>
<para>When using the <emphasis>
@@ -33,7 +33,7 @@
to a fully qualified classname.</para>
</section>
- <section id="hibernaterevengxmlfile" role="updated">
+ <section id="hibernaterevengxmlfile">
<title>hibernate.reveng.xml file</title>
<para>To have fine control over the process a <emphasis>
@@ -95,11 +95,11 @@
<foreign-key constraint-name="ORDER_CUST">
<many-to-one property="customer"/>
<set property="orders"/>
- </foreign-key>
- <!-- can also control a pure (shared pk) one-to-one -->
- <foreign-key constraint-name="ADDRESS_PERSON">
- <one-to-one exclude="false"/>
- <inverse-one-to-one exclude="true"/>
+ </foreign-key>
+ <!-- can also control a pure (shared pk) one-to-one -->
+ <foreign-key constraint-name="ADDRESS_PERSON">
+ <one-to-one exclude="false"/>
+ <inverse-one-to-one exclude="true"/>
</foreign-key>
</table>
@@ -714,14 +714,14 @@
exclude="true|false"/>
<set
property="aCollectionName"
- exclude="true|false"
-
- <one-to-one
- property="aPropertyName"
- exclude="true|false"/>
- <inverse-one-to-one
- property="aPropertyName"
+ exclude="true|false"
+
+ <one-to-one
+ property="aPropertyName"
exclude="true|false"/>
+ <inverse-one-to-one
+ property="aPropertyName"
+ exclude="true|false"/>
</foreign-key>]]></programlisting>
<table frame="topbot">
<title>Foreign-key attributes</title>
@@ -812,27 +812,27 @@
Exclude can be used to explicitly define that it should be created or not.</para></entry>
<entry><para>Optional</para></entry>
- </row>
-
- <row>
- <entry><para>one-to-one</para></entry>
-
- <entry><para>Defines that a one-to-one should be created and the
- property attribute specifies the name of the resulting property. Exclude can be
- used to explicitly define that it should be created or not.</para></entry>
-
- <entry><para>Optional</para></entry>
- </row>
-
- <row>
- <entry><para>inverse-one-to-one</para></entry>
-
- <entry><para>Defines that an inverse one-to-one should be created based on this foreign-key
- and the property attribute specifies the name of the resulting property.
- Exclude can be used to explicitly define that it should be created or not.</para></entry>
-
- <entry><para>Optional</para></entry>
</row>
+
+ <row>
+ <entry><para>one-to-one</para></entry>
+
+ <entry><para>Defines that a one-to-one should be created and the
+ property attribute specifies the name of the resulting property. Exclude can be
+ used to explicitly define that it should be created or not.</para></entry>
+
+ <entry><para>Optional</para></entry>
+ </row>
+
+ <row>
+ <entry><para>inverse-one-to-one</para></entry>
+
+ <entry><para>Defines that an inverse one-to-one should be created based on this foreign-key
+ and the property attribute specifies the name of the resulting property.
+ Exclude can be used to explicitly define that it should be created or not.</para></entry>
+
+ <entry><para>Optional</para></entry>
+ </row>
</tbody>
</tgroup>
15 years, 11 months
- 1
- 0