JBoss Tools SVN: r5663 - trunk/seam/docs/reference/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2008-01-14 09:28:00 -0500 (Mon, 14 Jan 2008)
New Revision: 5663
Modified:
trunk/seam/docs/reference/en/modules/creating_new_seam.xml
Log:
http://jira.jboss.com/jira/browse/JBDS-234 - updating according to Svetlana Mukhina remarks
Modified: trunk/seam/docs/reference/en/modules/creating_new_seam.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/creating_new_seam.xml 2008-01-14 14:27:22 UTC (rev 5662)
+++ trunk/seam/docs/reference/en/modules/creating_new_seam.xml 2008-01-14 14:28:00 UTC (rev 5663)
@@ -11,8 +11,8 @@
<title>Creating a New Seam Project via the New Seam Project wizard</title>
<para>In this chapter we provide you with the necessary steps to start working with Seam
Framework.</para>
- <para>At first, we suggest setting the specific Seam perspective that provides a necessary type
- of functionality. For that select <emphasis>
+ <para>At first, we suggest setting the specific Seam perspective that combines a number of
+ different views and editors needed for work with resources concerned. For that select <emphasis>
<property>Window > Open Perspective > Other > Seam</property>
</emphasis> or you can also access it through the button in the right top corner.</para>
@@ -31,14 +31,14 @@
experiment with it by creating variations.</para>
<para>Thus, you should select <emphasis>
<property>File > New > Seam Web Project</property>
- </emphasis> to run the <property>New Seam Project</property> wizard. It's necessary to
- enter a name and a location directory for your new project. The next wizard forms allow
- you to create runtime and server instances in order to get started creating, running,
- and debugging J2EE applications.</para>
+ </emphasis> to run the <property>New Seam Project</property> wizard. The wizard form
+ allows you to create runtime and server instances in order to get started creating,
+ running, and debugging J2EE applications.</para>
<para>Seam Web Project wizard has an option for selecting the actual Server (not just WTP
runtime) that will be used for the project. This allows the wizard to identify correctly
where the required datasource and driver libraries need to go.</para>
- <para>Let's get through the wizard step-by-step. First, you should type the name of your new project.</para>
+ <para>Let's get through the wizard step-by-step. First, you should enter a name and
+ a location directory for your new project</para>
<figure>
<title>New Seam Project Wizard</title>
<mediaobject>
@@ -51,10 +51,10 @@
<para>Clicking on <emphasis>
<property>New...</property>
- </emphasis> button in the Target Runtime section brings us to another dialog. Here, you
- can specify a new installed Runtime environment or the other type of runtime appropriate
- for configuring your project. Let's create a JBoss 4.2 Runtime. For that after choosing
- it click on <emphasis>
+ </emphasis> button in the Target Runtime section will bring you to another dialog. Here,
+ you can specify a new installed Runtime environment or the other type of runtime
+ appropriate for configuring your project. Let's create a JBoss 4.2 Runtime. For that
+ after choosing it click on <emphasis>
<property>Next</property>
</emphasis> button.</para>
@@ -144,17 +144,18 @@
</figure>
<para>The last section on this wizard step is <property>Configurations</property>. You can
- select one of the pre-defined project configurations or create your own. Having all needed options arranged click on
- <emphasis><property>Next</property></emphasis> to pass on to the other wizard.</para>
+ select one of the pre-defined project configurations or create your own. Having all
+ needed options arranged click on <emphasis>
+ <property>Next</property>
+ </emphasis> to pass on to the other wizard.</para>
</section>
<section id="projectFacets">
<title>Select the Project Facets</title>
- <para>This page of the wizard allows you to enable or disable specific facets. You can save
- or delete your preset of selected facets clicking on <emphasis>
- <property>Save</property>
- </emphasis> button.</para>
+ <para>This page of the wizard allows you to enable or disable specific facets that define
+ necessary characteristics for the project. The moment you switch to this wizard form,
+ all critical facets are already checked for the chosen Dynamic Web Project.</para>
<figure>
<title>Project Facets Selection</title>
@@ -165,6 +166,20 @@
</mediaobject>
</figure>
+ <para>Moreover, you can specify your own preset of selected facets by checking needed ones
+ in project facets window and clicking on <emphasis>
+ <property>Save</property>
+ </emphasis> button.</para>
+
+ <figure>
+ <title>Specifying Custom Facet Preset</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/create_new_seam/create_seam8_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
<para>You can also see all available runtimes after clicking on <emphasis>
<property>Show Runtimes</property>
</emphasis> or create new ones using the <emphasis>
@@ -175,21 +190,29 @@
<title>Project Facets Selection</title>
<mediaobject>
<imageobject>
- <imagedata fileref="images/create_new_seam/create_seam8_1.png"/>
+ <imagedata fileref="images/create_new_seam/create_seam8_2.png"/>
</imageobject>
</mediaobject>
</figure>
+ <para>Here, if more than one runtimes are checked, the <emphasis>
+ <property>Make Primary</property>
+ </emphasis> button won't be dimmed yet. So you can make use of it to mark
+ primary runtime.</para>
<para><emphasis>
- <property>Next</property>
- </emphasis> button will bring you to the Web Module wizard.</para>
+ <property>Next</property>
+ </emphasis> button will bring you to the Web Module wizard form.</para>
</section>
<section id="configureWebModule">
<title>How to Configure Web Module Settings</title>
- <para>A dynamic web application contains both web pages and Java code. The wizard will ask
- you where you want to put those files. You can just leave the default values.</para>
+ <para> As we deal with a dynamic web application we should first specify the top level
+ directory of our application for deploying it to a server afterwards. You know, this
+ kind of application contains both Web and Java code resources. Thus, it's also important
+ to indicate the content directory as well as Java source directory. The wizard will put
+ all those values itself. So you can leave everything as it is.</para>
+
<figure>
<title>Web Module Settings</title>
<mediaobject>
@@ -198,13 +221,16 @@
</imageobject>
</mediaobject>
</figure>
-
+ <para>Choose <emphasis>
+ <property>Next</property>
+ </emphasis> to switch to the next wizard form.</para>
</section>
-
+
<section id="addJSFCapab">
<title>Adding JSF Capabilities</title>
- <para>This wizard helps you to add JSF capabilities into your project. </para>
+ <para>This wizard helps you to add JSF capabilities into your project for representing
+ appropriate behaviours associated with JSF. </para>
<para>Checking <emphasis>
<property>Server Supplied JSF Implementation</property>
</emphasis> means that you will have a default JSF implementation given by server.</para>
@@ -222,9 +248,11 @@
button. You are able to create a library of jars by clicking on <emphasis>
<property>New</property>
</emphasis> button.</para>
- <para>Here, it's necessary to type a <property>Library Name</property>, select a <property>Version
- Supported</property> and add proper <property>Library jars</property>. Then click on
- <emphasis><property>Finish</property>.</emphasis></para>
+ <para>Here, it's necessary to type a <property>Library Name</property>, select a
+ <property>Version Supported</property> and add proper <property>Library
+ jars</property>. Then click on <emphasis>
+ <property>Finish</property>
+ </emphasis> to complete the choice.</para>
<figure>
<title>Create JSF Implementation Library</title>
<mediaobject>
@@ -234,10 +262,13 @@
</mediaobject>
</figure>
- <para>You can also add a <property>Component Libraries</property> (e.g. Richfaces) clicking
- on <emphasis>
+ <para>In the Component Libraries section of the wizard you can also add <property>Component
+ Libraries</property> (e.g. Richfaces). Just click on <emphasis>
<property>New</property>
- </emphasis> button in the Component Libraries section.</para>
+ </emphasis> button. Appeared dialog will ask you to type the Library name, supported
+ version and add necessary jar's. Press <emphasis>
+ <property>Finish</property>
+ </emphasis> to complete the choice.</para>
<figure>
<title>Create JSF Implementation Library</title>
@@ -260,6 +291,9 @@
</imageobject>
</mediaobject>
</figure>
+
+ <para>Finally, as we are arranging the Seam Web project, the last step we should do is to adjust project
+ configurations associated with Seam.</para>
</section>
<section id="seamFacet">
@@ -277,12 +311,12 @@
<itemizedlist>
<listitem>
- <para>Create Seam runtime and define Seam home folder. Click on <emphasis>
- <property>Add</property>
- </emphasis> button in the <property>General</property> section.</para>
+ <para>Create Seam runtime and define Seam home folder.</para>
</listitem>
</itemizedlist>
- <para>Notice that in this wizard presented below you can create a Seam runtime only for that
+ <para>For that click on <emphasis>
+ <property>Add</property>
+ </emphasis> button in the <property>General</property> section. Notice that in this wizard presented below you can create a Seam runtime only for that
version which was selected in the <link linkend="projectFacets">Project Facets</link>
wizard (version 1.2 in our case).</para>
@@ -314,7 +348,7 @@
</imageobject>
</mediaobject>
</figure>
-
+
<itemizedlist>
<listitem>
<para>and create a <emphasis>
@@ -326,6 +360,15 @@
</itemizedlist>
<figure>
+ <title>Connection Profile Options</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/create_new_seam/create_seam13_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <figure>
<title>Connection Profile Selecting</title>
<mediaobject>
<imageobject>
@@ -352,6 +395,7 @@
<para>Click on <emphasis>
<property>Finish</property>
</emphasis> to generate a project.</para>
-
+
+ <para></para>
</section>
</chapter>
16 years, 5 months
- 1
- 0
JBoss Tools SVN: r5662 - trunk/seam/docs/reference/en/images/create_new_seam.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2008-01-14 09:27:22 -0500 (Mon, 14 Jan 2008)
New Revision: 5662
Added:
trunk/seam/docs/reference/en/images/create_new_seam/create_seam13_1.png
trunk/seam/docs/reference/en/images/create_new_seam/create_seam8_2.png
Modified:
trunk/seam/docs/reference/en/images/create_new_seam/create_seam8_1.png
Log:
http://jira.jboss.com/jira/browse/JBDS-234 - adding new screenshots
Added: trunk/seam/docs/reference/en/images/create_new_seam/create_seam13_1.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/create_new_seam/create_seam13_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: trunk/seam/docs/reference/en/images/create_new_seam/create_seam8_1.png
===================================================================
(Binary files differ)
Added: trunk/seam/docs/reference/en/images/create_new_seam/create_seam8_2.png
===================================================================
(Binary files differ)
Property changes on: trunk/seam/docs/reference/en/images/create_new_seam/create_seam8_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
16 years, 5 months
- 1
- 0
JBoss Tools SVN: r5661 - trunk/common/tests/org.jboss.tools.common.kb.test/src/org/jboss/tools/common/kb/test.
by jbosstools-commits＠lists.jboss.org
Author: akazakov
Date: 2008-01-14 08:54:29 -0500 (Mon, 14 Jan 2008)
New Revision: 5661
Modified:
trunk/common/tests/org.jboss.tools.common.kb.test/src/org/jboss/tools/common/kb/test/TldTest.java
Log:
Removed System.out.println();
Modified: trunk/common/tests/org.jboss.tools.common.kb.test/src/org/jboss/tools/common/kb/test/TldTest.java
===================================================================
--- trunk/common/tests/org.jboss.tools.common.kb.test/src/org/jboss/tools/common/kb/test/TldTest.java 2008-01-14 07:55:17 UTC (rev 5660)
+++ trunk/common/tests/org.jboss.tools.common.kb.test/src/org/jboss/tools/common/kb/test/TldTest.java 2008-01-14 13:54:29 UTC (rev 5661)
@@ -110,9 +110,6 @@
NodeList nl = parentElement.getElementsByTagName(elementName);
Node node = nl.item(0);
String value = node.getTextContent();
- if(value==null) {
- System.out.println("!");
- }
return value.trim();
}
16 years, 5 months
- 1
- 0
JBoss Tools SVN: r5660 - trunk/hibernatetools/docs/reference/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2008-01-14 02:55:17 -0500 (Mon, 14 Jan 2008)
New Revision: 5660
Modified:
trunk/hibernatetools/docs/reference/en/modules/ant.xml
trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml
Log:
http://jira.jboss.com/jira/browse/JBDS-238 - updating the end of four and the beginning of the five chapters
Modified: trunk/hibernatetools/docs/reference/en/modules/ant.xml
===================================================================
--- trunk/hibernatetools/docs/reference/en/modules/ant.xml 2008-01-13 15:10:49 UTC (rev 5659)
+++ trunk/hibernatetools/docs/reference/en/modules/ant.xml 2008-01-14 07:55:17 UTC (rev 5660)
@@ -744,7 +744,7 @@
<property>hibernate.cfg.xml</property>
</emphasis>. Intended to be used together with a <emphasis>
<property><jdbcconfiguration></property>
- </emphasis> when performing reverse engineering, but can be used with any kind of
+ </emphasis> when performing reverse engineering, but it can be used with any kind of
configuration. The <emphasis>
<property><hbm2cfgxml></property>
</emphasis> will contain the properties used and adds mapping entries for each mapped class.</para>
@@ -786,8 +786,8 @@
<para><emphasis>
<property><query></property>
- </emphasis> is used to execute a HQL query statements and optionally send the output to a
- file. Can be used for verifying the mappings and for basic data extraction.</para>
+ </emphasis> is used to execute a HQL query statements and optionally sends the output to a
+ file. It can be used for verifying the mappings and for basic data extraction.</para>
<programlisting><![CDATA[<query
destfile="filename">
@@ -797,14 +797,14 @@
<para>Currently one session is opened and used for all queries and the query is executed via
the list() method. In the future more options might become available, like performing
- executeUpdate(), use named queries etc.</para>
+ executeUpdate(), use named queries and etc.</para>
<para/>
<section>
<title>Examples</title>
- <para>Simplest usage of <emphasis>
+ <para>The simplest usage of <emphasis>
<property><query></property>
</emphasis> will just execute the query without dumping to a file. This can be used to
verify that queries can actually be performed.</para>
@@ -839,7 +839,7 @@
<section id="hbmtemplate">
<title>Generic Hibernate metamodel exporter (<literal><hbmtemplate></literal>)</title>
- <para>Generic exporter that can be controlled by an user provided template or class.</para>
+ <para>Generic exporter that can be controlled by an user provides a template or class.</para>
<programlisting><![CDATA[<hbmtemplate
filepattern="{package-name}/{class-name}.ftl"
@@ -857,7 +857,7 @@
<para>The following is an example of reverse engineering via <emphasis>
<property><jdbcconfiguration></property>
- </emphasis> and use a custom Exporter via the <emphasis>
+ </emphasis> and usage of a custom Exporter via the <emphasis>
<property><hbmtemplate></property>
</emphasis>.</para>
@@ -916,17 +916,17 @@
<property>
<literal><propertyset></literal>
</property>
- </emphasis>. The functionality of <emphasis>
+ </emphasis> that is used for grouping a set of properties. More about the functionality of <emphasis>
<property>
<literal><propertyset></literal>
</property>
- </emphasis> is explained in detail in the Ant task manual.</para>
+ </emphasis> is explained in detail in the <ulink url="http://ant.apache.org/manual/">Ant manual</ulink>.</para>
</section>
<section>
<title>Getting access to user specific classes</title>
- <para>If the templates need to access some user class it is possible by specifying a <emphasis>
+ <para>If the templates need to access some user class it becomes possible by specifying a <emphasis>
<property>"toolclass"</property>
</emphasis> in the properties.</para>
Modified: trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml
===================================================================
--- trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml 2008-01-13 15:10:49 UTC (rev 5659)
+++ trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml 2008-01-14 07:55:17 UTC (rev 5660)
@@ -3,52 +3,52 @@
<title>Controlling reverse engineering</title>
<para>When using the <emphasis>
- <property><jdbcconfiguration></property></emphasis> the ant task will read the
- database metadata and from that perform a reverse engineering of the
- database schema into a normal Hibernate Configuration. It is from this
- object e.g. <emphasis>
- <property><hbm2java></property></emphasis>can generate other artifacts such as <emphasis>
- <property>.java</property></emphasis>,
- <emphasis>
- <property>.hbm.xml</property></emphasis> etc.</para>
+ <property><jdbcconfiguration></property>
+ </emphasis> the ant task will read the database metadata and from that will perform a reverse
+ engineering of the database schema into a normal Hibernate Configuration. It is from this object
+ e.g. <emphasis>
+ <property><hbm2java></property>
+ </emphasis>can generate other artifacts such as <emphasis>
+ <property>.java</property>
+ </emphasis>, <emphasis>
+ <property>.hbm.xml</property>
+ </emphasis> etc.</para>
- <para>To govern this process <property>Hibernate</property> uses a reverse engineering strategy.
- A reverse engineering strategy is mainly called to provide more java like
- names for tables, column and foreignkeys into classes, properties and
- associations. It also used to provide mappings from SQL types to <property>Hibernate</property>
- types. The strategy can be customized by the user. The user can even provide
- its own custom reverse engineering strategy if the provided strategy is not
- enough, or simply just provide a small part of the strategy and delegate the
- rest to the default strategy.</para>
+ <para>To govern this process <property>Hibernate</property> uses a reverse engineering strategy. A
+ reverse engineering strategy is mainly called to provide more java like names for tables, column
+ and foreignkeys into classes, properties and associations. It also used to provide mappings from
+ SQL types to <property>Hibernate</property> types. The strategy can be customized by a user. The
+ user can even provide its own custom reverse engineering strategy if the provided strategy is
+ not enough, or simply just provide a small part of the strategy and delegate the rest to the
+ default strategy.</para>
<section>
<title>Default reverse engineering strategy</title>
- <para>The default strategy uses some rules for mapping JDBC artifact names
- to java artifact names. It also provide basic typemappings from JDBC types
- to
- <property>Hibernate</property>
- types. It is the default strategy that uses the packagename
- attribute to convert a table name to a fully qualified classname.</para>
+ <para>The default strategy uses some rules for mapping JDBC artifact names to java artifact
+ names. It also provide basic typemappings from JDBC types to <property>Hibernate</property>
+ types. It is the default strategy that uses the packagename attribute to convert a table name
+ to a fully qualified classname.</para>
</section>
<section id="hibernaterevengxmlfile">
<title>hibernate.reveng.xml file</title>
<para>To have fine control over the process a <emphasis>
- <property>hibernate.reveng.xml</property></emphasis> file
- can be provided. In this file you can specify type mappings and table
- filtering. This file can be created by hand (its just basic XML) or you
- can use the Hibernate plugins which have a specialized editor.</para>
+ <property>hibernate.reveng.xml</property>
+ </emphasis> file can be provided. In this file you can specify type mappings and table
+ filtering. This file can be created by hand (it's just basic XML) or you can use the
+ Hibernate plugins which have a specialized editor.</para>
- <note><para>Many databases are case-sensitive with their names and thus if
- you cannot make some table match and you are sure it is not excluded by a
- <table-filter>then check if the case matches; most databases stores
- table names in uppercase.</para></note>
+ <note>
+ <para>Many databases are case-sensitive with their names and thus if you cannot make some
+ table match and you are sure it is not excluded by a <table-filter>then check
+ if the case matches; most databases stores table names in uppercase.</para>
+ </note>
<para>The following is an example of a <emphasis>
- <property>reveng.xml</property></emphasis>. Following the example
- is more details about the format.</para>
+ <property>reveng.xml</property>
+ </emphasis>. Following the example gives you more details about the format.</para>
<programlisting><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE hibernate-reverse-engineering
@@ -96,59 +96,55 @@
</hibernate-reverse-engineering>]]></programlisting>
-
+
<section>
<title>Schema Selection (<schema-selection>)</title>
<para><emphasis>
- <property><schema-selection></property></emphasis> is used to drive which
- schema's the reverse engineering will try and process.</para>
+ <property><schema-selection></property>
+ </emphasis> is used to drive which schema's the reverse engineering will try and
+ process.</para>
- <para>By default the reverse engineering will read all schemas and then
- use <emphasis>
- <property><table-filter></property></emphasis> to decide which tables get
- reverse engineered and which do not; this makes it easy to get started
- but can be inefficient on databases with many schemas.</para>
+ <para>By default the reverse engineering will read all schemas and then use <emphasis>
+ <property><table-filter></property>
+ </emphasis> to decide which tables get reverse engineered and which do not; this makes it
+ easy to get started but can be inefficient on databases with many schemas.</para>
<para>With <emphasis>
- <property><schema-selection></property></emphasis> it is thus
- possible to limit the actual processed schemas and thus significantly
- speed-up the reverse engineering.
- <emphasis>
- <property><table-filter></property></emphasis> is still used to then decide
- which tables will be included/excluded.</para>
+ <property><schema-selection></property>
+ </emphasis> it is thus possible to limit the actual processed schemas and thus significantly
+ speed-up the reverse engineering. <emphasis>
+ <property><table-filter></property>
+ </emphasis> is still used to then decide which tables will be included/excluded.</para>
- <note> <para>If no <literal><schema-selection></literal> is
- specified, the reverse engineering works as if all schemas should be
- processed. </para></note>
-
-
-
- <para>This is equal to:</para>
+ <note>
+ <para>If no <literal><schema-selection></literal> is specified, the reverse
+ engineering works as if all schemas should be processed. This is equal to:
+ <![CDATA[<schema-selection/>]]>. Which in turn is equal
+ to:
+ <![CDATA[<schema-selection match-catalog=".*" match-schema=".*" match-table=".*"/>]]></para>
+ </note>
- <programlisting><![CDATA[<schema-selection/>]]></programlisting>
-
- <para>Which in turn is equal to:</para>
-
- <programlisting><![CDATA[<schema-selection match-catalog=".*" match-schema=".*" match-table=".*"/>]]></programlisting>
-
<section>
<title>Examples</title>
<para>The following will process all tables from <emphasis>
- <property>"MY_SCHEMA"</property></emphasis>.</para>
+ <property>"MY_SCHEMA"</property>
+ </emphasis>.</para>
<programlisting><![CDATA[<schema-selection match-schema="MY_SCHEMA"/>]]></programlisting>
- <para>It is possible to have multiple
- <literal>schema-selection</literal>'s to support multi-schema reading
- or simply to limit the processing to very specific tables. The
- following example process all tables in <emphasis>
- <property>"MY_SCHEMA"</property></emphasis>, a specific <emphasis>
- <property>"CITY"</property></emphasis>
- table plus all tables that starts with <emphasis>
- <property>"CODES_"</property></emphasis> in <emphasis>
- <property>COMMON_SCHEMA"</property></emphasis>.</para>
+ <para>It is possible to have multiple <literal>schema-selection</literal>'s to support
+ multi-schema reading or simply to limit the processing to very specific tables. The
+ following example processes all tables in <emphasis>
+ <property>"MY_SCHEMA"</property>
+ </emphasis>, a specific <emphasis>
+ <property>"CITY"</property>
+ </emphasis> table plus all tables that starts with <emphasis>
+ <property>"CODES_"</property>
+ </emphasis> in <emphasis>
+ <property>COMMON_SCHEMA"</property>
+ </emphasis>.</para>
<programlisting><![CDATA[<schema-selection match-schema="MY_SCHEMA"/>
<schema-selection match-schema="COMMON_SCHEMA" match-table="CITY"/>
@@ -160,12 +156,11 @@
<title>Type mappings (<type-mapping>)</title>
<para>The <emphasis>
- <property><type-mapping></property></emphasis> section specifies how
- the JDBC types found in the database should be mapped to Hibernate
- types. e.g. java.sql.Types.VARCHAR with a length of 1 should be mapped
- to the Hibernate type <literal>yes_no</literal> or
- java.sql.Types.NUMERIC should generally just be converted to the
- Hibernate type <literal>long</literal>.</para>
+ <property><type-mapping></property>
+ </emphasis> section specifies how the JDBC types found in the database should be mapped to
+ Hibernate types. e.g. java.sql.Types.VARCHAR with a length of 1 should be mapped to the
+ Hibernate type <literal>yes_no</literal> or java.sql.Types.NUMERIC should generally just be
+ converted to the Hibernate type <literal>long</literal>.</para>
<programlisting><![CDATA[<type-mapping>
<sql-type
@@ -178,18 +173,16 @@
/>
</type-mapping>]]></programlisting>
- <para>The number of attributes specified and the sequence of the
- <literal>sql-type</literal>'s is important. Meaning that <property>Hibernate</property> will
- search for the most specific first, and if no specific match is found it
- will seek from top to bottom when trying to resolve a type
- mapping.</para>
+ <para>The number of attributes specified and the sequence of the <literal>sql-type</literal>'s
+ is important. Meaning that <property>Hibernate</property> will search for the most specific
+ first, and if no specific match is found it will seek from top to bottom when trying to
+ resolve a type mapping.</para>
<section>
<title>Example</title>
- <para>The following is an example of a type-mapping which shows the
- flexibility and the importance of ordering of the type
- mappings.</para>
+ <para>The following is an example of a type-mapping which shows the flexibility and the
+ importance of ordering of the type mappings.</para>
<programlisting><![CDATA[<type-mapping>
<sql-type jdbc-type="NUMERIC" precision="15" hibernate-type="big_decimal"/>
@@ -201,26 +194,25 @@
<sql-type jdbc-type="VARCHAR" hibernate-type="string"/>
</type-mapping>]]></programlisting>
- <para>The following table shows how this affects an example table
- named CUSTOMER:</para>
+ <para>The following table shows how this affects an example table named CUSTOMER:</para>
<table frame="topbot">
<title>sql-type examples</title>
<tgroup cols="7">
- <colspec colwidth="0.5*" />
+ <colspec colwidth="0.5*"/>
- <colspec colwidth="0.5*" />
+ <colspec colwidth="0.5*"/>
- <colspec colwidth="0.2*" />
+ <colspec colwidth="0.2*"/>
- <colspec colwidth="0.2*" />
+ <colspec colwidth="0.2*"/>
- <colspec colwidth="0.2*" />
+ <colspec colwidth="0.2*"/>
- <colspec colwidth="0.5*" />
+ <colspec colwidth="0.5*"/>
- <colspec colwidth="1.0*" />
+ <colspec colwidth="1.0*"/>
<thead>
<row>
@@ -246,7 +238,7 @@
<entry>INTEGER</entry>
- <entry></entry>
+ <entry/>
<entry>10</entry>
@@ -254,8 +246,7 @@
<entry>int</entry>
- <entry>Nothing defined for INTEGER. Falling back to default
- behavior.</entry>
+ <entry>Nothing is defined for INTEGER. Falling back to default behavior.</entry>
</row>
<row>
@@ -265,15 +256,15 @@
<entry>30</entry>
- <entry></entry>
+ <entry/>
<entry>false</entry>
<entry>your.package.TrimStringUserType</entry>
- <entry>No type-mapping matches length=30 and not-null=false,
- but type-mapping matches the 2 mappings which only specifies
- VARCHAR. The type-mapping that comes first is chosen.</entry>
+ <entry>No type-mapping matches length=30 and not-null=false, but type-mapping
+ matches the 2 mappings which only specifies VARCHAR. The type-mapping that comes
+ first is chosen.</entry>
</row>
<row>
@@ -283,16 +274,16 @@
<entry>1</entry>
- <entry></entry>
+ <entry/>
<entry>false</entry>
<entry>char</entry>
- <entry>Even though there is a generic match for VARCHAR, the
- more specific type-mapping for VARCHAR with not-null="false" is
- chosen. The first VARCHAR sql-type matches in length but has
- no value for not-null and thus is not considered.</entry>
+ <entry>Even though there is a generic match for VARCHAR, the more specific
+ type-mapping for VARCHAR with not-null="false" is chosen. The first VARCHAR
+ sql-type matches in length but has no value for not-null and thus is not
+ considered.</entry>
</row>
<row>
@@ -302,14 +293,13 @@
<entry>1</entry>
- <entry></entry>
+ <entry/>
<entry>true</entry>
<entry>java.lang.Character</entry>
- <entry>The most specific VARCHAR with not-null="true" is
- selected</entry>
+ <entry>The most specific VARCHAR with not-null="true" is selected</entry>
</row>
<row>
@@ -317,7 +307,7 @@
<entry>NUMERIC</entry>
- <entry></entry>
+ <entry/>
<entry>15</entry>
@@ -325,8 +315,7 @@
<entry>big_decimal</entry>
- <entry>There is a precise match for NUMERIC with precision
- 15</entry>
+ <entry>There is a precise match for NUMERIC with precision 15</entry>
</row>
<row>
@@ -334,7 +323,7 @@
<entry>NUMERIC</entry>
- <entry></entry>
+ <entry/>
<entry>3</entry>
@@ -348,7 +337,7 @@
</tgroup>
</table>
- <para></para>
+ <para/>
</section>
</section>
@@ -356,22 +345,22 @@
<title>Table filters (<table-filter>)</title>
<para>The <emphasis>
- <property><table-filter></property></emphasis> let you specify matching rules for
- performing general filtering/setup for tables, e.g. let you include or
- exclude specific tables based on the schema or even a specific
- prefix.</para>
+ <property><table-filter></property>
+ </emphasis> let you specify matching rules for performing general filtering/setup for
+ tables, e.g. let you include or exclude specific tables based on the schema or even a
+ specific prefix.</para>
<programlistingco>
<areaspec>
- <area coords="2 55" id="tablefilter-matchcatalog" />
+ <area coords="2 55" id="tablefilter-matchcatalog"/>
- <area coords="3 55" id="tablefilter-matchschema" />
+ <area coords="3 55" id="tablefilter-matchschema"/>
- <area coords="4 55" id="tablefilter-matchname" />
+ <area coords="4 55" id="tablefilter-matchname"/>
- <area coords="5 55" id="tablefilter-exclude" />
+ <area coords="5 55" id="tablefilter-exclude"/>
- <area coords="6 55" id="tablefilter-package" />
+ <area coords="6 55" id="tablefilter-package"/>
</areaspec>
<programlisting><![CDATA[<table-filter
@@ -384,28 +373,25 @@
<calloutlist>
<callout arearefs="tablefilter-matchcatalog">
- <para>match-catalog (default: .*): Pattern for matching catalog
- part of the table</para>
+ <para>match-catalog (default: .*): Pattern for matching catalog part of the table</para>
</callout>
<callout arearefs="tablefilter-matchschema">
- <para>match-schema (default: .*): Pattern for matching schema part
- of the table</para>
+ <para>match-schema (default: .*): Pattern for matching schema part of the table</para>
</callout>
<callout arearefs="tablefilter-matchname">
- <para>match-table (default: .*): Pattern for matching table part
- of the table</para>
+ <para>match-table (default: .*): Pattern for matching table part of the table</para>
</callout>
<callout arearefs="tablefilter-exclude">
- <para>exclude (default: false): if true the table will not be part
- of the reverse engineering</para>
+ <para>exclude (default: false): if true the table will not be part of the reverse
+ engineering</para>
</callout>
<callout arearefs="tablefilter-package">
- <para>package (default: ""): The default package name to use for
- classes based on tables matched by this table-filter</para>
+ <para>package (default: ""): The default package name to use for classes based on tables
+ matched by this table-filter</para>
</callout>
</calloutlist>
</programlistingco>
@@ -415,21 +401,20 @@
<title>Specific table configuration (<table>)</title>
<para><emphasis>
- <property><table></property></emphasis> allows you to provide explicit
- configuration on how a table should be reverse engineered. Amongst other
- things it allow control over the naming of a class for the table,
- specify which identifier generator should be used for the primary key
- etc.</para>
+ <property><table></property>
+ </emphasis> allows you to provide explicit configuration on how a table should be reverse
+ engineered. Amongst other things it allows controlling over the naming of a class for the table,
+ specifying which identifier generator should be used for the primary key etc.</para>
<programlistingco>
<areaspec>
- <area coords="2 55" id="table-catalog" />
+ <area coords="2 55" id="table-catalog"/>
- <area coords="3 55" id="table-schema" />
+ <area coords="3 55" id="table-schema"/>
- <area coords="4 55" id="table-name" />
+ <area coords="4 55" id="table-name"/>
- <area coords="5 55" id="table-class" />
+ <area coords="5 55" id="table-class"/>
</areaspec>
<programlisting><![CDATA[<table
@@ -445,20 +430,24 @@
<calloutlist>
<callout arearefs="tablefilter-matchcatalog">
- <para>catalog (Optional): Catalog name for table. Has to be specified if you are reverse engineering multiple catalogs or if it is not equal to <literal>hiberante.default_catalog. </literal></para>
+ <para>catalog (Optional): Catalog name for a table. It has to be specified if you are reverse
+ engineering multiple catalogs or if it is not equal to
+ <literal>hiberante.default_catalog. </literal></para>
</callout>
<callout arearefs="tablefilter-matchschema">
- <para>schema (Optional): Schema name for table. Has to be specified if you are reverse engineering multiple schemas or if it is not equal to <literal>hiberante.default_schema.</literal></para>
+ <para>schema (Optional): Schema name for a table. It has to be specified if you are reverse
+ engineering multiple schemas or if it is not equal to
+ <literal>hiberante.default_schema.</literal></para>
</callout>
<callout arearefs="tablefilter-matchname">
- <para>name (Required): Name for table</para>
+ <para>name (Required): Name for a table</para>
</callout>
<callout arearefs="tablefilter-exclude">
- <para>clase (Optional): The class name for table. Default name is
- camelcase version of the table name.</para>
+ <para>clase (Optional): The class name for a table. Default name is a camelcase version of
+ the table name.</para>
</callout>
</calloutlist>
</programlistingco>
@@ -467,19 +456,18 @@
<title><primary-key></title>
<para>A <emphasis>
- <property><primary-key></property></emphasis> allows you to define a
- primary-key for tables that does not have such defined in the
- database, and probably more importantly it allows you to define which
- identifier strategy that should be used (even for already existing
- primary-key's).</para>
+ <property><primary-key></property>
+ </emphasis> allows you to define a primary-key for tables that don't have such defined
+ in the database, and probably more importantly it allows you to define which identifier
+ strategy should be used (even for already existing primary-key's).</para>
<programlistingco>
<areaspec>
- <area coords="2 55" id="pk-generatorclass" />
+ <area coords="2 55" id="pk-generatorclass"/>
- <area coords="3 55" id="pk-generatorparam" />
+ <area coords="3 55" id="pk-generatorparam"/>
- <area coords="5 55" id="pk-keycolumn" />
+ <area coords="5 55" id="pk-keycolumn"/>
</areaspec>
<programlisting><![CDATA[<primary-key
@@ -491,22 +479,19 @@
<calloutlist>
<callout arearefs="pk-generatorclass">
- <para>generator/class (Optional): defines which identifier
- generator should be used. The class name is any hibernate short
- hand name or fully qualified class name for an identifier
- strategy.</para>
+ <para>generator/class (Optional): defines which identifier generator should be used.
+ The class name is any hibernate short hand name or fully qualified class name for an
+ identifier strategy.</para>
</callout>
<callout arearefs="pk-generatorparam">
- <para>generator/param (Optional): Allows to specify which
- parameter with name and value should be passed to the identifier
- generator</para>
+ <para>generator/param (Optional): Allows to specify which parameter with a name and
+ value should be passed to the identifier generator</para>
</callout>
<callout arearefs="pk-keycolumn">
- <para>key-column (Optional): Specifies which column(s ) the
- primary-key consists of. A key-column is same as column, but
- does not have the exclude property.</para>
+ <para>key-column (Optional): Specifies which column(s ) the primary-key consists of. A
+ key-column is same as column, but does not have the exclude property.</para>
</callout>
</calloutlist>
</programlistingco>
@@ -516,22 +501,23 @@
<title><column></title>
<para>With a <emphasis>
- <property><column></property></emphasis> it is possible to explicitly name the
- resulting property for a column. It is also possible to redefine what
- jdbc and/or Hibernate type a column should be processed and finally it
- is possible to completely exclude a column from processing.</para>
+ <property><column></property>
+ </emphasis> it is possible to explicitly name the resulting property for a column. It is
+ also possible to redefine what jdbc and/or Hibernate type a column should be processed as and
+ finally it is possible to completely exclude a column from processing.</para>
- <para><programlistingco>
+ <para>
+ <programlistingco>
<areaspec>
- <area coords="2 55" id="column-name" />
+ <area coords="2 55" id="column-name"/>
- <area coords="3 55" id="column-jdbctype" />
+ <area coords="3 55" id="column-jdbctype"/>
- <area coords="4 55" id="column-type" />
+ <area coords="4 55" id="column-type"/>
- <area coords="5 55" id="column-propertytype" />
+ <area coords="5 55" id="column-propertytype"/>
- <area coords="6 55" id="column-exclude" />
+ <area coords="6 55" id="column-exclude"/>
</areaspec>
<programlisting><![CDATA[<column
@@ -548,56 +534,55 @@
</callout>
<callout arearefs="column-jdbctype">
- <para>jdbc-type (Optional): Which jdbc-type this column should
- be processed as. A value from java.sql.Types, either numerical
- (93) or the constant name (TIMESTAMP).</para>
+ <para>jdbc-type (Optional): Which jdbc-type this column should be processed as. A
+ value from java.sql.Types, either numerical (93) or the constant name
+ (TIMESTAMP).</para>
</callout>
<callout arearefs="column-type">
- <para>type (Optional): Which hibernate-type to use for this
- specific column</para>
+ <para>type (Optional): Which hibernate-type to use for this specific column</para>
</callout>
<callout arearefs="column-propertytype">
- <para>property (Optional): What property name will be
- generated for this column</para>
+ <para>property (Optional): What property name will be generated for this
+ column</para>
</callout>
<callout arearefs="column-exclude">
- <para>exclude (default: false): set to true if this column
- should be ignored</para>
+ <para>exclude (default: false): set to true if this column should be ignored</para>
</callout>
</calloutlist>
- </programlistingco></para>
+ </programlistingco>
+ </para>
</section>
<section>
<title><foreign-key></title>
<para>The <emphasis>
- <property><foreign-key></property></emphasis> has two purposes. One for allowing to
- define foreign-keys in databases that does not support them or does
- not have them defined in their schema. Secondly, to allow defining the
- name of the resulting properties (many-to-one and
- one-to-many's).</para>
+ <property><foreign-key></property>
+ </emphasis> has two purposes. One for allowing to define foreign-keys in databases that
+ does not support them or does not have them defined in their schema. Secondly, to allow
+ defining the name of the resulting properties (many-to-one and one-to-many's).</para>
<para>Note:</para>
- <para><programlistingco>
+ <para>
+ <programlistingco>
<areaspec>
- <area coords="2 55" id="foreignkey-name" />
+ <area coords="2 55" id="foreignkey-name"/>
- <area coords="3 55" id="foreignkey-catalog" />
+ <area coords="3 55" id="foreignkey-catalog"/>
- <area coords="4 55" id="foreignkey-schema" />
+ <area coords="4 55" id="foreignkey-schema"/>
- <area coords="5 55" id="foreignkey-table" />
+ <area coords="5 55" id="foreignkey-table"/>
- <area coords="7 55" id="foreignkey-columnref" />
+ <area coords="7 55" id="foreignkey-columnref"/>
- <area coords="8 55" id="foreignkey-manytoone" />
+ <area coords="8 55" id="foreignkey-manytoone"/>
- <area coords="10 55" id="foreignkey-set" />
+ <area coords="10 55" id="foreignkey-set"/>
</areaspec>
<programlisting><![CDATA[<foreign-key
@@ -617,52 +602,46 @@
<calloutlist>
<callout arearefs="foreignkey-name">
- <para>constraint-name (Required): Name of the foreign key
- constraint. Important when naming many-to-one and set. It is
- the constraint-name that is used to link the processed
- foreign-keys with the resulting property names.</para>
+ <para>constraint-name (Required): Name of the foreign key constraint. Important when
+ naming many-to-one and set. It is the constraint-name that is used to link the
+ processed foreign-keys with the resulting property names.</para>
</callout>
<callout arearefs="foreignkey-catalog">
- <para>foreign-catalog (Optional): Name of the foreign table's
- catalog. (Only relevant if you want to explicitly define a
- foreign key).</para>
+ <para>foreign-catalog (Optional): Name of the foreign table's catalog. (Only
+ relevant if you want to explicitly define a foreign key).</para>
</callout>
<callout arearefs="foreignkey-schema">
- <para>foreign-schema (Optional): Name of the foreign table's
- schema. (Only relevant if you want to explicitly define a
- foreign key).</para>
+ <para>foreign-schema (Optional): Name of the foreign table's schema. (Only relevant
+ if you want to explicitly define a foreign key).</para>
</callout>
<callout arearefs="foreignkey-table">
- <para>foreign-table (Optional): Name of the foreign table.
- (Only relevant if you want to explicitly define a foreign
- key).</para>
+ <para>foreign-table (Optional): Name of the foreign table. (Only relevant if you
+ want to explicitly define a foreign key).</para>
</callout>
<callout arearefs="foreignkey-columnref">
- <para>column-ref (Optional): Defines that the foreign-key
- constraint between a local-column and foreign-column name.
- (Only relevant if you want to explicitly define a foreign
- key).</para>
+ <para>column-ref (Optional): Defines that the foreign-key constraint between a
+ local-column and foreign-column name. (Only relevant if you want to explicitly
+ define a foreign key).</para>
</callout>
<callout arearefs="foreignkey-manytoone">
- <para>many-to-one (Optional): Defines that a many-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>
+ <para>many-to-one (Optional): Defines that a many-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>
</callout>
<callout arearefs="foreignkey-set">
- <para>set (Optional): Defines that a set should be created
- based on this foreign-key and the property attribute specifies
- the name of the resulting (set) property. Exclude can be used
- to explicitly define that it should be created or not.</para>
+ <para>set (Optional): Defines that a set should be created based on this foreign-key
+ and the property attribute specifies the name of the resulting (set) property.
+ Exclude can be used to explicitly define that it should be created or not.</para>
</callout>
</calloutlist>
- </programlistingco></para>
+ </programlistingco>
+ </para>
</section>
</section>
</section>
@@ -670,17 +649,17 @@
<section id="custom-reveng-strategy">
<title>Custom strategy</title>
- <para>It is possible to implement an user strategy. Such strategy must
- implement <emphasis>
- <property>org.hibernate.cfg.reveng.ReverseEngineeringStrategy</property></emphasis>. It is
- recommended that one uses the <property>DelegatingReverseEngineeringStrategy</property> and
- provide a public constructor which takes another
- <property>ReverseEngineeringStrategy </property> as argument. This will allow you to only
- implement the relevant methods and provide a fallback strategy. Example of
- custom delegating strategy which converts all column names that ends with
- <emphasis>
- <property>"PK"</property></emphasis> into a property named <emphasis>
- <property>"id"</property></emphasis>.</para>
+ <para>It is possible to implement an user strategy. Such strategy must implement <emphasis>
+ <property>org.hibernate.cfg.reveng.ReverseEngineeringStrategy</property>
+ </emphasis>. It is recommended that one uses the
+ <property>DelegatingReverseEngineeringStrategy</property> and provide a public constructor
+ which takes another <property>ReverseEngineeringStrategy </property> as argument. This will
+ allow you to only implement the relevant methods and provide a fallback strategy. Example of
+ custom delegating strategy which converts all column names that ends with <emphasis>
+ <property>"PK"</property>
+ </emphasis> into a property named <emphasis>
+ <property>"id"</property>
+ </emphasis>.</para>
<programlisting><![CDATA[public class ExampleStrategy extends DelegatingReverseEngineeringStrategy {
@@ -701,23 +680,21 @@
<section>
<title>Custom Database Metadata</title>
- <para>By default the reverse engineering is performed by reading using the
- JDBC database metadata API. This is done via the class
- <emphasis>
- <property>org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect</property></emphasis>
- which is an implementation of
- <emphasis>
- <property>org.hibernate.cfg.reveng.dialect.MetaDataDialect</property></emphasis>.</para>
+ <para>By default the reverse engineering is performed by reading using the JDBC database
+ metadata API. This is done via the class <emphasis>
+ <property>org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect</property>
+ </emphasis> which is an implementation of <emphasis>
+ <property>org.hibernate.cfg.reveng.dialect.MetaDataDialect</property>
+ </emphasis>.</para>
- <para>The default implementation can be replaced with an alternative
- implementation by setting the property
- <emphasis>
- <property>hibernatetool.metadatadialect</property></emphasis> to a fully qualified
- classname for a class that implements
- <property>JDBCMetaDataDialect</property>.</para>
+ <para>The default implementation can be replaced with an alternative implementation by setting
+ the property <emphasis>
+ <property>hibernatetool.metadatadialect</property>
+ </emphasis> to a fully qualified classname for a class that implements
+ <property>JDBCMetaDataDialect</property>.</para>
- <para>This can be used to provide database specific optimized metadata
- reading. If you create an optimized/better metadata reading for your
- database it will be a very welcome contribution.</para>
+ <para>This can be used to provide database specific optimized metadata reading. If you create an
+ optimized/better metadata reading for your database it will be a very welcome
+ contribution.</para>
</section>
-</chapter>
\ No newline at end of file
+</chapter>
16 years, 5 months
- 1
- 0
JBoss Tools SVN: r5659 - in trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test: src/org/jboss/tools/jsf/vpe/richfaces/test and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: dsakovich
Date: 2008-01-13 10:10:49 -0500 (Sun, 13 Jan 2008)
New Revision: 5659
Added:
trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/resources/richFacesTest/WebContent/pages/components/componentControl.xhtml
Modified:
trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/resources/richFacesTest/WebContent/pages/components/richFacesTest.xhtml
trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/src/org/jboss/tools/jsf/vpe/richfaces/test/RichFacesComponentTest.java
Log:
http://jira.jboss.com/jira/browse/JBIDE-1582
Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/resources/richFacesTest/WebContent/pages/components/componentControl.xhtml
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/resources/richFacesTest/WebContent/pages/components/componentControl.xhtml (rev 0)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/resources/richFacesTest/WebContent/pages/components/componentControl.xhtml 2008-01-13 15:10:49 UTC (rev 5659)
@@ -0,0 +1,15 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:a4j="http://richfaces.org/a4j"
+ xmlns:rich="http://richfaces.org/rich">
+
+<head>
+</head>
+<body>
+ <h:inputText value="#{user}" id="inputText"/>
+ <rich:componentControl for="inputText" attachTo="link" operation="show" event="onclick"/>
+</body>
+</html>
\ No newline at end of file
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/resources/richFacesTest/WebContent/pages/components/richFacesTest.xhtml
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/resources/richFacesTest/WebContent/pages/components/richFacesTest.xhtml 2008-01-13 14:45:48 UTC (rev 5658)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/resources/richFacesTest/WebContent/pages/components/richFacesTest.xhtml 2008-01-13 15:10:49 UTC (rev 5659)
@@ -534,8 +534,10 @@
<h:outputText value="Modal Panel Title" />
</f:facet>
</rich:modalPanel>
+
+ <!-- componentControl -->
+ <rich:componentControl for="mp" attachTo="link" operation="show" event="onclick"/>
-
</a4j:form>
</body>
</html>
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/src/org/jboss/tools/jsf/vpe/richfaces/test/RichFacesComponentTest.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/src/org/jboss/tools/jsf/vpe/richfaces/test/RichFacesComponentTest.java 2008-01-13 14:45:48 UTC (rev 5658)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.richfaces.test/src/org/jboss/tools/jsf/vpe/richfaces/test/RichFacesComponentTest.java 2008-01-13 15:10:49 UTC (rev 5659)
@@ -196,5 +196,10 @@
performTestForVpeComponent((IFile) TestUtil.getComponentPath(
"components/virtualEarth.xhtml", IMPORT_PROJECT_NAME)); // $NON-NLS-1$
}
+
+ public void testComponentControl() throws PartInitException, Throwable {
+ performTestForVpeComponent((IFile) TestUtil.getComponentPath(
+ "components/componentControl.xhtml", IMPORT_PROJECT_NAME)); // $NON-NLS-1$
+ }
}
16 years, 5 months
- 1
- 0
JBoss Tools SVN: r5658 - trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/templates.
by jbosstools-commits＠lists.jboss.org
Author: dsakovich
Date: 2008-01-13 09:45:48 -0500 (Sun, 13 Jan 2008)
New Revision: 5658
Modified:
trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/templates/vpe-templates-richfaces.xml
Log:
http://jira.jboss.com/jira/browse/JBIDE-1582
Modified: trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/templates/vpe-templates-richfaces.xml
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/templates/vpe-templates-richfaces.xml 2008-01-12 17:06:36 UTC (rev 5657)
+++ trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/templates/vpe-templates-richfaces.xml 2008-01-13 14:45:48 UTC (rev 5658)
@@ -605,6 +605,14 @@
</span>
</vpe:template>
</vpe:tag>
+
+ <vpe:tag name="rich:componentControl" case-sensitive="yes">
+ <vpe:template children="no" modify="yes">
+ <span style="display:none">
+ </span>
+ </vpe:template>
+ </vpe:tag>
+
<vpe:tag name="rich:insert" case-sensetive="yes">
<vpe:template children="yes" modify="yes" class="org.jboss.tools.jsf.vpe.richfaces.template.RichFacesInsertTemplate">
16 years, 5 months
- 1
- 0
JBoss Tools SVN: r5657 - trunk/seam/docs/reference/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2008-01-12 12:06:36 -0500 (Sat, 12 Jan 2008)
New Revision: 5657
Modified:
trunk/seam/docs/reference/en/modules/creating_new_seam.xml
trunk/seam/docs/reference/en/modules/intro.xml
Log:
http://jira.jboss.com/jira/browse/JBDS-234 - making changes according to Sveta remarks
Modified: trunk/seam/docs/reference/en/modules/creating_new_seam.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/creating_new_seam.xml 2008-01-12 17:05:08 UTC (rev 5656)
+++ trunk/seam/docs/reference/en/modules/creating_new_seam.xml 2008-01-12 17:06:36 UTC (rev 5657)
@@ -11,8 +11,8 @@
<title>Creating a New Seam Project via the New Seam Project wizard</title>
<para>In this chapter we provide you with the necessary steps to start working with Seam
Framework.</para>
- <para>At first, we suggest browsing the specific Seam perspective.</para>
- <para>For that select <emphasis>
+ <para>At first, we suggest setting the specific Seam perspective that provides a necessary type
+ of functionality. For that select <emphasis>
<property>Window > Open Perspective > Other > Seam</property>
</emphasis> or you can also access it through the button in the right top corner.</para>
@@ -31,14 +31,14 @@
experiment with it by creating variations.</para>
<para>Thus, you should select <emphasis>
<property>File > New > Seam Web Project</property>
- </emphasis> to run the <property>New Seam Project</property> wizard.</para>
- <para>It's necessary to enter a name and a location directory for your new project. The next
- wizard forms allow you to create runtime and server instances in order to get started
- creating, running, and debugging J2EE applications.</para>
+ </emphasis> to run the <property>New Seam Project</property> wizard. It's necessary to
+ enter a name and a location directory for your new project. The next wizard forms allow
+ you to create runtime and server instances in order to get started creating, running,
+ and debugging J2EE applications.</para>
<para>Seam Web Project wizard has an option for selecting the actual Server (not just WTP
runtime) that will be used for the project. This allows the wizard to identify correctly
where the required datasource and driver libraries need to go.</para>
-
+ <para>Let's get through the wizard step-by-step. First, you should type the name of your new project.</para>
<figure>
<title>New Seam Project Wizard</title>
<mediaobject>
@@ -51,14 +51,15 @@
<para>Clicking on <emphasis>
<property>New...</property>
- </emphasis> button in the Target Runtime section brings us to another dialog. Here, you can
- specify a new installed Runtime environment or the other type of runtime appropriate for
- configuring your project. Let's create a JBoss 4.2 Runtime. For that after choosing it click on <emphasis>
+ </emphasis> button in the Target Runtime section brings us to another dialog. Here, you
+ can specify a new installed Runtime environment or the other type of runtime appropriate
+ for configuring your project. Let's create a JBoss 4.2 Runtime. For that after choosing
+ it click on <emphasis>
<property>Next</property>
</emphasis> button.</para>
<figure>
- <title>New Server Runtime Dialog</title>
+ <title>Specifying Target Runtime</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/create_new_seam/create_seam2.png"/>
@@ -66,16 +67,14 @@
</mediaobject>
</figure>
- <para>All what you need here is to name runtime, type or locate using <emphasis>
- <property>Browse</property></emphasis> button the path to its install directory, select a
- Java Runtime Environment, and select which configuration you want. Clicking on <emphasis>
- <property>Finish</property>
- </emphasis> returns you to the previous dialog. The next step is to define an installed server. You can do it by clicking on <emphasis>
- <property>New...</property>
- </emphasis> button in the Target section. </para>
+ <para>All what you need here is to name runtime, type the path to its install directory or
+ locate it by using <emphasis>
+ <property>Browse</property>
+ </emphasis> button, select a Java Runtime Environment, and select which configuration
+ you want.</para>
<figure>
- <title>New Server Runtime Dialog</title>
+ <title>Specifying Target Server Runtime</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/create_new_seam/create_seam3.png"/>
@@ -83,13 +82,21 @@
</mediaobject>
</figure>
- <para>It's possible to select a server version and a
- server runtime. Use <emphasis>
- <property>Installed Runtimes</property>
- </emphasis> button to see or edit what runtimes are installed. Click on Next</para>
+ <para> Clicking on <emphasis>
+ <property>Finish</property>
+ </emphasis> returns you to the previous dialog. The next step is to define an installed
+ server that you can do by clicking on <emphasis>
+ <property>New...</property>
+ </emphasis> button in the Target Server section. In appeared Server Dialog it's possible
+ to select a server version. For jBoss AS 4.2 it's also possible to indicate a server
+ runtime. Use <emphasis>
+ <property>Installed Runtimes...</property>
+ </emphasis> button to see or edit what runtimes are installed. Click on <emphasis>
+ <property>Next</property>
+ </emphasis>.</para>
<figure>
- <title>New Server Dialog</title>
+ <title>Specifying Target Server</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/create_new_seam/create_seam4.png"/>
@@ -97,7 +104,10 @@
</mediaobject>
</figure>
- <para>Leave everything as is and click on next.</para>
+ <para>Next dialog allows you to verify chosen Runtime information as well as set login
+ credentials and specify a deploy directory. Leave everything as it is and click on <emphasis>
+ <property>Next</property>
+ </emphasis>.</para>
<figure>
<title>New Server Dialog</title>
@@ -120,7 +130,9 @@
</figure>
- <para>After clicking on Finish button you should have the following wizard view:</para>
+ <para>After clicking on <emphasis>
+ <property>Finish</property>
+ </emphasis> button you should have the following wizard view:</para>
<figure>
<title>New Seam Project Creation</title>
@@ -132,8 +144,8 @@
</figure>
<para>The last section on this wizard step is <property>Configurations</property>. You can
- select one of the pre-defined project configuration or create your own. Click on
- <emphasis><property>Next</property>.</emphasis></para>
+ select one of the pre-defined project configurations or create your own. Having all needed options arranged click on
+ <emphasis><property>Next</property></emphasis> to pass on to the other wizard.</para>
</section>
<section id="projectFacets">
@@ -168,11 +180,13 @@
</mediaobject>
</figure>
+ <para><emphasis>
+ <property>Next</property>
+ </emphasis> button will bring you to the Web Module wizard.</para>
</section>
<section id="configureWebModule">
<title>How to Configure Web Module Settings</title>
-
<para>A dynamic web application contains both web pages and Java code. The wizard will ask
you where you want to put those files. You can just leave the default values.</para>
@@ -184,8 +198,9 @@
</imageobject>
</mediaobject>
</figure>
-
+
</section>
+
<section id="addJSFCapab">
<title>Adding JSF Capabilities</title>
@@ -207,8 +222,8 @@
button. You are able to create a library of jars by clicking on <emphasis>
<property>New</property>
</emphasis> button.</para>
- <para>Type a <property>Library Name</property>, select a <property>Version
- Supported</property> and add <property>Library jars</property>. Click on
+ <para>Here, it's necessary to type a <property>Library Name</property>, select a <property>Version
+ Supported</property> and add proper <property>Library jars</property>. Then click on
<emphasis><property>Finish</property>.</emphasis></para>
<figure>
<title>Create JSF Implementation Library</title>
@@ -235,7 +250,7 @@
<para>The last wizard options allows to edit a path for <property>JSF Configuration
File</property>, a name for <property>JSF Servlet</property>, <property>JSF Servlet
- Classname</property> and change an <property>URL Mapping Patterns</property>.</para>
+ Classname</property> and change <property>URL Mapping Patterns</property>.</para>
<figure>
<title>JSF Capabilities Wizard</title>
@@ -245,7 +260,6 @@
</imageobject>
</mediaobject>
</figure>
-
</section>
<section id="seamFacet">
Modified: trunk/seam/docs/reference/en/modules/intro.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/intro.xml 2008-01-12 17:05:08 UTC (rev 5656)
+++ trunk/seam/docs/reference/en/modules/intro.xml 2008-01-12 17:06:36 UTC (rev 5657)
@@ -24,7 +24,7 @@
<section>
<title>Other relevant resources on the topic</title>
- <para>On JBoss you can find a number of benefits and other extra information on the <ulink url="http://www.jboss.com/products/seam">Seam Framework</ulink>.</para>
+ <para>On JBoss you can find a set of benefits and other extra information on <ulink url="http://www.jboss.com/products/seam">Seam Framework</ulink>.</para>
</section>
</chapter>
16 years, 5 months
- 1
- 0
JBoss Tools SVN: r5656 - trunk/seam/docs/reference/en/images/create_new_seam.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2008-01-12 12:05:08 -0500 (Sat, 12 Jan 2008)
New Revision: 5656
Modified:
trunk/seam/docs/reference/en/images/create_new_seam/create_seam0.png
Log:
http://jira.jboss.com/jira/browse/JBDS-234 - making changes according to Sveta remarks
Modified: trunk/seam/docs/reference/en/images/create_new_seam/create_seam0.png
===================================================================
(Binary files differ)
16 years, 5 months
- 1
- 0
JBoss Tools SVN: r5655 - trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/src/org/jboss/tools/jsf/vpe/facelets/test.
by jbosstools-commits＠lists.jboss.org
Author: dsakovich
Date: 2008-01-12 11:50:41 -0500 (Sat, 12 Jan 2008)
New Revision: 5655
Modified:
trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/src/org/jboss/tools/jsf/vpe/facelets/test/FaceletsComponentTest.java
Log:
http://jira.jboss.com/jira/browse/JBIDE-1584
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/src/org/jboss/tools/jsf/vpe/facelets/test/FaceletsComponentTest.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/src/org/jboss/tools/jsf/vpe/facelets/test/FaceletsComponentTest.java 2008-01-12 16:27:13 UTC (rev 5654)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/src/org/jboss/tools/jsf/vpe/facelets/test/FaceletsComponentTest.java 2008-01-12 16:50:41 UTC (rev 5655)
@@ -219,13 +219,13 @@
*/
public void testDecorate() throws Throwable {
// check absolute path
- nsIDOMElement element = performTestForFaceletComponent("components/composition_absolute.xhtml");
+ nsIDOMElement element = performTestForFaceletComponent("components/decorate_absolute.xhtml");
checkTemplatePage(element, "Page Header",
"Template with absolute path is not included");
// check related path
- element = performTestForFaceletComponent("components/composition_related.xhtml");
+ element = performTestForFaceletComponent("components/decorate_related.xhtml");
checkTemplatePage(element, "Page Header",
"Template with related path is not included");
@@ -273,13 +273,13 @@
*/
public void testInclude() throws Throwable {
// check absolute path
- nsIDOMElement element = performTestForFaceletComponent("components/composition_absolute.xhtml");
+ nsIDOMElement element = performTestForFaceletComponent("components/include_absolute.xhtml");
checkTemplatePage(element, "Page Header",
"Template with absolute path is not included");
// check related path
- element = performTestForFaceletComponent("components/composition_related.xhtml");
+ element = performTestForFaceletComponent("components/include_related.xhtml");
checkTemplatePage(element, "Page Header",
"Template with related path is not included");
@@ -374,7 +374,7 @@
*/
public void testParam() throws Throwable {
// check absolute path
- nsIDOMElement element = performTestForFaceletComponent("components/composition_absolute.xhtml");
+ nsIDOMElement element = performTestForFaceletComponent("components/param.xhtml");
nsIDOMNode node = (nsIDOMNode) element
.queryInterface(nsIDOMNode.NS_IDOMNODE_IID);
16 years, 5 months
- 1
- 0
JBoss Tools SVN: r5654 - in trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test: src/org/jboss/tools/jsf/vpe/facelets/test and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: dsakovich
Date: 2008-01-12 11:27:13 -0500 (Sat, 12 Jan 2008)
New Revision: 5654
Modified:
trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/resources/faceletsTest/WebContent/pages/components/insert.xhtml
trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/resources/faceletsTest/WebContent/pages/components/param.xhtml
trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/src/org/jboss/tools/jsf/vpe/facelets/test/FaceletsComponentTest.java
Log:
http://jira.jboss.com/jira/browse/JBIDE-1584
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/resources/faceletsTest/WebContent/pages/components/insert.xhtml
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/resources/faceletsTest/WebContent/pages/components/insert.xhtml 2008-01-12 15:35:46 UTC (rev 5653)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/resources/faceletsTest/WebContent/pages/components/insert.xhtml 2008-01-12 16:27:13 UTC (rev 5654)
@@ -38,7 +38,7 @@
</td>
</tr>
<tr>
- <td height="1" width="100%" bgcolor="#CAD6E0"></td>
+ <td height="1" width="100%" bgcolor="#CAD6E0" align="center">#{user}</td>
</tr>
<tr>
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/resources/faceletsTest/WebContent/pages/components/param.xhtml
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/resources/faceletsTest/WebContent/pages/components/param.xhtml 2008-01-12 15:35:46 UTC (rev 5653)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/resources/faceletsTest/WebContent/pages/components/param.xhtml 2008-01-12 16:27:13 UTC (rev 5654)
@@ -10,8 +10,7 @@
<body bgcolor="#ffffff">
<ui:include src="insert.xhtml">
- <ui:param name="user" value="#{currentUser}" />
- <ui:param name="page" value="home"/>
+ <ui:param name="user" value="#{currentUser}" />
</ui:include>
</body>
</html>
\ No newline at end of file
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/src/org/jboss/tools/jsf/vpe/facelets/test/FaceletsComponentTest.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/src/org/jboss/tools/jsf/vpe/facelets/test/FaceletsComponentTest.java 2008-01-12 15:35:46 UTC (rev 5653)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.facelets.test/src/org/jboss/tools/jsf/vpe/facelets/test/FaceletsComponentTest.java 2008-01-12 16:27:13 UTC (rev 5654)
@@ -23,6 +23,7 @@
import org.mozilla.interfaces.nsIDOMDocument;
import org.mozilla.interfaces.nsIDOMElement;
import org.mozilla.interfaces.nsIDOMNode;
+import org.mozilla.interfaces.nsIDOMNodeList;
import org.mozilla.interfaces.nsIDOMText;
/**
@@ -95,20 +96,26 @@
// find "span" elements
TestUtil.findElementsByName(node, elements, HTML.TAG_SPAN);
- assertEquals(2, elements.size());
+ assertEquals(3, elements.size());
nsIDOMElement elementSpan0 = (nsIDOMElement) elements.get(0)
.queryInterface(nsIDOMElement.NS_IDOMELEMENT_IID);
nsIDOMElement elementSpan1 = (nsIDOMElement) elements.get(1)
.queryInterface(nsIDOMElement.NS_IDOMELEMENT_IID);
+ nsIDOMElement elementSpan2 = (nsIDOMElement) elements.get(2)
+ .queryInterface(nsIDOMElement.NS_IDOMELEMENT_IID);
nsIDOMText text0 = (nsIDOMText) elementSpan0.getFirstChild()
.queryInterface(nsIDOMText.NS_IDOMTEXT_IID);
nsIDOMText text1 = (nsIDOMText) elementSpan1.getFirstChild()
.queryInterface(nsIDOMText.NS_IDOMTEXT_IID);
+ nsIDOMText text2 = (nsIDOMText) elementSpan2.getFirstChild()
+ .queryInterface(nsIDOMText.NS_IDOMTEXT_IID);
assertEquals("Defined content is not shown", text0.getNodeValue(),
"Greeting Page");
assertEquals("Defined content is not shown", text1.getNodeValue(),
+ "#{user}");
+ assertEquals("Defined content is not shown", text2.getNodeValue(),
"#{person.name}!");
if (getException() != null) {
@@ -250,7 +257,7 @@
nsIDOMElement elementDT = (nsIDOMElement) elementDL.getFirstChild()
.queryInterface(nsIDOMElement.NS_IDOMELEMENT_IID);
-
+
assertEquals("Component's content is not shown", HTML.TAG_DT, elementDT
.getNodeName().toUpperCase());
@@ -360,6 +367,53 @@
return element;
}
+ /**
+ * Test for ui:param
+ *
+ * @throws Throwable
+ */
+ public void testParam() throws Throwable {
+ // check absolute path
+ nsIDOMElement element = performTestForFaceletComponent("components/composition_absolute.xhtml");
+
+ nsIDOMNode node = (nsIDOMNode) element
+ .queryInterface(nsIDOMNode.NS_IDOMNODE_IID);
+
+ List<nsIDOMNode> elements = new ArrayList<nsIDOMNode>();
+
+ // find "table" elements
+ TestUtil.findElementsByName(node, elements, HTML.TAG_TABLE);
+
+ assertEquals("Component's content is not shown", 1, elements.size());
+
+ nsIDOMElement table = (nsIDOMElement) elements.get(0).queryInterface(
+ nsIDOMElement.NS_IDOMELEMENT_IID);
+ nsIDOMElement tbody = (nsIDOMElement) table.getFirstChild()
+ .queryInterface(nsIDOMElement.NS_IDOMELEMENT_IID);
+
+ nsIDOMNodeList list = tbody.getChildNodes();
+
+ assertEquals("Component's content is not shown", 4, list.getLength());
+
+ nsIDOMElement tr = (nsIDOMElement) list.item(1).queryInterface(
+ nsIDOMElement.NS_IDOMELEMENT_IID);
+
+ nsIDOMElement td = (nsIDOMElement) tr.getFirstChild().queryInterface(
+ nsIDOMElement.NS_IDOMELEMENT_IID);
+ nsIDOMElement span = (nsIDOMElement) td.getFirstChild().queryInterface(
+ nsIDOMElement.NS_IDOMELEMENT_IID);
+
+ nsIDOMText text = (nsIDOMText) span.getFirstChild().queryInterface(
+ nsIDOMText.NS_IDOMTEXT_IID);
+
+ assertEquals("Component's content is not shown", text.getNodeValue(),
+ "#{currentUser}");
+
+ if (getException() != null) {
+ throw getException();
+ }
+ }
+
private void checkTemplatePage(nsIDOMElement element, String contextString,
String message) {
nsIDOMNode node = (nsIDOMNode) element
16 years, 5 months
- 1
- 0