From jbosstools-commits at lists.jboss.org Wed Mar 3 06:18:52 2010 Content-Type: multipart/mixed; boundary="===============1442580220153906883==" MIME-Version: 1.0 From: jbosstools-commits at lists.jboss.org To: jbosstools-commits at lists.jboss.org Subject: [jbosstools-commits] JBoss Tools SVN: r20591 - in branches/jbosstools-3.1.x/bpel/docs/reference: en and 1 other directory. Date: Wed, 03 Mar 2010 06:18:52 -0500 Message-ID: <201003031118.o23BIqh7007081@svn01.web.mwc.hst.phx2.redhat.com> --===============1442580220153906883== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: ochikvina Date: 2010-03-03 06:18:52 -0500 (Wed, 03 Mar 2010) New Revision: 20591 Modified: branches/jbosstools-3.1.x/bpel/docs/reference/en/master.xml branches/jbosstools-3.1.x/bpel/docs/reference/en/master_output.xml branches/jbosstools-3.1.x/bpel/docs/reference/pom.xml Log:

https://jira.jboss.org/jira/browse/JBDS-1107 -Updated docs source files = here with the ones for JBDS 3.0.0 GA release.

Modified: branches/jbosstools-3.1.x/bpel/docs/reference/en/master.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- branches/jbosstools-3.1.x/bpel/docs/reference/en/master.xml 2010-03-03 = 11:14:36 UTC (rev 20590) +++ branches/jbosstools-3.1.x/bpel/docs/reference/en/master.xml 2010-03-03 = 11:18:52 UTC (rev 20591) @@ -28,12 +28,12 @@ DennyXud= xu(a)redhat.com GridQian= fqian(a)redhat.com = - 2009 + 2009 2010 JBoss by Red Hat - Version: 1.0.0.CR1 + Version: 1.0.0.trunk Modified: branches/jbosstools-3.1.x/bpel/docs/reference/en/master_output.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- branches/jbosstools-3.1.x/bpel/docs/reference/en/master_output.xml 2010= -03-03 11:14:36 UTC (rev 20590) +++ branches/jbosstools-3.1.x/bpel/docs/reference/en/master_output.xml 2010= -03-03 11:18:52 UTC (rev 20591) @@ -8,503 +8,507 @@ <!ENTITY deploy SYSTEM "modules/deploy.xml"> = = -]><book xmlns:diffmk=3D"http://diffmk.sf.net/ns/diff"> - = - <bookinfo> - <title>JBoss BPEL User Guide - = - - - - - = - - - = - = - - DennyXud= xu(a)redhat.com - GridQian= fqian(a)redhat.com = - August 2009 - - 2009 - JBoss by Red Hat - - - Version: 1.0.0.CR1 - - - - - PDF version - - - - - - = - = - = - - JBoss BPEL project Overview - - JBoss BPEL project is a WS-BPEL 2.0 project that gives a way to c= reate, edit, validate and deploy BPEL files to JBoss BPEL runtime. It is ba= sed on Eclipse = - BPEL - project . - = - It improves the Eclipse BPEL project in the following way: - - Implements close integration with JBoss BPEL runti= me. Adds a new project type for the deployment to JBoss BPEL runtime. - Supports two ways of deployment: one way is to dep= loy a bpel project directly to JBoss BPEL runtime. The other way is to depl= oy bpel files in JBoss ESB project to JBoss BPEL runtime. - Improves the BPEL validator and increases Eclipse = BPEL editor's quality. - - = - - WS-BPEL 2.0 = - stands for Web Service Business Process Execution Language. Like EAI, B= PEL 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 co= mplex calculations and = - asset reallocation. - - -
- Key Features of JBoss BPEL project - Let's start with looking through the table of the main features = of JBoss BPEL editor project: - = - - = - Key Functionality for JBoss BPEL editor project - = - - - - - Feature - Benefit - = - - = - = - - WS-BPEL 2.0 support - JBoss BPEL project supports the newest WS= -BPEL 2.0 specifications. = - = - - Close integration with JBoss BPEL runtime= - There are two ways to deploy BPEL files t= o 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. = - = - - BPEL file editor - The user can use the editor separately to= edit a BPEL file. = - = - - BPEL file validator - The validator can give the error messages= about BPEL files to the user. = - = - = - -
- = -
- -
- = - - Installation JBoss BPEL Tools -
- Installation JBoss BPEL editor - At first, you need Eclipse 3.5. You can get it from Eclipse Web Site. = - - The JBoss BPEL editor is included into JBoss Tools. = - You have some methods to install JBoss Tools. = - See Installing JBoss Tools for more information. - If you want to install only the JBoss BPEL editor, you can = install it from JBo= ss Tools page separately. - Please, note, that only JBoss Tools 3.1 or higher version incl= udes JBoss BPEL editor. - -
-
- Installation JBoss BPEL Runtime - 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 JBoss RiftSaw page . - -
-
- = - - Creating and editing a BPEL project - In the chapter we describe the necessary steps to create a new B= PEL project and edit the BPEL files. - First of all, you should create a BPEL project. - -
- Creating a BPEL project - Create the project by selecting = - New > Project... >= BPEL 2.0 > BPEL Project from the menu bar. - Then click the Next but= ton. = - -
- New BPEL Project - - - - - -
- On this page of the New BPEL Pro= ject Wizard enter a project name in the Project Name - field,e.g enter HelloWorld. - = -
- New BPEL Project Wizard - - - - - -
- Click the Finish butt= on. So you have created the BPEL project named = HelloWorld. Its structure is like this: -
- The BPEL Project structure - - - - - -
-
-
- Creating a BPEL process - Now you should create a BPEL process. You can create it by s= electing = - New > Others... >= ; BPEL 2.0 > New BPEL Process File. - -
- New BPEL Process File - - - - - -
- Click the Next button= . Enter the following information: - - = - Fields and values - = - - - - - Field - Value - = - - = - = - - BPEL Process Name - enter a process name. For example, HelloWorld. = - = - - Namespace - enter or select a namespace for the B= PEL process. = - = - - Template - select a template for the BPEL proces= s. When you select the template, you will see the information about the tem= plate below on the page. = - = - = - = - -
- -
- New BPEL Process File Wizard - - - - - -
- Click the Next button= . On the second page make sure that the folder = HelloWorld/bpelContent is selected. - Click Finish. - - - All of your files that are used in your BPEL project mus= t be under the bpelContent folder. Only in this case = - these files can be deployed to JBoss server. - - - - Up to now, you have got a simple BPEL process as on the scree= n below. -
- A simple BPEL Process File - - - - - -
- The next step, you can do is to edit the BPEL process file a= nd then deploy it to JBoss server. -
-
- Editing a BPEL process file - If the Properties view= and Palette vi= ew are not opened, you can open the views by right-cl= icking the BPEL editor and selecting = - Show in Properties, <= property moreinfo=3D"none">Show Palette in Palette view. Then yo= u should have the view like this: = - -
- The BPEL editor view - - - - - -
= - In the Palette view, you can drag a BPEL element to the BPEL editor and dro= p it in the place you want. = - In the Properties view= , 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: = - - - = - Tabs of the Property view - = - - - - - Tab - Description - = - - = - = - - Description - Shows the descriptive information abo= ut the element,e.g. Name of the elem= ent. = - = - - Details - Shows the detailed and important info= rmation about the element. - It is the most important section of an element. - Most of the properties of an element are set i= n this section. = - = - - Join Behavior - Shows the Join Failure property of the element. = - = - - Documentation - Shows the documentation sub-element of an element. = - = - - Other - Every BPEL element has its own sectio= ns: Correlation section, Message Exchange section, and so on. We will - introduce them while using them. = - = - = - -
- In order to see how a simple BPEL process works in action, y= ou should do some steps as below: = - - - Add an Assign= element between the receiveInput el= ement and replyOutput element. - - - Click the Assign element in the BPEL editor in order to get the properties information o= f it in the Properties view. = - - - - In the Details section of Properties view, you should click the New button to add a copy sub-element to the element. = - Assign "input->payload->input" to "output->pa= yload->result". At this time, an "initialize= r" popup dialog appears. Click on the Yes button in the dialog. - -
- Add <property moreinfo=3D"none">Assign</propert= y> to the process - - - - - -
= -
= - - Open the file "HelloWorl= dArtifacts.wsdl" in the "HelloWorld<= /property>" project by double-clicking the file. Right-click the WSDL edito= r and select = - Add Service. A = new service should appear in the editor. Name it HelloWorldProcessService. It has the Port = - named NewPort. = Select it, right-click on it and rename it to H= elloWorldProcessPort in the Properties = - view. - -
- Add <property moreinfo=3D"none">Service</proper= ty> to the WSDL file - - - - - -
= -
- - Right-click somewhere in the whitespace of the WSDL = editor and select = - Add Binding. A = new Binding component will appear in the editor. Name it HelloWorldSOAPBinding. Select it, in the = - General tab of the Properties view and select HelloWorld as a port type in the PortType. Then click on the = - Generate Binding Content..= . button to open the Binding Wizard= . In the wizard, select SOAP = - as the Protocol= . Finally, click the Finish button = to close the wizard. - -
- Add a <property moreinfo=3D"none">Binding</prop= erty> to the WSDL file - - - - - -
= -
- - Click the HelloWorldProc= essPort property in the General section of the Properties view, = select HelloWorldSOAPBinding in - the Binding com= bobox. In the Address field input http://lo= calhost:8080/bpel/processes/HelloWorld?wsdl. - -
- Add the <property moreinfo=3D"none">HelloWorldS= OAPBinding</property> to the <property moreinfo=3D"none">HelloWorldProcessP= ort</property> - - - - - -
= -
= -
- Now you have finished creating a simple BPEL process.As a ne= xt step, you can deploy the BPEL project to JBoss BPEL Runtime. = = - = -
= -
- - = - - Deploy a JBoss BPEL project to JBoss BPEL Runtime -
- Creating a bpel-deploy.xml file - 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: - - - - Create the bpel-deploy.xml by selecting = - New > Other..= . > BPEL 2.0 > Apache ODE Deployment Descriptor= . Click the Next button. = - -
- New BPEL Deploy file - - - - - -
= -
- - On the next wizard page you should enter the followi= ng information: - BPEL Project: Click the Browse... button to select the BPEL project in your workspace which you want t= o deploy to the runtime. - Please note, that you should select the bpelContent folder in your new BPEL project as a value of BPEL Project field because the bpel-deploy.x= ml should be created in this place. - - File name: The default value is bpel-deploy.xml. Please, don't chan= ge it. - Click on Finish button to close the wizard and a new bpel-deploy.xml file will be create= d. -
- New BPEL Deploy file Wizard - - - - - -
= -
- - Double-click the bpel-deploy.xml file to open it in = ODE Descriptor Deployment Editor. - In the Inbound Interfaces<= /property> section, click the = - Associated Port= column and select HelloWorldProcessPort - in the dropdown box.The R= elated Service and Binding Used = - columns should be automatically filled in. Save the <= emphasis>bpel-deploy.xml. - -
- bpel-deploy.xml file editor - - - - - -
= -
= -
-
-
- Creating JBoss BPEL Server - Suppose you have installed the J= Boss BPEL Runtime-RiftSaw, now you can create a server for JBoss= BPEL runtime. - - - Open the JBoss Server vi= ew by selecting = - Windows > Sho= w View > Other... > Server > JBoss Server view. - = - - - Right-click the JBoss Server view and select = - New > Server<= /property> to open the New Server Wizard: = - -
- New Server Wizard - - - - - -
= -
- - Select JBoss AS 5.1 as a server type. - - Please note, that only JBoss As 5.1 or higher ve= rsion supports BPEL. - - - - = - Click the Next button. On the next page, you should input your JBoss As location. Then click the Next button and - you will get the page like this: = - -
- Add resource to the server - - - - - -
= -
- - Select HelloWorld, then click the Add button to = add the project to the server. - Then click on the Finish button. - - Start the server by right-clicking on the server and= selecting the Start item. = - = -
- The started server - - - - - -
= - If some aspects of server creation is not clear, ple= ase, read JBoss Server Manager Reference Guide = for more details. -
- - You can enter the link http://localhost:8080/bpel/processes.html to the browser to get the deployed processes. = -
- The BPEL console - - - - - -
= -
= -
= - If there's anything we didn't cover or you can't figure out,= please feel free to visit our JBoss Tools Users Forum to ask questions. - There we are also waiting for your suggestions and comments. = -
-
- +]> + = + + JBoss BPEL User Guide + = + + + + + = + + + = + = + + DennyXud= xu(a)redhat.com + GridQian= fqian(a)redhat.com = + + 2009 + 2010 + JBoss by Red Hat + + + Version: 1.0.0.trunk + + + + + PDF version + + + + + + = + = + = + + JBoss BPEL project Overview + + JBoss BPEL project is a WS-BPEL 2.0 project that gives a way to c= reate, edit, validate and deploy BPEL files to JBoss BPEL runtime. It is ba= sed on Eclipse = + BPEL + project . + = + It improves the Eclipse BPEL project in the following way: + + Implements close integration with JBoss BPEL runti= me. Adds a new project type for the deployment to JBoss BPEL runtime. + Supports two ways of deployment: one way is to dep= loy a bpel project directly to JBoss BPEL runtime. The other way is to depl= oy bpel files in JBoss ESB project to JBoss BPEL runtime. + Improves the BPEL validator and increases Eclipse = BPEL editor's quality. + + = + + WS-BPEL 2.0 = + stands for Web Service Business Process Execution Language. Like EAI, B= PEL 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 co= mplex calculations and = + asset reallocation. + + +
+ Key Features of JBoss BPEL project + Let's start with looking through the table of the main features = of JBoss BPEL editor project: + = + + = + Key Functionality for JBoss BPEL editor project + = + + + + + Feature + Benefit + = + + = + = + + WS-BPEL 2.0 support + JBoss BPEL project supports the newest WS= -BPEL 2.0 specifications. = + = + + Close integration with JBoss BPEL runtime= + There are two ways to deploy BPEL files t= o 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. = + = + + BPEL file editor + The user can use the editor separately to= edit a BPEL file. = + = + + BPEL file validator + The validator can give the error messages= about BPEL files to the user. = + = + = + +
+ = +
+ +
+ = + + Installation JBoss BPEL Tools +
+ Installation JBoss BPEL editor + At first, you need Eclipse 3.5. You can get it from Eclipse Web Site. = + + The JBoss BPEL editor is included into JBoss Tools. = + You have some methods to install JBoss Tools. = + See Installing JBoss Tools for more information. + If you want to install only the JBoss BPEL editor, you can = install it from JBo= ss Tools page separately. + Please, note, that only JBoss Tools 3.1 or higher version incl= udes JBoss BPEL editor. + +
+
+ Installation JBoss BPEL Runtime + 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 JBoss RiftSaw page . + +
+
+ = + + Creating and editing a BPEL project + In the chapter we describe the necessary steps to create a new B= PEL project and edit the BPEL files. + First of all, you should create a BPEL project. + +
+ Creating a BPEL project + Create the project by selecting = + New > Project... >= BPEL 2.0 > BPEL Project from the menu bar. + Then click the Next but= ton. = + +
+ New BPEL Project + + + + + +
+ On this page of the New BPEL Pro= ject Wizard enter a project name in the Project Name + field,e.g enter HelloWorld. + = +
+ New BPEL Project Wizard + + + + + +
+ Click the Finish butt= on. So you have created the BPEL project named = HelloWorld. Its structure is like this: +
+ The BPEL Project structure + + + + + +
+
+
+ Creating a BPEL process + Now you should create a BPEL process. You can create it by s= electing = + New > Others... >= ; BPEL 2.0 > New BPEL Process File. + +
+ New BPEL Process File + + + + + +
+ Click the Next button= . Enter the following information: + + = + Fields and values + = + + + + + Field + Value + = + + = + = + + BPEL Process Name + enter a process name. For example, HelloWorld. = + = + + Namespace + enter or select a namespace for the B= PEL process. = + = + + Template + select a template for the BPEL proces= s. When you select the template, you will see the information about the tem= plate below on the page. = + = + = + = + +
+ +
+ New BPEL Process File Wizard + + + + + +
+ Click the Next button= . On the second page make sure that the folder = HelloWorld/bpelContent is selected. + Click Finish. + + + All of your files that are used in your BPEL project mus= t be under the bpelContent folder. O= nly in this case = + these files can be deployed to JBoss server. + + + + Up to now, you have got a simple BPEL process as on the scree= n below. +
+ A simple BPEL Process File + + + + + +
+ The next step, you can do is to edit the BPEL process file a= nd then deploy it to JBoss server. +
+
+ Editing a BPEL process file + If the Properties view= and Palette vi= ew are not opened, you can open the views by right-cl= icking the BPEL editor and selecting = + Show in Properties, <= property moreinfo=3D"none">Show Palette in Palette view. Then yo= u should have the view like this: = + +
+ The BPEL editor view + + + + + +
= + In the Palette view, you can drag a BPEL element to the BPEL editor and dro= p it in the place you want. = + In the Properties view= , 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: = + + + = + Tabs of the Property view + = + + + + + Tab + Description + = + + = + = + + Description + Shows the descriptive information abo= ut the element,e.g. Name of the elem= ent. = + = + + Details + Shows the detailed and important info= rmation about the element. + It is the most important section of an element. + Most of the properties of an element are set i= n this section. = + = + + Join Behavior + Shows the Join Failure property of the element. = + = + + Documentation + Shows the documentation sub-element of an element. = + = + + Other + Every BPEL element has its own sectio= ns: Correlation section, Message Exchange section, and so on. We will + introduce them while using them. = + = + = + +
+ In order to see how a simple BPEL process works in action, y= ou should do some steps as below: = + + + Add an Assign= element between the receiveInput el= ement and replyOutput element. + + + Click the Assign element in the BPEL editor in order to get the properties information o= f it in the Properties view. = + + + + In the Details section of Properties view, you should click the New button to add a copy sub-element to the element. = + Assign "input->payload->input" to "output->pa= yload->result". At this time, an "initialize= r" popup dialog appears. Click on the Yes button in the dialog. + +
+ Add <property moreinfo=3D"none">Assign</propert= y> to the process + + + + + +
= +
= + + Open the file "HelloWorl= dArtifacts.wsdl" in the "HelloWorld<= /property>" project by double-clicking the file. Right-click the WSDL edito= r and select = + Add Service. A = new service should appear in the editor. Name it HelloWorldProcessService. It has the Port = + named NewPort. = Select it, right-click on it and rename it to H= elloWorldProcessPort in the Properties = + view. + +
+ Add <property moreinfo=3D"none">Service</proper= ty> to the WSDL file + + + + + +
= +
+ + Right-click somewhere in the whitespace of the WSDL = editor and select = + Add Binding. A = new Binding component will appear in the editor. Name it HelloWorldSOAPBinding. Select it, in the = + General tab of the Properties view and select HelloWorld as a port type in the PortType. Then click on the = + Generate Binding Content..= . button to open the Binding Wizard= . In the wizard, select SOAP = + as the Protocol= . Finally, click the Finish button = to close the wizard. + +
+ Add a <property moreinfo=3D"none">Binding</prop= erty> to the WSDL file + + + + + +
= +
+ + Click the HelloWorldProc= essPort property in the General section of the Properties view, = select HelloWorldSOAPBinding in + the Binding com= bobox. In the Address field input http://lo= calhost:8080/bpel/processes/HelloWorld?wsdl. + +
+ Add the <property moreinfo=3D"none">HelloWorldS= OAPBinding</property> to the <property moreinfo=3D"none">HelloWorldProcessP= ort</property> + + + + + +
= +
= +
+ Now you have finished creating a simple BPEL process.As a ne= xt step, you can deploy the BPEL project to JBoss BPEL Runtime. = = + = +
= +
+ + = + + Deploy a JBoss BPEL project to JBoss BPEL Runtime +
+ Creating a bpel-deploy.xml file + 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: + + + + Create the bpel-deploy.xml by selecting = + New > Other..= . > BPEL 2.0 > Apache ODE Deployment Descriptor= . Click the Next button. = + +
+ New BPEL Deploy file + + + + + +
= +
+ + On the next wizard page you should enter the followi= ng information: + BPEL Project: Click the Browse... button to select the BPEL project in your workspace which you want t= o deploy to the runtime. + Please note, that you should select the bpelContent folder in your new BPEL project as a v= alue of BPEL Project field because t= he bpel-deploy.xml should be created in this place. + + File name: The default value is bpel-deploy.xml. Please, don't chan= ge it. + Click on Finish button to close the wizard and a new bpel-deploy.xml file will be create= d. +
+ New BPEL Deploy file Wizard + + + + + +
= +
+ + Double-click the bpel-deploy.xml file to open it in = ODE Descriptor Deployment Editor. + In the Inbound Interfaces<= /property> section, click the = + Associated Port= column and select HelloWorldProcessPort + in the dropdown box.The R= elated Service and Binding Used = + columns should be automatically filled in. Save the <= emphasis>bpel-deploy.xml. + +
+ bpel-deploy.xml file editor + + + + + +
= +
= +
+
+
+ Creating JBoss BPEL Server + Suppose you have installed the J= Boss BPEL Runtime-RiftSaw, now you can create a server for JBoss= BPEL runtime. + + + Open the JBoss Server vi= ew by selecting = + Windows > Sho= w View > Other... > Server > JBoss Server view. + = + + + Right-click the JBoss Server view and select = + New > Server<= /property> to open the New Server Wizard: = + +
+ New Server Wizard + + + + + +
= +
+ + Select JBoss AS 5.1 as a server type. + + Please note, that only JBoss As 5.1 or higher ve= rsion supports BPEL. + + + + = + Click the Next button. On the next page, you should input your JBoss As location. Then click the Next button and + you will get the page like this: = + +
+ Add resource to the server + + + + + +
= +
+ + Select HelloWorld, then click the Add button to = add the project to the server. + Then click on the Finish button. + + Start the server by right-clicking on the server and= selecting the Start item. = + = +
+ The started server + + + + + +
= + If some aspects of server creation is not clear, ple= ase, read JBoss Server Manager Reference Guide = for more details. +
+ + You can enter the link http://localhost:8080/bpel/processes.html to the browser to get the deployed processes. = +
+ The BPEL console + + + + + +
= +
= +
= + If there's anything we didn't cover or you can't figure out, + please feel free to visit our = + JBoss Tools Users Forum to ask questions. + There we are also waiting for your suggestions and comments. = +
+
+
Modified: branches/jbosstools-3.1.x/bpel/docs/reference/pom.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- branches/jbosstools-3.1.x/bpel/docs/reference/pom.xml 2010-03-03 11:14:= 36 UTC (rev 20590) +++ branches/jbosstools-3.1.x/bpel/docs/reference/pom.xml 2010-03-03 11:18:= 52 UTC (rev 20591) @@ -22,7 +22,7 @@ releaseJBDS - master_output.xml + master.xml classpath:/xslt/com/jboss/tools/xhtml-single-release-nomar= ker.xsl classpath:/xslt/com/jboss/tools/xhtml-release-nomarker.xs= l classpath:/xslt/com/jboss/tools/pdf.xsl --===============1442580220153906883==--