JBoss Tools SVN: r27932 - in trunk/esb/docs/esb_ref_guide/en-US: images/esb_project and 1 other directory.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-05 21:26:24 -0500 (Wed, 05 Jan 2011)
New Revision: 27932
Modified:
trunk/esb/docs/esb_ref_guide/en-US/images/esb_project/01_create_esb_project.png
trunk/esb/docs/esb_ref_guide/en-US/images/esb_project/02_create_esb_project.png
trunk/esb/docs/esb_ref_guide/en-US/images/esb_project/02a_create_esb_project.png
trunk/esb/docs/esb_ref_guide/en-US/images/esb_project/03_create_esb_project.png
trunk/esb/docs/esb_ref_guide/en-US/introduction.xml
trunk/esb/docs/esb_ref_guide/en-US/tasks.xml
Log:
Fixed screenshots for 2.1. Creating a ESB Project
Modified: trunk/esb/docs/esb_ref_guide/en-US/images/esb_project/01_create_esb_project.png
===================================================================
(Binary files differ)
Modified: trunk/esb/docs/esb_ref_guide/en-US/images/esb_project/02_create_esb_project.png
===================================================================
(Binary files differ)
Modified: trunk/esb/docs/esb_ref_guide/en-US/images/esb_project/02a_create_esb_project.png
===================================================================
(Binary files differ)
Modified: trunk/esb/docs/esb_ref_guide/en-US/images/esb_project/03_create_esb_project.png
===================================================================
(Binary files differ)
Modified: trunk/esb/docs/esb_ref_guide/en-US/introduction.xml
===================================================================
--- trunk/esb/docs/esb_ref_guide/en-US/introduction.xml 2011-01-06 02:03:45 UTC (rev 27931)
+++ trunk/esb/docs/esb_ref_guide/en-US/introduction.xml 2011-01-06 02:26:24 UTC (rev 27932)
@@ -94,7 +94,7 @@
<para>This section will provide you with the information on how to install
JBoss ESB plugin into Eclipse.</para>
- <para>ESB Tools come as one module of JBoss Tools project. Since ESB Tools have a
+ <para>ESB Tools come as one module of the JBoss Tools project. Since ESB Tools have a
dependence on other JBoss Tools modules we recommend you to install a bundle
of all <ulink url="http://labs.jboss.com/tools/download.html">JBoss
Tools plug-ins</ulink>. You can find all necessary installation instructions on JBoss Wiki in the <ulink url="http://www.jboss.org/tools/download/installation"
Modified: trunk/esb/docs/esb_ref_guide/en-US/tasks.xml
===================================================================
--- trunk/esb/docs/esb_ref_guide/en-US/tasks.xml 2011-01-06 02:03:45 UTC (rev 27931)
+++ trunk/esb/docs/esb_ref_guide/en-US/tasks.xml 2011-01-06 02:26:24 UTC (rev 27932)
@@ -1,541 +1,638 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="tasks" role="updated">
- <?dbhtml filename="etasks.html"?>
- <chapterinfo>
- <keywordset>
- <keyword>JBoss Developer Studio</keyword>
- <keyword>Eclipse</keyword>
- <keyword>ESB</keyword>
- <keyword>Java</keyword>
- <keyword>JBoss</keyword>
- </keywordset>
- </chapterinfo>
+ <?dbhtml filename="etasks.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>ESB</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
- <title>Tasks</title>
+ <title>Tasks</title>
- <para>In this section we will focus on all concepts that <property>JBoss Tools</property>
+ <para>In this section we will focus on all concepts that <property>JBoss Tools</property>
integrate for working with JBoss ESB.</para>
-
- <section>
- <title>Creating a ESB Project</title>
- <para>In this chapter we suggest a step-by-step walk-through of creating a new
+
+ <section>
+ <title>Creating a ESB Project</title>
+ <para>In this chapter we suggest a step-by-step walk-through of creating a new
ESB project. Let's try to create a new JBoss ESB project.</para>
- <para>We will show you how to use the ESB Project Creation wizard for creating a new ESB project and setting basic ESB classpath.</para>
+ <para>We will show you how to use the ESB Project Creation wizard for creating a new ESB project and setting basic ESB classpath.</para>
- <para>Select <emphasis>
- <property>File >New > Project...</property>
- </emphasis> in the main menu bar or context menu for selected project and
- then <emphasis>
- <property>ESB > ESB Project</property>
- </emphasis> in the dialog opened:</para>
+ <para>Select
+ <menuchoice>
+ <guimenuitem>File</guimenuitem>
+ <guimenuitem>New</guimenuitem>
+ <guimenuitem>Project...</guimenuitem>
+ </menuchoice>
+ in the main menu bar or context menu for selected project and then
+ <menuchoice>
+ <guimenuitem>ESB</guimenuitem>
+ <guimenuitem>ESB Project</guimenuitem>
+ </menuchoice>
+ in the dialog opened:</para>
- <figure>
- <title>Select a Wizard dialog</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/01_create_esb_project.png"/>
- </imageobject>
- </mediaobject>
- </figure>
+ <figure>
+ <title>Select a Wizard dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/01_create_esb_project.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <para> Clicking <emphasis>
+ <para> Clicking <emphasis>
<property>Next</property>
- </emphasis> brings you to the JBoss ESB Project wizard page where a project name, ESB version and target JBoss Runtime are to be specified. Specify, for example, <emphasis>
+ </emphasis> brings you to the JBoss ESB Project wizard page where a project name, ESB version and target JBoss Runtime are to be specified. Specify, for example, <emphasis>
<property>helloworld</property>
- </emphasis> as a Project name and accept the default ESB version.</para>
- <figure>
- <title>JBoss ESB Project wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/02_create_esb_project.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>By clicking <emphasis>Modify</emphasis> button you can open <emphasis>Project Facets Wizard</emphasis> page,where you can select
+ </emphasis> as a Project name and accept the default ESB version.</para>
+ <figure>
+ <title>JBoss ESB Project wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/02_create_esb_project.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>By clicking <emphasis>Modify</emphasis> button you can open <emphasis>Project Facets Wizard</emphasis> page,where you can select
facets that should be enabled for this project.
On the <emphasis>Project Facets Wizard</emphasis> page you can also configure runtime for the application</para>
- <figure>
- <title>Project Facets Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/02a_create_esb_project.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Next step provides you an opportunity to configure your project for building a java application</para>
-
- <para> Clicking <emphasis>
- <property>Next</property> on this form
- </emphasis> brings you to the ESB facet installation page where you can
- specify Java Source Directory and ESB Content Directory. ESB Content Directory is a folder that contains the most of
+ <figure>
+ <title>Project Facets Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/02a_create_esb_project.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Click the <guibutton>Next</guibutton> button to move to the next step in the wizard, where you can select the source and output folders.</para>
+
+ <figure>
+ <title>Project Facets Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/02b_create_esb_project.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Next step provides you an opportunity to configure your project for building a java application</para>
+
+ <para> Clicking <guibutton>Next</guibutton> on this form brings you to the ESB facet installation page where you can
+ specify the ESB Content Directory. ESB Content Directory is a folder that contains the most of
artifacts that an ESB archive needs. You also can configure ESB libraries to the project by selecting a ESB runtime using one of the options:
</para>
- <para>1. Use <emphasis>
+ <para>1. Use <emphasis>
<property>Server Supplied ESB Runtime</property>
- </emphasis>
-
+ </emphasis>
+
+ </para>
+ <para> 2. Select a ESB runtime from the JBoss ESB runtime list predefined in the preferences. If you choose the first option, make sure that the project has the Target JBoss Runtime set and this runtime has a ESB runtime installed.
</para>
- <para> 2. Select a ESB runtime from the JBoss ESB runtime list predefined in the preferences. If you choose the first option, make sure that the project has the Target JBoss Runtime set and this runtime has a ESB runtime installed.
- </para>
- <para>3. Choose ESB Config Vertion. From the version 3.1.0 JBoss ESB Tools supports three different jboss-esb.xsd versions: jbossesb-1.0.1.xsd, jbossesb-1.1.0.xsd and jbossesb-1.2.0.xsd.</para>
- <note><title>Note:</title>
- <para>If you use ESB 4.7 you should select jbossesb-1.2.0.xsd.</para></note>
- <figure>
- <title>Install ESB facet step</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/03_create_esb_project.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Click <emphasis>
+ <para>3. Choose ESB Config Vertion. From the version 3.1.0 JBoss ESB Tools supports three different jboss-esb.xsd versions: jbossesb-1.0.1.xsd, jbossesb-1.1.0.xsd and jbossesb-1.2.0.xsd.</para>
+ <note>
+ <title>Note:</title>
+ <para>If you use ESB 4.7 you should select jbossesb-1.2.0.xsd.</para>
+ </note>
+ <figure>
+ <title>Install ESB facet step</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/03_create_esb_project.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click <emphasis>
<property>Finish</property>
- </emphasis> and a ESB project with the default <emphasis><property>jboss-esb.xml</property></emphasis>
+ </emphasis> and a ESB project with the default <emphasis><property>jboss-esb.xml</property>
+ </emphasis>
will be created. </para>
- <figure>
- <title>The generated ESB project structure</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/04_create_esb_project.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- </section>
-
- <section id="ESB_project_wizard" xreflabel="here">
- <title>Using ESB Project Examples</title>
- <para>JBoss Tools provides a Project Example wizard that is an easy way for users to create some kinds of projects to be used as examples with some predefined structure. Let's start
+ <figure>
+ <title>The generated ESB project structure</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/04_create_esb_project.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+
+ <section id="ESB_project_wizard" xreflabel="here">
+ <title>Using ESB Project Examples</title>
+ <para>JBoss Tools provides a Project Example wizard that is an easy way for users to create some kinds of projects to be used as examples with some predefined structure. Let's start
creating a ESB project using this wizard.</para>
-
- <para>Before creating a ESB project example create JBoss Runtime with name <emphasis><property>
- JBoss 4.2 Runtime</property></emphasis>, it will be used by your ESB project example. </para>
- <para>Select <emphasis>
+ <para>Before creating a ESB project example create JBoss Runtime with name <emphasis><property>
+ JBoss 4.2 Runtime</property>
+ </emphasis>, it will be used by your ESB project example. </para>
+
+ <para>Select <emphasis>
<property>File >New > Others </property>
- </emphasis> , in the main menu bar or context menu for selected project and
+ </emphasis> , in the main menu bar or context menu for selected project and
then <emphasis>
<property>JBoss Tools > Project Examples</property>
- </emphasis> in the New dialog:</para>
+ </emphasis> in the New dialog:</para>
- <figure>
- <title>Select a wizard - Project Examples</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/05_esb_project_example.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para> Clicking <emphasis>
+ <figure>
+ <title>Select a wizard - Project Examples</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/05_esb_project_example.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> Clicking <emphasis>
<property>Next</property>
</emphasis> brings you to the wizard page where you can select a ESB project example from the example list.</para>
-
- <figure>
- <title>Project Example Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/05a_esb_project_example.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <note>
- <title>Note:</title>
- <para>Under the <property>Projects</property>
+
+ <figure>
+ <title>Project Example Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/05a_esb_project_example.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <note>
+ <title>Note:</title>
+ <para>Under the <property>Projects</property>
section you can find two categories related to ESB:</para>
-
- <itemizedlist>
- <listitem><para>ESB</para></listitem>
- <listitem><para>ESB for SOA-P 5.0</para></listitem>
- </itemizedlist>
-
+
+ <itemizedlist>
+ <listitem>
+ <para>ESB</para>
+ </listitem>
+ <listitem>
+ <para>ESB for SOA-P 5.0</para>
+ </listitem>
+ </itemizedlist>
- <para>It means that if you use a runtime pointed to a SOA-P 5.0, you should download the examples from
+
+ <para>It means that if you use a runtime pointed to a SOA-P 5.0, you should download the examples from
the <emphasis>
<property>ESB for SOA-P 5.0</property>
- </emphasis> category in order to avoid the incompatibility errors.
+ </emphasis> category in order to avoid the incompatibility errors.
</para>
- </note>
-
- <para>Every ESB example has two projects, one is a ESB project and another is a Java project used to test the ESB project.</para>
- <para>Here is a list of ready examples available in both categories (ESB and ESB for SOA-P 5.0):</para>
-
- <itemizedlist>
-
- <listitem><para><emphasis role="bold">JBoss ESB HelloWorld Example</emphasis> - demonstrates the minimal files necessary to make a basic ESB component execute as well as to prove that the ESB is properly configured.</para></listitem>
- <listitem><para><emphasis role="bold">JBoss ESB HelloWorld Action Example</emphasis> - demonstrates the use of multiple action invocations from a single configuration. You can use a single Action class and make multiple method calls or use multiple Action classes. </para></listitem>
- <listitem><para><emphasis role="bold">JBoss ESB HelloWorld File Action Example</emphasis> - demonstrates using the File gateway feature of the JBoss ESB. Files that are found in a particular directory with a particular extension are sent to a JMS queue with actions for processing.</para></listitem>
- <listitem><para><emphasis role="bold">JBoss ESB Web Service consumer1 Example</emphasis> - demonstrates how to consume a 181 Web Service in an ESB action.</para></listitem>
- <listitem><para><emphasis role="bold">JBoss ESB Web Service producer Example</emphasis> - demonstrates how to deploy a JSR181 Webservice endpoint on JBossESB using the SOAPProcessor action.</para></listitem>
- <listitem><para><emphasis role="bold">JBoss ESB Smooks CSV -> XML Example</emphasis> - demonstrates how to transform a comma separated value (CSV) file to an XML.</para></listitem>
- <listitem><para><emphasis role="bold">JBoss ESB Smooks XML -> POJO Example</emphasis> - demonstrates the use of Smooks performing a simple transformation by converting an XML file into Java POJOs.</para></listitem>
- <listitem><para><emphasis role="bold">JBoss ESB Smooks XML -> XML date-manipulation Example</emphasis> - demonstrates how to manually define and apply a Message Transformation within JBoss ESB.</para></listitem>
- <listitem><para><emphasis role="bold">JBoss ESB Smooks XML -> XML Example</emphasis> - a very basic example of how to manually define and apply a Message Transformation within JBoss ESB. It applies a very simple XSLT to a SampleOrder.xml message and prints the before and after XML to the console. </para></listitem>
-
- </itemizedlist>
-
+ </note>
+
+ <para>Every ESB example has two projects, one is a ESB project and another is a Java project used to test the ESB project.</para>
+ <para>Here is a list of ready examples available in both categories (ESB and ESB for SOA-P 5.0):</para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">JBoss ESB HelloWorld Example</emphasis> - demonstrates the minimal files necessary to make a basic ESB component execute as well as to prove that the ESB is properly configured.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">JBoss ESB HelloWorld Action Example</emphasis> - demonstrates the use of multiple action invocations from a single configuration. You can use a single Action class and make multiple method calls or use multiple Action classes. </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">JBoss ESB HelloWorld File Action Example</emphasis> - demonstrates using the File gateway feature of the JBoss ESB. Files that are found in a particular directory with a particular extension are sent to a JMS queue with actions for processing.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">JBoss ESB Web Service consumer1 Example</emphasis> - demonstrates how to consume a 181 Web Service in an ESB action.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">JBoss ESB Web Service producer Example</emphasis> - demonstrates how to deploy a JSR181 Webservice endpoint on JBossESB using the SOAPProcessor action.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">JBoss ESB Smooks CSV -> XML Example</emphasis> - demonstrates how to transform a comma separated value (CSV) file to an XML.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">JBoss ESB Smooks XML -> POJO Example</emphasis> - demonstrates the use of Smooks performing a simple transformation by converting an XML file into Java POJOs.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">JBoss ESB Smooks XML -> XML date-manipulation Example</emphasis> - demonstrates how to manually define and apply a Message Transformation within JBoss ESB.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">JBoss ESB Smooks XML -> XML Example</emphasis> - a very basic example of how to manually define and apply a Message Transformation within JBoss ESB. It applies a very simple XSLT to a SampleOrder.xml message and prints the before and after XML to the console. </para>
+ </listitem>
+
+ </itemizedlist>
- <para>We will take as our example <emphasis><property>JBoss ESB HelloWorld Example</property> </emphasis> ESB and Client project:</para>
+
+ <para>We will take as our example <emphasis><property>JBoss ESB HelloWorld Example</property>
+ </emphasis> ESB and Client project:</para>
+
+ <figure>
+ <title>JBoss Tools ESB Project Examples</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/06_esb_project_example.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <figure>
- <title>JBoss Tools ESB Project Examples</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/06_esb_project_example.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
-
- <para>Choose them using the Ctrl button and then click
- <emphasis><property>Finish</property></emphasis>. As a result you will get two projects created:</para>
- <figure>
- <title>JBoss ESB Project Examples: helloworld and helloworld_testclient</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/07_esb_project_example.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para> Deploy the HelloWorld ESB project and run a test class in the client Java project to see the test result in the Console view.</para>
- </section>
+
+ <para>Choose them using the Ctrl button and then click
+ <emphasis><property>Finish</property>
+ </emphasis>. As a result you will get two projects created:</para>
+ <figure>
+ <title>JBoss ESB Project Examples: helloworld and helloworld_testclient</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/07_esb_project_example.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <section>
- <title>Deploying a ESB Project</title>
- <para>In this chapter you will see how to deploy a ESB project using the WTP deployment framework.</para>
+ <para> Deploy the HelloWorld ESB project and run a test class in the client Java project to see the test result in the Console view.</para>
+ </section>
+
+ <section>
+ <title>Deploying a ESB Project</title>
+ <para>In this chapter you will see how to deploy a ESB project using the WTP deployment framework.</para>
- <para>Before deploying the project, open the Servers View by selecting <emphasis><property>Window > Show View > Other >
- Server > Servers</property></emphasis>,
+ <para>Before deploying the project, open the Servers View by selecting <emphasis><property>Window > Show View > Other >
+ Server > Servers</property>
+ </emphasis>,
create a JBoss Server in the Server view and start it, and then right click the created JBoss server,
select <emphasis><property> </property> Add and Remove Projects</emphasis>,
and add the ESB projects you want to deploy from the left side to the right side in the opened dialog. </para>
- <figure>
- <title>Add and Remove Projects</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/08_esb_project_deploy.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Click <emphasis><property>Finish</property> </emphasis> to add the project to the server.
+ <figure>
+ <title>Add and Remove Projects</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/08_esb_project_deploy.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Click <emphasis><property>Finish</property>
+ </emphasis> to add the project to the server.
You also can drag the ESB project from the Project View to the server.</para>
-
- <figure>
- <title>Servers View</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/09_esb_runtime_new.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Thus, you have just added the ESB project to the JBoss server module list. Right click the JBoss Server and select <emphasis><property>Publish</property></emphasis> to publish the project on the server.
- You can check the deploying result in the Console view.</para>
- <para>The <emphasis><property>Run</property></emphasis> and <emphasis><property>Debug</property></emphasis> options work on ESB projects causing a (re)deploy for a user designated server.</para>
- <para>You can also use the "Finger touch" for a quick restart of the project without restarting the server:</para>
- <figure>
- <title>Finger Touch button</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/23_finger_touch.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>The "Finger" touches descriptors dependent on project (i.e. web.xml for WAR, application.xml for EAR) and now it is also available for jboss-esb.xml in ESB projects.</para>
- <para>You can also deploy your ESB project as an .esb archive. Right-click on the project, choose <emphasis><property>Export</property></emphasis>:</para>
-
- <figure>
- <title>Export of ESB project</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/24_export_button.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Choose <emphasis><property>ESB</property></emphasis> > <emphasis><property>ESB File</property></emphasis> and click <emphasis><property>Next</property></emphasis>:</para>
+
+ <figure>
+ <title>Servers View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/09_esb_runtime_new.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Thus, you have just added the ESB project to the JBoss server module list. Right click the JBoss Server and select <emphasis><property>Publish</property>
+ </emphasis> to publish the project on the server.
+ You can check the deploying result in the Console view.</para>
+ <para>The <emphasis><property>Run</property>
+ </emphasis> and <emphasis><property>Debug</property>
+ </emphasis> options work on ESB projects causing a (re)deploy for a user designated server.</para>
+ <para>You can also use the "Finger touch" for a quick restart of the project without restarting the server:</para>
+ <figure>
+ <title>Finger Touch button</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/23_finger_touch.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The "Finger" touches descriptors dependent on project (i.e. web.xml for WAR, application.xml for EAR) and now it is also available for jboss-esb.xml in ESB projects.</para>
+ <para>You can also deploy your ESB project as an .esb archive. Right-click on the project, choose <emphasis><property>Export</property>
+ </emphasis>:</para>
+
+ <figure>
+ <title>Export of ESB project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/24_export_button.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <figure><title>Choosing ESB File</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/25_esb_file.png"/>
- </imageobject>
- </mediaobject>
- </figure>
+ <para>Choose <emphasis><property>ESB</property>
+ </emphasis> > <emphasis><property>ESB File</property>
+ </emphasis> and click <emphasis><property>Next</property>
+ </emphasis>:</para>
+
+ <figure>
+ <title>Choosing ESB File</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/25_esb_file.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <para>And finally export the ESB project to the file system: choose the destination, choose the target runtime if need a specific one and make the appropriate settings for the archive. Then click <emphasis><property>Finish</property></emphasis>.</para>
-
- <figure><title>ESB Export</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/26_esb_export.png"/>
- </imageobject>
- </mediaobject>
- </figure>
+ <para>And finally export the ESB project to the file system: choose the destination, choose the target runtime if need a specific one and make the appropriate settings for the archive. Then click <emphasis><property>Finish</property>
+ </emphasis>.</para>
+
+ <figure>
+ <title>ESB Export</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/26_esb_export.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Your project is deployed as an .esb archive.</para>
+ <para>An ESB archive can be created for ESB projects only. It is also possible to deploy an .esb archive to a JBoss AS based server with JBoss ESB installed.</para>
- <para>Your project is deployed as an .esb archive.</para>
- <para>An ESB archive can be created for ESB projects only. It is also possible to deploy an .esb archive to a JBoss AS based server with JBoss ESB installed.</para>
-
-
- </section>
-
- <section id="creating_esb_file">
- <title>Creating a ESB File</title>
- <para>In this chapter we suggest a step-by-step walk-through of creating your own
+
+ </section>
+
+ <section id="creating_esb_file">
+ <title>Creating a ESB File</title>
+ <para>In this chapter we suggest a step-by-step walk-through of creating your own
simple file. Let's try to organize a new ESB file.</para>
- <para>We will show you how to use the Creation wizard for creating a new ESB file.</para>
+ <para>We will show you how to use the Creation wizard for creating a new ESB file.</para>
- <para>At first you should open any project. Select <emphasis>
+ <para>At first you should open any project. Select <emphasis>
<property>File >New > Other...</property>
- </emphasis> in the main menu bar or context menu for selected project and
+ </emphasis> in the main menu bar or context menu for selected project and
then <emphasis>
<property>ESB > ESB File</property>
- </emphasis> in the New dialog:</para>
+ </emphasis> in the New dialog:</para>
- <figure>
- <title>Select a wizard - ESB File</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_support/01_create_esb.png"/>
- </imageobject>
- </mediaobject>
- </figure>
+ <figure>
+ <title>Select a wizard - ESB File</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_support/01_create_esb.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <para> Clicking <emphasis>
+ <para> Clicking <emphasis>
<property>Next</property>
- </emphasis> brings you to the wizard page where a folder, a name and a version for the file should be specified. Choose, for example, <emphasis>
+ </emphasis> brings you to the wizard page where a folder, a name and a version for the file should be specified. Choose, for example, <emphasis>
<property>jboss-esb.xml</property>
- </emphasis> as the name and accept the selected projects folder and the default
+ </emphasis> as the name and accept the selected projects folder and the default
version.</para>
-
- <note><title>Note:</title>
- <para>From the version 3.1.0 JBoss ESB Tools supports three different jboss-esb.xsd versions: jbossesb-1.0.1.xsd, jbossesb-1.1.0.xsd and jbossesb-1.2.0.xsd.
+
+ <note>
+ <title>Note:</title>
+ <para>From the version 3.1.0 JBoss ESB Tools supports three different jboss-esb.xsd versions: jbossesb-1.0.1.xsd, jbossesb-1.1.0.xsd and jbossesb-1.2.0.xsd.
If you use ESB 4.7 you should select jbossesb-1.2.0.xsd.
</para>
- </note>
- <figure>
- <title>Folder, Name and Version for ESB file</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_support/02_create_esb.png"/>
- </imageobject>
- </mediaobject>
- </figure>
+ </note>
+ <figure>
+ <title>Folder, Name and Version for ESB file</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_support/02_create_esb.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <para>Thus, your file will be created in the selected projects folder by default. If
+ <para>Thus, your file will be created in the selected projects folder by default. If
you want to change the folder for your future file click <emphasis>
<property>Browse...</property>
- </emphasis> button to set needed folder or simply type it.</para>
+ </emphasis> button to set needed folder or simply type it.</para>
- <para>Clicking on <emphasis>
+ <para>Clicking on <emphasis>
<property>Finish</property>
- </emphasis> results in the file being generated. The wizard creates one xml
+ </emphasis> results in the file being generated. The wizard creates one xml
file.</para>
- </section>
- <section id="creating_esb_action">
- <title>Creating a ESB Action</title>
- <para>From this chapter you will find out how to create a <emphasis><property>ESB Action Java File</property></emphasis>.</para>
- <para>At first you need to open a <property>ESB</property> or simple <property>Java</property> project. Then you should select <emphasis><property>File > New>Other</property></emphasis> in the main menu or from the context project menu. Then click <emphasis><property>ESB > ESB Action</property></emphasis> in the <emphasis><property>New </property></emphasis> dialog.</para>
- <figure>
- <title>Select a wizard - ESB Action</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_support/03_create_esb.png"/>
- </imageobject>
-
- </mediaobject>
- </figure>
- <para>After that click <emphasis><property>Next</property></emphasis> and you will be brought to the <emphasis><property>New ESB Action</property></emphasis> wizard. In this wizard the class name should be specified, also you can set a package or add a interface as for any Java class.</para>
- <figure>
- <title>New ESB Action wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_support/04_create_esb.png"/>
- </imageobject>
-
- </mediaobject>
- </figure>
- <para>As a result, the <property>ESB Action Java File</property> will be created in the selected package and it will have <property>org.jboss.soa.esb.actions.AbstractActionPipelineProcessor </property>as superclass. </para>
- <para>Clicking on <emphasis><property>Finish</property></emphasis> will generate the <property>ESB Action</property> class. Also this class will become available in <property>ESB Editor</property> wizards.</para>
- </section>
-
- <section role="updated">
- <title>Configuring ESB Runtime in Preferences</title>
- <para>In this chapter you will know how to predefine a JBoss ESB runtime on the Preferences page.</para>
+ </section>
+ <section id="creating_esb_action">
+ <title>Creating a ESB Action</title>
+ <para>From this chapter you will find out how to create a <emphasis><property>ESB Action Java File</property>
+ </emphasis>.</para>
+ <para>At first you need to open a <property>ESB</property> or simple <property>Java</property> project. Then you should select <emphasis><property>File > New>Other</property>
+ </emphasis> in the main menu or from the context project menu. Then click <emphasis><property>ESB > ESB Action</property>
+ </emphasis> in the <emphasis><property>New </property>
+ </emphasis> dialog.</para>
+ <figure>
+ <title>Select a wizard - ESB Action</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_support/03_create_esb.png"/>
+ </imageobject>
- <para>You may already know, there are two ways to set JBoss ESB runtime when creating a ESB project,
+ </mediaobject>
+ </figure>
+ <para>After that click <emphasis><property>Next</property>
+ </emphasis> and you will be brought to the <emphasis><property>New ESB Action</property>
+ </emphasis> wizard. In this wizard the class name should be specified, also you can set a package or add a interface as for any Java class.</para>
+ <figure>
+ <title>New ESB Action wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_support/04_create_esb.png"/>
+ </imageobject>
+
+ </mediaobject>
+ </figure>
+ <para>As a result, the <property>ESB Action Java File</property> will be created in the selected package and it will have <property>org.jboss.soa.esb.actions.AbstractActionPipelineProcessor </property>as superclass. </para>
+ <para>Clicking on <emphasis><property>Finish</property>
+ </emphasis> will generate the <property>ESB Action</property> class. Also this class will become available in <property>ESB Editor</property> wizards.</para>
+ </section>
+
+ <section role="updated">
+ <title>Configuring ESB Runtime in Preferences</title>
+ <para>In this chapter you will know how to predefine a JBoss ESB runtime on the Preferences page.</para>
+
+ <para>You may already know, there are two ways to set JBoss ESB runtime when creating a ESB project,
one is to use the project target JBoss runtime, and another is to select a JBoss ESB runtime predefined in JBoss Tools preferences.
Let's configure it.</para>
- <para>Select <emphasis>
+ <para>Select <emphasis>
<property>Window >Preferences > JBoss Tools > JBoss ESB Runtime</property>
- </emphasis>, to open the JBoss ESB Runtime Preferences page where you can add, remove and Edit a JBoss ESB runtime.</para>
+ </emphasis>, to open the JBoss ESB Runtime Preferences page where you can add, remove and Edit a JBoss ESB runtime.</para>
- <figure>
- <title>JBoss ESB Runtimes</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/10_esb_runtime.png"/>
- </imageobject>
- </mediaobject>
- </figure>
+ <figure>
+ <title>JBoss ESB Runtimes</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/10_esb_runtime.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <para> Select <emphasis><property>Add</property></emphasis> to open a dialog where you can specify the JBoss ESB runtime location, name and version number. It's also possible to define configuration if you point the home location to a Jboss AS or SOA-p, in case you select a standalone ESB runtime location, the configuration combo will be empty and should be ignored.
- You can also customize the libraries of the runtime by checking the <emphasis><property>Customize JBoss ESB Runtime jars</property> </emphasis> checkbox. </para>
-
- <figure>
- <title>Configure new JBoss ESB Runtime</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/11_esb_runtime_new.png"/>
- </imageobject>
- </mediaobject>
- </figure>
+ <para> Select <emphasis><property>Add</property>
+ </emphasis> to open a dialog where you can specify the JBoss ESB runtime location, name and version number. It's also possible to define configuration if you point the home location to a Jboss AS or SOA-p, in case you select a standalone ESB runtime location, the configuration combo will be empty and should be ignored.
+ You can also customize the libraries of the runtime by checking the <emphasis><property>Customize JBoss ESB Runtime jars</property>
+ </emphasis> checkbox. </para>
- <para>The new JBoss ESB Runtime will be configured. Click <emphasis> <property>OK</property> </emphasis> to finish and save the preferences.
+ <figure>
+ <title>Configure new JBoss ESB Runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/11_esb_runtime_new.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The new JBoss ESB Runtime will be configured. Click <emphasis> <property>OK</property>
+ </emphasis> to finish and save the preferences.
You can use the configuration when creating a JBoss ESB project. </para>
- <para>When a ESB runtime is configured for your ESB project you are able to change it to any other using the classpath container page for ESB runtime. To do that, turn to the Package Explorer view and right-click the "JBoss ESB Runtime" library. Select <emphasis><property>Properties</property></emphasis> and a table listing all available JBoss ESB runtimes will appear:</para>
+ <para>When a ESB runtime is configured for your ESB project you are able to change it to any other using the classpath container page for ESB runtime. To do that, turn to the Package Explorer view and right-click the "JBoss ESB Runtime" library. Select <emphasis><property>Properties</property>
+ </emphasis> and a table listing all available JBoss ESB runtimes will appear:</para>
+
+ <figure>
+ <title>Classpath Container Page to change ESB runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/20_classpath_container.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <figure>
- <title>Classpath Container Page to change ESB runtime</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/20_classpath_container.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
-
- <para>Choose one of them to set to the ESB project and click <emphasis><property>Ok</property></emphasis>.</para>
- <para>ESB container allows Source and JavaDoc locations to be set via the Properties dialog on each contained .jar: right-click on any .jar file, select <emphasis><property>Properties</property></emphasis>. Choose <emphasis><property>Java Source Attachment</property></emphasis> and select location (folder, JAR or zip) containing new source for the chosen .jar using one of the suggested options (workspace, external folder or file) or enter the path manually:</para>
-
- <figure>
- <title>Classpath Container: Java Source Attachment</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/21_source.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Click on <emphasis><property>Apply</property></emphasis> and then on <emphasis><property>Ok</property></emphasis>.</para>
- <para>To change Javadoc Location choose <emphasis><property>Javadoc Location</property></emphasis> and specify URL to the documentation generated by Javadoc. The Javadoc location will contain a file called <emphasis><property>package-list</property></emphasis>:</para>
-
- <figure>
- <title>Classpath Container: Javadoc Location</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/22_Javadoc.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Click on <emphasis><property>Apply</property></emphasis> and then on <emphasis><property>Ok</property></emphasis>.</para>
-
- </section>
+ <para>Choose one of them to set to the ESB project and click <emphasis><property>Ok</property>
+ </emphasis>.</para>
+ <para>ESB container allows Source and JavaDoc locations to be set via the Properties dialog on each contained .jar: right-click on any .jar file, select <emphasis><property>Properties</property>
+ </emphasis>. Choose <emphasis><property>Java Source Attachment</property>
+ </emphasis> and select location (folder, JAR or zip) containing new source for the chosen .jar using one of the suggested options (workspace, external folder or file) or enter the path manually:</para>
- <section id="using_SOA">
- <title>Using and Configuring SOA Platform</title>
-
- <para>In this chapter you will know what is JBoss Enterprise SOA Platform and how you can configure it to use for your ESB projects. </para>
+ <figure>
+ <title>Classpath Container: Java Source Attachment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/21_source.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click on <emphasis><property>Apply</property>
+ </emphasis> and then on <emphasis><property>Ok</property>
+ </emphasis>.</para>
+ <para>To change Javadoc Location choose <emphasis><property>Javadoc Location</property>
+ </emphasis> and specify URL to the documentation generated by Javadoc. The Javadoc location will contain a file called <emphasis><property>package-list</property>
+ </emphasis>:</para>
+
+ <figure>
+ <title>Classpath Container: Javadoc Location</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/22_Javadoc.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click on <emphasis><property>Apply</property>
+ </emphasis> and then on <emphasis><property>Ok</property>
+ </emphasis>.</para>
+
+ </section>
+
+
+ <section id="using_SOA">
+ <title>Using and Configuring SOA Platform</title>
+
+ <para>In this chapter you will know what is JBoss Enterprise SOA Platform and how you can configure it to use for your ESB projects. </para>
+
+ <para>JBoss Enterprise SOA Platform delivers a flexible, standards-based platform to integrate applications, SOA services, business events and automate business processes. The SOA Platform integrates specific versions of JBoss ESB, jBPM, Drools and the JBoss Enterprise Application Platform that are certified to work together in a single supported enterprise distribution.</para>
+ <para>Having configured JBoss Enterprise SOA Platform for your ESB project you don't need to install and configure ESB server and runtime as they are already included.</para>
+
+ <para>Check here to find more details on the platform: <ulink url="http://www.jboss.com/products/platforms/soa">JBoss Enterprise SOA Platform</ulink> and <ulink url="http://www.jboss.com/products/platforms/soa/components">JBoss Enterprise SOA Platform Component Details</ulink>.</para>
+ <para>You can find out what is SOA here: <ulink url="http://www.jboss.org/jbossesb/resources/SOABasics.html">Basics of SOA</ulink> and <ulink url="http://www.jboss.org/jbossesb/resources/SOAEOA.html">SOA and EOA</ulink>.</para>
+
+ <para>To configure the JBoss Enterprise SOA platform select <emphasis>
+ <property>Window > Preferences > Server > Runtime Environments</property>
+ </emphasis>, that will open the Server Runtime Environments Preferences page where you can add, remove and edit a Server Runtime Environment.</para>
+
+ <figure>
+ <title>Configure new Server Runtime Environment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/13NewServerRuntimeEnv.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Select <emphasis><property>Add</property>
+ </emphasis>, choose <emphasis><property>JBoss 4.2 Runtime</property>
+ </emphasis> as a type of runtime environment, check the <emphasis><property>Create a new local server</property>
+ </emphasis> checkbox and click <emphasis><property>Next</property>
+ </emphasis>:</para>
+ <figure>
+ <title>Type of Server Runtime Environment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/14typeOfRuntime.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>On the next step you can specify a name of the server runtime environment and browse to its location. Click <emphasis><property>Finish</property>
+ </emphasis> to add the server runtime environment.</para>
- <para>JBoss Enterprise SOA Platform delivers a flexible, standards-based platform to integrate applications, SOA services, business events and automate business processes. The SOA Platform integrates specific versions of JBoss ESB, jBPM, Drools and the JBoss Enterprise Application Platform that are certified to work together in a single supported enterprise distribution.</para>
- <para>Having configured JBoss Enterprise SOA Platform for your ESB project you don't need to install and configure ESB server and runtime as they are already included.</para>
- <para>Check here to find more details on the platform: <ulink url="http://www.jboss.com/products/platforms/soa">JBoss Enterprise SOA Platform</ulink> and <ulink url="http://www.jboss.com/products/platforms/soa/components">JBoss Enterprise SOA Platform Component Details</ulink>.</para>
- <para>You can find out what is SOA here: <ulink url="http://www.jboss.org/jbossesb/resources/SOABasics.html">Basics of SOA</ulink> and <ulink url="http://www.jboss.org/jbossesb/resources/SOAEOA.html">SOA and EOA</ulink>.</para>
-
- <para>To configure the JBoss Enterprise SOA platform select <emphasis>
- <property>Window > Preferences > Server > Runtime Environments</property></emphasis>, that will open the Server Runtime Environments Preferences page where you can add, remove and edit a Server Runtime Environment.</para>
-
- <figure>
- <title>Configure new Server Runtime Environment</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/13NewServerRuntimeEnv.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Select <emphasis><property>Add</property></emphasis>, choose <emphasis><property>JBoss 4.2 Runtime</property></emphasis> as a type of runtime environment, check the <emphasis><property>Create a new local server</property></emphasis> checkbox and click <emphasis><property>Next</property></emphasis>:</para>
- <figure>
- <title>Type of Server Runtime Environment</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/14typeOfRuntime.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>On the next step you can specify a name of the server runtime environment and browse to its location. Click <emphasis><property>Finish</property></emphasis> to add the server runtime environment.</para>
-
-
- <figure>
- <title>New Server Runtime Environment Details</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/15AddNew.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Now you have your SOA platform configured. To check the configuration create a ESB Project using instructions described <xref linkend="ESB_project_wizard"/>. As a result you will have two projects created:</para>
-
- <figure>
- <title>Helloworld Projects Created</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/16HelloworldProjects.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Then you will need to add JBoss ESB libraries to your projects to configure the SOA server runtime exactly for your projects. Right-click on your project, select <emphasis><property>Build Path > Add Libraries</property></emphasis>:</para>
-
- <figure>
- <title>Add Libraries</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/17_Add_new_libraries.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Choose <emphasis><property>JBoss ESB Libraries</property></emphasis> and click <emphasis><property>Next</property></emphasis>:</para>
-
- <figure>
- <title>ESB Libraries</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/18_select_libraries.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Select the necessary runtime to add to the project classpath:</para>
-
+ <figure>
+ <title>New Server Runtime Environment Details</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/15AddNew.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Now you have your SOA platform configured. To check the configuration create a ESB Project using instructions described <xref linkend="ESB_project_wizard"/>. As a result you will have two projects created:</para>
+
+ <figure>
+ <title>Helloworld Projects Created</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/16HelloworldProjects.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Then you will need to add JBoss ESB libraries to your projects to configure the SOA server runtime exactly for your projects. Right-click on your project, select <emphasis><property>Build Path > Add Libraries</property>
+ </emphasis>:</para>
+
+ <figure>
+ <title>Add Libraries</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/17_Add_new_libraries.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Choose <emphasis><property>JBoss ESB Libraries</property>
+ </emphasis> and click <emphasis><property>Next</property>
+ </emphasis>:</para>
+
+ <figure>
+ <title>ESB Libraries</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/18_select_libraries.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Select the necessary runtime to add to the project classpath:</para>
- <figure>
- <title>Select a ESB runtime</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/esb_project/19_select_runtime.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Click <emphasis><property>Finish</property></emphasis>.</para>
- <para>Now you can deploy your Helloworld project to the server and run a test class in the client Java project to see the test result in the Console view.</para>
+
+ <figure>
+ <title>Select a ESB runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/esb_project/19_select_runtime.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click <emphasis><property>Finish</property>
+ </emphasis>.</para>
+ <para>Now you can deploy your Helloworld project to the server and run a test class in the client Java project to see the test result in the Console view.</para>
+
+ </section>
-</section>
@@ -544,6 +641,5 @@
-
-
-</chapter>
\ No newline at end of file
+
+ </chapter>
\ No newline at end of file
13 years, 5 months
JBoss Tools SVN: r27931 - trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide.
by jbosstools-commits@lists.jboss.org
Author: dgolovin
Date: 2011-01-05 21:03:45 -0500 (Wed, 05 Jan 2011)
New Revision: 27931
Modified:
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3734Test.java
Log:
fix for test errors in Jsf.vpe.jsf.test plugin
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3734Test.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3734Test.java 2011-01-06 02:02:44 UTC (rev 27930)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3734Test.java 2011-01-06 02:03:45 UTC (rev 27931)
@@ -52,7 +52,7 @@
nsIDOMElement body = vpeController.getVisualBuilder().getContentArea();
assertEquals("bold", body.getAttribute(HTML.ATTR_CLASS)); //$NON-NLS-1$
- assertEquals("background-color: black;", body.getAttribute(HTML.ATTR_STYLE)); //$NON-NLS-1$
+ assertTrue(body.getAttribute(HTML.ATTR_STYLE).contains("background-color: black;")); //$NON-NLS-1$
if(getException()!=null) {
throw getException();
13 years, 5 months
JBoss Tools SVN: r27930 - trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test.
by jbosstools-commits@lists.jboss.org
Author: dgolovin
Date: 2011-01-05 21:02:44 -0500 (Wed, 05 Jan 2011)
New Revision: 27930
Modified:
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java
Log:
test for disabling JSP indexing
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2011-01-06 01:01:31 UTC (rev 27929)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2011-01-06 02:02:44 UTC (rev 27930)
@@ -13,6 +13,7 @@
import junit.framework.Test;
import junit.framework.TestSuite;
+import org.eclipse.jst.jsp.core.internal.java.search.JSPIndexManager;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.ChangeMessageBundleTest_JBIDE5818;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.ContextMenuDoubleInsertionTest_JBIDE3888;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.EditFontFamilyTest_JBIDE5872;
@@ -122,7 +123,7 @@
public static final String IMPORT_TEST_WITH_2_URL_PATTERNS_PROJECT_NAME = "TestWith2URLPatterns"; //$NON-NLS-1$
public static Test suite() {
-
+ JSPIndexManager.getInstance().shutdown();
TestSuite suite = new TestSuite("Tests for Vpe Jsf components"); //$NON-NLS-1$
// $JUnit-BEGIN$
/*
13 years, 5 months
JBoss Tools SVN: r27929 - trunk/documentation/guides/Beginners_Guide/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-05 20:01:31 -0500 (Wed, 05 Jan 2011)
New Revision: 27929
Modified:
trunk/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml
Log:
Editing and reviewing
Modified: trunk/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml
===================================================================
--- trunk/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml 2011-01-06 00:47:01 UTC (rev 27928)
+++ trunk/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml 2011-01-06 01:01:31 UTC (rev 27929)
@@ -31,7 +31,7 @@
</mediaobject>
</figure>
<para>
- Refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/Visual_Web_To...">Editors</ulink> chapter of <citetitle pubwork="book">Visual Web Tools Reference Guide</citetitle> for full details.
+ Refer to the <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html-single/...">Editors</ulink> chapter of <citetitle pubwork="book">Visual Web Tools Reference Guide</citetitle> for full details.
</para>
</listitem>
</varlistentry>
13 years, 5 months
JBoss Tools SVN: r27928 - in trunk/documentation/guides/Beginners_Guide/en-US: images and 1 other directory.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-05 19:47:01 -0500 (Wed, 05 Jan 2011)
New Revision: 27928
Modified:
trunk/documentation/guides/Beginners_Guide/en-US/The_interface.xml
trunk/documentation/guides/Beginners_Guide/en-US/images/JBoss_AS_localhost.png
Log:
Updated screenshot and fixed instructions on addin a new Jboss server
Modified: trunk/documentation/guides/Beginners_Guide/en-US/The_interface.xml
===================================================================
--- trunk/documentation/guides/Beginners_Guide/en-US/The_interface.xml 2011-01-06 00:27:57 UTC (rev 27927)
+++ trunk/documentation/guides/Beginners_Guide/en-US/The_interface.xml 2011-01-06 00:47:01 UTC (rev 27928)
@@ -211,10 +211,10 @@
</listitem>
<listitem>
<para>
- Click the <guibutton>Next ></guibutton> button to display the <guilabel>Runtime Information</guilabel> for the server you are about to add. If all the information is correct click the <guibutton>Finish</guibutton> button.
+ If all the information is correct click the <guibutton>Finish</guibutton> button.
</para>
<para>
- If you need to change any information click the <guibutton>< Back</guibutton> button until you reach the screen with the information that needs to be altered and then navigate back to the <guilabel>Runtime Information</guilabel> screen and click the <guibutton>Finish</guibutton> button.
+ If you need to change any information click the <guibutton>< Back</guibutton> button until you reach the screen with the information that needs to be altered and then navigate back to the <guilabel>JBoss RunTime</guilabel> screen and click the <guibutton>Finish</guibutton> button.
</para>
</listitem>
</orderedlist>
Modified: trunk/documentation/guides/Beginners_Guide/en-US/images/JBoss_AS_localhost.png
===================================================================
(Binary files differ)
13 years, 5 months
JBoss Tools SVN: r27927 - in trunk/jbpm/docs/converter_ref/en-US: images and 1 other directory.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-05 19:27:57 -0500 (Wed, 05 Jan 2011)
New Revision: 27927
Modified:
trunk/jbpm/docs/converter_ref/en-US/Revision_History.xml
trunk/jbpm/docs/converter_ref/en-US/bpmn2jpdl.xml
trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_1.png
trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_2.png
trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_3.png
trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_4.png
trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_5.png
trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_7.png
trunk/jbpm/docs/converter_ref/en-US/overview.xml
Log:
Screenshot refresh and some line editing.
Modified: trunk/jbpm/docs/converter_ref/en-US/Revision_History.xml
===================================================================
--- trunk/jbpm/docs/converter_ref/en-US/Revision_History.xml 2011-01-05 21:22:50 UTC (rev 27926)
+++ trunk/jbpm/docs/converter_ref/en-US/Revision_History.xml 2011-01-06 00:27:57 UTC (rev 27927)
@@ -5,6 +5,17 @@
<title>Revision History</title>
<simpara>
<revhistory>
+ <revision>
+ <revnumber>2</revnumber><date>Thu Jan 06 2011</date>
+ <author>
+ <firstname>JBoss Tools</firstname><surname>Documentation Team</surname><email>mcaspers(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>General updates and screenshot refresh</member>
+ </simplelist>
+ </revdescription>
+ </revision>
<revision>
<revnumber>1</revnumber><date>Wed Jun 09 2010</date>
<author>
Modified: trunk/jbpm/docs/converter_ref/en-US/bpmn2jpdl.xml
===================================================================
--- trunk/jbpm/docs/converter_ref/en-US/bpmn2jpdl.xml 2011-01-05 21:22:50 UTC (rev 27926)
+++ trunk/jbpm/docs/converter_ref/en-US/bpmn2jpdl.xml 2011-01-06 00:27:57 UTC (rev 27927)
@@ -1,16 +1,22 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<chapter id="bpmn2jpdl" >
- <title>Translate a Bpmn file to a JPDL file</title>
- <para>In this chapter we provide you with the necessary steps to translate a Bpmn file to a JPDL file.</para>
+ <title>Translate a Bpmn file to a JPDL file</title>
+ <para>This chapter provides you with the necessary steps to translate a Bpmn file to a JPDL file.</para>
<section id="createproject">
<title>Creating a project</title>
<para>Before creating a Bpmn file, you should have a Project created.</para>
- <para>Create a project by
- <emphasis><property>New > Project... > General > Project</property></emphasis>. Enter the following information:
- </para>
- <para>Project Name: test</para>
-
+ <para>
+ Create a project by selecting
+ <menuchoice>
+ <guimenuitem>File</guimenuitem>
+ <guimenuitem>New</guimenuitem>
+ <guimenuitem>Project...</guimenuitem>
+ <guimenuitem>General</guimenuitem>
+ <guimenuitem>Project</guimenuitem>
+ </menuchoice>.
+ </para>
+ <para>Enter <guilabel>test</guilabel> in the <guilabel>Project name</guilabel> field, and click the <guibutton>Finish</guibutton> button.</para>
<figure>
<title>Creating a Project</title>
<mediaobject>
@@ -19,15 +25,21 @@
</imageobject>
</mediaobject>
</figure>
- <para>Click on the <property>Finish</property> button.</para>
</section>
<section id="createbpmnfile">
- <title>Creating a Bpmn File by STP BPMN Editor</title>
- <para>Create a BPMN diagram file by
- <emphasis><property>New > Others... > Bpmn Diagram</property></emphasis>
- . Enter the following information:
+ <title>Creating a BPMN file using the STP BPMN editor</title>
+ <para>Create a BPMN diagram file by selecting
+ <menuchoice>
+ <guimenuitem>File</guimenuitem>
+ <guimenuitem>New</guimenuitem>
+ <guimenuitem>Other...</guimenuitem>
+ <guimenuitem>Other</guimenuitem>
+ <guimenuitem>Bpmn Diagram</guimenuitem>
+ </menuchoice>.
</para>
- <para>File Name: test</para>
+
+ <para>Enter <guilabel>test</guilabel> in the <guilabel>File name</guilabel> field, and click the <guibutton>Finish</guibutton> button.</para>
+
<figure>
<title>Creating BPMN Diagram</title>
<mediaobject>
@@ -36,19 +48,23 @@
</imageobject>
</mediaobject>
</figure>
- <para>Click on the <property>Finish</property> button.</para>
- <para>Open the test.bpmn_diagram file by double-click it.</para>
- <para>Draw the Bpmn diagram using STP BPMN editor. If you do not know how to use STP BPMN editor, please visit <ulink url="http://www.eclipse.org/bpmn/">BPMN project page for details</ulink>.</para>
+ <para>Open the <guilabel>test.bpmn_diagram</guilabel> file by double-clicking it.</para>
+ <para>Draw the Bpmn diagram using the STP BPMN editor. For more information on how to use the STP BPMN editor, please visit the <ulink url="http://www.eclipse.org/bpmn/">BPMN project page</ulink>.</para>
</section>
<section id="bpmntojpdl">
<title>Exporting a Bpmn File to Jpdl files</title>
<para>A Bpmn file may include more than one pool. Every pool can be mapped to a corresponding Jpdl file.</para>
<itemizedlist>
<listitem>
- <para>Select 'test.bpmn' file and right-click it. Open the export wizard by
- <emphasis><property>Export... -> BPMN -> BPMN to jPDL</property></emphasis>
- .
+ <para>Select the <guilabel>test.bpmn</guilabel> file and right-click on it. Open the export wizard by selecting
+ <menuchoice>
+ <guimenuitem>Export...</guimenuitem>
+ <guimenuitem>BPMN</guimenuitem>
+ <guimenuitem>BPMN to jPDL...</guimenuitem>
+ </menuchoice>
+ from the context menu.
</para>
+ <para>Click the <guibutton>Next</guibutton> button.</para>
<figure>
<title>BPMN Export</title>
<mediaobject>
@@ -57,10 +73,10 @@
</imageobject>
</mediaobject>
</figure>
- <para>Click on the <property>Next</property> button.</para>
+
</listitem>
<listitem>
- <para>Select the BPMN file that you want to translate.
+ <para>Select the BPMN file that you want to translate, and click the <guibutton>Next</guibutton> button.
</para>
<figure>
<title>Choosing a BPMN File</title>
@@ -70,10 +86,9 @@
</imageobject>
</mediaobject>
</figure>
- <para>Click on the <property>Next</property> button.</para>
</listitem>
<listitem>
- <para>Select the Pools of BPMN that you want to translate.
+ <para>Select the BPMN Pools that you want to translate, and click the <guibutton>Next</guibutton> button.
</para>
<figure>
<title>Choosing BPMN Pools</title>
@@ -83,16 +98,16 @@
</imageobject>
</mediaobject>
</figure>
- <para>Click on the <property>Next</property> button.</para>
</listitem>
<listitem>
<para>On the next page, you may get error or warning messages that occurred during the conversion. If there are no messages, this page is skipped.
</para>
- <para>Click on the <property>Next</property> button.</para>
+ <para>Click on the <guibutton>Next</guibutton> button.</para>
</listitem>
<listitem>
- <para>Select the target location to save the generated JPDL files.
+ <para>Select the target location where the generated JPDL files will be saved. If you'd like to overwrite existing resources,check this "Overwrite existing resources" checkbox.
</para>
+ <para>Click on the <guibutton>Finish</guibutton> button to generate the JPDL files in the target location.</para>
<figure>
<title>Target Location</title>
<mediaobject>
@@ -101,13 +116,9 @@
</imageobject>
</mediaobject>
</figure>
- <itemizedlist>
- <listitem>
- <para>If you'd like to overwrite existing resources,check this "Overwrite existing resources" checkbox.</para>
- </listitem>
- </itemizedlist>
- <para>Click on the <property>Finish</property> button.</para>
- <para>Then the JPDL files are generated to the target location.</para>
+
+
+ <para></para>
</listitem>
</itemizedlist>
<para>The generated files look like this: </para>
@@ -119,7 +130,7 @@
</imageobject>
</mediaobject>
</figure>
- <para>We hope, this guide helped you to get started with the JBoss BPMN Convert module. Besides, for additional information you are welcome on <ulink
+ <para>We hope this guide helped you to get started with the JBoss BPMN Convert module. For additional information and support please visit the <ulink
url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para>
</section>
Modified: trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_1.png
===================================================================
(Binary files differ)
Modified: trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_2.png
===================================================================
(Binary files differ)
Modified: trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_3.png
===================================================================
(Binary files differ)
Modified: trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_4.png
===================================================================
(Binary files differ)
Modified: trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_5.png
===================================================================
(Binary files differ)
Modified: trunk/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_7.png
===================================================================
(Binary files differ)
Modified: trunk/jbpm/docs/converter_ref/en-US/overview.xml
===================================================================
--- trunk/jbpm/docs/converter_ref/en-US/overview.xml 2011-01-05 21:22:50 UTC (rev 27926)
+++ trunk/jbpm/docs/converter_ref/en-US/overview.xml 2011-01-06 00:27:57 UTC (rev 27927)
@@ -3,13 +3,13 @@
<title>BPMN Convert Overview</title>
<para>This chapter gives you a short overview of JBoss BPMN Convert module.</para>
<para>JBoss BPMN Convert module is a tool used for a BPMN file translation.</para>
- <para>As a part of JBoss tools, JBoss BPMN Convert module implements BPMN -> JPDL translation. You can get a basic JPDL file from a BPMN file by using this module.</para>
- <para>The BPMN file may be written by hands or with the help of some editors. In this guide, we use STP BPMN editor to draw a BPMN file.</para>
- <para>You can download the editor which is included into BPMN Modeler from Eclipse download or update site. On the <ulink url="http://www.eclipse.org/bpmn">Eclipse BPMN project page</ulink> you can find the necessary links and other related information.</para>
+ <para>As a part of JBoss tools, JBoss BPMN Convert module implements BPMN to JPDL translation. You can get a basic JPDL file from a BPMN file by using this module.</para>
+ <para>The BPMN file may be written by hand, or with the help of an editor. In this guide, we use the STP BPMN editor to draw a BPMN file.</para>
+ <para>You can download the editor, which is included with the BPMN Modeler, using Eclipse and the SOA Tools project update site. You can find the necessary links and other related information on the <ulink url="http://www.eclipse.org/bpmn">Eclipse BPMN project page</ulink>.</para>
<section>
<title>Key Features of JBoss BPMN Convert module</title>
- <para>For a start, we propose you to look through the table of main features of JBoss BPMN Convert module:</para>
+ <para>To start, take a look through the table of JBoss BPMN Convert module main features:</para>
<table>
@@ -32,9 +32,9 @@
<row>
<entry><para>STP BPMN Editor</para></entry>
- <entry><para>JBoss BPMN Convert module contains STP Business Process Modeling Notation (BPMN) Editor which is a tool to express any processes in a graphical form (simple diagrams with a set of some graphical elements). Created BPMN files can then be converted to jPDL.</para></entry>
+ <entry><para>JBoss BPMN Convert module contains the STP Business Process Modeling Notation (BPMN) Editor, which is a tool to express any processes in a graphical form (as simple diagrams with a set of graphical elements). These BPMN files can then be converted to jPDL.</para></entry>
<entry>
- <link linkend="createbpmnfile">creating a BPMN file by STP BPMN editor</link>
+ <link linkend="createbpmnfile">Creating a BPMN file using the STP BPMN editor</link>
</entry>
</row>
13 years, 5 months
JBoss Tools SVN: r27926 - in trunk/ws/tests/org.jboss.tools.ws.creation.core.test: META-INF and 1 other directory.
by jbosstools-commits@lists.jboss.org
Author: nickboldt
Date: 2011-01-05 16:22:50 -0500 (Wed, 05 Jan 2011)
New Revision: 27926
Modified:
trunk/ws/tests/org.jboss.tools.ws.creation.core.test/.classpath
trunk/ws/tests/org.jboss.tools.ws.creation.core.test/META-INF/MANIFEST.MF
trunk/ws/tests/org.jboss.tools.ws.creation.core.test/pom.xml
Log:
https://issues.jboss.org/browse/JBIDE-6581 bump up to source/target = 1.6 and increase test timeout from 30 to 45 mins
Modified: trunk/ws/tests/org.jboss.tools.ws.creation.core.test/.classpath
===================================================================
--- trunk/ws/tests/org.jboss.tools.ws.creation.core.test/.classpath 2011-01-05 20:42:54 UTC (rev 27925)
+++ trunk/ws/tests/org.jboss.tools.ws.creation.core.test/.classpath 2011-01-05 21:22:50 UTC (rev 27926)
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
- <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
+ <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6"/>
<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
<classpathentry kind="src" path="src"/>
<classpathentry kind="output" path="bin"/>
Modified: trunk/ws/tests/org.jboss.tools.ws.creation.core.test/META-INF/MANIFEST.MF
===================================================================
--- trunk/ws/tests/org.jboss.tools.ws.creation.core.test/META-INF/MANIFEST.MF 2011-01-05 20:42:54 UTC (rev 27925)
+++ trunk/ws/tests/org.jboss.tools.ws.creation.core.test/META-INF/MANIFEST.MF 2011-01-05 21:22:50 UTC (rev 27926)
@@ -40,5 +40,5 @@
Bundle-Vendor: %Bundle-Vendor.0
Bundle-Localization: plugin
Import-Package: org.eclipse.jdt.launching
-Bundle-RequiredExecutionEnvironment: J2SE-1.5
+Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Modified: trunk/ws/tests/org.jboss.tools.ws.creation.core.test/pom.xml
===================================================================
--- trunk/ws/tests/org.jboss.tools.ws.creation.core.test/pom.xml 2011-01-05 20:42:54 UTC (rev 27925)
+++ trunk/ws/tests/org.jboss.tools.ws.creation.core.test/pom.xml 2011-01-05 21:22:50 UTC (rev 27926)
@@ -1,19 +1,45 @@
<project
-xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <modelVersion>4.0.0</modelVersion>
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"
+ xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
+ <modelVersion>4.0.0</modelVersion>
<parent>
- <groupId>org.jboss.tools</groupId>
- <artifactId>org.jboss.tools.parent.pom</artifactId>
- <version>0.0.1-SNAPSHOT</version>
+ <groupId>org.jboss.tools</groupId>
+ <artifactId>org.jboss.tools.parent.pom</artifactId>
+ <version>0.0.1-SNAPSHOT</version>
</parent>
<groupId>org.jboss.tools.ws.tests</groupId>
- <artifactId>org.jboss.tools.ws.creation.core.test</artifactId>
+ <artifactId>org.jboss.tools.ws.creation.core.test</artifactId>
<version>1.0.0-SNAPSHOT</version>
<packaging>eclipse-test-plugin</packaging>
<properties>
- <systemProperties>-Djbosstools.test.jboss.home.4.2=${requirement.build.root}/jboss-4.2.3.GA</systemProperties>
+ <systemProperties>-Djbosstools.test.jboss.home.4.2=${requirement.build.root}/jboss-4.2.3.GA</systemProperties>
<emma.filter>org.jboss.tools.ws.creation.core*</emma.filter>
<emma.instrument.bundles>org.jboss.tools.ws.creation.core</emma.instrument.bundles>
</properties>
+
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.sonatype.tycho</groupId>
+ <artifactId>maven-osgi-compiler-plugin</artifactId>
+ <version>${tychoVersion}</version>
+ <configuration>
+ <source>1.6</source>
+ <target>1.6</target>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.sonatype.tycho</groupId>
+ <artifactId>maven-osgi-test-plugin</artifactId>
+ <version>${tychoVersion}</version>
+ <configuration>
+ <!-- timeout in seconds -->
+ <surefire.timeout>2700</surefire.timeout>
+ <forkedProcessTimeoutInSeconds>2700</forkedProcessTimeoutInSeconds>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
+
</project>
13 years, 5 months
JBoss Tools SVN: r27925 - trunk/build/parent.
by jbosstools-commits@lists.jboss.org
Author: nickboldt
Date: 2011-01-05 15:42:54 -0500 (Wed, 05 Jan 2011)
New Revision: 27925
Modified:
trunk/build/parent/pom.xml
Log:
add documentation on how to set compiler source/target for a given plugin or component
Modified: trunk/build/parent/pom.xml
===================================================================
--- trunk/build/parent/pom.xml 2011-01-05 20:39:26 UTC (rev 27924)
+++ trunk/build/parent/pom.xml 2011-01-05 20:42:54 UTC (rev 27925)
@@ -177,6 +177,20 @@
<parallel>true</parallel>
</configuration>
</plugin>
+ <plugin>
+ <groupId>org.sonatype.tycho</groupId>
+ <artifactId>maven-osgi-compiler-plugin</artifactId>
+ <version>${tychoVersion}</version>
+ <!-- not strictly needed but this suppresses warnings when compiling
+ that the default value (1.5) is being overwritten by the value in the MANIFEST.MF.
+ You can use this in your plugins or their aggregator pom.xml files to set
+ this for your plugins -->
+ <configuration>
+ <!-- <source>1.6</source> -->
+ <!-- <target>1.6</target> -->
+ </configuration>
+ </plugin>
+
</plugins>
</build>
@@ -825,7 +839,7 @@
</repository>
</repositories>
</profile>
-
+
<profile>
<id>jbosstools-nightly-staging-composite-trunk</id>
<activation>
@@ -845,7 +859,7 @@
</repository>
</repositories>
</profile>
-
+
<profile>
<!-- this plugin is available from https://github.com/nickboldt/maven-plugins/tree/master/unique-GAV-plugin/ -->
<id>GAV</id>
13 years, 5 months
JBoss Tools SVN: r27924 - in trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration: wizard and 1 other directory.
by jbosstools-commits@lists.jboss.org
Author: rob.stryker(a)jboss.com
Date: 2011-01-05 15:39:26 -0500 (Wed, 05 Jan 2011)
New Revision: 27924
Modified:
trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/rse/util/RSEUtils.java
trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/wizard/CreateRSEFromInstanceJob.java
trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/wizard/RSEandASWizardPage.java
Log:
JBIDE-7889 delay and wait for ssh port to come up
Modified: trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/rse/util/RSEUtils.java
===================================================================
--- trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/rse/util/RSEUtils.java 2011-01-05 20:30:14 UTC (rev 27923)
+++ trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/rse/util/RSEUtils.java 2011-01-05 20:39:26 UTC (rev 27924)
@@ -96,6 +96,38 @@
return services[0];
}
+ public static IStatus connect(IConnectorService service, IProgressMonitor monitor) throws Exception {
+ monitor.worked(1);
+ service.connect(monitor);
+ monitor.done();
+ return Status.OK_STATUS;
+ }
+
+ public static IStatus connect(IConnectorService service, int timeout, IProgressMonitor monitor) {
+ monitor.beginTask("Connecting to remote server", timeout);
+ monitor.setTaskName("Connecting to remote server");
+ IStatus status = null;
+ int count = 0;
+ while( status == null && count < timeout) {
+ try {
+ status = connect(service, monitor);
+ monitor.done();
+ return status;
+ } catch(Exception e) {
+ System.out.println("Exception " + e.getMessage() + " at timeout " + count);
+ count += 1000;
+ monitor.worked(1000);
+ try {
+ Thread.sleep(1000);
+ } catch(InterruptedException ie) {
+ }
+ }
+ }
+ monitor.done();
+ return status;
+ }
+
+
public static Job connect(String connectionName, final IConnectorService service)
throws Exception {
// TODO: internationalize strings
@@ -107,11 +139,9 @@
@Override
protected IStatus run(IProgressMonitor monitor) {
try {
- monitor.worked(1);
- service.connect(monitor);
- monitor.done();
- return Status.OK_STATUS;
- } catch (Exception e) {
+ return connect(service, monitor);
+ } catch(Exception e) {
+ e.printStackTrace();
// odd behavior: service reports connection failure even if things seem to work (view opens up with connection in it)
// ignore errors since things work
//
Modified: trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/wizard/CreateRSEFromInstanceJob.java
===================================================================
--- trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/wizard/CreateRSEFromInstanceJob.java 2011-01-05 20:30:14 UTC (rev 27923)
+++ trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/wizard/CreateRSEFromInstanceJob.java 2011-01-05 20:39:26 UTC (rev 27924)
@@ -13,11 +13,13 @@
import org.eclipse.core.runtime.IProgressMonitor;
import org.eclipse.core.runtime.IStatus;
import org.eclipse.core.runtime.Status;
+import org.eclipse.core.runtime.SubProgressMonitor;
import org.eclipse.core.runtime.jobs.Job;
import org.eclipse.core.runtime.preferences.InstanceScope;
import org.eclipse.osgi.util.NLS;
import org.eclipse.rse.core.model.IHost;
import org.eclipse.swt.widgets.Display;
+import org.eclipse.ui.internal.progress.ProgressManagerUtil;
import org.jboss.tools.deltacloud.core.DeltaCloudInstance;
import org.jboss.tools.deltacloud.core.job.AbstractInstanceJob;
import org.jboss.tools.deltacloud.integration.Messages;
@@ -45,6 +47,7 @@
String hostname = RSEUtils.createHostName(instance);
if (hostname != null && hostname.length() > 0 && isAutoconnect()) {
try {
+ monitor.beginTask("Create RSE Server", 100);
String connectionName = RSEUtils.createConnectionName(instance);
IHost host = RSEUtils.createHost(connectionName,
RSEUtils.createHostName(instance),
@@ -53,7 +56,10 @@
if( nextJob2 != null && nextJob2 instanceof CreateServerFromRSEJob) {
((CreateServerFromRSEJob)nextJob2).setHost(host);
}
- RSEUtils.connect(connectionName, RSEUtils.getConnectorService(host));
+ monitor.worked(10);
+
+ SubProgressMonitor submon = new SubProgressMonitor(monitor, 90);
+ RSEUtils.connect(RSEUtils.getConnectorService(host), 90000, submon);
} catch (Exception e) {
return ErrorUtils.handleError(Messages.ERROR,
NLS.bind(Messages.COULD_NOT_LAUNCH_RSE_EXPLORER2, instance.getName()),
Modified: trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/wizard/RSEandASWizardPage.java
===================================================================
--- trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/wizard/RSEandASWizardPage.java 2011-01-05 20:30:14 UTC (rev 27923)
+++ trunk/deltacloud/plugins/org.jboss.tools.deltacloud.integration/src/org/jboss/tools/deltacloud/integration/wizard/RSEandASWizardPage.java 2011-01-05 20:39:26 UTC (rev 27924)
@@ -216,9 +216,10 @@
private void refreshServerWidgets() {
boolean enabled = createServer.getSelection();
- boolean enabled2 = false;
serverDetailsGroup.setEnabled(enabled);
autoScanCheck.setEnabled(enabled);
+ autoLocalRuntimeLabel.setEnabled(enabled);
+ autoLocalRuntimeCombo.setEnabled(enabled);
remoteDetailsLoc.setEnabled(enabled);
hardCodeServerDetails.setEnabled(enabled);
serverHomeText.setEnabled(enabled);
13 years, 5 months
JBoss Tools SVN: r27923 - trunk/modeshape/plugins/org.jboss.tools.modeshape.rest.
by jbosstools-commits@lists.jboss.org
Author: nickboldt
Date: 2011-01-05 15:30:14 -0500 (Wed, 05 Jan 2011)
New Revision: 27923
Modified:
trunk/modeshape/plugins/org.jboss.tools.modeshape.rest/pom.xml
Log:
add org.sonatype.tycho:maven-osgi-compiler-plugin with source/target == 1.6 to suppress warnings in log
Modified: trunk/modeshape/plugins/org.jboss.tools.modeshape.rest/pom.xml
===================================================================
--- trunk/modeshape/plugins/org.jboss.tools.modeshape.rest/pom.xml 2011-01-05 19:44:18 UTC (rev 27922)
+++ trunk/modeshape/plugins/org.jboss.tools.modeshape.rest/pom.xml 2011-01-05 20:30:14 UTC (rev 27923)
@@ -14,6 +14,17 @@
<build>
<plugins>
<plugin>
+ <groupId>org.sonatype.tycho</groupId>
+ <artifactId>maven-osgi-compiler-plugin</artifactId>
+ <version>${tychoVersion}</version>
+ <!-- not strictly needed but this suppresses warnings when compiling
+ that the default value (1.5) is being overwritten by the value in the MANIFEST.MF -->
+ <configuration>
+ <source>1.6</source>
+ <target>1.6</target>
+ </configuration>
+ </plugin>
+ <plugin>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.4</version>
<executions>
@@ -21,13 +32,10 @@
<phase>validate</phase>
<configuration>
<tasks>
- <!-- JBDS-1343 uncomment this to pull a fresh copy of the jar from this or another location as needed -->
- <!--
- <delete file="modeshape-client.jar" quiet="true" />
- <get
- src="http://jawa05.englab.brq.redhat.com/candidate/SOA-5.1-ER3/JBDS/modeshape-..."
- dest="modeshape-client.jar" usetimestamp="true" />
- -->
+ <!-- JBDS-1343 uncomment this to pull a fresh copy of the jar from
+ this or another location as needed -->
+ <!-- <delete file="modeshape-client.jar" quiet="true" /> <get src="http://jawa05.englab.brq.redhat.com/candidate/SOA-5.1-ER3/JBDS/modeshape-..."
+ dest="modeshape-client.jar" usetimestamp="true" /> -->
</tasks>
</configuration>
<goals>
13 years, 5 months