JBoss Tools SVN: r4825 - in trunk/jsf/docs/jbossjsftools/userguide/en: modules and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: afedosik
Date: 2007-11-09 10:17:04 -0500 (Fri, 09 Nov 2007)
New Revision: 4825
Added:
trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/CAJSFComp.png
trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/CAJSFCompAttr.png
trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/JSFCCodeAssist.png
Removed:
trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/JFSCCodeAssist.png
trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/JSFComponentCodeAssist.png
Modified:
trunk/jsf/docs/jbossjsftools/userguide/en/modules/JavaServerFacesSupport.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-260 Code assist for Facelets update
Added: trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/CAJSFComp.png
===================================================================
(Binary files differ)
Property changes on: trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/CAJSFComp.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/CAJSFCompAttr.png
===================================================================
(Binary files differ)
Property changes on: trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/CAJSFCompAttr.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/JFSCCodeAssist.png
===================================================================
(Binary files differ)
Added: trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/JSFCCodeAssist.png
===================================================================
(Binary files differ)
Property changes on: trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/JSFCCodeAssist.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: trunk/jsf/docs/jbossjsftools/userguide/en/images/JSFSupport/JSFComponentCodeAssist.png
===================================================================
(Binary files differ)
Modified: trunk/jsf/docs/jbossjsftools/userguide/en/modules/JavaServerFacesSupport.xml
===================================================================
--- trunk/jsf/docs/jbossjsftools/userguide/en/modules/JavaServerFacesSupport.xml 2007-11-09 14:25:14 UTC (rev 4824)
+++ trunk/jsf/docs/jbossjsftools/userguide/en/modules/JavaServerFacesSupport.xml 2007-11-09 15:17:04 UTC (rev 4825)
@@ -109,23 +109,46 @@
</imageobject>
</mediaobject>
</figure>
-<para>You also get code assist for <emphasis role="italic"><property>"jsfc"</property></emphasis> attribute in any HTML tag and then for JSF components:</para>
-<figure>
+
+ <itemizedlist>
+ <listitem><para>In any HTML tag you also get the code assist for <emphasis role="italic"><property>"jsfc"</property></emphasis> attribute</para></listitem>
+ </itemizedlist>
+
+ <figure>
<title>Code Assist for Jsfc Attribute</title>
<mediaobject>
<imageobject>
- <imagedata fileref="images/JSFSupport/JFSCCodeAssist.png"/>
+ <imagedata fileref="images/JSFSupport/JSFCCodeAssist.png"/>
</imageobject>
</mediaobject>
-</figure>
+ </figure>
+
+ <itemizedlist>
+ <listitem><para>Then you get the code assist for JSF components are available on the page</para></listitem>
+ </itemizedlist>
+
<figure>
<title>Code Assist for JSF Components</title>
<mediaobject>
<imageobject>
- <imagedata fileref="images/JSFSupport/JSFComponentCodeAssist.png"/>
+ <imagedata fileref="images/JSFSupport/CAJSFComp.png"/>
</imageobject>
</mediaobject>
</figure>
+
+ <itemizedlist>
+ <listitem><para>Then you will see all available attributes for the component.</para></listitem>
+ </itemizedlist>
+
+ <figure>
+ <title></title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/JSFSupport/CAJSFCompAttr.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
<para>Using Red Hat Developer Studio OpenOn feature, you can easily navigate between the <property>Facelets
templates</property> and other parts of your projects. Just by holding down the Control key while hovering the
mouse cursor over a reference to a template, the reference becomes a hyperlink to open that template.</para>
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4823 - trunk/jsf/docs/jbossjsftools/userguide/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: afedosik
Date: 2007-11-09 09:15:23 -0500 (Fri, 09 Nov 2007)
New Revision: 4823
Modified:
trunk/jsf/docs/jbossjsftools/userguide/en/modules/EditorsFeatures.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-263 "Adding dynamic code assist to custom components..." section updated.
Modified: trunk/jsf/docs/jbossjsftools/userguide/en/modules/EditorsFeatures.xml
===================================================================
--- trunk/jsf/docs/jbossjsftools/userguide/en/modules/EditorsFeatures.xml 2007-11-09 13:47:25 UTC (rev 4822)
+++ trunk/jsf/docs/jbossjsftools/userguide/en/modules/EditorsFeatures.xml 2007-11-09 14:15:23 UTC (rev 4823)
@@ -433,58 +433,42 @@
<para>Here is what you need to do to add project based code assist to a custom component added in
Red Hat Developer Studio:</para>
<orderedlist>
-<listitem><para>Create a new file in
- <emphasis><property>RedHatDeveloperStudio > eclipse > plugins > com.exadel.prompting.knowledgebase_7.1.0 > schemas > tld</property></emphasis>. For example call it JeniaFaces.xml</para></listitem>
- </orderedlist>
-<para>Here is a sample code snipped that adds code assist to the component you mention above:</para>
-
-<programlisting role="Java"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
-<Schema location="" prefix="jdt" uri="http://www.jenia.org/jsf/dataTools">
- <ElementType bodyContent="refused" content="mixed" endTag="required"
- name="singleRowSelector" startTag="required">
- <AttributeType name="selection" required="true">
- <proposal type="jsfVariables"/>
- <proposal type="beanProperty">
- <param name="type" value="java.lang.String"/>
- </proposal>
- </AttributeType>
- <attribute type="selection"/>
- </ElementType>
-</Schema>
-]]></programlisting>
-<orderedlist continuation="continues">
-<listitem><para>Adds code assist for JSF pre-defined objects, such as value=<emphasis role="italic"><property>"#{param}"</property></emphasis>:</para></listitem>
+ <listitem><para>Create a new xml file in <emphasis><property><RHDS_home>rhds/eclipse/plugins/org.jboss.tools.common.kb_***/schemas/tld/</property></emphasis>. For example call it JeniaFaces.xml. The file should be written according to <emphasis><property><RHDS_home>/rhds/eclipse/plugins/org.jboss.tools.common.kb/kb.jar/org/jboss/tools/common/kb/kb-schema_1.0.dtd</property></emphasis></para></listitem>
</orderedlist>
+ <para>Here is how you set what is available for code assist:</para>
+<itemizedlist>
+<listitem><para>Adds code assist for JSF pre-defined objects, such as value=<emphasis role="italic"><property>"#{param}"</property></emphasis>:</para></listitem>
+</itemizedlist>
<programlisting role="XML"><![CDATA[<AttributeType ...>
<proposal type="jsfVariables"/>
</AttributeType>
]]></programlisting>
-<orderedlist continuation="continues">
+ <itemizedlist>
<listitem><para>Adds bundle resource (property file) <property>code assist</property>:</para></listitem>
-</orderedlist>
+ </itemizedlist>
<programlisting role="XML"><![CDATA[<AttributeType ...>
<proposal type="bundleProperty"/>
</AttributeType>
]]></programlisting>
-<orderedlist continuation="continues">
+ <itemizedlist>
<listitem><para>Adds managed bean property <property>code assist</property>:</para></listitem>
-</orderedlist>
+ </itemizedlist>
<programlisting role="XML"><![CDATA[<AttributeType ...>
<proposal type="beanProperty"/>
</AttributeType>
]]></programlisting>
-<orderedlist continuation="continues">
+ <itemizedlist>
<listitem><para>Adds managed bean property but with a specified type:</para></listitem>
-</orderedlist>
+ </itemizedlist>
<programlisting role="XML"><![CDATA[<AttributeType ...>
<proposal type="beanProperty">
<param name="type" value="java.lang.Boolean"/>
</proposal>
</AttributeType>
]]></programlisting>
-<orderedlist continuation="continues">
+ <itemizedlist>
<listitem><para>Adds managed bean method with a signature:</para></listitem>
-</orderedlist>
+ </itemizedlist>
<programlisting role="XML"><![CDATA[<AttributeType ...>
<proposal type="beanMethodBySignature">
<param name="paramType" value="javax.faces.context.FacesContext"/>
@@ -494,8 +478,18 @@
</proposal>
</AttributeType>
]]></programlisting>
+ <orderedlist continuation="continues">
+ <listitem><para>Add information on your xml file in <emphasis><property><RHDS_home>/rhds/eclipse/plugins/org.jboss.common.kb_***/plugin.xml</property></emphasis></para></listitem>
+ </orderedlist>
+ <programlisting role="XML"><![CDATA[
+ <tld
+ jsf="true"
+ name="Jenia Faces"
+ schema-location="schemas/tld/myJSF.xml"
+ uri="http://www.jenia.org/jsf/dataTools"/>]]>
+ </programlisting>
<orderedlist continuation="continues">
-<listitem><para>Restart Eclipse. You should now have code assist for the component. The new XML file will be copied to the workspace.</para></listitem>
+<listitem><para>Restart Eclipse. You should now have code assist for the component.</para></listitem>
</orderedlist>
</section>
</section>
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4822 - in trunk/documentation/guides/userguide/Exadel-migration/en: images and 3 other directories.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2007-11-09 08:47:25 -0500 (Fri, 09 Nov 2007)
New Revision: 4822
Added:
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration1.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_2.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_21.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_3.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_4.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_5.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration3.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration4.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration5.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration1.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war1.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_1.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_2.png
trunk/documentation/guides/userguide/Exadel-migration/en/modules/introduction.xml
trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts.xml
trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts_war.xml
trunk/documentation/guides/userguide/Exadel-migration/en/modules/workspace.xml
Removed:
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration1.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_2.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_21.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_3.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_4.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_5.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration3.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration4.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration5.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war1.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2_1.png
trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2_2.png
trunk/documentation/guides/userguide/Exadel-migration/en/modules/intro_migration.xml
trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration.xml
trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_war.xml
trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_ws.xml
Modified:
trunk/documentation/guides/userguide/Exadel-migration/en/master.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-298 xml files names made shorter, used only lower case and _ to seperate words + new structure for images folders
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration1.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_2.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_21.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_21.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_3.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_4.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_5.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration3.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration4.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration5.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration1.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war1.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_1.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_2.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration1.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_2.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_21.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_3.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_4.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_5.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration3.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration4.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration5.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war1.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2_1.png
===================================================================
(Binary files differ)
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2_2.png
===================================================================
(Binary files differ)
Modified: trunk/documentation/guides/userguide/Exadel-migration/en/master.xml
===================================================================
--- trunk/documentation/guides/userguide/Exadel-migration/en/master.xml 2007-11-09 12:09:16 UTC (rev 4821)
+++ trunk/documentation/guides/userguide/Exadel-migration/en/master.xml 2007-11-09 13:47:25 UTC (rev 4822)
@@ -2,10 +2,10 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN"
"../../../resources/support/docbook-dtd/docbookx.dtd"
-[<!ENTITY migration SYSTEM "modules/migration.xml">
-<!ENTITY migrationwar SYSTEM "modules/migration_war.xml">
-<!ENTITY intro_migration SYSTEM "modules/intro_migration.xml">
-<!ENTITY migration_ws SYSTEM "modules/migration_ws.xml">
+[<!ENTITY jsf_struts SYSTEM "modules/jsf_struts.xml">
+<!ENTITY jsf_struts_war SYSTEM "modules/jsf_struts_war.xml">
+<!ENTITY introduction SYSTEM "modules/introduction.xml">
+<!ENTITY workspace SYSTEM "modules/workspace.xml">
]>
<book>
@@ -21,10 +21,10 @@
</bookinfo>
<toc/>
-&intro_migration;
-&migration_ws;
-&migration;
-&migrationwar;
+&introduction;
+&workspace;
+&jsf_struts;
+&jsf_struts_war;
</book>
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/modules/intro_migration.xml
===================================================================
--- trunk/documentation/guides/userguide/Exadel-migration/en/modules/intro_migration.xml 2007-11-09 12:09:16 UTC (rev 4821)
+++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/intro_migration.xml 2007-11-09 13:47:25 UTC (rev 4822)
@@ -1,17 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="intro_migration" xreflabel="intro_migration">
- <?dbhtml filename="intro_migration.html"?>
- <chapterinfo>
- <keywordset>
- <keyword>Red Hat Developer Studio</keyword>
- <keyword>RHDS</keyword>
- <keyword>Exadel Studio Pro</keyword>
- </keywordset>
- </chapterinfo>
-
- <title>Introduction</title>
- <para>This document is intended to help you to migrate an existing Exadel JSF or Struts projects
- into <property>Red Hat Developer Studio</property>. Preferences can be exported from Eclipse 3.2.0 (3.2.1 or 3.2.2) and imported in Eclipse 3.3 by the standard Eclipse means.
- </para>
-
- </chapter>
Added: trunk/documentation/guides/userguide/Exadel-migration/en/modules/introduction.xml
===================================================================
--- trunk/documentation/guides/userguide/Exadel-migration/en/modules/introduction.xml (rev 0)
+++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/introduction.xml 2007-11-09 13:47:25 UTC (rev 4822)
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="introduction" xreflabel="introduction">
+ <?dbhtml filename="introduction.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>Red Hat Developer Studio</keyword>
+ <keyword>RHDS</keyword>
+ <keyword>Exadel Studio Pro</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Introduction</title>
+ <para>This document is intended to help you to migrate an existing Exadel JSF or Struts projects
+ into <property>Red Hat Developer Studio</property>. Preferences can be exported from Eclipse 3.2.0 (3.2.1 or 3.2.2) and imported in Eclipse 3.3 by the standard Eclipse means.
+ </para>
+
+ </chapter>
Added: trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts.xml
===================================================================
--- trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts.xml (rev 0)
+++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts.xml 2007-11-09 13:47:25 UTC (rev 4822)
@@ -0,0 +1,182 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="jsf_struts" xreflabel="jsf_struts">
+ <?dbhtml filename="jsf_struts.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>Red Hat Developer Studio</keyword>
+ <keyword>RHDS</keyword>
+ <keyword>Exadel Studio Pro</keyword>
+ <keyword>Migration</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Migration of JSF and Struts Projects</title>
+ <section>
+ <title>JSF</title>
+ <para>Red Hat Developer Studio includes an Import <property>JSF Project</property> Wizard that radically simplifies the process of bringing your existing JSF applications
+ into your Red Hat Developer Studio workspace as JSF projects. You just need to follow these four steps:</para>
+ <orderedlist>
+ <listitem><para><emphasis><property>Select File > Import...</property></emphasis> from the menu bar, and then select <emphasis><property>Other > JSF Project </property></emphasis>from the Import dialog box that appears.</para></listitem>
+ </orderedlist>
+
+ <figure>
+ <title>Selecting the Import Menu Item</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts/migration1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <figure>
+ <title>Selecting the Import JSF Project Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts/migration2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <orderedlist continuation="continues">
+ <listitem><para>In the first screen of the wizard, select the <emphasis><property>Change...</property></emphasis> button next to the web.xml Location field. Browse to the location of the web.xml file for the application you
+ want to import as a <property>JSF project</property>. Once you select it, you'll be returned to the dialog box to see a project name derived from the web.xml file you selected.
+ You can edit this project name, if you wish.</para></listitem>
+ </orderedlist>
+
+ <figure>
+ <title>Selecting the Web.xml File in the The Project Location Screen</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts/migration3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <orderedlist continuation="continues">
+ <listitem><para>In the <emphasis><property>Project Folders</property></emphasis> screen, you can configure the rest of your project. Afterwards click on the <emphasis><property>Finish</property></emphasis> button.</para></listitem>
+ </orderedlist>
+ <para>On this step Red Hat Developer Studio will try to determine your project
+ structure and set the values for: <emphasis><property>Web Root</property></emphasis>, <emphasis><property>Source Folder</property></emphasis>, <emphasis><property>Classes Folder</property></emphasis>, <emphasis><property>Lib Folder</property></emphasis>. If your project has a custom structure, some values might not be
+ set. If this is the case, you can manually set those values by clicking the <emphasis><property>Change...</property></emphasis> button.</para>
+ <para>After dealing with these settings, you have to work through a few more configuration settings. These settings deal primarily with how the project will be deployed within Red Hat Developer Studio.</para>
+ <para>First, if the project you are importing is not already a JSF project, select the <emphasis><property>Add Libraries</property></emphasis> check box to add all the JSF-related libraries to your project. </para>
+ <para>Then, you may select the JavaServer Faces implementation (<emphasis><property>Environment</property></emphasis>) and <emphasis><property>Servlet Version</property></emphasis>.</para>
+ <para>The <emphasis><property>Context Path</property></emphasis> is the name under which the application will be deployed. </para>
+ <para>The <emphasis><property>Runtime</property></emphasis> value tells Eclipse where to find Web libraries in order to build the project. It is not possible to finish the importing of a project without selecting a Runtime. If you don't have any choices displayed for this, select <emphasis><property>New...</property></emphasis> to add a new Runtime.</para>
+ <para>Finally, <emphasis><property>Target Server</property></emphasis> sets the server to deploy the application under. The Target Server corresponds to the Runtime value selected above. If you don't want to deploy the application, uncheck this value.</para>
+
+
+ <figure>
+ <title>The Project Folders Screen</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts/migration4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <orderedlist continuation="continues">
+ <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem>
+ </orderedlist>
+
+ <figure>
+ <title>Imported Project in the Package Explorer View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts/migration5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+ <section>
+ <title>Struts</title>
+ <orderedlist>
+ <listitem><para><emphasis><property>Select File > Import...</property></emphasis> from the menu bar, and then select <emphasis><property>Other > Struts Project</property></emphasis> from the Import dialog box that appears.</para></listitem>
+ </orderedlist>
+
+ <figure>
+ <title>Selecting the Import Menu Item</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts/migration1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <figure>
+ <title>Selecting the Import Struts Project Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts/migration2_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <orderedlist continuation="continues">
+ <listitem><para>In the Project Location screen of the wizard, select the <emphasis><property>Change... </property></emphasis>button next to the web.xml Location field. Browse the location of the web.xml file for the application you
+ want to import as a <property>Struts project</property>. Once you select it, you'll be returned to the dialog box to see a project name derived from the web.xml file you selected.
+ You can edit this project name, if you wish.</para></listitem>
+ </orderedlist>
+
+ <figure>
+ <title>The Project Location Screen</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts/migration2_21.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <orderedlist continuation="continues">
+ <listitem><para>In the next screen, Red Hat Developer Studio will try to determine your project structure. The upper pane shows the modules in this project.
+ The lower pane allows you to edit the details of the select module. If the project structure is non-standard, some values might be left blank.
+ You can edit any values by hand or by using the <emphasis><property>Change...</property></emphasis> button.</para></listitem>
+ </orderedlist>
+
+ <figure>
+ <title>The Project Modules Screen</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts/migration2_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <orderedlist continuation="continues">
+ <listitem><para>In the <emphasis><property>Project Folders</property></emphasis> screen, you can configure the rest of your project. Afterwards click on the <emphasis><property>Finish</property></emphasis> button.</para>
+ </listitem>
+ </orderedlist>
+ <para>On this step Red Hat Developer Studio will try to determine your project structure and set the values for: <emphasis><property>Classes Folder</property></emphasis>, <emphasis><property>Lib Folder</property></emphasis>, and <emphasis><property>Ant Build File</property></emphasis>. If your project has a custom structure, some values might not be set. If this is the case, you can manually set those values by clicking <emphasis><property>Change</property></emphasis>.</para>
+ <para>After dealing with these settings, you have to work through a few more configuration settings. These settings deal primarily with how the project will be deployed within Red Hat Developer Studio.</para>
+ <para>First, if the project you are importing is not already a Struts project, select the <emphasis><property>Add Libraries</property></emphasis> check box to add all the Struts-related libraries to your project. </para>
+ <para>Then, you may select the Struts <emphasis><property>Environment</property></emphasis> and <emphasis><property>Servlet Version</property></emphasis>.</para>
+ <para>The <emphasis><property>Context Path</property></emphasis> is the name under which the application will be deployed. </para>
+ <para>The <emphasis><property>Runtime</property></emphasis> value tells Eclipse where to find Web libraries in order to build the project. It is not possible to finish the importing of a project without selecting a Runtime. If you don't have any choices displayed for this, select<emphasis><property> New...</property></emphasis> to add a new Runtime.</para>
+ <para>Finally, <emphasis><property>Target Server</property></emphasis> sets the server to deploy the application under. The Target Server corresponds to the Runtime value selected above. If you don't want to deploy the application, uncheck this value.</para>
+
+
+ <figure>
+ <title>The Project Folders Screen</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts/migration2_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <orderedlist continuation="continues">
+ <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem>
+ </orderedlist>
+
+ <figure>
+ <title>Imported Project in the Package Explorer View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts/migration2_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+</chapter>
Added: trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts_war.xml
===================================================================
--- trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts_war.xml (rev 0)
+++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts_war.xml 2007-11-09 13:47:25 UTC (rev 4822)
@@ -0,0 +1,148 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="jsf_struts_war" xreflabel="jsf_struts_war">
+ <?dbhtml filename="jsf_struts_war.html"?>
+
+ <chapterinfo>
+ <keywordset>
+ <keyword>Red Hat Developer Studio</keyword>
+
+ <keyword>RHDS</keyword>
+
+ <keyword>Exadel Studio Pro</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Migrate JSF and Struts projects from *.war file</title>
+
+ <section>
+ <title>JSF</title>
+
+ <orderedlist>
+ <listitem>
+ <para>Select <emphasis><property>File > Import...</property></emphasis> from the menu bar, and then select
+ <emphasis><property>Other > JSF Project From *.war</property></emphasis> from the Import dialog box that
+ appears.</para>
+ </listitem>
+ </orderedlist>
+
+ <figure>
+ <title>Selecting the Import Menu Item</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts_war/migration1.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <figure>
+ <title>Selecting the JSF Project From *.war Import Wizard</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts_war/migration_war1.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <orderedlist continuation="continues">
+ <listitem>
+ <para>In the wizard screen, select the <emphasis><property>Change...</property></emphasis> button next to
+ the <emphasis><property>*.war Location</property></emphasis> field. Browse to the location of the *.war file for
+ the application you want to import as a JSF project. Once you select
+ it, you'll be returned to the dialog box to see a project name
+ derived from the *.war file you selected. You can edit this name, if
+ you wish.</para>
+
+ <para>Uncheck the <emphasis><property>Use Default Path</property></emphasis> check box if you want to import
+ your project outside of the Eclipse workspace. In this case, you would
+ use <emphasis><property> Change... </property></emphasis> button next to the <emphasis><property>Location</property></emphasis> field to choose a
+ location.</para>
+
+ <para><emphasis><property>Context Path</property></emphasis> is the name under which the application will be
+ deployed.</para>
+
+ <para>The <emphasis><property>Runtime</property></emphasis> value tells Eclipse where to find Web libraries in
+ order to build the project. It is not possible to finish project
+ import without selecting Runtime. If you don't have any options
+ here, select <emphasis><property>New...</property></emphasis> to add a new Runtime.</para>
+
+ <para>Finally, <emphasis><property>Target Server</property></emphasis> sets the server to deploy the application
+ under. The Target Server corresponds to the Runtime value selected
+ above. If you don't want to deploy the application, uncheck this
+ value.</para>
+ </listitem>
+ </orderedlist>
+
+ <figure>
+ <title>The JSF Project From *.war Import Wizard</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts_war/migration_war2.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <orderedlist continuation="continues">
+ <listitem>
+ <para>Click on the <emphasis><property>Finish</property></emphasis> button.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+
+ <section>
+ <title>Struts</title>
+
+ <orderedlist>
+ <listitem>
+ <para>Select <emphasis><property>File > Import...</property></emphasis> from the menu bar, and then select
+ <emphasis><property>Other > Struts Project From *.war</property></emphasis> from the Import dialog box that
+ appears.</para>
+ </listitem>
+ </orderedlist>
+
+ <figure>
+ <title>Selecting the Import Menu Item</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts_war/migration1.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <figure>
+ <title>Selecting the Struts Project From *.war Import Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts_war/migration_war2_1.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <orderedlist continuation="continues">
+ <listitem>
+ <para>Follow the same steps as with the JSF Project From <property>*.war</property> import
+ wizard.</para>
+ </listitem>
+ </orderedlist>
+
+ <figure>
+ <title>The Struts Project From *.war Import Wizard</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_struts_war/migration_war2_2.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <orderedlist continuation="continues">
+ <listitem>
+ <para>Click on the <emphasis><property>Finish</property></emphasis> button.</para>
+ </listitem>
+ </orderedlist>
+ <para>The migration process is completed</para>
+ </section>
+</chapter>
\ No newline at end of file
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration.xml
===================================================================
--- trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration.xml 2007-11-09 12:09:16 UTC (rev 4821)
+++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration.xml 2007-11-09 13:47:25 UTC (rev 4822)
@@ -1,182 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="RHDS_migration" xreflabel="RHDS_migration">
- <?dbhtml filename="RHDS_migration.html"?>
- <chapterinfo>
- <keywordset>
- <keyword>Red Hat Developer Studio</keyword>
- <keyword>RHDS</keyword>
- <keyword>Exadel Studio Pro</keyword>
- <keyword>Migration</keyword>
- </keywordset>
- </chapterinfo>
-
- <title>Migration of JSF and Struts Projects</title>
- <section>
- <title>JSF</title>
- <para>Red Hat Developer Studio includes an Import <property>JSF Project</property> Wizard that radically simplifies the process of bringing your existing JSF applications
- into your Red Hat Developer Studio workspace as JSF projects. You just need to follow these four steps:</para>
- <orderedlist>
- <listitem><para><emphasis><property>Select File > Import...</property></emphasis> from the menu bar, and then select <emphasis><property>Other > JSF Project </property></emphasis>from the Import dialog box that appears.</para></listitem>
- </orderedlist>
-
- <figure>
- <title>Selecting the Import Menu Item</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <figure>
- <title>Selecting the Import JSF Project Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration2.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <orderedlist continuation="continues">
- <listitem><para>In the first screen of the wizard, select the <emphasis><property>Change...</property></emphasis> button next to the web.xml Location field. Browse to the location of the web.xml file for the application you
- want to import as a <property>JSF project</property>. Once you select it, you'll be returned to the dialog box to see a project name derived from the web.xml file you selected.
- You can edit this project name, if you wish.</para></listitem>
- </orderedlist>
-
- <figure>
- <title>Selecting the Web.xml File in the The Project Location Screen</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration3.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <orderedlist continuation="continues">
- <listitem><para>In the <emphasis><property>Project Folders</property></emphasis> screen, you can configure the rest of your project. Afterwards click on the <emphasis><property>Finish</property></emphasis> button.</para></listitem>
- </orderedlist>
- <para>On this step Red Hat Developer Studio will try to determine your project
- structure and set the values for: <emphasis><property>Web Root</property></emphasis>, <emphasis><property>Source Folder</property></emphasis>, <emphasis><property>Classes Folder</property></emphasis>, <emphasis><property>Lib Folder</property></emphasis>. If your project has a custom structure, some values might not be
- set. If this is the case, you can manually set those values by clicking the <emphasis><property>Change...</property></emphasis> button.</para>
- <para>After dealing with these settings, you have to work through a few more configuration settings. These settings deal primarily with how the project will be deployed within Red Hat Developer Studio.</para>
- <para>First, if the project you are importing is not already a JSF project, select the <emphasis><property>Add Libraries</property></emphasis> check box to add all the JSF-related libraries to your project. </para>
- <para>Then, you may select the JavaServer Faces implementation (<emphasis><property>Environment</property></emphasis>) and <emphasis><property>Servlet Version</property></emphasis>.</para>
- <para>The <emphasis><property>Context Path</property></emphasis> is the name under which the application will be deployed. </para>
- <para>The <emphasis><property>Runtime</property></emphasis> value tells Eclipse where to find Web libraries in order to build the project. It is not possible to finish the importing of a project without selecting a Runtime. If you don't have any choices displayed for this, select <emphasis><property>New...</property></emphasis> to add a new Runtime.</para>
- <para>Finally, <emphasis><property>Target Server</property></emphasis> sets the server to deploy the application under. The Target Server corresponds to the Runtime value selected above. If you don't want to deploy the application, uncheck this value.</para>
-
-
- <figure>
- <title>The Project Folders Screen</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration4.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <orderedlist continuation="continues">
- <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem>
- </orderedlist>
-
- <figure>
- <title>Imported Project in the Package Explorer View</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration5.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- </section>
- <section>
- <title>Struts</title>
- <orderedlist>
- <listitem><para><emphasis><property>Select File > Import...</property></emphasis> from the menu bar, and then select <emphasis><property>Other > Struts Project</property></emphasis> from the Import dialog box that appears.</para></listitem>
- </orderedlist>
-
- <figure>
- <title>Selecting the Import Menu Item</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <figure>
- <title>Selecting the Import Struts Project Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration2_2.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <orderedlist continuation="continues">
- <listitem><para>In the Project Location screen of the wizard, select the <emphasis><property>Change... </property></emphasis>button next to the web.xml Location field. Browse the location of the web.xml file for the application you
- want to import as a <property>Struts project</property>. Once you select it, you'll be returned to the dialog box to see a project name derived from the web.xml file you selected.
- You can edit this project name, if you wish.</para></listitem>
- </orderedlist>
-
- <figure>
- <title>The Project Location Screen</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration2_21.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <orderedlist continuation="continues">
- <listitem><para>In the next screen, Red Hat Developer Studio will try to determine your project structure. The upper pane shows the modules in this project.
- The lower pane allows you to edit the details of the select module. If the project structure is non-standard, some values might be left blank.
- You can edit any values by hand or by using the <emphasis><property>Change...</property></emphasis> button.</para></listitem>
- </orderedlist>
-
- <figure>
- <title>The Project Modules Screen</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration2_3.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <orderedlist continuation="continues">
- <listitem><para>In the <emphasis><property>Project Folders</property></emphasis> screen, you can configure the rest of your project. Afterwards click on the <emphasis><property>Finish</property></emphasis> button.</para>
- </listitem>
- </orderedlist>
- <para>On this step Red Hat Developer Studio will try to determine your project structure and set the values for: <emphasis><property>Classes Folder</property></emphasis>, <emphasis><property>Lib Folder</property></emphasis>, and <emphasis><property>Ant Build File</property></emphasis>. If your project has a custom structure, some values might not be set. If this is the case, you can manually set those values by clicking <emphasis><property>Change</property></emphasis>.</para>
- <para>After dealing with these settings, you have to work through a few more configuration settings. These settings deal primarily with how the project will be deployed within Red Hat Developer Studio.</para>
- <para>First, if the project you are importing is not already a Struts project, select the <emphasis><property>Add Libraries</property></emphasis> check box to add all the Struts-related libraries to your project. </para>
- <para>Then, you may select the Struts <emphasis><property>Environment</property></emphasis> and <emphasis><property>Servlet Version</property></emphasis>.</para>
- <para>The <emphasis><property>Context Path</property></emphasis> is the name under which the application will be deployed. </para>
- <para>The <emphasis><property>Runtime</property></emphasis> value tells Eclipse where to find Web libraries in order to build the project. It is not possible to finish the importing of a project without selecting a Runtime. If you don't have any choices displayed for this, select<emphasis><property> New...</property></emphasis> to add a new Runtime.</para>
- <para>Finally, <emphasis><property>Target Server</property></emphasis> sets the server to deploy the application under. The Target Server corresponds to the Runtime value selected above. If you don't want to deploy the application, uncheck this value.</para>
-
-
- <figure>
- <title>The Project Folders Screen</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration2_4.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <orderedlist continuation="continues">
- <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem>
- </orderedlist>
-
- <figure>
- <title>Imported Project in the Package Explorer View</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration2_5.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- </section>
-</chapter>
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_war.xml
===================================================================
--- trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_war.xml 2007-11-09 12:09:16 UTC (rev 4821)
+++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_war.xml 2007-11-09 13:47:25 UTC (rev 4822)
@@ -1,148 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="RHDS_migration_war" xreflabel="RHDS_migration_war">
- <?dbhtml filename="RHDS_migration_war.html"?>
-
- <chapterinfo>
- <keywordset>
- <keyword>Red Hat Developer Studio</keyword>
-
- <keyword>RHDS</keyword>
-
- <keyword>Exadel Studio Pro</keyword>
- </keywordset>
- </chapterinfo>
-
- <title>Migrate JSF and Struts projects from *.war file</title>
-
- <section>
- <title>JSF</title>
-
- <orderedlist>
- <listitem>
- <para>Select <emphasis><property>File > Import...</property></emphasis> from the menu bar, and then select
- <emphasis><property>Other > JSF Project From *.war</property></emphasis> from the Import dialog box that
- appears.</para>
- </listitem>
- </orderedlist>
-
- <figure>
- <title>Selecting the Import Menu Item</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration1.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <figure>
- <title>Selecting the JSF Project From *.war Import Wizard</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration_war1.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <orderedlist continuation="continues">
- <listitem>
- <para>In the wizard screen, select the <emphasis><property>Change...</property></emphasis> button next to
- the <emphasis><property>*.war Location</property></emphasis> field. Browse to the location of the *.war file for
- the application you want to import as a JSF project. Once you select
- it, you'll be returned to the dialog box to see a project name
- derived from the *.war file you selected. You can edit this name, if
- you wish.</para>
-
- <para>Uncheck the <emphasis><property>Use Default Path</property></emphasis> check box if you want to import
- your project outside of the Eclipse workspace. In this case, you would
- use <emphasis><property> Change... </property></emphasis> button next to the <emphasis><property>Location</property></emphasis> field to choose a
- location.</para>
-
- <para><emphasis><property>Context Path</property></emphasis> is the name under which the application will be
- deployed.</para>
-
- <para>The <emphasis><property>Runtime</property></emphasis> value tells Eclipse where to find Web libraries in
- order to build the project. It is not possible to finish project
- import without selecting Runtime. If you don't have any options
- here, select <emphasis><property>New...</property></emphasis> to add a new Runtime.</para>
-
- <para>Finally, <emphasis><property>Target Server</property></emphasis> sets the server to deploy the application
- under. The Target Server corresponds to the Runtime value selected
- above. If you don't want to deploy the application, uncheck this
- value.</para>
- </listitem>
- </orderedlist>
-
- <figure>
- <title>The JSF Project From *.war Import Wizard</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration_war2.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <orderedlist continuation="continues">
- <listitem>
- <para>Click on the <emphasis><property>Finish</property></emphasis> button.</para>
- </listitem>
- </orderedlist>
- </section>
-
- <section>
- <title>Struts</title>
-
- <orderedlist>
- <listitem>
- <para>Select <emphasis><property>File > Import...</property></emphasis> from the menu bar, and then select
- <emphasis><property>Other > Struts Project From *.war</property></emphasis> from the Import dialog box that
- appears.</para>
- </listitem>
- </orderedlist>
-
- <figure>
- <title>Selecting the Import Menu Item</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration1.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <figure>
- <title>Selecting the Struts Project From *.war Import Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration_war2_1.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <orderedlist continuation="continues">
- <listitem>
- <para>Follow the same steps as with the JSF Project From <property>*.war</property> import
- wizard.</para>
- </listitem>
- </orderedlist>
-
- <figure>
- <title>The Struts Project From *.war Import Wizard</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration_war2_2.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <orderedlist continuation="continues">
- <listitem>
- <para>Click on the <emphasis><property>Finish</property></emphasis> button.</para>
- </listitem>
- </orderedlist>
- <para>The migration process is completed</para>
- </section>
-</chapter>
\ No newline at end of file
Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_ws.xml
===================================================================
--- trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_ws.xml 2007-11-09 12:09:16 UTC (rev 4821)
+++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_ws.xml 2007-11-09 13:47:25 UTC (rev 4822)
@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="migration_ws" xreflabel="migration_ws">
- <?dbhtml filename="migration_ws.html"?>
- <chapterinfo>
- <keywordset>
- <keyword>Red Hat Developer Studio</keyword>
- <keyword>RHDS</keyword>
- <keyword>Exadel Studio Pro</keyword>
- </keywordset>
- </chapterinfo>
-
- <title>Migrate workspace</title>
- <para>You will not be able to run projects in Red Hat Developer Studio
- using <property>Exadel Studio workspace</property>. In this case, project capabilities and settings specified in Exadel Studio will be lost. The simplest way to avoid this, is to copy your projects in <property>Red Hat Developer Studio workspace</property> and make an import as it is described in the following chapters.</para>
-</chapter>
Added: trunk/documentation/guides/userguide/Exadel-migration/en/modules/workspace.xml
===================================================================
--- trunk/documentation/guides/userguide/Exadel-migration/en/modules/workspace.xml (rev 0)
+++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/workspace.xml 2007-11-09 13:47:25 UTC (rev 4822)
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="workspace" xreflabel="workspace">
+ <?dbhtml filename="workspace.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>Red Hat Developer Studio</keyword>
+ <keyword>RHDS</keyword>
+ <keyword>Exadel Studio Pro</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Migrate workspace</title>
+ <para>You will not be able to run projects in Red Hat Developer Studio
+ using <property>Exadel Studio workspace</property>. In this case, project capabilities and settings specified in Exadel Studio will be lost. The simplest way to avoid this, is to copy your projects in <property>Red Hat Developer Studio workspace</property> and make an import as it is described in the following chapters.</para>
+</chapter>
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4821 - in trunk/documentation/guides/userguide/GettingStartedGuide/en: modules and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: sabrashevich
Date: 2007-11-09 07:09:16 -0500 (Fri, 09 Nov 2007)
New Revision: 4821
Added:
trunk/documentation/guides/userguide/GettingStartedGuide/en/images/WriteYourFirst/SeamNewProj051.png
trunk/documentation/guides/userguide/GettingStartedGuide/en/images/WriteYourFirst/SeamNewProj052.png
Modified:
trunk/documentation/guides/userguide/GettingStartedGuide/en/modules/GetStartSeamGen.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-164 added description of seam components filters
Added: trunk/documentation/guides/userguide/GettingStartedGuide/en/images/WriteYourFirst/SeamNewProj051.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/GettingStartedGuide/en/images/WriteYourFirst/SeamNewProj051.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/userguide/GettingStartedGuide/en/images/WriteYourFirst/SeamNewProj052.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/userguide/GettingStartedGuide/en/images/WriteYourFirst/SeamNewProj052.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: trunk/documentation/guides/userguide/GettingStartedGuide/en/modules/GetStartSeamGen.xml
===================================================================
--- trunk/documentation/guides/userguide/GettingStartedGuide/en/modules/GetStartSeamGen.xml 2007-11-09 12:00:30 UTC (rev 4820)
+++ trunk/documentation/guides/userguide/GettingStartedGuide/en/modules/GetStartSeamGen.xml 2007-11-09 12:09:16 UTC (rev 4821)
@@ -105,9 +105,29 @@
<para>For the deployment format, choose WAR deployment if you want to use POJOs for UI event handling and business logic; choose EAR deployment if you want to EJB3 beans for added features. In most web applications, the WAR deployment option would suffice. You should also enter Java packages for the entity beans (for database mapping) and session beans (for action handlers). All generated code will be placed in those packages. </para>
- <para>Click on <emphasis><property>Finish</property></emphasis> to generate a project. The generated project contains all the necessary library JARs, XML configuration files, the ANT build script, as well as simple XHTML web pages and Java classes for the skeleton web application.</para>
-
-
+ <para>Click on <emphasis><property>Finish</property></emphasis> to generate a project. The generated project contains all the necessary library JARs, XML configuration files, the ANT build script, as well as simple XHTML web pages and Java classes for the skeleton web application. The project will be shown in Project Explorer as well as in <emphasis><property>Seam Components</property></emphasis> view. If Seam Components view is not open select <emphasis><property>Window > Show View > Seam Components</property></emphasis>.</para>
+ <figure>
+ <title>Seam Components View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/WriteYourFirst/SeamNewProj051.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>You can hide unused Seam components from this view.</para>
+ <itemizedlist>
+ <listitem><para>Click the button <emphasis><property>Menu</property></emphasis> on the top of the view (down-pointing arrow)</para></listitem>
+ <listitem><para>Choose <emphasis><property>Customize View..</property></emphasis></para></listitem>
+ <listitem><para>In the dialog <emphasis><property>Available Customization</property></emphasis> check the filter you want to apply under the <emphasis><property>Filters</property></emphasis> tab</para></listitem>
+ </itemizedlist>
+ <figure>
+ <title>Seam Components Filtering</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/WriteYourFirst/SeamNewProj052.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
</section>
<section>
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4820 - in trunk/jsf/docs/jbossjsftools/userguide/en: modules and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: ykryvinchanka
Date: 2007-11-09 07:00:30 -0500 (Fri, 09 Nov 2007)
New Revision: 4820
Modified:
trunk/jsf/docs/jbossjsftools/userguide/en/images/Preferences/preferences28templ.png
trunk/jsf/docs/jbossjsftools/userguide/en/images/Preferences/preferencestempl.png
trunk/jsf/docs/jbossjsftools/userguide/en/images/Preferences/preferencestempl2.png
trunk/jsf/docs/jbossjsftools/userguide/en/images/Preferences/preferencestempl3.png
trunk/jsf/docs/jbossjsftools/userguide/en/modules/StudioPreferences.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-238 screens and path corrected
Modified: trunk/jsf/docs/jbossjsftools/userguide/en/images/Preferences/preferences28templ.png
===================================================================
(Binary files differ)
Modified: trunk/jsf/docs/jbossjsftools/userguide/en/images/Preferences/preferencestempl.png
===================================================================
(Binary files differ)
Modified: trunk/jsf/docs/jbossjsftools/userguide/en/images/Preferences/preferencestempl2.png
===================================================================
(Binary files differ)
Modified: trunk/jsf/docs/jbossjsftools/userguide/en/images/Preferences/preferencestempl3.png
===================================================================
(Binary files differ)
Modified: trunk/jsf/docs/jbossjsftools/userguide/en/modules/StudioPreferences.xml
===================================================================
--- trunk/jsf/docs/jbossjsftools/userguide/en/modules/StudioPreferences.xml 2007-11-09 11:29:50 UTC (rev 4819)
+++ trunk/jsf/docs/jbossjsftools/userguide/en/modules/StudioPreferences.xml 2007-11-09 12:00:30 UTC (rev 4820)
@@ -40,7 +40,6 @@
<listitem><link linkend="Verification">Verification</link></listitem>
<listitem><link linkend="View">View</link></listitem>
<listitem><link linkend="VisualPageEditor2">Visual Page Editor</link></listitem>
- <listitem><link linkend="Web">Web</link></listitem>
<listitem><link linkend="XDoclet">XDoclet</link></listitem>
<listitem><link linkend="XDocletTemplets">XDoclet Templets</link></listitem>
<listitem><link linkend="XDocletsVariables">XDoclets Variables</link></listitem>
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4819 - trunk/jsf/docs/jbossjsftools/userguide/en.
by jbosstools-commits＠lists.jboss.org
Author: afedosik
Date: 2007-11-09 06:29:50 -0500 (Fri, 09 Nov 2007)
New Revision: 4819
Modified:
trunk/jsf/docs/jbossjsftools/userguide/en/master.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-271 guide rename - Jboss JSF and Struts Tools
Modified: trunk/jsf/docs/jbossjsftools/userguide/en/master.xml
===================================================================
--- trunk/jsf/docs/jbossjsftools/userguide/en/master.xml 2007-11-09 09:09:15 UTC (rev 4818)
+++ trunk/jsf/docs/jbossjsftools/userguide/en/master.xml 2007-11-09 11:29:50 UTC (rev 4819)
@@ -33,7 +33,7 @@
]>
<book>
<bookinfo>
- <title>JBoss JSF Tools</title>
+ <title>JBoss JSF and Struts Tools</title>
<!-- <subtitle>A JSF component library built on Ajax4jsf for incorporating rich UI widgets into Web applications</subtitle> -->
<copyright>
<year>2007</year>
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4818 - in trunk/documentation/guides/userguide: Legacy-jsf-struts/en/modules and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: sabrashevich
Date: 2007-11-09 04:09:15 -0500 (Fri, 09 Nov 2007)
New Revision: 4818
Modified:
trunk/documentation/guides/userguide/GettingStartedGuide/en/images/ManageJBossAS/serveroverview.png
trunk/documentation/guides/userguide/Legacy-jsf-struts/en/modules/GettingStartedGuideforCreatingaStrutsApplication.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-136 corrected palette mention, new screenshot
Modified: trunk/documentation/guides/userguide/GettingStartedGuide/en/images/ManageJBossAS/serveroverview.png
===================================================================
(Binary files differ)
Modified: trunk/documentation/guides/userguide/Legacy-jsf-struts/en/modules/GettingStartedGuideforCreatingaStrutsApplication.xml
===================================================================
--- trunk/documentation/guides/userguide/Legacy-jsf-struts/en/modules/GettingStartedGuideforCreatingaStrutsApplication.xml 2007-11-09 06:51:43 UTC (rev 4817)
+++ trunk/documentation/guides/userguide/Legacy-jsf-struts/en/modules/GettingStartedGuideforCreatingaStrutsApplication.xml 2007-11-09 09:09:15 UTC (rev 4818)
@@ -9,14 +9,14 @@
application, generate stub code for the application, fill in the stub coding, compile the application,
and run the application all from inside Red Hat Developer Studio.</para>
<para>We assume that you have already launched Eclipse with Red Hat Developer Studio installed and also that the Web Development perspective is the current perspective. (If not,
- make it active by selecting <emphasis><property>Window > Open Perspective > Other > Web Development</property></emphasis> from the menu bar.)</para>
+ make it active by selecting <emphasis><property>Window > Open Perspective > Other > Web Development</property></emphasis> from the menu bar.)</para>
<section id="StartingUp">
<title>Starting Up</title>
<para>We are first going to create a new project for the application.</para>
<itemizedlist>
-<listitem><para>Go to the menu bar and select <emphasis><property>File > New > Project...</property></emphasis>.</para></listitem>
-<listitem><para>Select <emphasis><property>JBoss Tools Web > Struts > Struts Project</property></emphasis> in the New Project dialog box</para></listitem>
+<listitem><para>Go to the menu bar and select <emphasis><property>File > New > Project...</property></emphasis>.</para></listitem>
+<listitem><para>Select <emphasis><property>JBoss Tools Web > Struts > Struts Project</property></emphasis> in the New Project dialog box</para></listitem>
<listitem><para>Click <emphasis><property>Next </property></emphasis></para></listitem>
<listitem><para>Enter "StrutsHello" as the project name</para></listitem>
<listitem><para>Leave everything else as is, and click <emphasis><property>Next</property></emphasis></para></listitem>
@@ -374,7 +374,12 @@
]]></programlisting>
<listitem><para>Select the <emphasis><property>Visual</property></emphasis> pane of the editor</para></listitem>
- <listitem><para>Then, in the JBoss Tools Palette, expand the <emphasis><property>Struts Form</property></emphasis> library, select <emphasis><property>text</property></emphasis>, and drag it onto the box</para></listitem>
+ <listitem><para>Then, in the JBoss Tools Palette, expand the <emphasis><property>Struts Form</property></emphasis> library, select <emphasis><property>text</property></emphasis>, and drag it onto the box
+ <note>
+ <title>Note:</title>
+ <para>By default there are only four groups on the JBoss Tools Palette. If you wish to make some group visible click the <emphasis><property>Show/Hide</property></emphasis> button on the top of palette and in the prompted dialog check the group (or groups) you want to be shown.</para>
+ </note>
+ </para></listitem>
</itemizedlist>
<figure>
<title>JBoss Tools Palette</title>
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4817 - tags/jbosstools-2.0.0.CR1.
by jbosstools-commits＠lists.jboss.org
Author: mculpepper(a)jboss.com
Date: 2007-11-09 01:51:43 -0500 (Fri, 09 Nov 2007)
New Revision: 4817
Added:
tags/jbosstools-2.0.0.CR1/legacy/
Log:
tagging legacy
Copied: tags/jbosstools-2.0.0.CR1/legacy (from rev 4816, trunk/legacy)
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4816 - tags/jbosstools-2.0.0.CR1.
by jbosstools-commits＠lists.jboss.org
Author: mculpepper(a)jboss.com
Date: 2007-11-09 01:36:02 -0500 (Fri, 09 Nov 2007)
New Revision: 4816
Added:
tags/jbosstools-2.0.0.CR1/vpe/
Log:
tagging vpe
Copied: tags/jbosstools-2.0.0.CR1/vpe (from rev 4815, trunk/vpe)
17 years, 2 months
- 1
- 0
JBoss Tools SVN: r4815 - tags/jbosstools-2.0.0.CR1.
by jbosstools-commits＠lists.jboss.org
Author: mculpepper(a)jboss.com
Date: 2007-11-09 01:35:04 -0500 (Fri, 09 Nov 2007)
New Revision: 4815
Added:
tags/jbosstools-2.0.0.CR1/struts/
Log:
tagging struts
Copied: tags/jbosstools-2.0.0.CR1/struts (from rev 4814, trunk/struts)
17 years, 2 months
- 1
- 0