You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ode.apache.org by va...@apache.org on 2012/12/31 18:06:09 UTC
svn commit: r1427180 - in /ode/site/trunk/content: bpelc-command.mdtext
index.mdtext sendsoap-command.mdtext war-deployment.mdtext
Author: vanto
Date: Mon Dec 31 17:06:09 2012
New Revision: 1427180
URL: http://svn.apache.org/viewvc?rev=1427180&view=rev
Log:
readded bpelc and sendsoap
Added:
ode/site/trunk/content/bpelc-command.mdtext
ode/site/trunk/content/sendsoap-command.mdtext
Modified:
ode/site/trunk/content/index.mdtext
ode/site/trunk/content/war-deployment.mdtext
Added: ode/site/trunk/content/bpelc-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/bpelc-command.mdtext?rev=1427180&view=auto
==============================================================================
--- ode/site/trunk/content/bpelc-command.mdtext (added)
+++ ode/site/trunk/content/bpelc-command.mdtext Mon Dec 31 17:06:09 2012
@@ -0,0 +1,57 @@
+Title: bpelc Command
+Category: documentation
+
+## Overview
+
+The `bpelc` commandline tool {excerpt}compiles [BPEL4WS 1.1](bpel4ws-11.html) or [WS-BPEL 2.0] processes for execution by the ODE runtime engine.{excerpt}
+
+<a name="bpelcCommand-Synopsis"></a>
+## Synopsis
+
+ :::text
+ bpelc [-q|-v|-vv] [-o directory] [-rr rrfile] [-wsdl uri] url ... url
+
+<a name="bpelcCommand-Description"></a>
+## Description
+
+The `bpelc` commandline tool compiles BPEL processes (either 1.1 or 2.0) for execution by the PXE runtime engine. The compiler will automatically detect the version of the process and configure itself appropriately. For comparison, the [`<bpelc>` Task](bpelc-task.html) performs the same operation, and the BPEL compiler can be used directly.
+
+For more information about the BPEL compiler, see [Compiler Toolchain].
+
+<a name="bpelcCommand-Options"></a>
+## Options
+
+<table class="table table-bordered table-striped">
+ <thead>
+ <tr>
+ <th>Option/Argument</th>
+ <th>Effect</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><code>-o directory</code></td><td>the directory to write the output files to.</td>
+ </tr>
+ <tr>
+ <td><code>-rr rrfile</code></td><td>the filename of the ZIP resource repository to read WSDL definitions from. If this parameter is not specified, the compiler will dereference URIs directly as URLs.</td>
+ </tr>
+ <tr>
+ <td><code>-wsdl uri</code></td><td>for BPEL4WS 1.1 processes, the URI of WSDL definitions to include from the ZIP resource repository. This hint is ignored for WS-BPEL 2.0 processes in favor of the <code><bpel:import></code> mechanism.</td>
+ </tr>
+ <tr>
+ <td><code>url ... url</code></td><td>the URLs of BPEL process definitions to be compiled.</td>
+ </tr>
+ <tr>
+ <td><code>-q|-v|-vv</code></td><td>adjust the verbosity of logging output.</td>
+ </tr>
+ <tr>
+ <td><code>-h</code></td><td>prints a synopsis to the console and exits.</td>
+ </tr>
+ </tbody>
+</table>
+
+<div class="alert alert-tip">
+ You have to use the full path for the bpel process file, like:
+ *./bpelc ./HelloWorld.bpel*, not -./bpelc HelloWorld.bpel-
+</div>
+
Modified: ode/site/trunk/content/index.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/index.mdtext?rev=1427180&r1=1427179&r2=1427180&view=diff
==============================================================================
--- ode/site/trunk/content/index.mdtext (original)
+++ ode/site/trunk/content/index.mdtext Mon Dec 31 17:06:09 2012
@@ -34,7 +34,7 @@ WS-BPEL (Business Process Execution Lang
<li><i class="icon-check"></i> Possibility to map process variables <a href="/extensions/external-variables.html">externally</a> to a database table of your choice.</li>
<li><i class="icon-check"></i> High level API to the engine that allows you to integrate the core with virtually any communication layer.</li>
<li><i class="icon-check"></i> Hot-deployment of your processes.</li>
- <li><i class="icon-check"></i> Compiled approach to BPEL that provides detailed analysis and validation at the ommand line or at deployment.</li>
+ <li><i class="icon-check"></i> Compiled approach to BPEL that provides detailed analysis and validation at the <a href="bpelc-command.html">command line</a> line or at deployment.</li>
<li><i class="icon-check"></i> <a href="management-api.html">Management interface</a> for processes, instances and messages.</li>
</ul>
</div>
Added: ode/site/trunk/content/sendsoap-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/sendsoap-command.mdtext?rev=1427180&view=auto
==============================================================================
--- ode/site/trunk/content/sendsoap-command.mdtext (added)
+++ ode/site/trunk/content/sendsoap-command.mdtext Mon Dec 31 17:06:09 2012
@@ -0,0 +1,47 @@
+Title: sendsoap Command
+Category: documentation
+
+## Overview
+
+The `sendsoap` command uses a lightweight HTTP client to send SOAP messages via POST.
+
+<a name="sendsoapCommand-Synopsis"></a>
+## Synopsis
+
+ :::text
+ sendsoap [-q|-v|-vv] [-o outfile] url -
+ sendsoap -h
+
+## Description
+
+The `sendsoap` command uses a lightweight HTTP client to send SOAP messages via POST using either a file or standard in as the source for the message. The command is useful for testing HTTP endpoints in ODE or external HTTP services that ODE will interact with, as `sendsoap` uses the same Axis2 client as the Axis2 Integration Layer.
+
+## Options
+
+<table class="table table-bordered table-striped">
+ <thead>
+ <th>Option/Argument</th>
+ <th>Effect</th>
+ </thead>
+ <tbody>
+ <tr>
+ <td><code>url</code></td><td>the HTTP URL to post the message to.</td>
+ </tr>
+ <tr>
+ <td><code>file</code></td><td>a file containing the message to post.</td>
+ </tr>
+ <tr>
+ <td><code>-</code></td><td>read the message data from standard in instead of a file.</td>
+ </tr>
+ <tr>
+ <td><code>-o file</code></td><td>sets a file to write the output to; otherwise, output is sent to the console.</td>
+ </tr>
+ <tr>
+ <td><code>-q|-v|-vv</code></td><td>adjust the verbosity of logging output.</td>
+ </tr>
+ <tr>
+ <td><code>-h</code></td><td>prints a synopsis to the console and exits.</td>
+ </tr>
+ </tbody>
+</table>
+
Modified: ode/site/trunk/content/war-deployment.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/war-deployment.mdtext?rev=1427180&r1=1427179&r2=1427180&view=diff
==============================================================================
--- ode/site/trunk/content/war-deployment.mdtext (original)
+++ ode/site/trunk/content/war-deployment.mdtext Mon Dec 31 17:06:09 2012
@@ -11,13 +11,13 @@ Get the WAR file in the distribution roo
<a name="WARDeployment-Examples"></a>
### Examples
-Copy the content of the _examples_ directory in the distribution (the 3 sub-directories) to _tomcat/webapps/ode/WEB-INF/processes_, this will automatically deploy the 3 example processes. Use the sendsoap command located in the distribution _bin_ directory to send test messages. The messages to run each of the 3 examples are provided in their respective directory (testRequest.soap). For each example type something like:
+Copy the content of the _examples_ directory in the distribution (the 3 sub-directories) to _tomcat/webapps/ode/WEB-INF/processes_, this will automatically deploy the 3 example processes. Use the [sendsoap command](sendsoap-command.html) located in the distribution _bin_ directory to send test messages. The messages to run each of the 3 examples are provided in their respective directory (testRequest.soap). For each example type something like:
:::text
$ bin/sendsoap http://localhost:8080/ode/processes/helloWorld examples/HelloWorld2/testRequest.soap
-The *sendsoap* executable can be found in the distribution _bin_ directory. The urls should be updated according to the address defined in the WSDL file for the process service.
+The [sendsoap](sendsoap-command.html) executable can be found in the distribution _bin_ directory. The urls should be updated according to the address defined in the WSDL file for the process service.
<a name="WARDeployment-ConfiguringODEinTomcatwithaMySQLdatabase"></a>
### Configuring ODE in Tomcat with a MySQL database