Author: manaRH Date: 2010-05-11 09:53:50 -0400 (Tue, 11 May 2010) New Revision: 12711 Added: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/server_properties_1.png Removed: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/generate_entities_0.xcf branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_4.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_5.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_6.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/server_properties.png Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/Tutorial.xml branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/generate_entities_0.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_action_0.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_action_1.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_1.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_2.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_3.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_form_0.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_form_1.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_seam_runtime.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_server_1.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_server_2.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_server_runtime_1.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_server_runtime_2.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_web_project_0.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_web_project_1.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_web_project_2.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/restart_deployment.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/run_test.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/server_properties_0.png branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/start_server.png Log: JBPAPP-3818 updating Getting started with JBDS Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml =================================================================== --- branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml 2010-05-11 08:14:53 UTC (rev 12710) +++ branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml 2010-05-11 13:53:50 UTC (rev 12711) @@ -2,7 +2,7 @@ <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"> <chapter id="gettingstartedwithjbosstools"> - <title>Getting started with Seam, using JBoss Tools</title> + <title>Getting started with Seam, using JBoss Developer Studio</title> <para> JBoss Tools is a collection of Eclipse plugins. JBoss Tools a project @@ -11,27 +11,29 @@ a graphical editor for Seam configuration files, support for running Seam integration tests from within Eclipse, and much more. </para> - + <para> - In short, if you are an Eclipse user, then you'll want JBoss Tools! + JBoss Developer Studio is bundled Eclipse platform with JBoss Tools plus additional + usefull Eclipse plugins for web development. More you can see at <ulink + url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/htm... + JBoss Developer Studio Getting started guide</ulink> </para> - <para> - JBoss Tools, as with seam-gen, works best with JBoss AS, but it's possible - with a few tweaks to get your app running on other application servers. - The changes are much like those described for seam-gen later in this - reference manual. - </para> - <section> <title>Before you start</title> <para> - Make sure you have JDK 5, JBoss EAP 5, Eclipse 3.3, the JBoss + Make sure you have JDK 6, JBoss EAP 5, Eclipse 3.5 and the JBoss Tools plugins (at least Seam Tools, the Visual Page Editor, jBPM Tools - and JBoss AS Tools) and the TestNG plugin for Eclipse correctly + and JBoss AS Tools) or JBDS 3.0 and the TestNG plugin for Eclipse correctly installed before starting. </para> + + <para> + In case of using JBoss Developer Studio read JBDS documentation <ulink url=" + http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/"> + JBDS Update Guide</ulink>. + </para> <para> Please see the official <ulink @@ -39,8 +41,8 @@ installation</ulink> page for the quickest way to get JBoss Tools setup in Eclipse. You can also check out the <ulink url="http://www.jboss.org/community/wiki/InstallingJBossTools"&... - JBoss Tools</ulink> page on the JBoss community wiki for the gory - details and a set of alternative installation approaches. + JBoss Tools</ulink> page on the JBoss community wiki for the detailed + description and a set of alternative installation approaches. </para> </section> @@ -71,16 +73,13 @@ <para> First, enter a name for your new project. For this tutorial, we're going to use - <literal>helloworld</literal> - . - </para> - - + <literal>helloworld</literal>. + </para> + <para> - Now, we need to tell JBoss Tools about JBoss AS. In this example we - are using JBoss AS 4.2, though you can certainly use JBoss AS 5.0 as - well. Selecting JBoss AS is a two step process. First we need to - define a runtime. Again, we'll choose JBoss AS 4.2 in this case: + Now, we need to tell JBoss Tools about JBoss AS runtime. In this example we + are using JBoss EAP 5. Selecting JBoss AS is a two step process. First we need to + define a runtime. Again, we'll choose predefined JBoss EAP 5.0 from JBDS in this case: </para> <mediaobject> @@ -111,8 +110,9 @@ <para> Next, we need to define a server JBoss Tools can deploy the project to. - Make sure to again select JBoss AS 4.2, and also the runtime you just - defined: + Make sure to again select JBoss EAP 5.0, and also the runtime you just + defined, give the server a name, and hit + <emphasis>Next</emphasis>: </para> <mediaobject> @@ -126,7 +126,7 @@ </mediaobject> <para> - On the next screen give the server a name, and hit + On the next screen check the server settings, and hit <emphasis>Finish</emphasis>: </para> @@ -143,7 +143,7 @@ <para> Make sure the runtime and server you just created are selected, select - <emphasis>Dynamic Web Project with Seam 2.0 (technology preview)</emphasis> + <emphasis>Dynamic Web Project with Seam 2.2</emphasis> and hit <emphasis>Next</emphasis>: </para> @@ -165,10 +165,10 @@ </para> <para> - The first step here is to tell JBoss Tools about the Seam download you - want to use. <emphasis>Add</emphasis> a new + The first step here is to tell JBoss Tools about the Seam installation you + want to use. Select the predefined Seam runtime or <emphasis>Add</emphasis> a new <emphasis>Seam Runtime</emphasis> - make sure to give it a name, and - select <emphasis>2.0</emphasis> as the version: + select <emphasis>2.2</emphasis> as the version: </para> <mediaobject> @@ -187,19 +187,19 @@ and WAR deployment of your project. EAR projects support EJB 3.0 and require Java EE 5. WAR projects do not support EJB 3.0, but may be deployed to a J2EE environment. The packaging of a WAR is also simpler - to understand. If you installed an EJB3-ready application server like - JBoss, choose <emphasis>EAR</emphasis>. Otherwise, choose - <emphasis>WAR</emphasis>. We'll assume that you've chosen a WAR + to understand. If you use an EJB3-ready application server like + JBoss AS 5, you can choose both - <emphasis>EAR</emphasis> or + <emphasis>WAR</emphasis>. We'll assume that you've chosen a WAR deployment for the rest of the tutorial, but you can follow exactly the same steps for a EAR deployment. </para> <para> Next, select your database type. We'll assume you have MySQL installed, - with an existing schema. You'll need to tell JBoss Tools about + with an existing schema. You'll need to tell JBDS about the database, select <emphasis>MySQL</emphasis> as the database, and - create a new connection profile. Select <emphasis>Generic JDBC - Connection</emphasis>: + choose a MySQL connection profile type. Select <emphasis>MySQL</emphasis> and + give it a name: </para> <mediaobject> @@ -214,7 +214,8 @@ </mediaobject> <para> - Give it a name: + Select existing MySQL driver from dropdown and specify database name, JDBC URL + and JDBC username and password: </para> <mediaobject> @@ -229,13 +230,14 @@ </mediaobject> <para> - JBoss Tools doesn't come with drivers for any databases, so you need to - tell JBoss Tools where the MySQL JDBC driver is. Tell it about the - driver by clicking <emphasis>...</emphasis>. + JBoss Tools comes with common drivers for any databases, in case of MySQL you need to + tell JBoss Tools where the location of your MySQL JDBC driver is. Tell it about the + driver location by clicking on delta icon on the right next to dropdown list. </para> <para> - Locate MySQL 5, and hit <emphasis>Add...</emphasis>: + You need to set location of MySQL 5 JDBC driver on second tab - <emphasis>jar list</emphasis>, + and hit <emphasis>Edit JAR/Zip...</emphasis>: </para> <mediaobject> @@ -250,56 +252,9 @@ </mediaobject> <para> - Choose the <emphasis>MySQL JDBC Driver</emphasis> template: - </para> - - <mediaobject> - <imageobject role="fo"> - <imagedata fileref="images/new_connection_profile_4.png" - align="center" scalefit="1" /> - </imageobject> - <imageobject role="html"> - <imagedata fileref="images/new_connection_profile_4.png" - align="center" /> - </imageobject> - </mediaobject> - - <para> - Locate the jar on your computer by choosing <emphasis>Edit - Jar/Zip</emphasis>: - </para> - - <mediaobject> - <imageobject role="fo"> - <imagedata fileref="images/new_connection_profile_5.png" - align="center" scalefit="1" /> - </imageobject> - <imageobject role="html"> - <imagedata fileref="images/new_connection_profile_5.png" - align="center" /> - </imageobject> - </mediaobject> - - <para> - Review the username and password used to connect, and if correct, hit - <emphasis>Ok</emphasis>. - </para> - - <para> Finally, choose the newly created driver: </para> - - <mediaobject> - <imageobject role="fo"> - <imagedata fileref="images/new_connection_profile_6.png" - align="center" scalefit="1" /> - </imageobject> - <imageobject role="html"> - <imagedata fileref="images/new_connection_profile_6.png" - align="center" /> - </imageobject> - </mediaobject> - + <para> If you are working with an existing data model, make sure you tell JBoss Tools that the tables already exist in the database. @@ -328,18 +283,15 @@ </mediaobject> <para> - JBoss has sophisticated support for hot re-deployment of WARs and EARs. - Unfortunately, due to bugs in the JVM, repeated redeployment of an - EAR—which is common during development—eventually causes the JVM to run - out of perm gen space. For this reason, we recommend running JBoss in a - JVM with a large perm gen space at development time. We suggest the - following values: + JBoss Developer Studio has sophisticated support for hot re-deployment + of WARs and EARs. Unfortunately, due to bugs in the JVM, repeated + redeployment of an EAR—which is common during development—eventually + causes the JVM to run out of perm gen space. For this reason, we + recommend running JBoss AS in a JVM with a large perm gen space at + development time. If you use the predefined JBoss EAP 5.0 runtime, the best + values are set in, but you can customize these to fit your enviroment. </para> - <programlisting> - -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512 - </programlisting> - <para> If you don't have so much memory available, the following is our minimum recommendation: @@ -350,9 +302,8 @@ </programlisting> <para> - Locate the server in the <emphasis>JBoss Server View</emphasis>, right - click on the server and select <emphasis>Edit Launch - Configuration</emphasis>: + Locate the server in the <emphasis>Servers View</emphasis>, right + click on the server and select <emphasis>Open</emphasis>: </para> <mediaobject> @@ -367,16 +318,17 @@ </mediaobject> <para> - Then, alter the VM arguements: + Then, in opened Server properties click on Open launch configuration and + alter the VM arguments: </para> <mediaobject> <imageobject role="fo"> - <imagedata fileref="images/server_properties.png" + <imagedata fileref="images/server_properties_1.png" align="center" scalefit="1" /> </imageobject> <imageobject role="html"> - <imagedata fileref="images/server_properties.png" + <imagedata fileref="images/server_properties_1.png" align="center" /> </imageobject> </mediaobject> @@ -388,7 +340,7 @@ </para> <para> - To start JBoss, and deploy the project, just right click on the server + To start JBoss AS, and deploy the project, just right click on the server you created, and click <emphasis>Start</emphasis>, (or <emphasis>Debug</emphasis> to start in debug mode): </para> @@ -423,7 +375,7 @@ </para> <para> - First, select <emphasis>New</emphasis> -> <emphasis>Seam Action</emphasis>: + First, select <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> <emphasis>Seam Action</emphasis>: </para> <mediaobject> @@ -488,7 +440,7 @@ <title>Creating a form with an action</title> <para> - The first step is to create a form. Select <emphasis>New</emphasis> -> + The first step is to create a form. Select <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> <emphasis>Seam Form</emphasis>: </para> @@ -523,8 +475,8 @@ Go to <literal>http://localhost:8080/helloworld/hello.seam</literal>. Then take a look at the generated code. Run the test. Try adding some new fields to the form and Seam component (note, you don't need to - restart the app server each time you change the code in - <literal>src/action</literal> as Seam hot reloads the component for + restart the app server each time you change the code as Seam hot + reloads the component for you <xref linkend="gettingstartedwithjbosstools.hotdeployment" />). </para> </section> @@ -535,7 +487,7 @@ <para> Manually create some tables in your database. (If you need to switch to a different database, create a new project, and select the correct - database). Then, select <emphasis>New</emphasis> -> + database). Then, select <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> <emphasis>Seam Generate Entities</emphasis>: </para> @@ -675,8 +627,7 @@ <para> If you create a WAR project using JBoss Tools, incremental hot deployment - is available out of the box for classes in the - <literal>src/action</literal> source directory. However, JBoss Tools + is available out of the box. However, JBoss Tools does not support incremental hot deployment for EAR projects. </para> </section> Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/Tutorial.xml =================================================================== --- branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2010-05-11 08:14:53 UTC (rev 12710) +++ branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2010-05-11 13:53:50 UTC (rev 12711) @@ -67,10 +67,22 @@ <title>Running the example tests</title> <para> Most of the examples come with a suite of TestNG integration tests. The easiest way to run the tests is - to run <literal>ant test</literal>. It is also possible to run the tests inside your IDE using the - TestNG plugin. Consult the readme.txt in the examples directory of the Seam distribution for more - information. + to run <literal>ant test</literal>. </para> + + <para> + It is also possible to run the tests inside your IDE using the + TestNG plugin. This requires to run ant test, before running or debugging Seam test cases in Eclipse IDE. + +So the following steps are the corect way: +1. Run ant test for the used example in its directory, e.g. booking -> go to booking example directory and in that location run ant test. +2. Create a New Java project in Eclipse from existing ant build file and select booking example build file. +3. Select testng suite or testng class and Choose Run As -> TestNg Test, you can cancel the processing of testng run. +4. Go to Run -> Run configurations and edit the created TestNG runner. +5. If you use java 6 as runtime, add jvm argument "-Dsun.lang.ClassLoader.allowArraySyntax=true" on Arguments tab. +6. goto Classpath tab and remove all User entries. +7. Then in according to this page http://seamframework.org/Community/GettingStartedDevelopingTheSeamFramewo..., add necessary jars and folders (&lt;instalation_of_seam&gt;/bootstrap, booking/test-build). + </para> </section> </section> Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/generate_entities_0.png =================================================================== (Binary files differ) Deleted: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/generate_entities_0.xcf =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_action_0.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_action_1.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_1.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_2.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_3.png =================================================================== (Binary files differ) Deleted: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_4.png =================================================================== (Binary files differ) Deleted: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_5.png =================================================================== (Binary files differ) Deleted: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_connection_profile_6.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_form_0.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_form_1.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_seam_runtime.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_server_1.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_server_2.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_server_runtime_1.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_server_runtime_2.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_web_project_0.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_web_project_1.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/new_web_project_2.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/restart_deployment.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/run_test.png =================================================================== (Binary files differ) Deleted: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/server_properties.png =================================================================== (Binary files differ) Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/server_properties_0.png =================================================================== (Binary files differ) Added: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/server_properties_1.png =================================================================== (Binary files differ) Property changes on: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/server_properties_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: branches/enterprise/JBPAPP_5_0/doc/Seam_Reference_Guide/en-US/images/start_server.png =================================================================== (Binary files differ)