November 2010 - jbosstools-commits

JBoss Tools SVN: r26898 - trunk/deltacloud/docs/Cloud_Tools_Reference_Guide.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2010-11-24 20:17:56 -0500 (Wed, 24 Nov 2010) New Revision: 26898 Modified: trunk/deltacloud/docs/Cloud_Tools_Reference_Guide/pom.xml Log: removing nexus links Modified: trunk/deltacloud/docs/Cloud_Tools_Reference_Guide/pom.xml =================================================================== --- trunk/deltacloud/docs/Cloud_Tools_Reference_Guide/pom.xml 2010-11-25 01:17:14 UTC (rev 26897) +++ trunk/deltacloud/docs/Cloud_Tools_Reference_Guide/pom.xml 2010-11-25 01:17:56 UTC (rev 26898) @@ -15,37 +15,6 @@ <docname>Cloud_Tools_Reference_Guid</docname> <bookname>Cloud Tools Reference Guid</bookname> </properties> - - <repositories> - <repository> - <id>jboss-public-repository-group</id> - <name>JBoss Public Maven Repository Group</name> - <url>https://repository.jboss.org/nexus/content/groups/public/</url> - <layout>default</layout> - <releases> - <enabled>true</enabled> - <updatePolicy>never</updatePolicy> - </releases> - <snapshots> - <enabled>true</enabled> - <updatePolicy>never</updatePolicy> - </snapshots> - </repository> - </repositories> - <pluginRepositories> - <pluginRepository> - <id>jboss-public-repository-group</id> - <name>JBoss Public Maven Repository Group</name> - <url>https://repository.jboss.org/nexus/content/groups/public/</url> - <layout>default</layout> - <releases> - <enabled>true</enabled> - </releases> - <snapshots> - <enabled>true</enabled> - </snapshots> - </pluginRepository> - </pluginRepositories> <profiles>

13 years, 6 months

1
0
0 / 0

JBoss Tools SVN: r26897 - trunk/birt/docs.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2010-11-24 20:17:14 -0500 (Wed, 24 Nov 2010) New Revision: 26897 Modified: trunk/birt/docs/pom.xml Log: removing nexus links Modified: trunk/birt/docs/pom.xml =================================================================== --- trunk/birt/docs/pom.xml 2010-11-25 01:07:06 UTC (rev 26896) +++ trunk/birt/docs/pom.xml 2010-11-25 01:17:14 UTC (rev 26897) @@ -15,37 +15,6 @@ <docname>Birt_Reference_Guide</docname> <bookname>Birt Reference Guide</bookname> </properties> - - <repositories> - <repository> - <id>jboss-public-repository-group</id> - <name>JBoss Public Maven Repository Group</name> - <url>https://repository.jboss.org/nexus/content/groups/public/</url> - <layout>default</layout> - <releases> - <enabled>true</enabled> - <updatePolicy>never</updatePolicy> - </releases> - <snapshots> - <enabled>true</enabled> - <updatePolicy>never</updatePolicy> - </snapshots> - </repository> - </repositories> - <pluginRepositories> - <pluginRepository> - <id>jboss-public-repository-group</id> - <name>JBoss Public Maven Repository Group</name> - <url>https://repository.jboss.org/nexus/content/groups/public/</url> - <layout>default</layout> - <releases> - <enabled>true</enabled> - </releases> - <snapshots> - <enabled>true</enabled> - </snapshots> - </pluginRepository> - </pluginRepositories> <profiles>

13 years, 6 months

1
0
0 / 0

JBoss Tools SVN: r26896 - trunk/bpel/docs/reference.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2010-11-24 20:07:06 -0500 (Wed, 24 Nov 2010) New Revision: 26896 Modified: trunk/bpel/docs/reference/pom.xml Log: updated pom file to use new jdocbook system Modified: trunk/bpel/docs/reference/pom.xml =================================================================== --- trunk/bpel/docs/reference/pom.xml 2010-11-25 01:00:28 UTC (rev 26895) +++ trunk/bpel/docs/reference/pom.xml 2010-11-25 01:07:06 UTC (rev 26896) @@ -15,37 +15,6 @@ <docname>JBoss_BPEL_User_Guide</docname> <bookname>JBoss BPEL User Guide</bookname> </properties> - - <repositories> - <repository> - <id>jboss-public-repository-group</id> - <name>JBoss Public Maven Repository Group</name> - <url>https://repository.jboss.org/nexus/content/groups/public/</url> - <layout>default</layout> - <releases> - <enabled>true</enabled> - <updatePolicy>never</updatePolicy> - </releases> - <snapshots> - <enabled>true</enabled> - <updatePolicy>never</updatePolicy> - </snapshots> - </repository> - </repositories> - <pluginRepositories> - <pluginRepository> - <id>jboss-public-repository-group</id> - <name>JBoss Public Maven Repository Group</name> - <url>https://repository.jboss.org/nexus/content/groups/public/</url> - <layout>default</layout> - <releases> - <enabled>true</enabled> - </releases> - <snapshots> - <enabled>true</enabled> - </snapshots> - </pluginRepository> - </pluginRepositories> <profiles>

13 years, 6 months

1
0
0 / 0

JBoss Tools SVN: r26895 - trunk/bpel/docs/reference.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2010-11-24 20:00:28 -0500 (Wed, 24 Nov 2010) New Revision: 26895 Added: trunk/bpel/docs/reference/publican.cfg Log: added for building publican Added: trunk/bpel/docs/reference/publican.cfg =================================================================== --- trunk/bpel/docs/reference/publican.cfg (rev 0) +++ trunk/bpel/docs/reference/publican.cfg 2010-11-25 01:00:28 UTC (rev 26895) @@ -0,0 +1,7 @@ +# Config::Simple 4.59 +# Fri Nov 20 13:19:45 2009 + +xml_lang: en-US +type: Book +brand: JBoss +

13 years, 6 months

1
0
0 / 0

JBoss Tools SVN: r26894 - trunk/bpel/docs/reference/en-US.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2010-11-24 19:58:42 -0500 (Wed, 24 Nov 2010) New Revision: 26894 Added: trunk/bpel/docs/reference/en-US/Author_Group.xml trunk/bpel/docs/reference/en-US/Book_Info.xml trunk/bpel/docs/reference/en-US/Feedback.xml trunk/bpel/docs/reference/en-US/JBoss_BPEL_User_Guide.ent trunk/bpel/docs/reference/en-US/JBoss_BPEL_User_Guide.xml trunk/bpel/docs/reference/en-US/Preface.xml trunk/bpel/docs/reference/en-US/Revision_History.xml trunk/bpel/docs/reference/en-US/deploy.xml trunk/bpel/docs/reference/en-US/detail.xml trunk/bpel/docs/reference/en-US/install.xml trunk/bpel/docs/reference/en-US/overview.xml trunk/bpel/docs/reference/en-US/reference.xml trunk/bpel/docs/reference/en-US/summary.xml trunk/bpel/docs/reference/en-US/tasks.xml Log: added files Added: trunk/bpel/docs/reference/en-US/Author_Group.xml =================================================================== --- trunk/bpel/docs/reference/en-US/Author_Group.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/Author_Group.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,5 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<authorgroup><author><firstname>Denny</firstname><surname>Xu</surname><email>dxu(a)redhat.com</email></author> + <author><firstname>Grid</firstname><surname>Qian</surname><email>fqian(a)redhat.com</email></author></authorgroup> Added: trunk/bpel/docs/reference/en-US/Book_Info.xml =================================================================== --- trunk/bpel/docs/reference/en-US/Book_Info.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/Book_Info.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<bookinfo><title>JBoss BPEL User Guide</title><subtitle>Provides information relating to the BPEL Tools set.</subtitle><productname>JBoss Developer Studio</productname><productnumber>3.0</productnumber><edition>3.0.1</edition><pubsnumber>0</pubsnumber><abstract><para>The JBoss BPEL User Guide explains how to use the BPEL Tools to create BPEL files quickly and with precision.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo> Added: trunk/bpel/docs/reference/en-US/Feedback.xml =================================================================== --- trunk/bpel/docs/reference/en-US/Feedback.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/Feedback.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,20 @@ +<?xml version='1.0' encoding='utf-8' ?> + +<section id="sect-Beginners_Guide-We_Need_Feedback" lang="en-US"> + <title>We Need Feedback!</title> + <indexterm> + <primary>feedback</primary> + <secondary>contact information for this manual</secondary> + </indexterm> + <para> + If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in JIRA against JBoss Developer Studio: <ulink url="https://jira.jboss.org/jira/secure/CreateIssue.jspa?pid=12310500&issu...">https://jira.jboss.org/jira/secure/CreateIssue.jspa?pid=12310500&issu...</ulink> + </para> + <para> + When submitting a bug report, be sure to mention the manual's name and to select the "documentation" component. + </para> + <para> + If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily. + </para> +</section> + + Added: trunk/bpel/docs/reference/en-US/JBoss_BPEL_User_Guide.ent =================================================================== --- trunk/bpel/docs/reference/en-US/JBoss_BPEL_User_Guide.ent (rev 0) +++ trunk/bpel/docs/reference/en-US/JBoss_BPEL_User_Guide.ent 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,4 @@ +<!ENTITY PRODUCT "JBoss"> +<!ENTITY BOOKID "JBoss_BPEL_User_Guide"> +<!ENTITY YEAR "2010"> +<!ENTITY HOLDER "Red Hat"> Added: trunk/bpel/docs/reference/en-US/JBoss_BPEL_User_Guide.xml =================================================================== --- trunk/bpel/docs/reference/en-US/JBoss_BPEL_User_Guide.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/JBoss_BPEL_User_Guide.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,15 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<book> +<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="install.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="tasks.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> + +  +<xi:include href="reference.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="summary.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +</book> Added: trunk/bpel/docs/reference/en-US/Preface.xml =================================================================== --- trunk/bpel/docs/reference/en-US/Preface.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/Preface.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<preface><title>Preface</title><xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></xi:fallback></xi:include></preface> Added: trunk/bpel/docs/reference/en-US/Revision_History.xml =================================================================== --- trunk/bpel/docs/reference/en-US/Revision_History.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/Revision_History.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<appendix><title>Revision History</title><simpara><revhistory><revision><revnumber>0</revnumber><date>Tue Jul 06 2010</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix> Added: trunk/bpel/docs/reference/en-US/deploy.xml =================================================================== --- trunk/bpel/docs/reference/en-US/deploy.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/deploy.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,132 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<chapter id="deploy"> + <title>Deploy a JBoss BPEL project to JBoss BPEL Runtime</title> + <section id="createdeploy"> + <title>Creating a bpel-deploy.xml file</title> + <para>If you want to deploy a BPEL project to JBoss BPEL Runtime, you should create a bpel-deploy.xml file. + JBoss tools can help you to create it: + </para> + <itemizedlist> + <listitem> + <para>Create the bpel-deploy.xml by selecting + <emphasis><property>New > Other... > BPEL 2.0 > Apache ODE Deployment Descriptor</property></emphasis>. Click the <property>Next</property> button. + </para> + <figure> + <title>New BPEL Deploy file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_1.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>On the next wizard page you should enter the following information:</para> + <para><emphasis><property>BPEL Project</property></emphasis>: Click the <property>Browse...</property> button to select the BPEL project in your workspace which you want to deploy to the runtime. + Please note, that you should select the <property>bpelContent</property> folder in your new BPEL project as a value of <property>BPEL Project</property> field because the bpel-deploy.xml should be created in this place. + </para> + <para><emphasis><property>File name</property></emphasis>: The default value is bpel-deploy.xml. Please, don't change it.</para> + <para>Click on <property>Finish</property> button to close the wizard and a new bpel-deploy.xml file will be created.</para> + <figure> + <title>New BPEL Deploy file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_2.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Double-click the bpel-deploy.xml file to open it in ODE Descriptor Deployment Editor. + In the <property>Inbound Interfaces</property> section, click the + <property>Associated Port</property> column and select <property>HelloWorldProcessPort</property> + in the dropdown box.The <property>Related Service</property> and <property>Binding Used</property> + columns should be automatically filled in. Save the <emphasis><property>bpel-deploy.xml</property></emphasis>. + </para> + <figure> + <title>bpel-deploy.xml file editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_3.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + </section> + <section id="createruntime"> + <title>Creating JBoss BPEL Server</title> + <para>Suppose you have installed the <property>JBoss BPEL Runtime-RiftSaw</property>, now you can create a server for JBoss BPEL runtime.</para> + <itemizedlist> + <listitem> + <para>Open the <property>Servers</property> view by selecting + <emphasis><property>Windows > Show View > Other... > Server > Servers</property></emphasis>. + </para> + </listitem> + <listitem> + <para>Right-click the Servers view and select + <emphasis><property>New > Server</property></emphasis> to open the New Server Wizard: + </para> + <figure> + <title>New Server Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_4.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Select <property>JBoss AS 5.1 </property>as a server type. </para> + <note> + <para>Please note, that only JBoss As 5.1 or higher version supports BPEL.</para> + </note> + </listitem> + <listitem> + + <para>Click the <property>Next</property> button. On the next page, you should input your <emphasis><property>JBoss As</property></emphasis> location. Then click the <property>Next</property> button and + you will get the page like this: + </para> + <figure> + <title>Add resource to the server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_5.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Select <property>HelloWorld</property>, then click the <property>Add </property> button to add the project to the server. + Then click on the <property>Finish</property> button. + </para> + <para>Start the server by right-clicking on the server and selecting the <property>Start</property> item. </para> + + <figure> + <title>The started server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_6.png"/> + </imageobject> + </mediaobject> + </figure> + <para>If some aspects of server creation is not clear, please, read <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/as/html_single/index...">JBoss Server Manager Reference Guide</ulink> for more details.</para> + </listitem> + <listitem> + <para>You can enter the link <ulink url="http://localhost:8080/bpel/processes.html">http://localhost:8080/bpel/processes.html</ulink> to the browser to get the deployed processes.</para> + <figure> + <title>The BPEL console</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_7.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <para>If there's anything we didn't cover or you can't figure out, please feel free to visit our <ulink + url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201" + >JBoss Tools Users Forum</ulink> to ask questions. + There we are also waiting for your suggestions and comments.</para> + </section> +</chapter> \ No newline at end of file Added: trunk/bpel/docs/reference/en-US/detail.xml =================================================================== --- trunk/bpel/docs/reference/en-US/detail.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/detail.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,247 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<chapter id="detail"> + <title>Creating and editing a BPEL project</title> + <para>In the chapter we describe the necessary steps to create a new BPEL project and edit the BPEL files. + Here and further in the guide we will create + a simple echo example, used to respond to a sent message with a + modified version of the request message being returned in a response. + First of all, you should create a BPEL project. + + </para> + <section id="createproject"> + <title>Creating a BPEL project</title> + <para>Create the project by selecting + <emphasis><property>New > Project... > BPEL 2.0 > BPEL Project</property></emphasis> from the menu bar. + Then click the <property>Next</property> button. + </para> + <figure> + <title>New BPEL Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>On this page of the <property>New BPEL Project Wizard</property> enter a project name in the <property>Project Name</property> + field,e.g enter <property>HelloWorld</property>.</para> + + <figure> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click the <property>Finish</property> button. So you have created the BPEL project named <property>HelloWorld</property>. Its structure is like this: </para> + <figure> + <title>The BPEL Project structure</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_3.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="createprocess"> + <title>Creating a BPEL process</title> + <para>Now you should create a BPEL process. You can create it by selecting + <emphasis><property>New > Others... > BPEL 2.0 > New BPEL Process File</property></emphasis>. + </para> + <figure> + <title>New BPEL Process File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click the <property>Next</property> button. Enter the following information:</para> + <table> + + <title>Fields and values</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="2*"/> + <colspec colnum="2" colwidth="4*"/> + <thead> + <row> + <entry>Field</entry> + <entry>Value</entry> + + </row> + </thead> + <tbody> + <row> + <entry><para>BPEL Process Name</para></entry> + <entry><para>enter a process name. For example, <property>HelloWorld</property>.</para></entry> + </row> + <row> + <entry><para>Namespace</para></entry> + <entry><para>enter or select a namespace for the BPEL process.</para></entry> + </row> + <row> + <entry><para>Template</para></entry> + <entry><para>select a template for the BPEL process. When you select the template, you will see the information about the template below on the page.</para></entry> + </row> + + </tbody> + </tgroup> + </table> + + <figure> + <title>New BPEL Process File Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click the <property>Next</property> button. On the second page make sure that the folder <property>HelloWorld/bpelContent</property> is selected. + Click <property>Finish</property>. + </para> + <note> + <para>All of your files that are used in your BPEL project must be under the <property>bpelContent</property> folder. Only in this case + these files can be deployed to JBoss server. + </para> + </note> + + <para>Up to now, you have got a simple BPEL process as on the screen below.</para> + <figure> + <title>A simple BPEL Process File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The next step, you can do is to edit the BPEL process file and then deploy it to JBoss server. </para> + </section> + <section id="editprocess"> + <title>Editing a BPEL process file</title> + <para>If the <emphasis><property>Properties view</property></emphasis> and <emphasis><property>Palette view</property></emphasis> are not opened, you can open the views by right-clicking the BPEL editor and selecting + <property>Show in Properties</property>, <property>Show Palette in Palette view</property>. Then you should have the view like this: + </para> + <figure> + <title>The BPEL editor view</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>In the <emphasis><property>Palette view</property></emphasis>, you can drag a BPEL element to the BPEL editor and drop it in the place you want.</para> + <para>In the <emphasis><property>Properties view</property></emphasis>, you can get the information about every element of the BPEL process. + In the BPEL editor select any element you want,and then + the element's properties will be shown in the Properties view.The table below describes the tabs of the Properties view: + </para> + <table> + + <title>Tabs of the Property view</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="2*"/> + <colspec colnum="2" colwidth="4*"/> + <thead> + <row> + <entry>Tab</entry> + <entry>Description</entry> + + </row> + </thead> + <tbody> + <row> + <entry><para>Description</para></entry> + <entry><para>Shows the descriptive information about the element,e.g. <property>Name</property> of the element.</para></entry> + </row> + <row> + <entry><para>Details</para></entry> + <entry><para>Shows the detailed and important information about the element. + It is the most important section of an element. + Most of the properties of an element are set in this section.</para></entry> + </row> + <row> + <entry><para>Join Behavior</para></entry> + <entry><para>Shows the <property>Join Failure</property> property of the element.</para></entry> + </row> + <row> + <entry><para>Documentation</para></entry> + <entry><para>Shows the <property>documentation</property> sub-element of an element.</para></entry> + </row> + <row> + <entry><para>Other</para></entry> + <entry><para>Every BPEL element has its own sections: Correlation section, Message Exchange section, and so on. We will + introduce them while using them.</para></entry> + </row> + </tbody> + </tgroup> + </table> + <para>In order to see how a simple BPEL process works in action, you should do some steps as below: </para> + <itemizedlist> + <listitem> + <para>Add an <property>Assign</property> element between the <property>receiveInput</property> element and <property>replyOutput</property> element.</para> + </listitem> + <listitem> + <para>Click the <property>Assign</property> element in the BPEL editor in order to get the properties information of it in the Properties view. + </para> + </listitem> + <listitem> + <para>In the <property>Details</property> section of Properties view, you should click the <property>New</property> button to add a <property>copy</property> sub-element to the element. + Assign "input->payload->input" to "output->payload->result". At this time, an "<property>initializer</property>" popup dialog appears. Click on the <property>Yes</property> button in the dialog. + </para> + <figure> + <title>Add <property>Assign</property> to the process</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_2.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Open the file "<property>HelloWorldArtifacts.wsdl</property>" in the "<property>HelloWorld</property>" project by double-clicking the file. Right-click the WSDL editor and select + <property>Add Service</property>. A new service should appear in the editor. Name it <property>HelloWorldProcessService</property>. It has the Port + named <property>NewPort</property>. Select it, right-click on it and rename it to <property>HelloWorldProcessPort</property> in the Properties + view. + </para> + <figure> + <title>Add <property>Service</property> to the WSDL file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_3.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Right-click somewhere in the whitespace of the WSDL editor and select + <property>Add Binding</property>. A new Binding component will appear in the editor. Name it <property>HelloWorldSOAPBinding</property>. Select it, in the + General tab of the Properties view and select <property>HelloWorld</property> as a port type in the <property>PortType</property>. Then click on the + <property>Generate Binding Content...</property> button to open the <property>Binding Wizard</property>. In the wizard, select <property>SOAP </property> + as the <property>Protocol</property>. Finally, click the <property>Finish</property> button to close the wizard. + </para> + <figure> + <title>Add a <property>Binding</property> to the WSDL file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_4.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Click the <property>HelloWorldProcessPort</property> property in the General section of the Properties view, select <property>HelloWorldSOAPBinding</property> in + the <property>Binding</property> combobox. In the <property>Address</property> field input <ulink url="http://localhost:8080/bpel/processes/HelloWorld?wsdl">http://localhost:8080/bpel/processes/HelloWorld?wsdl</ulink>. + </para> + <figure> + <title>Add the <property>HelloWorldSOAPBinding</property> to the <property>HelloWorldProcessPort</property></title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_5.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <para>Now you have finished creating a simple BPEL process.As a next step, you can deploy the BPEL project to JBoss BPEL Runtime.</para> + + </section> +</chapter> Property changes on: trunk/bpel/docs/reference/en-US/detail.xml ___________________________________________________________________ Name: svn:executable + * Added: trunk/bpel/docs/reference/en-US/install.xml =================================================================== --- trunk/bpel/docs/reference/en-US/install.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/install.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,62 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<chapter id="install"> + <title>Installation JBoss BPEL Tools</title> + <section id="installeclipse"> + <title>Installation JBoss BPEL editor</title> + <para>At first, you need Eclipse 3.5. You can get it from <ulink url="http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo...">Eclipse Web Site</ulink>. + </para> + <para>The JBoss BPEL editor is included into JBoss Tools. + You have some methods to install JBoss Tools. + See <ulink url="http://www.jboss.org/tools/download/installation.html">Installing JBoss Tools</ulink> for more information.</para> + <para>If you want to install only the JBoss BPEL editor, you can install it from <ulink url="http://jboss.org/tools/download/dev.html">JBoss Tools</ulink> page separately. + Please, note, that only JBoss Tools 3.1 or higher version includes JBoss BPEL editor. + </para> + </section> + <section> + <title>Prerequisites</title> + <para>For installation and configuring BPEL engine into a JBossAS environment + you will need the following: </para> + <itemizedlist> + <listitem><para> JBossAS (version 5.1.0.GA or higher), + available from <ulink url="http://www.jboss.org/jbossas"> + http://www.jboss.org/jbossas</ulink>.</para></listitem> + <listitem><para>RiftSaw (version 2.0 or higher), available from <ulink url="http://www.jboss.org/riftsaw">http://www.jboss.org/riftsaw</ulink>.</para></listitem> + <listitem><para>Ant, available from <ulink url="http://ant.apache.org">here</ulink>.</para></listitem> + </itemizedlist> + + </section> + <section id="installRuntime"> + <title>Installation JBoss BPEL Runtime</title> + <itemizedlist> + <listitem> + <para>Unpack the JBossAS installation archive into the required location. + </para> + </listitem> + <listitem> + <para>Unpack the RiftSaw distribution into the location + alongside the JBossAS installation:</para> + <itemizedlist> + <listitem> + <para>Edit the <property>install/deployment.properties</property> file to update + the JBossAS location settings. + </para> + </listitem> + <listitem> + <para>From the <property>install</property> folder, + run: <property>ant deploy -Ddatabase=hsql</property> + to deploy RiftSaw to JBossAS. + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para>Then in the + <property>${RiftSaw}/install</property> folder run the command: + <property>ant deploy -Ddatabase=hsql -Dws.stack=native -Dws.version=3.2.2.GA</property> + It will help you to download the web service stack, and then upgrade it for JBoss AS. + </para> + </listitem> + </itemizedlist> + + </section> +</chapter> \ No newline at end of file Added: trunk/bpel/docs/reference/en-US/overview.xml =================================================================== --- trunk/bpel/docs/reference/en-US/overview.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/overview.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,67 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<chapter id="overview"> + <title>JBoss BPEL project Overview</title> + + <para>JBoss BPEL project is a WS-BPEL 2.0 project that gives a way to create, edit, validate and deploy BPEL files to JBoss BPEL runtime. It is based on Eclipse + <ulink url="http://www.eclipse.org/bpel/">BPEL + project </ulink>. </para> + + <para>It improves the Eclipse BPEL project in the following way: </para> + <itemizedlist> + <listitem><para> Implements close integration with JBoss BPEL runtime. Adds a new project type for the deployment to JBoss BPEL runtime.</para></listitem> + <listitem><para> Supports two ways of deployment: one way is to deploy a bpel project directly to JBoss BPEL runtime. The other way is to deploy bpel files in JBoss ESB project to JBoss BPEL runtime. </para></listitem> + <listitem><para> Improves the BPEL validator and increases Eclipse BPEL editor's quality. </para></listitem> + </itemizedlist> + + <para> + <ulink url="http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html">WS-BPEL 2.0</ulink> + stands for Web Service Business Process Execution Language. Like EAI, BPEL is an XML-based language, + but BPEL is more specific and targeted. A programmer uses BPEL to join sometimes + disparate functions into an integrated process, resulting in a seamless use of the Internet to + conduct business transactions ranging from simple money exchanges to complex calculations and + asset reallocation. + </para> + +<section> + <title>Key Features of JBoss BPEL project</title> + <para>Let's start with looking through the table of the main features of JBoss BPEL editor project: </para> + + <table> + + <title>Key Functionality for JBoss BPEL editor project</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="2*"/> + <colspec colnum="2" colwidth="4*"/> + <thead> + <row> + <entry>Feature</entry> + <entry>Benefit</entry> + + </row> + </thead> + <tbody> + <row> + <entry><para>WS-BPEL 2.0 support</para></entry> + <entry><para>JBoss BPEL project supports the newest WS-BPEL 2.0 specifications. </para></entry> + </row> + <row> + <entry><para>Close integration with JBoss BPEL runtime</para></entry> + <entry><para>There are two ways to deploy BPEL files to JBoss BPEL runtime. + The user can deploy a BPEL project as a whole and can deploy BPEL files in + JBoss ESB project to JBoss BPEL runtime. </para></entry> + </row> + <row> + <entry><para>BPEL file editor</para></entry> + <entry><para>The user can use the editor separately to edit a BPEL file. </para></entry> + </row> + <row> + <entry><para>BPEL file validator</para></entry> + <entry><para>The validator can give the error messages about BPEL files to the user. </para></entry> + </row> + </tbody> + </tgroup> + </table> + +</section> + +</chapter> \ No newline at end of file Property changes on: trunk/bpel/docs/reference/en-US/overview.xml ___________________________________________________________________ Name: svn:executable + * Added: trunk/bpel/docs/reference/en-US/reference.xml =================================================================== --- trunk/bpel/docs/reference/en-US/reference.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/reference.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,386 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="reference"> + <?dbhtml filename="reference.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>BPEL</keyword> + <keyword>JBT</keyword> + </keywordset> + </chapterinfo> + <title>Reference</title> + <para>This chapter includes detailed reference information about all BPEL tools wizards and editors.</para> + <section> + <title>Wizards</title> + <section> + <title>New BPEL project Wizard</title> + <para>This wizard helps to create new BPEL project.It is available with clicking + <property>File->New->Other->BPEL project</property> in the menu bar.</para> + <figure> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>It consists of only one page:</para> + <itemizedlist> + <listitem><para>On the page you can adjust the name of the project and the directory where it will be created.</para> + <para>If "<property>Use default</property>" option is checked the output directory will be the workspace, + othervise the user should specify it by himself using <property>Browse</property> button.</para> + <figure> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_2.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + </section> + <section> + <title>Apache ODE Deployment Descriptor Wizard</title> + <para>Using this wizard user can create ODE deployment descriptor (deploy.xml) and place it in the temporary directory.It is available with clicking + <property>File->New->Other->Apache ODE Deployment Descriptor Wizard</property> in the menu bar.</para> + <figure> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_2a.png"/> + </imageobject> + </mediaobject> + </figure> + <para>On the page you can adjust the name of the deployment descriptor and + the directory where it will be created.Note,that you should use <property> + /PROJECT_NAME/bpelContent</property> directory as an output one.</para> + + </section> + <section> + <title>New BPEL Process file Wizard</title> + <para>Using <property>New BPEL Process file Wizard</property> + user can create BPEL process file and WSDL file if it is necessary. + The wizard includes several pages:</para> + <itemizedlist> + <listitem><para>The first page has the following options to set:</para> + <table> + <title>New BPEL Process file Wizard. First Page Options.</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" align="left" colwidth="3*"/> + <colspec colnum="3" align="left" colwidth="1*"/> + + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Name</entry> + <entry>Enter the process name.</entry> + <entry>no default value</entry> + </row> + + + <row> + <entry>Namespace</entry> + <entry>Enter the namespace url here</entry> + <entry>no default value</entry> + </row> + + <row> + <entry>Template</entry> + <entry>Select one of the provided templates: + <itemizedlist> + <listitem><para><emphasis>Asynchronous BPEL Process</emphasis> - + generates the basis of orchestration logic: receive and reply activities + are included into the process;client WSDL is generated, + service is defined in the <property>parentlink</property> of the process. + The caller is notified asynchronously when the process completes. + </para></listitem> + <listitem><para><emphasis>Empty BPEL Process</emphasis> - list of services participating in this BPEL process together + with the one of messages used within the process is empty.There are no any orchestration logic.</para></listitem> + <listitem><para><emphasis>Synchronous BPEL Process</emphasis> - + similar to Asynchronous BPEL Process template except the fact that here + the caller is notified synchronously when the process completes.</para></listitem> + </itemizedlist></entry> + <entry>Asynchronous BPEL Process</entry> + </row> + <row> + <entry>Abstract Process</entry> + <entry>Specifies the created process as an abstract one -partially + specified processes that are not intended to be executed.</entry> + <entry>unchecked</entry> + </row> + </tbody> + </tgroup> + </table> + <figure> + <title>New BPEL Process file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_3.png"/> + </imageobject> + </mediaobject> + </figure> + + </listitem> + <listitem><para>On the second page the user should select the BPEL project + and folder where the process file will be created:</para> + <figure> + <title>New BPEL Process file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_4.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <note> + <para>Process files that are used in the BPEL project must be under the <property>bpelContent</property> folder. Only in this case + these files can be deployed to JBoss server. + </para> + </note> + </section> + </section> + <section> + <title>Editors</title> + <section> + <title>Business Process Editor</title> + <para>Business Process Editor is intended to facilitate the process of changing and + adding new logic to BPEL process file.You can open <emphasis>.bpel</emphasis> + in this editor by right click the file in the project explorer and selecting + <property>Open With...->Business Process Editor</property> + </para> + <figure> + <title>Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_5.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The editor consists of two tabs:<property>Design</property> tab and <property>Source</property> tab.</para> + <section> + <title>Design tab</title> + <para>Design tab is the main part of Business Process Editor.It consists of 3 parts:</para> + <itemizedlist> + <listitem><para>Visual Pane:</para> + <figure> + <title>Visual Pane of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_6.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The Visual Pane graphically displays the order in which the activities are executed.</para> + </listitem> + <listitem><para>Palette:</para> + <figure> + <title>Palette of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_7.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The <property>Palette</property> represents different elements of the BPEL activities + organized into functional categories. + Using it the user can easily add new elements to the sequence activity. + To do this,he should just click the required element and then drug + and drop it to the place on the Visual Pane where it should be added.</para> + </listitem> + <listitem><para>Behavior Components View:</para> + <figure> + <title>Behavior Components View of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_8.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Execution behavior components are grouped into the <property> + Behavior Components View</property>. + The view is also fully syncronized with Properties view where you can customize all + the properties of the component.</para> + <figure> + <title>Process Structure View of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_9.png"/> + </imageobject> + </mediaobject> + </figure> + <para>To add an element to some component group click plus(<inlinemediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_10.png"/> + </imageobject> + </inlinemediaobject>) icon, + for its deleting you should click the element and + use its <property>Delete</property> option in the popup menu.</para> + </listitem> + + </itemizedlist> + + + </section> + <section> + <title>Source tab</title> + <para>Source tab can be used for editing BPEL process file directly. + The validation of file structure is also available. + </para> + <figure> + <title>Validation error in Source tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_11.png"/> + </imageobject> + </mediaobject> + </figure> + <para>If the user wants to disable/unable validation he can do it by following + <property>Window->Preferences->Validation</property>.</para> + <figure> + <title>Validation configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_12.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + <section> + <title>ODE Deployment Descriptor Editor</title> + <para>To deploy your process in Ode you need to create a + simple deployment descriptor with basic information and + <property>ODE Deployment Descriptor Editor</property> facilitates the process of descriptor configuration. + You can see how the descriptor file,opened in the editor looks like on the picture below: + </para> + <figure> + <title>ODE Deployment Descriptor Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_13.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The table below describes the configuration options of the + ODE Deployment Descriptor Editor:</para> + <table> + <title>ODE Deployment Descriptor Editor.Options.</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" align="left" colwidth="3*"/> + <colspec colnum="3" align="left" colwidth="1*"/> + + <thead> + <row> + <entry>Section</entry> + <entry>Options</entry> + <entry>Description</entry> + </row> + </thead> + <tbody> + <row> + <entry morerows='1' valign='middle'><para> + General</para></entry> + + <entry>This process is</entry> + <entry>Select one of the provided options: + <itemizedlist> + <listitem> + <para><emphasis>activated</emphasis> + </para> + </listitem> + <listitem> + <para><emphasis>deactivated</emphasis></para> + </listitem> + <listitem> + <para><emphasis>retired</emphasis> + </para> + </listitem> + </itemizedlist></entry> + + </row> + <row><entry>Run this process in memory</entry> + <entry>for performance purposes, + you can define the process as being + executed only in-memory.</entry> + </row> + + <row> + <entry>Inbound Interfaces(Services)</entry> + <entry>Associated Port</entry> + <entry>Click Associated Port and the dropdown list with all available port names will appear. + Select the one you need ,other fields will be filled automatically. + This action configure the services + provided by the process and + bind each service to an endpoint + </entry> + + </row> + + <row> + <entry>Outbound Interfaces(Invokes)</entry> + <entry>Associated Port</entry> + <entry>Click Associated Port and the dropdown list with all available port names will appear. + Select the one you need, other fields will be filled automatically. + This action configure the services + invoked by the process</entry> + </row> + <row> + <entry>Process-level Monitoring Events</entry> + <entry> <itemizedlist> + <listitem><para> + <emphasis>None</emphasis> + </para></listitem> + <listitem> + <para> + <emphasis>All</emphasis> + </para> + </listitem> + <listitem> + <para> + <emphasis>Selected</emphasis>: + </para> + <itemizedlist> + <listitem><para>Instance life cycle</para></listitem> + <listitem><para>Activity life cycle</para></listitem> + <listitem><para>Data handling</para></listitem> + <listitem><para>Scope handling</para></listitem> + <listitem><para>Correlation</para></listitem> + + </itemizedlist> + + </listitem> + </itemizedlist> + </entry> + <entry>Using ODE's deployment descriptor, it's also + possible to make events generation to + filtrate which ones get created. + All option just duplicates the default behaviour, + when nothing is specified in the deployment.</entry> + </row> + <row> + <entry>Scope-level Monitoring Events</entry> + <entry>Scope</entry> + <entry>This section makes it possible to + define filtering for each scope of your process. + </entry> + </row> + </tbody> + </tgroup> + </table> + </section> + + </section> + + +</chapter> + Added: trunk/bpel/docs/reference/en-US/summary.xml =================================================================== --- trunk/bpel/docs/reference/en-US/summary.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/summary.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,21 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<chapter> + <?dbhtml filename="summary.html"?> + <title>Summary</title> + <para>In conclusion, with this document you know all the capabilities of BPEL Tools + and could easily start with them. + The chapters above walked you through the steps on how to create and configure BPEL process and + deployment descriptor files. + If you have questions or suggestions concerned both the documentation and tools behavior, + you are welcome to JBoss Tools Users forum. + Please, use Jira to report bugs and requests on documentation.</para> + + <section> + <title>Other relevant resources on the topic</title> + <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at + <ulink url="http://docs.jboss.org/tools">http://docs.jboss.org/tools</ulink> in the corresponding release directory. + </para> + <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs">http://download.jboss.org/jbosstools/nightly-docs</ulink>. </para> + + </section> +</chapter> Added: trunk/bpel/docs/reference/en-US/tasks.xml =================================================================== --- trunk/bpel/docs/reference/en-US/tasks.xml (rev 0) +++ trunk/bpel/docs/reference/en-US/tasks.xml 2010-11-25 00:58:42 UTC (rev 26894) @@ -0,0 +1,444 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<chapter id="tasks"> + <title>Tasks</title> + <section id="detail"> + <title>Creating and editing a BPEL project</title> + <para>In the chapter we describe the necessary steps to create a new BPEL project and edit the BPEL files. + You can get the source of the example from <property> + riftsaw/samples/quickstart/hello_world</property>. + Here and further in the guide we will create + a simple echo example, used to respond to a sent message with a + modified version of the request message being returned in a response. + First of all, you should create a BPEL project. + + </para> + <section id="createproject"> + <title>Creating a BPEL project</title> + <para>Create the project by selecting + <emphasis><property>New > Project... > BPEL 2.0 > BPEL Project</property></emphasis> from the menu bar. + Then click the <property>Next</property> button. + </para> + <figure> + <title>New BPEL Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>On this page of the <property>New BPEL Project Wizard</property> enter a project name in the <property>Project Name</property> + field,e.g enter <property>HelloWorld</property>.</para> + + <figure> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click the <property>Finish</property> button. + So you have created the BPEL project named <property>HelloWorld</property>. + Its structure is like this: </para> + <figure> + <title>The BPEL Project structure</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_3.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="createprocess"> + <title>Creating a BPEL process</title> + <para>Now you should create a BPEL process. You can create it by selecting + <emphasis><property>New > Others... > BPEL 2.0 > New BPEL Process File</property></emphasis>. + </para> + <figure> + <title>New BPEL Process File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click the <property>Next</property> button. Enter the following information:</para> + <table> + + <title>Fields and values</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="2*"/> + <colspec colnum="2" colwidth="4*"/> + <thead> + <row> + <entry>Field</entry> + <entry>Value</entry> + + </row> + </thead> + <tbody> + <row> + <entry><para>BPEL Process Name</para></entry> + <entry><para>enter a process name. For example, <property>HelloWorld</property>.</para></entry> + </row> + <row> + <entry><para>Namespace</para></entry> + <entry><para>enter or select a namespace for the BPEL process.</para></entry> + </row> + <row> + <entry><para>Template</para></entry> + <entry><para>Select the necessary template for the BPEL process. + When you select the template, you will see the information + about the template below on the page.In our case you should + select <property>Synchronous BPEL Process</property>.</para></entry> + </row> + + </tbody> + </tgroup> + </table> + + <figure> + <title>New BPEL Process File Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click the <property>Next</property> button. On the second page make sure that the folder <property>HelloWorld/bpelContent</property> is selected. + Click <property>Finish</property>. + </para> + <note> + <para>All of your files that are used in your BPEL project must be under the <property>bpelContent</property> folder. Only in this case + these files can be deployed to JBoss server. + </para> + </note> + + <para>Up to now, you have got a simple BPEL process as on the screen below.</para> + <figure> + <title>A simple BPEL Process File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The next step, you can do is to edit the BPEL process file and then deploy it to JBoss server. </para> + </section> + <section id="editprocess"> + <title>Editing a BPEL process file</title> + <para>If the <emphasis><property>Properties view</property></emphasis> and <emphasis><property>Palette view</property></emphasis> are not opened, you can open the views by right-clicking the BPEL editor and selecting + <property>Show in Properties</property>, <property>Show Palette in Palette view</property>. Then you should have the view like this: + </para> + <figure> + <title>The BPEL editor view</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>In the <emphasis><property>Palette view</property></emphasis>, you can drag a BPEL element to the BPEL editor and drop it in the place you want.</para> + <para>In the <emphasis><property>Properties view</property></emphasis>, you can get the information about every element of the BPEL process. + In the BPEL editor select any element you want,and then + the element's properties will be shown in the Properties view.The table below describes the tabs of the Properties view: + </para> + <table> + + <title>Tabs of the Property view</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="2*"/> + <colspec colnum="2" colwidth="4*"/> + <thead> + <row> + <entry>Tab</entry> + <entry>Description</entry> + + </row> + </thead> + <tbody> + <row> + <entry><para>Description</para></entry> + <entry><para>Shows the descriptive information about the element,e.g. <property>Name</property> of the element.</para></entry> + </row> + <row> + <entry><para>Details</para></entry> + <entry><para>Shows the detailed and important information about the element. + It is the most important section of an element. + Most of the properties of an element are set in this section.</para></entry> + </row> + <row> + <entry><para>Join Behavior</para></entry> + <entry><para>Shows the <property>Join Failure</property> property of the element.</para></entry> + </row> + <row> + <entry><para>Documentation</para></entry> + <entry><para>Shows the <property>documentation</property> sub-element of an element.</para></entry> + </row> + <row> + <entry><para>Other</para></entry> + <entry><para>Every BPEL element has its own sections: Correlation section, Message Exchange section, and so on. We will + introduce them while using them.</para></entry> + </row> + </tbody> + </tgroup> + </table> + <para>In order to see how a simple BPEL process works in action, you should do some steps as below: </para> + <itemizedlist> + <listitem> + <para>Modify two variables of the process:</para> + <itemizedlist> + <listitem><para>Click on the details tab of the input variable, + select <property>Browse...</property>. + Then choose <property>string</property> primitive from the list.</para> + <figure> + <title>Edit variable in <property>process</property> file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpel_task_1.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Select <property>xsd</property> as a namespace in the popup menu.</para> + </listitem> + </itemizedlist> + + </listitem> + <listitem> + <para>Add an <property>Assign</property> element between the <property>receiveInput</property> element and <property>replyOutput</property> element.</para> + </listitem> + <listitem> + <para>Click the <property>Assign</property> element in the BPEL editor in order to get the properties information of it in the Properties view. + </para> + </listitem> + <listitem> + <para>Set its name in the <property>Description</property> tab as <property>assignHelloMesg</property>.</para> + <para>In the <property>Details</property> section of Properties view, + you should click the <property>New</property> button to add a <property>copy</property> sub-element to the element. + Assign "Variable to Variable"(input:string to output). At this time, an "<property>initializer</property>" popup dialog appears. Click on the <property>Yes</property> button in the dialog. + </para> + <figure> + <title>Add <property>Assign</property> to the process</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpel_task_3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Then you should click <property>New</property> once more and select Expression to Variable + (assign <code>concat($input,' World'))</code> to <property>result:string</property>. </para> + <figure> + <title>Add <property>Expression assign</property> to the process</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpel_task_2.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + </section> + + <section id="wsdl"> + <title>Adding Service to WSDL file</title> + <para></para> + <itemizedlist> + + <listitem> + <para>Open the file "<property>HelloWorldArtifacts.wsdl</property>" in the "<property>HelloWorld</property>" project by double-clicking the file. Right-click the WSDL editor and select + <property>Add Service</property>. A new service should appear in the editor. Name it <property>HelloWorldProcessService</property>. It has the Port + named <property>NewPort</property>. Select it, right-click on it and rename it to <property>HelloWorldProcessPort</property> in the Properties + view. + </para> + <figure> + <title>Add <property>Service</property> to the WSDL file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_3.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Right-click somewhere in the whitespace of the WSDL editor and select + <property>Add Binding</property>. A new Binding component will appear in the editor. Name it <property>HelloWorldSOAPBinding</property>. Select it, in the + General tab of the Properties view and select <property>HelloWorld</property> as a port type in the <property>PortType</property>. Then click on the + <property>Generate Binding Content...</property> button to open the <property>Binding Wizard</property>. In the wizard, select <property>SOAP </property> + as the <property>Protocol</property>. Finally, click the <property>Finish</property> button to close the wizard. + </para> + <figure> + <title>Add a <property>Binding</property> to the WSDL file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_4.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Click the <property>HelloWorldProcessPort</property> property in the General section of the Properties view, select <property>HelloWorldSOAPBinding</property> in + the <property>Binding</property> combobox. In the <property>Address</property> field input <ulink url="http://localhost:8080/bpel/processes/HelloWorld?wsdl">http://localhost:8080/bpel/processes/HelloWorld?wsdl</ulink>. + </para> + <figure> + <title>Add the <property>HelloWorldSOAPBinding</property> to the <property>HelloWorldProcessPort</property></title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_5.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem><para>You should also change some service part configurations. + To do this,click part element in the WSDL editor, + then put the following data in the Properties view. + </para> + <figure> + <title>Configuration of service part</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_5.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + + <para>Now you have finished creating a simple BPEL process.As a next step, you can deploy the BPEL project to JBoss BPEL Runtime.</para> + + </section> + + </section> + <section id="deploy"> + <title>Deploy a JBoss BPEL project to JBoss BPEL Runtime</title> + <section id="createdeploy"> + <title>Creating a bpel-deploy.xml file</title> + <para>If you want to deploy a BPEL project to JBoss BPEL Runtime, you should create a bpel-deploy.xml file. + JBoss tools can help you to create it: + </para> + <itemizedlist> + <listitem> + <para>Create the bpel-deploy.xml by selecting + <emphasis><property>New > Other... > BPEL 2.0 > Apache ODE Deployment Descriptor</property></emphasis>. Click the <property>Next</property> button. + </para> + <figure> + <title>New BPEL Deploy file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_1.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>On the next wizard page you should enter the following information:</para> + <para><emphasis><property>BPEL Project</property></emphasis>: Click the <property>Browse...</property> button to select the BPEL project in your workspace which you want to deploy to the runtime. + Please note, that you should select the <property>bpelContent</property> folder in your new BPEL project as a value of <property>BPEL Project</property> field because the bpel-deploy.xml should be created in this place. + </para> + <para><emphasis><property>File name</property></emphasis>: The default value is bpel-deploy.xml. Please, don't change it.</para> + <para>Click on <property>Finish</property> button to close the wizard and a new bpel-deploy.xml file will be created.</para> + <figure> + <title>New BPEL Deploy file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_2.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Double-click the bpel-deploy.xml file to open it in ODE Descriptor Deployment Editor. + In the <property>Inbound Interfaces</property> section, click the + <property>Associated Port</property> column and select <property>HelloWorldProcessPort</property> + in the dropdown box.The <property>Related Service</property> and <property>Binding Used</property> + columns should be automatically filled in. Save the <emphasis><property>bpel-deploy.xml</property></emphasis>. + </para> + <figure> + <title>bpel-deploy.xml file editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_3.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + </section> + <section id="createruntime"> + <title>Creating JBoss BPEL Server</title> + <para>Suppose you have installed the <property>JBoss BPEL Runtime-RiftSaw</property> as it was described <link linkend="installRuntime">before</link>, now you can create a server for JBoss BPEL runtime.</para> + <itemizedlist> + <listitem> + <para>Open the <property>Servers</property> view by selecting + <emphasis><property>Windows > Show View > Other... > Server > Servers</property></emphasis>. + </para> + </listitem> + <listitem> + <para>Right-click the Servers view and select + <emphasis><property>New > Server</property></emphasis> to open the New Server Wizard: + </para> + <figure> + <title>New Server Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_4.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Select <property>JBoss AS 5.1 </property>as a server type. </para> + <note> + <para>Please note, that only JBoss As 5.1 or higher version supports BPEL.</para> + </note> + </listitem> + <listitem> + + <para>Click the <property>Next</property> button. On the next page, you should input your <emphasis><property>JBoss As</property></emphasis> location. Then click the <property>Next</property> button and + you will get the page like this: + </para> + <figure> + <title>Add resource to the server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_5.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Select <property>HelloWorld</property>, then click the <property>Add </property> button to add the project to the server. + Then click on the <property>Finish</property> button. + </para> + <para>Start the server by right-clicking on the server and selecting the <property>Start</property> item. </para> + + <figure> + <title>The started server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_6.png"/> + </imageobject> + </mediaobject> + </figure> + <para>If some aspects of server creation is not clear, please, read <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/as/html_single/index...">JBoss Server Manager Reference Guide</ulink> for more details.</para> + </listitem> + <listitem> + <para>You can enter the link <ulink url="http://localhost:8080/bpel/processes.html">http://localhost:8080/bpel/processes.html</ulink> to the browser to get the deployed processes.</para> + <figure> + <title>The BPEL console</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_7.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <para>If there's anything we didn't cover or you can't figure out, please feel free to visit our <ulink + url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201" + >JBoss Tools Users Forum</ulink> to ask questions. + There we are also waiting for your suggestions and comments.</para> + </section> + </section> +</chapter>

13 years, 6 months

1
0
0 / 0

JBoss Tools SVN: r26893 - trunk/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/deltacloud/ui/views.

by jbosstools-commits＠lists.jboss.org

Author: adietish Date: 2010-11-24 19:51:28 -0500 (Wed, 24 Nov 2010) New Revision: 26893 Modified: trunk/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/deltacloud/ui/views/InstanceView.java Log: [JBIDE-7694] applied a first fix Modified: trunk/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/deltacloud/ui/views/InstanceView.java =================================================================== --- trunk/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/deltacloud/ui/views/InstanceView.java 2010-11-25 00:47:10 UTC (rev 26892) +++ trunk/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/deltacloud/ui/views/InstanceView.java 2010-11-25 00:51:28 UTC (rev 26893) @@ -64,7 +64,6 @@ private Combo cloudSelector; private Label filterLabel; - private DeltaCloud[] clouds; private DeltaCloud currCloud; private InstanceViewLabelAndContentProvider contentProvider; @@ -81,7 +80,7 @@ if (currCloud != null) { currCloud.removeInstanceListListener(InstanceView.this); } - currCloud = clouds[index]; + setCurrentCloud(index); storeSelectedCloud(); Display.getCurrent().asyncExec(new Runnable() { @@ -89,7 +88,6 @@ public void run() { viewer.setInput(currCloud); currCloud.addInstanceListListener(InstanceView.this); - viewer.refresh(); } }); @@ -133,7 +131,7 @@ @Override public void dispose() { - for (DeltaCloud cloud : clouds) { + for (DeltaCloud cloud : getClouds()) { cloud.removeInstanceListListener(this); } DeltaCloudManager.getDefault().removeCloudManagerListener(this); @@ -148,7 +146,7 @@ layout.marginWidth = 0; container.setLayout(layout); - clouds = getClouds(); + DeltaCloud[] clouds = getClouds(); createCloudSelector(); initCloudSelector(getLastSelectedCloud(), cloudSelector, clouds); @@ -163,6 +161,7 @@ currCloud = getCurrentCloud(cloudSelector.getSelectionIndex(), clouds); addInstanceListener(currCloud, viewer); + setViewerInput(currCloud); setFilterLabelVisible(currCloud, filterLabel); Point p1 = cloudSelectorLabel.computeSize(SWT.DEFAULT, SWT.DEFAULT); @@ -195,12 +194,18 @@ PlatformUI.getWorkbench().getHelpSystem().setHelp(viewer.getControl(), "org.jboss.tools.deltacloud.ui.viewer"); hookContextMenu(viewer.getTable()); getSite().setSelectionProvider(viewer); - + DeltaCloudManager.getDefault().addCloudManagerListener(this); } + private void setViewerInput(DeltaCloud currentCloud) { + if (currentCloud != null) { + viewer.setInput(currentCloud); + } + } + private DeltaCloud[] getClouds() { - DeltaCloud[] clouds = new DeltaCloud[]{}; + DeltaCloud[] clouds = new DeltaCloud[] {}; try { clouds = DeltaCloudManager.getDefault().getClouds(); } catch (DeltaCloudException e) { @@ -213,6 +218,15 @@ return clouds; } + private void setCurrentCloud(int index) { + DeltaCloud[] clouds = getClouds(); + if (index >= clouds.length) { + currCloud = null; + } else { + currCloud = getClouds()[index]; + } + } + private void setFilterLabelVisible(DeltaCloud currentCloud, Label filterLabel) { if (currentCloud == null) { filterLabel.setVisible(false); @@ -227,7 +241,6 @@ if (currentCloud != null) { currentCloud.removeInstanceListListener(this); currentCloud.addInstanceListListener(this); - viewer.setInput(currentCloud); } } @@ -321,7 +334,7 @@ currName = currCloud.getName(); currIndex = cloudSelector.getSelectionIndex(); } - clouds = getClouds(); + DeltaCloud[] clouds = getClouds(); String[] cloudNames = new String[clouds.length]; int index = 0; for (int i = 0; i < clouds.length; ++i) { @@ -332,17 +345,22 @@ if (type == ICloudManagerListener.RENAME_EVENT) { index = currIndex; // no change in cloud displayed } - cloudSelector.removeModifyListener(cloudModifyListener); - cloudSelector.setItems(cloudNames); + + setCloudSelectorItems(cloudNames); + setCurrentCloud(index); + if (cloudNames.length > 0) { cloudSelector.setText(cloudNames[index]); - currCloud = clouds[index]; viewer.setInput(currCloud); } else { - currCloud = null; cloudSelector.setText(""); viewer.setInput(new DeltaCloudInstance[0]); } + } + + private void setCloudSelectorItems(String[] cloudNames) { + cloudSelector.removeModifyListener(cloudModifyListener); + cloudSelector.setItems(cloudNames); cloudSelector.addModifyListener(cloudModifyListener); } @@ -355,11 +373,8 @@ Display.getDefault().syncExec(new Runnable() { @Override public void run() { - currCloud.removeInstanceListListener(InstanceView.this); - + currCloud.addInstanceListListener(InstanceView.this); // does not add identical instance twice viewer.setInput(instances); - currCloud.addInstanceListListener(InstanceView.this); - viewer.refresh(); refreshToolbarCommandStates(); } });

13 years, 6 months

1
0
0 / 0

JBoss Tools SVN: r26892 - branches/jbosstools-3.2.0.Beta2/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/deltacloud/ui/views.

by jbosstools-commits＠lists.jboss.org

Author: adietish Date: 2010-11-24 19:47:10 -0500 (Wed, 24 Nov 2010) New Revision: 26892 Modified: branches/jbosstools-3.2.0.Beta2/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/deltacloud/ui/views/InstanceView.java Log: [JBIDE-7694] applied fix, need some more testing Modified: branches/jbosstools-3.2.0.Beta2/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/deltacloud/ui/views/InstanceView.java =================================================================== --- branches/jbosstools-3.2.0.Beta2/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/deltacloud/ui/views/InstanceView.java 2010-11-24 19:41:48 UTC (rev 26891) +++ branches/jbosstools-3.2.0.Beta2/deltacloud/plugins/org.jboss.tools.deltacloud.ui/src/org/jboss/tools/deltacloud/ui/views/InstanceView.java 2010-11-25 00:47:10 UTC (rev 26892) @@ -64,7 +64,6 @@ private Combo cloudSelector; private Label filterLabel; - private DeltaCloud[] clouds; private DeltaCloud currCloud; private InstanceViewLabelAndContentProvider contentProvider; @@ -81,7 +80,7 @@ if (currCloud != null) { currCloud.removeInstanceListListener(InstanceView.this); } - currCloud = clouds[index]; + setCurrentCloud(index); storeSelectedCloud(); Display.getCurrent().asyncExec(new Runnable() { @@ -89,7 +88,6 @@ public void run() { viewer.setInput(currCloud); currCloud.addInstanceListListener(InstanceView.this); - viewer.refresh(); } }); @@ -133,7 +131,7 @@ @Override public void dispose() { - for (DeltaCloud cloud : clouds) { + for (DeltaCloud cloud : getClouds()) { cloud.removeInstanceListListener(this); } DeltaCloudManager.getDefault().removeCloudManagerListener(this); @@ -148,7 +146,7 @@ layout.marginWidth = 0; container.setLayout(layout); - clouds = getClouds(); + DeltaCloud[] clouds = getClouds(); createCloudSelector(); initCloudSelector(getLastSelectedCloud(), cloudSelector, clouds); @@ -163,6 +161,7 @@ currCloud = getCurrentCloud(cloudSelector.getSelectionIndex(), clouds); addInstanceListener(currCloud, viewer); + setViewerInput(currCloud); setFilterLabelVisible(currCloud, filterLabel); Point p1 = cloudSelectorLabel.computeSize(SWT.DEFAULT, SWT.DEFAULT); @@ -195,12 +194,18 @@ PlatformUI.getWorkbench().getHelpSystem().setHelp(viewer.getControl(), "org.jboss.tools.deltacloud.ui.viewer"); hookContextMenu(viewer.getTable()); getSite().setSelectionProvider(viewer); - + DeltaCloudManager.getDefault().addCloudManagerListener(this); } + private void setViewerInput(DeltaCloud currentCloud) { + if (currentCloud != null) { + viewer.setInput(currentCloud); + } + } + private DeltaCloud[] getClouds() { - DeltaCloud[] clouds = new DeltaCloud[]{}; + DeltaCloud[] clouds = new DeltaCloud[] {}; try { clouds = DeltaCloudManager.getDefault().getClouds(); } catch (DeltaCloudException e) { @@ -213,6 +218,15 @@ return clouds; } + private void setCurrentCloud(int index) { + DeltaCloud[] clouds = getClouds(); + if (index >= clouds.length) { + currCloud = null; + } else { + currCloud = getClouds()[index]; + } + } + private void setFilterLabelVisible(DeltaCloud currentCloud, Label filterLabel) { if (currentCloud == null) { filterLabel.setVisible(false); @@ -227,7 +241,6 @@ if (currentCloud != null) { currentCloud.removeInstanceListListener(this); currentCloud.addInstanceListListener(this); - viewer.setInput(currentCloud); } } @@ -321,7 +334,7 @@ currName = currCloud.getName(); currIndex = cloudSelector.getSelectionIndex(); } - clouds = getClouds(); + DeltaCloud[] clouds = getClouds(); String[] cloudNames = new String[clouds.length]; int index = 0; for (int i = 0; i < clouds.length; ++i) { @@ -332,17 +345,22 @@ if (type == ICloudManagerListener.RENAME_EVENT) { index = currIndex; // no change in cloud displayed } - cloudSelector.removeModifyListener(cloudModifyListener); - cloudSelector.setItems(cloudNames); + + setCloudSelectorItems(cloudNames); + setCurrentCloud(index); + if (cloudNames.length > 0) { cloudSelector.setText(cloudNames[index]); - currCloud = clouds[index]; viewer.setInput(currCloud); } else { - currCloud = null; cloudSelector.setText(""); viewer.setInput(new DeltaCloudInstance[0]); } + } + + private void setCloudSelectorItems(String[] cloudNames) { + cloudSelector.removeModifyListener(cloudModifyListener); + cloudSelector.setItems(cloudNames); cloudSelector.addModifyListener(cloudModifyListener); } @@ -355,11 +373,8 @@ Display.getDefault().syncExec(new Runnable() { @Override public void run() { - currCloud.removeInstanceListListener(InstanceView.this); - + currCloud.addInstanceListListener(InstanceView.this); // does not add identical instance twice viewer.setInput(instances); - currCloud.addInstanceListListener(InstanceView.this); - viewer.refresh(); refreshToolbarCommandStates(); } });

13 years, 6 months

1
0
0 / 0

JBoss Tools SVN: r26891 - in trunk/portlet/plugins/org.jboss.tools.portlet.core/src/org/jboss/tools/portlet/core: internal/project/facet and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: snjeza Date: 2010-11-24 14:41:48 -0500 (Wed, 24 Nov 2010) New Revision: 26891 Modified: trunk/portlet/plugins/org.jboss.tools.portlet.core/src/org/jboss/tools/portlet/core/IPortletConstants.java trunk/portlet/plugins/org.jboss.tools.portlet.core/src/org/jboss/tools/portlet/core/internal/project/facet/PortletPostInstallListener.java Log: JBIDE-7702 Richfaces libraries not added to new project Modified: trunk/portlet/plugins/org.jboss.tools.portlet.core/src/org/jboss/tools/portlet/core/IPortletConstants.java =================================================================== --- trunk/portlet/plugins/org.jboss.tools.portlet.core/src/org/jboss/tools/portlet/core/IPortletConstants.java 2010-11-24 19:41:40 UTC (rev 26890) +++ trunk/portlet/plugins/org.jboss.tools.portlet.core/src/org/jboss/tools/portlet/core/IPortletConstants.java 2010-11-24 19:41:48 UTC (rev 26891) @@ -52,6 +52,8 @@ static final String JSF_SECTION = "jsfSection"; //$NON-NLS-1$ static final String WEB_INF_LIB = "WEB-INF/lib"; //$NON-NLS-1$ + + static final String LIB = "lib"; //$NON-NLS-1$ static final String JBOSS_PORTLET_FILE = "WEB-INF/jboss-portlet.xml"; //$NON-NLS-1$ Modified: trunk/portlet/plugins/org.jboss.tools.portlet.core/src/org/jboss/tools/portlet/core/internal/project/facet/PortletPostInstallListener.java =================================================================== --- trunk/portlet/plugins/org.jboss.tools.portlet.core/src/org/jboss/tools/portlet/core/internal/project/facet/PortletPostInstallListener.java 2010-11-24 19:41:40 UTC (rev 26890) +++ trunk/portlet/plugins/org.jboss.tools.portlet.core/src/org/jboss/tools/portlet/core/internal/project/facet/PortletPostInstallListener.java 2010-11-24 19:41:48 UTC (rev 26891) @@ -433,6 +433,9 @@ deleteOldRichFacesApi(folder); destPath = folder.getFullPath(); ZipEntry root = zipFile.getEntry(IPortletConstants.WEB_INF_LIB); + if (root == null) { + root = zipFile.getEntry(IPortletConstants.LIB); + } op = new ImportOperation( destPath, root, structureProvider, OVERWRITE_NONE_QUERY, list ); @@ -446,14 +449,30 @@ } private File getRichFacesExamples(File examplesHome) { - File file = new File(examplesHome,"RichFacesPortlet.war"); //$NON-NLS-1$ - if (file.exists() && file.isFile()) { + File file = getExampleFile(examplesHome,"RichFacesPortlet", "war"); //$NON-NLS-1$ //$NON-NLS-2$ + if (file != null && file.isFile()) { return file; } + file = getExampleFile(examplesHome, "richFacesPortlet", ".war"); //$NON-NLS-1$//$NON-NLS-2$ + if (file != null && file.isFile()) { + return file; + } + file = getExampleFile(examplesHome, "seamPortlet", ".war"); //$NON-NLS-1$//$NON-NLS-2$ + if (file != null && file.isFile()) { + return file; + } + file = getExampleFile(examplesHome, "seam", ".ear"); //$NON-NLS-1$//$NON-NLS-2$ + if (file != null && file.isFile()) { + return file; + } + return null; + } + + private File getExampleFile(File examplesHome, final String prefix, final String suffix) { File[] listFiles = examplesHome.listFiles(new FilenameFilter() { public boolean accept(File dir, String name) { - if (name.startsWith("seamPortlet") && name.endsWith(".war")) { //$NON-NLS-1$ //$NON-NLS-2$ + if (name.startsWith(prefix) && name.endsWith(suffix)) { return true; } return false;

13 years, 6 months

1
0
0 / 0

JBoss Tools SVN: r26890 - in trunk/hibernatetools/tests/org.hibernate.eclipse.console.test: src/org/hibernate/eclipse/console/test and 1 other directories.

by jbosstools-commits＠lists.jboss.org

Author: vyemialyanchyk Date: 2010-11-24 14:41:40 -0500 (Wed, 24 Nov 2010) New Revision: 26890 Added: trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/res/project2/testLaunchCfg_all_exporters_external.launch trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/res/project2/testLaunchCfg_all_exporters_internal.launch Modified: trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/src/org/hibernate/eclipse/console/test/CodeGenExternalProcessExecutionTest.java trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/src/org/hibernate/eclipse/console/test/project/LaunchConfigTestProject2.java Log: https://jira.jboss.org/browse/JBIDE-7708 - fixed; https://jira.jboss.org/browse/JBIDE-7709 - partially fixed Added: trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/res/project2/testLaunchCfg_all_exporters_external.launch =================================================================== --- trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/res/project2/testLaunchCfg_all_exporters_external.launch (rev 0) +++ trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/res/project2/testLaunchCfg_all_exporters_external.launch 2010-11-24 19:41:40 UTC (rev 26890) @@ -0,0 +1,51 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<launchConfiguration type="org.hibernate.eclipse.launch.CodeGenerationLaunchConfigurationType"> +<stringAttribute key="org.eclipse.jdt.launching.CLASSPATH_PROVIDER" value="org.eclipse.ant.ui.AntClasspathProvider"/> +<booleanAttribute key="org.eclipse.jdt.launching.DEFAULT_CLASSPATH" value="true"/> +<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="org.eclipse.ant.internal.launching.remote.InternalAntRunner"/> +<stringAttribute key="org.eclipse.ui.externaltools.ATTR_LOCATION" value="\LaunchConfigTestProject2\build_2794024212908788293xml"/> +<stringAttribute key="org.hibernate.tools.configurationname" value="LaunchConfigTestProject2"/> +<booleanAttribute key="org.hibernate.tools.ejb3" value="false"/> +<listAttribute key="org.hibernate.tools.exporters"> +<listEntry value="org.hibernate.tools.hbm2java"/> +<listEntry value="org.hibernate.tools.hbm2hbmxml"/> +<listEntry value="org.hibernate.tools.hbm2dao"/> +<listEntry value="org.hibernate.tools.hbmtemplate"/> +<listEntry value="org.hibernate.tools.hbm2cfgxml"/> +<listEntry value="org.hibernate.tools.hbm2doc"/> +<listEntry value="org.hibernate.tools.hbm2ddl"/> +<listEntry value="org.hibernate.tools.query"/> +</listAttribute> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2cfgxml" value="true"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2cfgxml.extension_id" value="org.hibernate.tools.hbm2cfgxml"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2dao" value="true"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2dao.extension_id" value="org.hibernate.tools.hbm2dao"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2ddl" value="true"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2ddl.extension_id" value="org.hibernate.tools.hbm2ddl"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2doc" value="false"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2doc.extension_id" value="org.hibernate.tools.hbm2doc"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2hbmxml" value="true"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2hbmxml.extension_id" value="org.hibernate.tools.hbm2hbmxml"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2java" value="true"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2java.extension_id" value="org.hibernate.tools.hbm2java"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbmtemplate" value="false"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbmtemplate.extension_id" value="org.hibernate.tools.hbmtemplate"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.query" value="false"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.query.extension_id" value="org.hibernate.tools.query"/> +<mapAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.query.properties"> +<mapEntry key="outputFileName" value="asdf.txt"/> +<mapEntry key="outputdir" value="\LaunchConfigTestProject2\temp_test_out_folder_all_exporters_external"/> +<mapEntry key="query_string" value="from org.jboss.seam.example.booking.Booking"/> +</mapAttribute> +<booleanAttribute key="org.hibernate.tools.jdk5" value="false"/> +<stringAttribute key="org.hibernate.tools.outputdir" value="\LaunchConfigTestProject2\temp_test_out_folder_all_exporters_external"/> +<stringAttribute key="org.hibernate.tools.package" value="hsql"/> +<booleanAttribute key="org.hibernate.tools.prefercompositeids" value="true"/> +<booleanAttribute key="org.hibernate.tools.reveng.detect_many_to_many" value="true"/> +<booleanAttribute key="org.hibernate.tools.reveng.detect_one_to_one" value="true"/> +<booleanAttribute key="org.hibernate.tools.reveng.detect_optimistc_lock" value="true"/> +<booleanAttribute key="org.hibernate.tools.schema2hbm" value="false"/> +<booleanAttribute key="org.hibernate.tools.useExternalProcess" value="true"/> +<booleanAttribute key="org.hibernate.tools.useOwnTemplates" value="false"/> +<stringAttribute key="process_factory_id" value="org.eclipse.ant.ui.remoteAntProcessFactory"/> +</launchConfiguration> Added: trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/res/project2/testLaunchCfg_all_exporters_internal.launch =================================================================== --- trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/res/project2/testLaunchCfg_all_exporters_internal.launch (rev 0) +++ trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/res/project2/testLaunchCfg_all_exporters_internal.launch 2010-11-24 19:41:40 UTC (rev 26890) @@ -0,0 +1,51 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<launchConfiguration type="org.hibernate.eclipse.launch.CodeGenerationLaunchConfigurationType"> +<stringAttribute key="org.eclipse.jdt.launching.CLASSPATH_PROVIDER" value="org.eclipse.ant.ui.AntClasspathProvider"/> +<booleanAttribute key="org.eclipse.jdt.launching.DEFAULT_CLASSPATH" value="true"/> +<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="org.eclipse.ant.internal.launching.remote.InternalAntRunner"/> +<stringAttribute key="org.eclipse.ui.externaltools.ATTR_LOCATION" value="\LaunchConfigTestProject2\build_2794024212908788293xml"/> +<stringAttribute key="org.hibernate.tools.configurationname" value="LaunchConfigTestProject2"/> +<booleanAttribute key="org.hibernate.tools.ejb3" value="false"/> +<listAttribute key="org.hibernate.tools.exporters"> +<listEntry value="org.hibernate.tools.hbm2java"/> +<listEntry value="org.hibernate.tools.hbm2hbmxml"/> +<listEntry value="org.hibernate.tools.hbm2dao"/> +<listEntry value="org.hibernate.tools.hbmtemplate"/> +<listEntry value="org.hibernate.tools.hbm2cfgxml"/> +<listEntry value="org.hibernate.tools.hbm2doc"/> +<listEntry value="org.hibernate.tools.hbm2ddl"/> +<listEntry value="org.hibernate.tools.query"/> +</listAttribute> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2cfgxml" value="true"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2cfgxml.extension_id" value="org.hibernate.tools.hbm2cfgxml"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2dao" value="true"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2dao.extension_id" value="org.hibernate.tools.hbm2dao"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2ddl" value="true"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2ddl.extension_id" value="org.hibernate.tools.hbm2ddl"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2doc" value="false"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2doc.extension_id" value="org.hibernate.tools.hbm2doc"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2hbmxml" value="true"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2hbmxml.extension_id" value="org.hibernate.tools.hbm2hbmxml"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2java" value="true"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbm2java.extension_id" value="org.hibernate.tools.hbm2java"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbmtemplate" value="false"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.hbmtemplate.extension_id" value="org.hibernate.tools.hbmtemplate"/> +<booleanAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.query" value="false"/> +<stringAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.query.extension_id" value="org.hibernate.tools.query"/> +<mapAttribute key="org.hibernate.tools.exporters.org.hibernate.tools.query.properties"> +<mapEntry key="outputFileName" value="asdf.txt"/> +<mapEntry key="outputdir" value="\LaunchConfigTestProject2\temp_test_out_folder_all_exporters_internal"/> +<mapEntry key="query_string" value="from org.jboss.seam.example.booking.Booking"/> +</mapAttribute> +<booleanAttribute key="org.hibernate.tools.jdk5" value="false"/> +<stringAttribute key="org.hibernate.tools.outputdir" value="\LaunchConfigTestProject2\temp_test_out_folder_all_exporters_internal"/> +<stringAttribute key="org.hibernate.tools.package" value="hsql"/> +<booleanAttribute key="org.hibernate.tools.prefercompositeids" value="true"/> +<booleanAttribute key="org.hibernate.tools.reveng.detect_many_to_many" value="true"/> +<booleanAttribute key="org.hibernate.tools.reveng.detect_one_to_one" value="true"/> +<booleanAttribute key="org.hibernate.tools.reveng.detect_optimistc_lock" value="true"/> +<booleanAttribute key="org.hibernate.tools.schema2hbm" value="false"/> +<booleanAttribute key="org.hibernate.tools.useExternalProcess" value="false"/> +<booleanAttribute key="org.hibernate.tools.useOwnTemplates" value="false"/> +<stringAttribute key="process_factory_id" value="org.eclipse.ant.ui.remoteAntProcessFactory"/> +</launchConfiguration> Modified: trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/src/org/hibernate/eclipse/console/test/CodeGenExternalProcessExecutionTest.java =================================================================== --- trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/src/org/hibernate/eclipse/console/test/CodeGenExternalProcessExecutionTest.java 2010-11-24 18:46:42 UTC (rev 26889) +++ trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/src/org/hibernate/eclipse/console/test/CodeGenExternalProcessExecutionTest.java 2010-11-24 19:41:40 UTC (rev 26890) @@ -10,9 +10,14 @@ ******************************************************************************/ package org.hibernate.eclipse.console.test; +import java.io.InputStream; +import java.util.Arrays; +import java.util.Comparator; + import org.eclipse.core.externaltools.internal.IExternalToolConstants; import org.eclipse.core.resources.IFile; import org.eclipse.core.resources.IFolder; +import org.eclipse.core.resources.IResource; import org.eclipse.core.runtime.CoreException; import org.eclipse.core.runtime.IPath; import org.eclipse.core.runtime.Path; @@ -25,12 +30,18 @@ import org.hibernate.console.KnownConfigurations; import org.hibernate.eclipse.console.EclipseLaunchConsoleConfigurationPreferences; import org.hibernate.eclipse.console.test.project.LaunchConfigTestProject2; +import org.hibernate.eclipse.console.test.utils.ResourceReadUtils; import junit.framework.TestCase; /** * Execute codegeneration launch configuration in external process, * to check the generation is successful. + * Execute codegeneration launch configuration in internal process, + * to check the generation is successful. + * Compare generated results - should be the same. + * Currently both tests are fail, should be success + * when JBIDE-7441 be fixed. * * @author Vitali Yemialyanchyk */ @@ -128,7 +139,152 @@ } assertTrue(nTest > 0); } + + public void testExecute2LaunchConfigs_External_and_Internal() { + // + ILaunchConfiguration launchConfig = null; + ILaunchConfigurationWorkingCopy launchConfigWC = null; + IFolder testFolderAllExportersExternal = null; + IFolder testFolderAllExportersInternal = null; + int nTest = -1; + // + testFolderAllExportersExternal = project.getTestFolderAllExportersExternal(); + nTest = -1; + try { + nTest = testFolderAllExportersExternal.members().length; + } catch (CoreException e) { + } + assertEquals(0, nTest); + // + final String fileNameCodeGenExtern = LaunchConfigTestProject2.LAUNCH_CODE_GEN_TEST_FILE_ALL_EXPORTERS_EXTERN; + launchConfig = loadLaunchConfigFromFile(fileNameCodeGenExtern); + launchConfigWC = null; + try { + launchConfigWC = launchConfig.getWorkingCopy(); + } catch (CoreException e) { + } + assertNotNull(launchConfigWC); + launchConfigWC.setAttribute(IExternalToolConstants.ATTR_LAUNCH_IN_BACKGROUND, false); + DebugUIPlugin.launchInForeground(launchConfigWC, ILaunchManager.RUN_MODE); + nTest = -1; + try { + nTest = testFolderAllExportersExternal.members().length; + } catch (CoreException e) { + } + assertTrue(nTest > 0); + // + testFolderAllExportersInternal = project.getTestFolderAllExportersInternal(); + nTest = -1; + try { + nTest = testFolderAllExportersInternal.members().length; + } catch (CoreException e) { + } + assertEquals(0, nTest); + // + final String fileNameCodeGenIntern = LaunchConfigTestProject2.LAUNCH_CODE_GEN_TEST_FILE_ALL_EXPORTERS_INTERN; + launchConfig = loadLaunchConfigFromFile(fileNameCodeGenIntern); + launchConfigWC = null; + try { + launchConfigWC = launchConfig.getWorkingCopy(); + } catch (CoreException e) { + } + assertNotNull(launchConfigWC); + launchConfigWC.setAttribute(IExternalToolConstants.ATTR_LAUNCH_IN_BACKGROUND, false); + DebugUIPlugin.launchInForeground(launchConfigWC, ILaunchManager.RUN_MODE); + nTest = -1; + try { + nTest = testFolderAllExportersInternal.members().length; + } catch (CoreException e) { + } + assertTrue(nTest > 0); + // + boolean res = compareFolders(testFolderAllExportersExternal, testFolderAllExportersInternal); + assertTrue(res); + } + protected class ResComparator implements Comparator<IResource> { + @Override + public int compare(IResource o1, IResource o2) { + return o1.getName().compareTo(o2.getName()); + } + } + + public boolean compareFiles(IFile testFile1, IFile testFile2) { + boolean res = false; + InputStream is1 = null, is2 = null; + try { + is1 = testFile1.getContents(); + } catch (CoreException e) { + } + try { + is2 = testFile2.getContents(); + } catch (CoreException e) { + } + if (is1 == null || is2 == null) { + res = is1 == is2; + if (!res) { + res = false; + } + return res; + } + String str1 = ResourceReadUtils.readStream(is1); + String str2 = ResourceReadUtils.readStream(is2); + if (str1 == null || str2 == null) { + res = str1 == str2; + if (!res) { + res = false; + } + return res; + } + res = 0 == str1.compareTo(str2); + if (!res) { + res = false; + } + return res; + } + + public boolean compareFolders(IFolder testFolder1, IFolder testFolder2) { + boolean res = false; + IResource[] res1 = null, res2 = null; + try { + res1 = testFolder1.members(); + } catch (CoreException e) { + } + try { + res2 = testFolder2.members(); + } catch (CoreException e) { + } + if (res1 == null || res2 == null) { + return res1 == res2; + } + if (res1.length != res2.length) { + return res; + } + final ResComparator cmp = new ResComparator(); + Arrays.sort(res1, cmp); + Arrays.sort(res2, cmp); + res = true; + for (int i = 0; res && i < res1.length; i++) { + if (0 != res1[i].getName().compareTo(res2[i].getName())) { + res = false; + } + if (res1[i].getType() != res2[i].getType()) { + res = false; + } + if (res && ((IResource.FOLDER & res1[i].getType()) == IResource.FOLDER)) { + IFolder tf1 = (IFolder)res1[i]; + IFolder tf2 = (IFolder)res2[i]; + res = compareFolders(tf1, tf2); + } + //if (res && ((IResource.FILE & res1[i].getType()) == IResource.FILE)) { + // IFile tf1 = (IFile)res1[i]; + // IFile tf2 = (IFile)res2[i]; + // res = compareFiles(tf1, tf2); + //} + } + return res; + } + protected LaunchConfigTestProject2 getProject() { return this.project; } Modified: trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/src/org/hibernate/eclipse/console/test/project/LaunchConfigTestProject2.java =================================================================== --- trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/src/org/hibernate/eclipse/console/test/project/LaunchConfigTestProject2.java 2010-11-24 18:46:42 UTC (rev 26889) +++ trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/src/org/hibernate/eclipse/console/test/project/LaunchConfigTestProject2.java 2010-11-24 19:41:40 UTC (rev 26890) @@ -40,12 +40,16 @@ public class LaunchConfigTestProject2 extends TestProject { public static final String TEST_TMP_OUT_FOLDER = "temp_test_out_folder"; //$NON-NLS-1$ + public static final String TEST_TMP_OUT_FOLDER_ALL_EXPORTERS_EXTERNAL = "temp_test_out_folder_all_exporters_external"; //$NON-NLS-1$ + public static final String TEST_TMP_OUT_FOLDER_ALL_EXPORTERS_INTERNAL = "temp_test_out_folder_all_exporters_internal"; //$NON-NLS-1$ public static final String META_INF_FOLDER = "src/META-INF".replaceAll("//", File.separator); //$NON-NLS-1$ //$NON-NLS-2$ public static final String PROJECT_PATH = "res/project2/".replaceAll("//", File.separator); //$NON-NLS-1$ //$NON-NLS-2$ public static final String RESOURCE_SRC_PATH = "res/project2/src/".replaceAll("//", File.separator); //$NON-NLS-1$ //$NON-NLS-2$ public static final String RESOURCE_LIB_PATH = "res/project2/lib/".replaceAll("//", File.separator); //$NON-NLS-1$ //$NON-NLS-2$ public static final String HIBERNATE_PLUGIN_LIB_PATH = "lib"; //$NON-NLS-1$ + public static final String LAUNCH_CODE_GEN_TEST_FILE_ALL_EXPORTERS_EXTERN = "testLaunchCfg_all_exporters_external.launch"; //$NON-NLS-1$ + public static final String LAUNCH_CODE_GEN_TEST_FILE_ALL_EXPORTERS_INTERN = "testLaunchCfg_all_exporters_internal.launch"; //$NON-NLS-1$ public static final String LAUNCH_CODE_GEN_TEST_FILE_EXTERN = "testLaunchCfg_external.launch"; //$NON-NLS-1$ public static final String LAUNCH_CODE_GEN_TEST_FILE_INTERN = "testLaunchCfg_internal.launch"; //$NON-NLS-1$ public static final String LAUNCH_CONSOLE_CONFIG_TEST_FILE = "LaunchConfigTestProject2.launch"; //$NON-NLS-1$ @@ -77,7 +81,13 @@ super.buildProject(); IPackageFragmentRoot tst = createFolder(TEST_TMP_OUT_FOLDER); tst.getResource().refreshLocal(IResource.DEPTH_INFINITE, null); + tst = createFolder(TEST_TMP_OUT_FOLDER_ALL_EXPORTERS_EXTERNAL); + tst.getResource().refreshLocal(IResource.DEPTH_INFINITE, null); + tst = createFolder(TEST_TMP_OUT_FOLDER_ALL_EXPORTERS_INTERNAL); + tst.getResource().refreshLocal(IResource.DEPTH_INFINITE, null); // + importFileToProject(LAUNCH_CODE_GEN_TEST_FILE_ALL_EXPORTERS_EXTERN); + importFileToProject(LAUNCH_CODE_GEN_TEST_FILE_ALL_EXPORTERS_INTERN); importFileToProject(LAUNCH_CODE_GEN_TEST_FILE_EXTERN); importFileToProject(LAUNCH_CODE_GEN_TEST_FILE_INTERN); importFileToProject(LAUNCH_CONSOLE_CONFIG_TEST_FILE); @@ -103,6 +113,14 @@ public IFolder getTestFolder() { return project.getFolder(TEST_TMP_OUT_FOLDER); } + + public IFolder getTestFolderAllExportersExternal() { + return project.getFolder(TEST_TMP_OUT_FOLDER_ALL_EXPORTERS_EXTERNAL); + } + + public IFolder getTestFolderAllExportersInternal() { + return project.getFolder(TEST_TMP_OUT_FOLDER_ALL_EXPORTERS_INTERNAL); + } public boolean setupSourceTestFolder() throws IOException, CoreException { ArrayList<String> foldersList = new ArrayList<String>();

13 years, 6 months

1
0
0 / 0

JBoss Tools SVN: r26889 - in trunk/documentation/whatsnew/bpel: images and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: bbrodt Date: 2010-11-24 13:46:42 -0500 (Wed, 24 Nov 2010) New Revision: 26889 Added: trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.beta2.html trunk/documentation/whatsnew/bpel/images/CreateMessageProperty.png trunk/documentation/whatsnew/bpel/images/CreatePropertyAlias.png Log: https://jira.jboss.org/browse/JBIDE-7659 New & Noteworthy for BPEL editor Added: trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.beta2.html =================================================================== --- trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.beta2.html (rev 0) +++ trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.beta2.html 2010-11-24 18:46:42 UTC (rev 26889) @@ -0,0 +1,81 @@ +<?xml version="1.0" encoding="iso-8859-1"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> +<meta http-equiv="Content-Language" content="en-us" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +<link rel="stylesheet" href="../whatsnew.css" /> +<title>BPEL Tools 1.1.0.beta1 What's New</title> +</head> +<body> +<h1>JBoss Eclipse BPEL Editor 1.1.0.beta1 What's New</h1> + +<p align="right"><a href="../index.html">< Main Index</a> <a href="../esb/esb-news-1.4.0.M2.html">ESB Tools ></a></p> +<table border="0" cellpadding="10" cellspacing="0" width="80%"> + <tr> + <td colspan="2"> + <hr /> + <h3>General</h3> + <hr /> + </td> + </tr> + <tr> + <td valign="top" align="right"><a name="itemname3" id="itemname3"></a><b>BPEL + Editor</b></td> + <td valign="top">The following issues were fixed. + <ol> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7724">JBIDE-7724</a> BPEL Editor throws SWTException on startup because color registry is not initialized <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7620">JBIDE-7620</a> Server view throws an NPE if process no longer exists in app server <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7526">JBIDE-7526</a> "Unknown Marker ID" exception being thrown by editor on mousehover over error decorator <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7520">JBIDE-7520</a> BPEL Editor crashes on startup if extension model is corrupt <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7504">JBIDE-7504</a> NPE when create a eventhandler for a scope <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7497">JBIDE-7497</a> Decoration icons for Error Markers do not show up on compound activities <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7486">JBIDE-7486</a> BPELModuleContentProvider throws NPE if Servers view contains a deleted or closed module (project) <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7480">JBIDE-7480</a> NPE when trying to add an activity to onAlarm branch in pick. <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7478">JBIDE-7478</a> BPEL validator marks missing WSDL imports only as warnings. <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7477">JBIDE-7477</a> ODE deployment descriptor editor is not closed when deploy.xml file is deleted. <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7254">JBIDE-7254</a> [BPEL] Prevented recursive attempt to activate part ProjectExplorer while activating bpeleditor <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7250">JBIDE-7250</a> NPE when changing size of a FLOW <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7165">JBIDE-7165</a> BPEL Editor does not create WSDL as part of process creation wizard <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7116">JBIDE-7116</a> BPEL Editor not seeing message structure when imported into WSDL <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7107">JBIDE-7107</a> Problems when creating BPEL Correlation Set <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7028">JBIDE-7028</a> New ODE deployment descriptor wizard should create deploy.xml file instead of bpel-deploy.xml <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-6748">JBIDE-6748</a> Enhance Assign Activity Initializer to support complex message types that include choice elements <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-6661">JBIDE-6661</a> Deploying BPEL process with dependent jars <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-6170">JBIDE-6170</a> BPEL source folder should not be hard-coded as "bpelContent" <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-6016">JBIDE-6016</a> Error markers are not removed after correcting BPEL <br></br> + </ol> + We are also doing nightly builds at the + <a href="http://eclipse.org/bpel">Eclipse BPEL project</a> + and maintaining parallel codelines there. + The goal is to push the BPEL Designer back upstream for general consumption. + </tr> + <tr> + <td colspan="2"> + <hr /> + <h3>UI Changes</h3> + <hr /> + </td> + </tr> + <tr> + <td valign="top" align="right"><a name="itemname3" id="itemname3"></a><b> + Correlation Set Dialogs + </b></td> + <td> + The Correlation Set creation dialogs have been simplified. + See + <a href="https://jira.jboss.org/browse/JBIDE-7107">JBIDE-7107</a> for details. + <p></p> + <img src="images/CreateMessageProperty.png"/> + <p></p> + <img src="images/CreatePropertyAlias.png"/> + </td> + + </tr> + +</table> + +</body> + +</html> Added: trunk/documentation/whatsnew/bpel/images/CreateMessageProperty.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/whatsnew/bpel/images/CreateMessageProperty.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/whatsnew/bpel/images/CreatePropertyAlias.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/whatsnew/bpel/images/CreatePropertyAlias.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream

13 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits November 2010