JBoss Tools SVN: r17466 - in trunk/bpel/docs/reference/en: images and 1 other directories.
by jbosstools-commits＠lists.jboss.org
Author: chukhutsina
Date: 2009-09-04 10:39:03 -0400 (Fri, 04 Sep 2009)
New Revision: 17466
Modified:
trunk/bpel/docs/reference/en/images/deploy_createdeploy_3.png
trunk/bpel/docs/reference/en/images/deploy_createdeploy_7.png
trunk/bpel/docs/reference/en/images/detail_createprocess_3.png
trunk/bpel/docs/reference/en/images/detail_editprocess_1.png
trunk/bpel/docs/reference/en/images/detail_editprocess_2.png
trunk/bpel/docs/reference/en/master.xml
trunk/bpel/docs/reference/en/modules/deploy.xml
trunk/bpel/docs/reference/en/modules/detail.xml
trunk/bpel/docs/reference/en/modules/install.xml
trunk/bpel/docs/reference/en/modules/overview.xml
Log:
<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/jira/browse/JBDS-780 -Checked,formated and a bit restructured the Guide.Mistakes were corrected. </p>
</body></html>
Modified: trunk/bpel/docs/reference/en/images/deploy_createdeploy_3.png
===================================================================
(Binary files differ)
Modified: trunk/bpel/docs/reference/en/images/deploy_createdeploy_7.png
===================================================================
(Binary files differ)
Modified: trunk/bpel/docs/reference/en/images/detail_createprocess_3.png
===================================================================
(Binary files differ)
Modified: trunk/bpel/docs/reference/en/images/detail_editprocess_1.png
===================================================================
(Binary files differ)
Modified: trunk/bpel/docs/reference/en/images/detail_editprocess_2.png
===================================================================
(Binary files differ)
Modified: trunk/bpel/docs/reference/en/master.xml
===================================================================
--- trunk/bpel/docs/reference/en/master.xml 2009-09-04 14:29:33 UTC (rev 17465)
+++ trunk/bpel/docs/reference/en/master.xml 2009-09-04 14:39:03 UTC (rev 17466)
@@ -6,6 +6,8 @@
<!ENTITY install SYSTEM "modules/install.xml">
<!ENTITY detail SYSTEM "modules/detail.xml">
<!ENTITY deploy SYSTEM "modules/deploy.xml">
+
+
]>
<book>
Modified: trunk/bpel/docs/reference/en/modules/deploy.xml
===================================================================
--- trunk/bpel/docs/reference/en/modules/deploy.xml 2009-09-04 14:29:33 UTC (rev 17465)
+++ trunk/bpel/docs/reference/en/modules/deploy.xml 2009-09-04 14:39:03 UTC (rev 17466)
@@ -1,15 +1,15 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<chapter id="deploy">
- <title>Deploy a JBoss BPEL project into JBoss BPEL Runtime</title>
+ <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 into JBoss BPEL Runtime, you need to create a bpel-deploy.xml file.
- Our tools can help you to create it:
+ <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 on the <property>Next</property> button.
+ <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>
@@ -21,11 +21,12 @@
</figure>
</listitem>
<listitem>
- <para>BPEL Project: Click on the <property>Browse...</property> button to select a BPEL project in your workspace which you want to deploy into the runtime.
- Please note that you should select the bpel folder under the BPEL project because the bpel-deploy.xml should be at this place.
+ <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>bpel</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>File name: The default value is bpel-deploy.xml. Please don't change it.</para>
- <para>Click on <property>Finish</property> button to close the wizard.</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>
@@ -36,10 +37,11 @@
</figure>
</listitem>
<listitem>
- <para>Double-click on the bpel-deploy.xml file to open it. In the <property>Inbound Interface</property> section, click in the
- <property>Associated Port</property> column for the <property>client</property> Parner link. Then select <property>HelloWorldProcessPort</property>
- in the drop down box. Click in the other part of the eclipse, the <property>Related Service</property> and <property>Binding Used</property>
- clumns should automatically be filled in. Save the bpel-deploy.xml.
+ <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>
@@ -54,16 +56,16 @@
</section>
<section id="createruntime">
<title>Creating JBoss BPEL Server</title>
- <para>Suppose you have installed the JBoss BPEL Runtime-<property>RiftSaw</property>, now we can create a server for the JBoss BPEL runtime</para>
+ <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 view</property> by selecting
- <emphasis><property>Windows > Show View > Other... > Server > Servers</property></emphasis>.
+ <para>Open the <property>JBoss Server view</property> by selecting
+ <emphasis><property>Windows > Show View > Other... > Server > JBoss Server view</property></emphasis>.
</para>
</listitem>
<listitem>
- <para>In the Servers view, right-click and select
- <emphasis><property>New > Server</property></emphasis> to open a wizard:
+ <para>Right-click the JBoss Server view and select
+ <emphasis><property>New > Server</property></emphasis> to open the New Server Wizard:
</para>
<figure>
<title>New Server Wizard</title>
@@ -75,9 +77,15 @@
</figure>
</listitem>
<listitem>
- <para>Server type: select <property>JBoss AS 5.1</property>. Please note that only JBoss As 5.1 or higher version support BPEL.</para>
- <para>Click on the <property>Next</property> button. On the next page, you can input your JBoss As location. Then click on the <property>Next</property> button.
- you can get the page like this:
+ <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 support 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>
@@ -89,8 +97,8 @@
</figure>
</listitem>
<listitem>
- <para>Select <property>HelloWorld</property>, then click on the <property>Add > </property> button to add the project to the server.
- Then click on <property>Finish</property> button.
+ <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>
@@ -101,10 +109,11 @@
<imagedata fileref="images/deploy_createdeploy_6.png"/>
</imageobject>
</mediaobject>
- </figure>
+ </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 input the link <ulink url="http://localhost:8080/bpel/processes.html">http://localhost:8080/bpel/processes.html</ulink> in the browser to get the deployed processes.</para>
+ <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>
@@ -115,6 +124,9 @@
</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
Modified: trunk/bpel/docs/reference/en/modules/detail.xml
===================================================================
--- trunk/bpel/docs/reference/en/modules/detail.xml 2009-09-04 14:29:33 UTC (rev 17465)
+++ trunk/bpel/docs/reference/en/modules/detail.xml 2009-09-04 14:39:03 UTC (rev 17466)
@@ -1,13 +1,14 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<chapter id="detail">
- <title>Create and edit a BPEL project</title>
- <para>In the chapter we provide you with the necessary steps to create a BPEL project and edit the BPEL files.
- First you need to create a BPEL project.
+ <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.
+ First of all, you should create a BPEL project.
</para>
<section id="createproject">
<title>Creating a BPEL project</title>
- <para>Create a Web project by selecting
- <emphasis><property>New > Project... > BPEL 2.0 > BPEL Project</property></emphasis>. Click on the <property>Next</property> button.
+ <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>
@@ -17,12 +18,9 @@
</imageobject>
</mediaobject>
</figure>
- <para>Enter the following information:</para>
- <itemizedlist>
- <listitem>
- <para>Project Name: enter a project name. For example, enter <property>HelloWorld</property>. </para>
- </listitem>
- </itemizedlist>
+ <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>
@@ -31,9 +29,9 @@
</imageobject>
</mediaobject>
</figure>
- <para>Click on the <property>Finish</property> button. Now you have created a BPEL project named <property>HelloWorld</property>. It's structure is like this: </para>
+ <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>A BPEL Project structure</title>
+ <title>The BPEL Project structure</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/detail_createproject_3.png"/>
@@ -43,7 +41,7 @@
</section>
<section id="createprocess">
<title>Creating a BPEL process</title>
- <para>Create a BPEL process by selecting
+ <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>
@@ -54,18 +52,38 @@
</imageobject>
</mediaobject>
</figure>
- <para>Click on the <property>Next</property> button. Enter the following information:</para>
- <itemizedlist>
- <listitem>
- <para>BPEL Process Name: enter a process name. For example, <property>HelloWorld</property>. </para>
- </listitem>
- <listitem>
- <para>Namespace: enter or select a namespace for the BPEL process</para>
- </listitem>
- <listitem>
- <para>Template: select a template for the BPEL process. When you select a template, below the row, you will get the information for the template.</para>
- </listitem>
- </itemizedlist>
+ <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>
@@ -74,13 +92,16 @@
</imageobject>
</mediaobject>
</figure>
- <para>Click on the <property>Next</property> button. On the second page, make sure that the fold <property>HelloWorld/bpel</property> is selected.
- Clink on the <property>Finish</property> button.
+ <para>Click the <property>Next</property> button. On the second page make sure that the folder <property>HelloWorld/bpel</property> is selected.
+ Click <property>Finish</property>.
</para>
- <para>All of your files that are used in your BPEL project must be under the <property>bpel</property> folder. Only like this,
- these files can be deployed into JBoss server.
- </para>
- <para>Up to now, you have get a simple BPEL process as below. Next step, you can edit the BPEL process and then deploy it into JBoss server. </para>
+ <note>
+ <para>All of your files that are used in your BPEL project must be under the <property>bpel</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>
@@ -89,11 +110,12 @@
</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</title>
- <para>If you don't get the Properties view and Palette view opened, you can right-click on the BPEL editor and select the
- <property>Show in Properties</property>, <property>Show Palette in Palette view</property>. Then you can get the view like:
+ <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>
@@ -103,46 +125,66 @@
</imageobject>
</mediaobject>
</figure>
- <para>In the Palette view, you can drag a BPEL element into the BPEL editor and put it in the palace that you want.</para>
- <para>In the Properties view, you can get the information for every element of the BPEL process. Select a element in the BPEL editor,
- the element's properties will be shown in the Properties view:
+ <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>Description section: Show the described information of the element. For example, <property>Name</property> of the element.</para>
- </listitem>
- <listitem>
- <para>Details section: Show the detailed and important information of element. This is the most important section of a element.
- Many properties of a element will be set in this section.
- </para>
- </listitem>
- <listitem>
- <para>Join Behavior section: Show the <property>Join Failure</property> property of the element.</para>
- </listitem>
- <listitem>
- <para>Documentation section: Show the <property>documentation</property> sub-element of the element.</para>
- </listitem>
- <listitem>
- <para>Others sections: Every BPEL element has itself sections, Correlation section, Message Exchange section, and so on. We will
- introduce them when using them.
- </para>
- </listitem>
- </itemizedlist>
- <para>In order to show how a simple BPEL process work, we will 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>Select the <property>Assign</property> element in the BPEL editor, you can get the properties information of it in the Properties view.
+ <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 Details section, you can select <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 "initializer" popup dialog appears. Click on the <property>Yes</property> button.
+ <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 an <property>Assign</property> to the process</title>
+ <title>Add <property>Assign</property> to the process</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/detail_editprocess_2.png"/>
@@ -151,13 +193,13 @@
</figure>
</listitem>
<listitem>
- <para>Open the file "HelloWorldArtifacts.wsdl" in the "HelloWorld" project by double-clicking on it. Right-click in the WSDL editor and select
- <property>Add Service</property>. A new service appears on the editor. Name it <property>HelloWorldProcessService</property>. It has a Port
+ <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 a <property>Service</property> to the WSDL file</title>
+ <title>Add <property>Service</property> to the WSDL file</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/detail_editprocess_3.png"/>
@@ -167,10 +209,10 @@
</listitem>
<listitem>
<para>Right-click somewhere in the whitespace of the WSDL editor and select
- <property>Add Binding</property>. A new Binding appears on the editor. Name it <property>HelloWorldSOAPBinding</property>. Select it, in the
- Properties view, General section, select <property>HelloWorld</property> port type in the <property>PortType</property>. Then click on the
- <property>Generate Binding Content...</property> button to open a <property>Binding Wizard</property>. In the wizard, select the <property>SOAP</property>
- as the <property>Protocol</property>. Finally, click on the <property>Finish</property> button to close the wizard.
+ <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>
@@ -182,8 +224,8 @@
</figure>
</listitem>
<listitem>
- <para>Click on the <property>HelloWorldProcessPort</property>, in the Properties view, General section, select the <property>HelloWorldSOAPBinding</property> in
- the <property>Binding</property> Combo. 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>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>
@@ -195,7 +237,7 @@
</figure>
</listitem>
</itemizedlist>
- <para>For now, you have finished the simple BPEL process. Next step, you can deploy the BPEL project into JBoss BPEL Runtime.</para>
+ <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>
Modified: trunk/bpel/docs/reference/en/modules/install.xml
===================================================================
--- trunk/bpel/docs/reference/en/modules/install.xml 2009-09-04 14:29:33 UTC (rev 17465)
+++ trunk/bpel/docs/reference/en/modules/install.xml 2009-09-04 14:39:03 UTC (rev 17466)
@@ -1,19 +1,22 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<chapter id="install">
- <title>Install the JBoss BPEL editor</title>
+ <title>Installation JBoss BPEL Tools</title>
<section id="installeclipse">
- <title>Installing the JBoss BPEL editor</title>
- <para>At first, you need an Eclipse(3.5). You can get it from <ulink url="http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo...">Eclipse</ulink> Web Site.
+ <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 in 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 only want to install the JBoss BPEL editor, you may install it from <ulink url="http://jboss.org/tools/download/dev.html">JBoss Tools</ulink> page. Please note that
- only JBoss Tools 3.1 or higher version include the JBoss BPEL editor.
+ <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 id="installRuntime">
- <title>Installing the JBoss BPEL Runtime</title>
- <para>If you want to deploy a BPEL project to JBoss runtime, you need to download the JBoss BPEL Runtime by yourself. The JBoss BPEL Runtime
- is named RiftSaw. You can get it from <ulink url="http://jboss.org/riftsaw">JBoss RiftSaw</ulink> page.
+ <title>Installation JBoss BPEL Runtime</title>
+ <para>If you want to deploy a BPEL project to JBoss server,
+ you should download JBoss BPEL Runtime by yourself. The JBoss BPEL Runtime
+ is named RiftSaw. You can get it from <ulink url="http://jboss.org/riftsaw">JBoss RiftSaw page </ulink>.
</para>
</section>
</chapter>
\ No newline at end of file
Modified: trunk/bpel/docs/reference/en/modules/overview.xml
===================================================================
--- trunk/bpel/docs/reference/en/modules/overview.xml 2009-09-04 14:29:33 UTC (rev 17465)
+++ trunk/bpel/docs/reference/en/modules/overview.xml 2009-09-04 14:39:03 UTC (rev 17466)
@@ -1,26 +1,30 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<chapter id="overview">
- <title>JBoss BPEL editor project Overview</title>
+ <title>JBoss BPEL project Overview</title>
- <para>JBoss BPEL editor project is a WS-BPEL 2.0 editor that give a way to create, edit, validate and deploy BPEL files into JBoss BPEL runtime. It is based on the Eclipse
- <ulink url="http://www.eclipse.org/bpel/">BPEL</ulink>
- project. </para>
+ <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> Tight integration with JBoss BPEL runtime. Add a new project type for the deployment to JBoss BPEL runtime</para></listitem>
- <listitem><para> Support two ways to deploy: one is deploy a bpel project directly into JBoss BPEL runtime. The other is deploy bpel files in the JBoss ESB project into JBoss BPEL runtime. </para></listitem>
- <listitem><para> Improve the BPEL validator and the Eclipse BPEL editor's quality. </para></listitem>
+ <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. Specifically, 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.
+ 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 editor project</title>
- <para>For a start, we propose you to look through the table of main features of JBoss BPEL editor project: </para>
+ <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>
@@ -38,19 +42,21 @@
<tbody>
<row>
<entry><para>WS-BPEL 2.0 support</para></entry>
- <entry><para>JBoss BPEL editor project supports the newest WS-BPEL 2.0 specifications. </para></entry>
+ <entry><para>JBoss BPEL project supports the newest WS-BPEL 2.0 specifications. </para></entry>
</row>
<row>
- <entry><para>Tight integration with JBoss BPEL runtime</para></entry>
- <entry><para>There are two ways to deploy BPEL files into JBoss BPEL runtime. User can deploy a BPEL project as a whole and can deploy BPEL files in JBoss ESB project into JBoss BPEL runtime. </para></entry>
+ <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>A BPEL file editor</para></entry>
- <entry><para>User can use the editor freely to edit a BPEL file. </para></entry>
+ <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>A BPEL file validator</para></entry>
- <entry><para>The validator can give the error messages about BPEL files to user. </para></entry>
+ <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>
14 years, 8 months
JBoss Tools SVN: r17465 - branches/jbosstools-3.1.0.M3/hibernatetools/tests/org.jboss.tools.hibernate.ui.test/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/test.
by jbosstools-commits＠lists.jboss.org
Author: vyemialyanchyk
Date: 2009-09-04 10:29:33 -0400 (Fri, 04 Sep 2009)
New Revision: 17465
Modified:
branches/jbosstools-3.1.0.M3/hibernatetools/tests/org.jboss.tools.hibernate.ui.test/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/test/ExportImageActionTest.java
Log:
try to fix junit test on hudson
Modified: branches/jbosstools-3.1.0.M3/hibernatetools/tests/org.jboss.tools.hibernate.ui.test/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/test/ExportImageActionTest.java
===================================================================
--- branches/jbosstools-3.1.0.M3/hibernatetools/tests/org.jboss.tools.hibernate.ui.test/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/test/ExportImageActionTest.java 2009-09-04 14:29:31 UTC (rev 17464)
+++ branches/jbosstools-3.1.0.M3/hibernatetools/tests/org.jboss.tools.hibernate.ui.test/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/test/ExportImageActionTest.java 2009-09-04 14:29:33 UTC (rev 17465)
@@ -96,6 +96,7 @@
});
final ExportImageAction exportImageAction = new ExportImageAction(editor);
exportImageAction.setSaveDialog(saveDialog);
+ exportImageAction.setShowErrDialog(false);
exportImageAction.run();
// test is the file created
File file = new File(filePath);
14 years, 8 months
JBoss Tools SVN: r17464 - trunk/jsf/docs/userguide/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: smukhina
Date: 2009-09-04 10:29:31 -0400 (Fri, 04 Sep 2009)
New Revision: 17464
Modified:
trunk/jsf/docs/userguide/en/modules/editors.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-840 CSS editor is redesigned - perpective is already described, added a link from CSS editor chapter to CSS perspective chapter
Modified: trunk/jsf/docs/userguide/en/modules/editors.xml
===================================================================
--- trunk/jsf/docs/userguide/en/modules/editors.xml 2009-09-04 14:28:13 UTC (rev 17463)
+++ trunk/jsf/docs/userguide/en/modules/editors.xml 2009-09-04 14:29:31 UTC (rev 17464)
@@ -2156,8 +2156,10 @@
</mediaobject>
</figure>
+ <para>To make you work on CSS files more comfortable, CSS perspective is available, read more about it in <link linkend ="css_perspective">CSS Editing Perspective chapter</link></para>
</section>
<section id="JavaScriptEditor">
+
<title>JavaScript Editor</title>
14 years, 8 months
JBoss Tools SVN: r17463 - branches/jbosstools-3.1.0.M3/hibernatetools/plugins/org.jboss.tools.hibernate.ui/src/org/jboss/tools/hibernate/ui/diagram/editors/actions.
by jbosstools-commits＠lists.jboss.org
Author: vyemialyanchyk
Date: 2009-09-04 10:28:13 -0400 (Fri, 04 Sep 2009)
New Revision: 17463
Modified:
branches/jbosstools-3.1.0.M3/hibernatetools/plugins/org.jboss.tools.hibernate.ui/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/ExportImageAction.java
Log:
try to fix junit test on hudson
Modified: branches/jbosstools-3.1.0.M3/hibernatetools/plugins/org.jboss.tools.hibernate.ui/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/ExportImageAction.java
===================================================================
--- branches/jbosstools-3.1.0.M3/hibernatetools/plugins/org.jboss.tools.hibernate.ui/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/ExportImageAction.java 2009-09-04 14:21:08 UTC (rev 17462)
+++ branches/jbosstools-3.1.0.M3/hibernatetools/plugins/org.jboss.tools.hibernate.ui/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/ExportImageAction.java 2009-09-04 14:28:13 UTC (rev 17463)
@@ -29,6 +29,7 @@
import org.eclipse.swt.graphics.ImageData;
import org.eclipse.swt.graphics.ImageLoader;
import org.eclipse.swt.widgets.FileDialog;
+import org.hibernate.eclipse.console.HibernateConsolePlugin;
import org.jboss.tools.hibernate.ui.diagram.DiagramViewerMessages;
import org.jboss.tools.hibernate.ui.diagram.editors.DiagramViewer;
@@ -40,6 +41,7 @@
DiagramViewerMessages.ExportImageAction_jpg_format, DiagramViewerMessages.ExportImageAction_bmp_format };
private FileDialog saveDialog = null;
+ private boolean showErrDialog = true;
public static final ImageDescriptor img =
ImageDescriptor.createFromFile(DiagramViewer.class, "icons/export.png"); //$NON-NLS-1$
@@ -60,6 +62,10 @@
this.saveDialog = saveDialog;
}
+ public void setShowErrDialog(boolean showErrDialog) {
+ this.showErrDialog = showErrDialog;
+ }
+
public void run() {
if (saveDialog == null) {
@@ -91,9 +97,11 @@
outStream.write(imageData);
outStream.flush();
} catch (Exception e) {
- MessageDialog.openInformation(getDiagramViewer().getSite().getShell(),
+ HibernateConsolePlugin.getDefault().logErrorMessage("ExportImageAction", e); //$NON-NLS-1$
+ if (showErrDialog) {
+ MessageDialog.openInformation(getDiagramViewer().getSite().getShell(),
DiagramViewerMessages.ExportImageAction_error, DiagramViewerMessages.ExportImageAction_failed_to_export_image + e.getMessage());
- return;
+ }
}
finally {
if (outStream != null) {
14 years, 8 months
JBoss Tools SVN: r17462 - in trunk/hibernatetools: tests/org.jboss.tools.hibernate.ui.test/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/test and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: vyemialyanchyk
Date: 2009-09-04 10:21:08 -0400 (Fri, 04 Sep 2009)
New Revision: 17462
Modified:
trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/ExportImageAction.java
trunk/hibernatetools/tests/org.jboss.tools.hibernate.ui.test/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/test/ExportImageActionTest.java
Log:
try to fix junit test on hudson
Modified: trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/ExportImageAction.java
===================================================================
--- trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/ExportImageAction.java 2009-09-04 14:20:37 UTC (rev 17461)
+++ trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/ExportImageAction.java 2009-09-04 14:21:08 UTC (rev 17462)
@@ -29,6 +29,7 @@
import org.eclipse.swt.graphics.ImageData;
import org.eclipse.swt.graphics.ImageLoader;
import org.eclipse.swt.widgets.FileDialog;
+import org.hibernate.eclipse.console.HibernateConsolePlugin;
import org.jboss.tools.hibernate.ui.diagram.DiagramViewerMessages;
import org.jboss.tools.hibernate.ui.diagram.editors.DiagramViewer;
@@ -40,6 +41,7 @@
DiagramViewerMessages.ExportImageAction_jpg_format, DiagramViewerMessages.ExportImageAction_bmp_format };
private FileDialog saveDialog = null;
+ private boolean showErrDialog = true;
public static final ImageDescriptor img =
ImageDescriptor.createFromFile(DiagramViewer.class, "icons/export.png"); //$NON-NLS-1$
@@ -60,6 +62,10 @@
this.saveDialog = saveDialog;
}
+ public void setShowErrDialog(boolean showErrDialog) {
+ this.showErrDialog = showErrDialog;
+ }
+
public void run() {
if (saveDialog == null) {
@@ -91,9 +97,11 @@
outStream.write(imageData);
outStream.flush();
} catch (Exception e) {
- MessageDialog.openInformation(getDiagramViewer().getSite().getShell(),
+ HibernateConsolePlugin.getDefault().logErrorMessage("ExportImageAction", e); //$NON-NLS-1$
+ if (showErrDialog) {
+ MessageDialog.openInformation(getDiagramViewer().getSite().getShell(),
DiagramViewerMessages.ExportImageAction_error, DiagramViewerMessages.ExportImageAction_failed_to_export_image + e.getMessage());
- return;
+ }
}
finally {
if (outStream != null) {
Modified: trunk/hibernatetools/tests/org.jboss.tools.hibernate.ui.test/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/test/ExportImageActionTest.java
===================================================================
--- trunk/hibernatetools/tests/org.jboss.tools.hibernate.ui.test/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/test/ExportImageActionTest.java 2009-09-04 14:20:37 UTC (rev 17461)
+++ trunk/hibernatetools/tests/org.jboss.tools.hibernate.ui.test/src/org/jboss/tools/hibernate/ui/diagram/editors/actions/test/ExportImageActionTest.java 2009-09-04 14:21:08 UTC (rev 17462)
@@ -96,6 +96,7 @@
});
final ExportImageAction exportImageAction = new ExportImageAction(editor);
exportImageAction.setSaveDialog(saveDialog);
+ exportImageAction.setShowErrDialog(false);
exportImageAction.run();
// test is the file created
File file = new File(filePath);
14 years, 8 months
JBoss Tools SVN: r17461 - trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test.
by jbosstools-commits＠lists.jboss.org
Author: mareshkau
Date: 2009-09-04 10:20:37 -0400 (Fri, 04 Sep 2009)
New Revision: 17461
Modified:
trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/ComponentContentTest.java
Log:
fixing errors in junit tests
Modified: trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/ComponentContentTest.java
===================================================================
--- trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/ComponentContentTest.java 2009-09-04 14:11:32 UTC (rev 17460)
+++ trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/ComponentContentTest.java 2009-09-04 14:20:37 UTC (rev 17461)
@@ -180,10 +180,8 @@
controller.getVisualBuilder().setShowInvisibleTags(true);
controller.visualRefresh();
- TestUtil.waitForIdle();
-
// find visual element and check if it is not null
- visualElement = findElementById(controller, elementId);
+ visualElement = findElementById(controller, elementId,TestUtil.MAX_IDLE);
assertNotNull(visualElement);
// generate text for invisible tag
@@ -312,8 +310,29 @@
*
* @param controller
* @param elementId
+ * @param idle try element for some time period, for example when we need
+ * to wait for refresh job
* @return
*/
+ protected nsIDOMElement findElementById(VpeController controller,
+ String elementId, long idle) {
+ long start = System.currentTimeMillis();
+ nsIDOMElement result = null;
+ while (result==null) {
+ result = findElementById(controller, elementId);
+ TestUtil.delay(50);
+ if (result==null && ((System.currentTimeMillis()-start) > idle) )
+ throw new RuntimeException("A long running task detected"); //$NON-NLS-1$
+ }
+ return result;
+ }
+ /**
+ * find visual element by "id" entered in source part of vpe
+ *
+ * @param controller
+ * @param elementId
+ * @return
+ */
protected nsIDOMNode findNode(VpeController controller, Node node) {
VpeNodeMapping nodeMapping = controller.getDomMapping().getNodeMapping(
14 years, 8 months
JBoss Tools SVN: r17460 - in trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects: CAForELinStyleTest/WebContent/WEB-INF/lib and 4 other directories.
by jbosstools-commits＠lists.jboss.org
Author: vrubezhny
Date: 2009-09-04 10:11:32 -0400 (Fri, 04 Sep 2009)
New Revision: 17460
Removed:
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/common-annotations.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/commons-beanutils.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/commons-collections.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/commons-digester.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/commons-logging.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/standard.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/common-annotations.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/commons-beanutils.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/commons-collections.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/commons-digester.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/commons-logging.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/standard.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/classes/
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/common-annotations.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/commons-beanutils.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/commons-collections.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/commons-digester.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/commons-logging.jar
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/standard.jar
Modified:
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/.project
trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/JsfJbide1704Test/.project
Log:
JBIDE-4833: Reduce a number of jars in org.jboss.tools.jst.jsp.test\projects.
Unused jars are removed
Modified: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/.project
===================================================================
--- trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/.project 2009-09-04 11:39:25 UTC (rev 17459)
+++ trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/.project 2009-09-04 14:11:32 UTC (rev 17460)
@@ -15,6 +15,11 @@
<arguments>
</arguments>
</buildCommand>
+ <buildCommand>
+ <name>org.jboss.tools.jst.web.kb.kbbuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jem.workbench.JavaEMFNature</nature>
@@ -22,5 +27,6 @@
<nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>
<nature>org.jboss.tools.jsf.jsfnature</nature>
<nature>org.eclipse.wst.common.project.facet.core.nature</nature>
+ <nature>org.jboss.tools.jst.web.kb.kbnature</nature>
</natures>
</projectDescription>
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/common-annotations.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/commons-beanutils.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/commons-collections.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/commons-digester.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/commons-logging.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForELinStyleTest/WebContent/WEB-INF/lib/standard.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/common-annotations.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/commons-beanutils.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/commons-collections.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/commons-digester.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/commons-logging.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/CAForIDTest/WebContent/WEB-INF/lib/standard.jar
===================================================================
(Binary files differ)
Modified: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/JsfJbide1704Test/.project
===================================================================
--- trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/JsfJbide1704Test/.project 2009-09-04 11:39:25 UTC (rev 17459)
+++ trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/JsfJbide1704Test/.project 2009-09-04 14:11:32 UTC (rev 17460)
@@ -15,6 +15,11 @@
<arguments>
</arguments>
</buildCommand>
+ <buildCommand>
+ <name>org.jboss.tools.jst.web.kb.kbbuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jem.workbench.JavaEMFNature</nature>
@@ -22,5 +27,6 @@
<nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>
<nature>org.jboss.tools.jsf.jsfnature</nature>
<nature>org.eclipse.wst.common.project.facet.core.nature</nature>
+ <nature>org.jboss.tools.jst.web.kb.kbnature</nature>
</natures>
</projectDescription>
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/common-annotations.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/commons-beanutils.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/commons-collections.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/commons-digester.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/commons-logging.jar
===================================================================
(Binary files differ)
Deleted: trunk/jst/tests/org.jboss.tools.jst.jsp.test/projects/MissingKBBuilderTest/WebContent/WEB-INF/lib/standard.jar
===================================================================
(Binary files differ)
14 years, 8 months
JBoss Tools SVN: r17459 - trunk/common/plugins/org.jboss.tools.common.text.ext.
by jbosstools-commits＠lists.jboss.org
Author: dazarov
Date: 2009-09-04 07:39:25 -0400 (Fri, 04 Sep 2009)
New Revision: 17459
Modified:
trunk/common/plugins/org.jboss.tools.common.text.ext/plugin.xml
Log:
https://jira.jboss.org/jira/browse/JBIDE-4380
Modified: trunk/common/plugins/org.jboss.tools.common.text.ext/plugin.xml
===================================================================
--- trunk/common/plugins/org.jboss.tools.common.text.ext/plugin.xml 2009-09-03 23:28:27 UTC (rev 17458)
+++ trunk/common/plugins/org.jboss.tools.common.text.ext/plugin.xml 2009-09-04 11:39:25 UTC (rev 17459)
@@ -235,12 +235,16 @@
<partitionType id="org.jboss.tools.common.text.ext.xml.XML_ATTRIBUTE_VALUE">
<axis path="*/[http://java.sun.com/jstl/core]:import/url" />
<axis path="*/[http://java.sun.com/jstl/core]:redirect/url" />
+ <axis path="*/[http://java.sun.com/jsp/jstl/core]:import/url" />
+ <axis path="*/[http://java.sun.com/jsp/jstl/core]:redirect/url" />
</partitionType>
</contentType>
<contentType id="org.eclipse.jst.jsp.core.jspsource">
<partitionType id="org.jboss.tools.common.text.ext.xml.XML_ATTRIBUTE_VALUE">
<axis path="*/[http://java.sun.com/jstl/core]:import/url" />
<axis path="*/[http://java.sun.com/jstl/core]:redirect/url" />
+ <axis path="*/[http://java.sun.com/jsp/jstl/core]:import/url" />
+ <axis path="*/[http://java.sun.com/jsp/jstl/core]:redirect/url" />
</partitionType>
</contentType>
</hyperlinkPartitioner>
14 years, 8 months
JBoss Tools SVN: r17458 - in trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd: jpdl/editor and 1 other directories.
by jbosstools-commits＠lists.jboss.org
Author: koen.aers(a)jboss.com
Date: 2009-09-03 19:28:27 -0400 (Thu, 03 Sep 2009)
New Revision: 17458
Modified:
trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/AbstractContentProvider.java
trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/ContentProvider.java
trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/Editor.java
trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/GraphPage.java
trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/editor/JpdlContentProvider.java
trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/editor/JpdlEditor.java
trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/pf/editor/PageFlowEditor.java
Log:
JBIDE-3915: jBPM Eclipse plugin can't save graphical view if gpd.xml is marked as read only
Modified: trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/AbstractContentProvider.java
===================================================================
--- trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/AbstractContentProvider.java 2009-09-03 19:41:58 UTC (rev 17457)
+++ trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/AbstractContentProvider.java 2009-09-03 23:28:27 UTC (rev 17458)
@@ -81,14 +81,21 @@
return buffer.toString();
}
- protected String getNotationInfoFileName(String semanticInfoFileName) {
+ public String getNotationInfoFileName(String semanticInfoFileName) {
return ".gpd." + semanticInfoFileName;
}
-
- protected String getSemanticInfoFileName(String notationInfoFileName) {
- return notationInfoFileName.substring(5);
+
+ public String getDiagramImageFileName(String semanticInfoFileName) {
+ String result;
+ int index = semanticInfoFileName.indexOf(".xml");
+ result = index > -1 ? semanticInfoFileName.substring(0, index) : semanticInfoFileName;
+ return result + ".jpg";
}
+// public String getSemanticInfoFileName(String notationInfoFileName) {
+// return notationInfoFileName.substring(5);
+// }
+
protected void processRootContainer(RootContainer rootContainer, Element notationInfo) {
addDimension(rootContainer, notationInfo);
addNodes(rootContainer, notationInfo);
Modified: trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/ContentProvider.java
===================================================================
--- trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/ContentProvider.java 2009-09-03 19:41:58 UTC (rev 17457)
+++ trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/ContentProvider.java 2009-09-03 23:28:27 UTC (rev 17458)
@@ -8,4 +8,7 @@
boolean saveToInput(IEditorInput input, RootContainer rootContainer);
void addNotationInfo(RootContainer rootContainer, IEditorInput input);
+ String getNotationInfoFileName(String semanticInfoFileName);
+ String getDiagramImageFileName(String semanticInfoFileName);
+
}
Modified: trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/Editor.java
===================================================================
--- trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/Editor.java 2009-09-03 19:41:58 UTC (rev 17457)
+++ trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/Editor.java 2009-09-03 23:28:27 UTC (rev 17458)
@@ -1,7 +1,13 @@
package org.jbpm.gd.common.editor;
+import java.util.ArrayList;
import java.util.EventObject;
+import org.eclipse.core.resources.IContainer;
+import org.eclipse.core.resources.IFile;
+import org.eclipse.core.resources.IFolder;
+import org.eclipse.core.resources.ResourceAttributes;
+import org.eclipse.core.runtime.CoreException;
import org.eclipse.core.runtime.IProgressMonitor;
import org.eclipse.gef.DefaultEditDomain;
import org.eclipse.gef.EditDomain;
@@ -11,6 +17,7 @@
import org.eclipse.jface.action.IMenuManager;
import org.eclipse.jface.action.MenuManager;
import org.eclipse.jface.action.Separator;
+import org.eclipse.jface.dialogs.MessageDialog;
import org.eclipse.jface.viewers.ISelection;
import org.eclipse.swt.widgets.Control;
import org.eclipse.swt.widgets.Menu;
@@ -24,6 +31,7 @@
import org.eclipse.ui.IWorkbenchActionConstants;
import org.eclipse.ui.IWorkbenchPart;
import org.eclipse.ui.PartInitException;
+import org.eclipse.ui.part.FileEditorInput;
import org.eclipse.ui.views.contentoutline.IContentOutlinePage;
import org.eclipse.ui.views.properties.IPropertySheetPage;
import org.eclipse.ui.views.properties.tabbed.ITabbedPropertySheetPageContributor;
@@ -84,6 +92,7 @@
initSourcePage();
initGraphPage();
setActivePage(0);
+ checkReadOnly();
}
protected void addPage(int index, IEditorPart part, String label) {
@@ -198,11 +207,15 @@
private void handleCommandStackChanged() {
getActionRegistry().updateStackActions();
- if (!isDirty() && getCommandStack().isDirty()) {
+ if (!isDirty() && getCommandStack().isDirty() && editAllowed()) {
isDirty = true;
firePropertyChange(IEditorPart.PROP_DIRTY);
}
}
+
+ private boolean editAllowed() {
+ return true;
+ }
protected void pageChange(int newPageIndex) {
if (newPageIndex == 0) {
@@ -302,6 +315,7 @@
}
public void doSave(IProgressMonitor monitor) {
+ if (!checkReadOnly()) return;
super.doSave(monitor);
getGraphPage().doSave(monitor);
boolean saved = getContentProvider().saveToInput(getEditorInput(), getRootContainer());
@@ -316,12 +330,53 @@
super.dispose();
}
- public abstract String getDefaultImageFileName();
-
protected SelectionSynchronizer createSelectionSynchronizer() {
return new SelectionSynchronizer();
}
+ private boolean checkReadOnly() {
+ IFile inputFile = ((FileEditorInput)getEditorInput()).getFile();
+ IFolder inputFolder = (IFolder)inputFile.getParent();
+ IFile notationInfoFile = inputFolder.getFile(getContentProvider().getNotationInfoFileName(inputFile.getName()));
+ IFile diagramImageFile = inputFolder.getFile(getContentProvider().getDiagramImageFileName(inputFile.getName()));
+ String readOnlyFiles = "";
+ ArrayList readOnlyFilesList = new ArrayList();
+ if (inputFile.isReadOnly()) {
+ readOnlyFiles += ("- " + inputFile.getFullPath().toOSString() + "\n");
+ readOnlyFilesList.add(inputFile);
+ }
+ if (notationInfoFile.exists() && notationInfoFile.isReadOnly()) {
+ readOnlyFiles += ("- " + notationInfoFile.getFullPath().toOSString() + "\n");
+ readOnlyFilesList.add(notationInfoFile);
+ }
+ if (diagramImageFile.exists() && diagramImageFile.isReadOnly()) {
+ readOnlyFiles += ("- " + diagramImageFile.getFullPath().toOSString() + "\n");
+ readOnlyFilesList.add(diagramImageFile);
+ }
+ if (readOnlyFilesList.isEmpty()) return true;
+ boolean answer = MessageDialog.openQuestion(
+ getSite().getShell(),
+ "Read-only Input Files Detected",
+ "The following files have a read-only indicator which needs to be changed to read-write in order to be able to save the process correctly.\n\n" +
+ readOnlyFiles + "\n" +
+ "Do you want to perform this change now?");
+ if (answer) {
+ try {
+ ResourceAttributes resourceAttributes = new ResourceAttributes();
+ resourceAttributes.setReadOnly(false);
+ for (int i = 0; i < readOnlyFilesList.size(); i++) {
+ ((IFile)readOnlyFilesList.get(i)).setResourceAttributes(resourceAttributes);
+ }
+ return false;
+ } catch (CoreException e) {
+ Logger.logError("Error while trying to set files writeable", e);
+ return true;
+ }
+ } else {
+ return true;
+ }
+ }
+
protected abstract ContentProvider createContentProvider();
protected abstract SemanticElement createMainElement();
protected abstract GraphicalViewer createGraphicalViewer();
Modified: trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/GraphPage.java
===================================================================
--- trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/GraphPage.java 2009-09-03 19:41:58 UTC (rev 17457)
+++ trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/GraphPage.java 2009-09-03 23:28:27 UTC (rev 17458)
@@ -131,18 +131,13 @@
}
}
- private String getImageSavePath() {
+ public String getImageSavePath() {
IFile file = ((FileEditorInput)getEditorInput()).getFile();
- String name = file.getName();
- if (name.startsWith(".gpd.") && name.length() > 7) {
- name = name.substring(5, name.length() - 3) + "jpg";
- } else {
- name = editor.getDefaultImageFileName();
- }
+ String name = editor.getContentProvider().getDiagramImageFileName(file.getName());
IPath path = file.getRawLocation().removeLastSegments(1).append(name);
return path.toOSString();
}
-
+
public void doSaveAs() {
}
Modified: trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/editor/JpdlContentProvider.java
===================================================================
--- trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/editor/JpdlContentProvider.java 2009-09-03 19:41:58 UTC (rev 17457)
+++ trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/editor/JpdlContentProvider.java 2009-09-03 23:28:27 UTC (rev 17458)
@@ -36,7 +36,7 @@
public class JpdlContentProvider extends AbstractContentProvider{
- protected String getNotationInfoFileName(String semanticInfoFileName) {
+ public String getNotationInfoFileName(String semanticInfoFileName) {
if ("processdefinition.xml".equals(semanticInfoFileName)) {
return "gpd.xml";
} else {
@@ -44,14 +44,22 @@
}
}
- protected String getSemanticInfoFileName(String notationInfoFileName) {
- if ("gpd.xml".equals(notationInfoFileName)) {
- return "processdefinition.xml";
+ public String getDiagramImageFileName(String semanticInfoFileName) {
+ if ("processdefinition.xml".equals(semanticInfoFileName)) {
+ return "processimage.jpg";
} else {
- return super.getSemanticInfoFileName(notationInfoFileName);
+ return super.getDiagramImageFileName(semanticInfoFileName);
}
}
+// public String getSemanticInfoFileName(String notationInfoFileName) {
+// if ("gpd.xml".equals(notationInfoFileName)) {
+// return "processdefinition.xml";
+// } else {
+// return super.getSemanticInfoFileName(notationInfoFileName);
+// }
+// }
+
protected void addNodes(NodeContainer nodeContainer, Element notationInfo) {
NodeElementContainer nodeElementContainer = (NodeElementContainer)nodeContainer.getSemanticElement();
addNodes(nodeContainer, nodeElementContainer.getNodeElements(), notationInfo);
Modified: trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/editor/JpdlEditor.java
===================================================================
--- trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/editor/JpdlEditor.java 2009-09-03 19:41:58 UTC (rev 17457)
+++ trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/editor/JpdlEditor.java 2009-09-03 23:28:27 UTC (rev 17458)
@@ -144,8 +144,4 @@
super.dispose();
}
- public String getDefaultImageFileName() {
- return "processimage.jpg";
- }
-
}
Modified: trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/pf/editor/PageFlowEditor.java
===================================================================
--- trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/pf/editor/PageFlowEditor.java 2009-09-03 19:41:58 UTC (rev 17457)
+++ trunk/jbpm/plugins/org.jbpm.gd.jpdl/src/org/jbpm/gd/pf/editor/PageFlowEditor.java 2009-09-03 23:28:27 UTC (rev 17458)
@@ -1,6 +1,5 @@
package org.jbpm.gd.pf.editor;
-import org.eclipse.ui.part.FileEditorInput;
import org.jbpm.gd.common.editor.ContentProvider;
import org.jbpm.gd.common.editor.Editor;
import org.jbpm.gd.common.editor.GraphicalViewer;
@@ -11,13 +10,6 @@
public class PageFlowEditor extends Editor {
- public String getDefaultImageFileName() {
- String str = ((FileEditorInput)getEditorInput()).getName();
- int index = str.indexOf(".xml");
- str = index > -1 ? str.substring(0, index) : str;
- return str + ".jpg";
- }
-
protected ContentProvider createContentProvider() {
return new PageFlowContentProvider();
}
14 years, 8 months
JBoss Tools SVN: r17457 - trunk/as/tests/org.jboss.ide.eclipse.as.archives.integration.test/META-INF.
by jbosstools-commits＠lists.jboss.org
Author: dgolovin
Date: 2009-09-03 15:41:58 -0400 (Thu, 03 Sep 2009)
New Revision: 17457
Modified:
trunk/as/tests/org.jboss.ide.eclipse.as.archives.integration.test/META-INF/MANIFEST.MF
Log:
https://jira.jboss.org/jira/browse/JBIDE-4124 Add AS / Archives Integration test project to build
switched to junit 3 instead of junit4 to fix test execution error
Modified: trunk/as/tests/org.jboss.ide.eclipse.as.archives.integration.test/META-INF/MANIFEST.MF
===================================================================
--- trunk/as/tests/org.jboss.ide.eclipse.as.archives.integration.test/META-INF/MANIFEST.MF 2009-09-03 19:11:02 UTC (rev 17456)
+++ trunk/as/tests/org.jboss.ide.eclipse.as.archives.integration.test/META-INF/MANIFEST.MF 2009-09-03 19:41:58 UTC (rev 17457)
@@ -9,7 +9,6 @@
Bundle-Vendor: %Bundle-Vendor.0
Bundle-Localization: plugin
Require-Bundle: org.eclipse.core.runtime,
- org.junit4,
org.eclipse.core.resources;bundle-version="3.4.2",
org.eclipse.jdt;bundle-version="3.4.2",
org.eclipse.jdt.core;bundle-version="3.4.4",
@@ -20,6 +19,7 @@
org.jboss.ide.eclipse.archives.core;bundle-version="2.0.0",
org.jboss.ide.eclipse.archives.ui;bundle-version="1.0.0",
org.eclipse.jface;bundle-version="3.4.2",
- org.jboss.tools.tests;bundle-version="2.0.0"
+ org.jboss.tools.tests;bundle-version="2.0.0",
+ org.junit;bundle-version="3.8.2"
Bundle-RequiredExecutionEnvironment: J2SE-1.5
Export-Package: org.jboss.ide.eclipse.as.archives.integration.test
14 years, 8 months