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/28 12:29:07 UTC
svn commit: r1426460 - /ode/site/trunk/content/
Author: vanto
Date: Fri Dec 28 11:29:06 2012
New Revision: 1426460
URL: http://svn.apache.org/viewvc?rev=1426460&view=rev
Log:
inline code formatting.
Modified:
ode/site/trunk/content/assign.mdtext
ode/site/trunk/content/bpelc-task.mdtext
ode/site/trunk/content/ddvalidate-command.mdtext
ode/site/trunk/content/faq.mdtext
ode/site/trunk/content/process-contexts.mdtext
ode/site/trunk/content/pxe-activate-command.mdtext
ode/site/trunk/content/pxe-deactivate-command.mdtext
ode/site/trunk/content/pxe-deploy-command.mdtext
ode/site/trunk/content/pxe-status-command.mdtext
ode/site/trunk/content/pxe-undeploy-command.mdtext
ode/site/trunk/content/receive.mdtext
ode/site/trunk/content/rradd-command.mdtext
ode/site/trunk/content/rralias-command.mdtext
ode/site/trunk/content/rrdrop-command.mdtext
ode/site/trunk/content/rrget-command.mdtext
ode/site/trunk/content/sarcreate-command.mdtext
ode/site/trunk/content/sarls-command.mdtext
ode/site/trunk/content/sendsoap-command.mdtext
ode/site/trunk/content/urlalias-command.mdtext
ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext
Modified: ode/site/trunk/content/assign.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/assign.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/assign.mdtext (original)
+++ ode/site/trunk/content/assign.mdtext Fri Dec 28 11:29:06 2012
@@ -21,40 +21,40 @@ Title: assign
</assign>
- *throws* {{[bpel:invalidVariables](#invalidVariables)}}, {{[bpel:selectionFailure](#selectionFailure)}}, {{[bpel:subLanguageExecutionFault](#subLanguageExecutionFault)}}, {{[bpel:uninitializedVariable](#uninitializedVariable)}}, {{[bpel:mismatchedAssignmentFailure](#mismatchedAssignmentFailure)}}, {{[bpel:uninitializedPartnerRole](#uninitializedPartnerRole)}}
+ *throws* `[bpel:invalidVariables](#invalidVariables)`, `[bpel:selectionFailure](#selectionFailure)`, `[bpel:subLanguageExecutionFault](#subLanguageExecutionFault)`, `[bpel:uninitializedVariable](#uninitializedVariable)`, `[bpel:mismatchedAssignmentFailure](#mismatchedAssignmentFailure)`, `[bpel:uninitializedPartnerRole](#uninitializedPartnerRole)`
h3. Description
- The {{<assign>}} activity can be used to copy data from one variable to another, as well as to construct and insert new data using expressions. The {{<assign>}} activity can also be used to copy endpoint references to and from partnerLinks.
+ The `<assign>` activity can be used to copy data from one variable to another, as well as to construct and insert new data using expressions. The `<assign>` activity can also be used to copy endpoint references to and from partnerLinks.
- Each {{<assign>}} is made up of any number of {{<copy>}} entries which are each made up of a "to-spec" (lvalue), and a from-spec (rvalue).
+ Each `<assign>` is made up of any number of `<copy>` entries which are each made up of a "to-spec" (lvalue), and a from-spec (rvalue).
- - {{ignoreMissingFromData}} - (optional) Should the {{[bpel:selectionFailure](#selectionFailure)}} standard fault be suppressed?
- ** {{yes}} - suppress standard faults
- ** {{no}} - (default) do not suppress standard faults
+ - `ignoreMissingFromData` - (optional) Should the `[bpel:selectionFailure](#selectionFailure)` standard fault be suppressed?
+ ** `yes` - suppress standard faults
+ ** `no` - (default) do not suppress standard faults
{note}
- The {{ignoreMissingFromData}} element has been implemented in ODE 1.3+ (i.e., it is coming soon). See [ODE-141](http://issues.apache.org/jira/browse/ODE-141) for issue tracking.
+ The `ignoreMissingFromData` element has been implemented in ODE 1.3+ (i.e., it is coming soon). See [ODE-141](http://issues.apache.org/jira/browse/ODE-141) for issue tracking.
{note}
- - {{validate}} - (optional) validate modified variables?
- ** {{yes}} - the {{<assign>}} activity validates all the variables being modified by the activity. If the validation fails the {{[bpel:invalidVariables#invalidVariables]}} fault is thrown.
- ** {{no}} - (default) do not validate the modified variables
+ - `validate` - (optional) validate modified variables?
+ ** `yes` - the `<assign>` activity validates all the variables being modified by the activity. If the validation fails the `[bpel:invalidVariables#invalidVariables]` fault is thrown.
+ ** `no` - (default) do not validate the modified variables
{note}
ODE currently disregards the value of this attribute --- validation is never performed.
{note}
- - {{<copy>}} - defines a lvalue, rvalue pair.
- -- {{keepSrcElementName}} - (optional) should the element name of the destination (as selected by the to-spec) be replaced by the elementname of the source (as selected by the from-spec)?
- *** {{yes}} - element names are replaced
- *** {{no}} - (default) element names are not replaced
- -- {{<from>}} - specifies the rvalue (see [here](#variants))
- -- {{<to>}} - specifies the lvalue (see [here](#variants))
+ - `<copy>` - defines a lvalue, rvalue pair.
+ -- `keepSrcElementName` - (optional) should the element name of the destination (as selected by the to-spec) be replaced by the elementname of the source (as selected by the from-spec)?
+ *** `yes` - element names are replaced
+ *** `no` - (default) element names are not replaced
+ -- `<from>` - specifies the rvalue (see [here](#variants))
+ -- `<to>` - specifies the lvalue (see [here](#variants))
- - {{<extensionAssignOperation>}} - a container for assignment extensions. If the element contained within the extensionAssignOperation elements not recognized by ODE and is not subject to a mustUnderstand="yes" requirement from an extension declaration then the element will be ignored.
+ - `<extensionAssignOperation>` - a container for assignment extensions. If the element contained within the extensionAssignOperation elements not recognized by ODE and is not subject to a mustUnderstand="yes" requirement from an extension declaration then the element will be ignored.
{note}
- Since version 2.0 ODE fully supports {{extensionAssingOperation}} functionality.
+ Since version 2.0 ODE fully supports `extensionAssingOperation` functionality.
{note}
{anchor:variants}
@@ -89,7 +89,7 @@ Title: assign
<div class="alert alert-note">
- The {{<from extension="QName" />}} from-spec variant is not part of the WS-BPEL 2.0 specification. It is a non-standard ODE extension.
+ The `<from extension="QName" />` from-spec variant is not part of the WS-BPEL 2.0 specification. It is a non-standard ODE extension.
</div>
The to-spec must be one of the following variants:
@@ -116,7 +116,7 @@ The to-spec must be one of the following
<to variable="BPELVariableName" extension="QName" /> <!-- ODE SPECIFIC -->
<div class="alert alert-note">
- The {{<to extension="QName" />}} to-spec variant is not part of the WS-BPEL 2.0 specification. It is a non-standard ODE extension.
+ The `<to extension="QName" />` to-spec variant is not part of the WS-BPEL 2.0 specification. It is a non-standard ODE extension.
</div>
A to-spec must return an lvalue. If a to-spec does not return an lvalue then a `bpel:[selectionFailure](selectionfailure.html)` will be thrown. In the context of XPath, an lvalue is a node-list containing a single node from a variable or a partnerLink identified by the to-spec (e.g. the XPath expression `concat("foo""bar")` is not an lvalue).
@@ -126,7 +126,7 @@ A to-spec must return an lvalue. If a to
Assignment is an atomic operation; that is, either all `<copy>` s succeed, or no changes are made.
<div class="alert alert-warning">
- In ODE, each {{<copy>}} is atomic.
+ In ODE, each `<copy>` is atomic.
</div>
<a name="assign-VariableVariant"></a>
Modified: ode/site/trunk/content/bpelc-task.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/bpelc-task.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/bpelc-task.mdtext (original)
+++ ode/site/trunk/content/bpelc-task.mdtext Fri Dec 28 11:29:06 2012
@@ -20,20 +20,20 @@ The `<bpelc>` task is used to compile on
<div class="alert alert-tip"><h4 class="alert-heading">Naming Convention</h4>
h2. Attributes and Subelements
- h3. {{<bpelc>}} Attributes
+ h3. `<bpelc>` Attributes
||Attribute||Purpose||
- |{{rr}}|the path to the [resource repository] from which to read WSDL definitions and any other imported artifacts. If not supplied, the task will construct a temporary resource repository by dereferencing URIs directly as URLs.|
- |{{targetDir}}|the directory into which the compiled files will be written. The default, if no other value is specified, is the current working directory.|
+ |`rr`|the path to the [resource repository] from which to read WSDL definitions and any other imported artifacts. If not supplied, the task will construct a temporary resource repository by dereferencing URIs directly as URLs.|
+ |`targetDir`|the directory into which the compiled files will be written. The default, if no other value is specified, is the current working directory.|
- h3. Nested {{<wsdl>}} Element and Attributes
- A nested {{<wsdl>}} element defines a WSDL import for use by the compiler in compiling a [BPEL4WS 1.1] process. This hint is ignored for a [WS-BPEL 2.0] process in favor of the {{<import.../>}} construct.
+ h3. Nested `<wsdl>` Element and Attributes
+ A nested `<wsdl>` element defines a WSDL import for use by the compiler in compiling a [BPEL4WS 1.1] process. This hint is ignored for a [WS-BPEL 2.0] process in favor of the `<import.../>` construct.
||Attribute||Purpose||
- |{{uri}}|a URI (within the resource repository) that can be dereferenced to obtain the WSDL definitions.|
+ |`uri`|a URI (within the resource repository) that can be dereferenced to obtain the WSDL definitions.|
- h3. Nested {{<bpel>}} Element and Attributes
- A nested {{<bpel>}} element defines a [BPEL4WS 1.1] or [WS-BPEL 2.0] process definition to be compiled. At least one {{<bpel>}} element must be supplied.
+ h3. Nested `<bpel>` Element and Attributes
+ A nested `<bpel>` element defines a [BPEL4WS 1.1] or [WS-BPEL 2.0] process definition to be compiled. At least one `<bpel>` element must be supplied.
||Attribute||Purpose||
- |{{url}}|the URL from which to load the process definition.|
+ |`url`|the URL from which to load the process definition.|
Modified: ode/site/trunk/content/ddvalidate-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/ddvalidate-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/ddvalidate-command.mdtext (original)
+++ ode/site/trunk/content/ddvalidate-command.mdtext Fri Dec 28 11:29:06 2012
@@ -10,13 +10,13 @@ The `ddvalidate` command {excerpt}valida
ddvalidate -h{noformat}
h2. Description
- The {{ddvalidate}} command validates a [system deployment descriptor] contained in a local file.
+ The `ddvalidate` command validates a [system deployment descriptor] contained in a local file.
- {tip}The [{{sarcreate}}|sarcreate Command] command and [{{<pxe-sar>}}|pxe-sar Task] task also validate the [system deployment descriptor] when assembling an [system deployment archive], but {{ddvalidate}} is included so that the validation can be performed in a standalone fashion.{tip}
+ {tip}The [`sarcreate`|sarcreate Command] command and [`<pxe-sar>`|pxe-sar Task] task also validate the [system deployment descriptor] when assembling an [system deployment archive], but `ddvalidate` is included so that the validation can be performed in a standalone fashion.{tip}
h2. Options
||Option/Argument||Effect||
- |{{ddfile}}|the filename of the [system deployment descriptor].|
- |{{rrfile}}|the filename of a [resource repository] containing the root WSDL definitions for the system. If this argument is not supplied, the command only performs schema-level validation of the descriptor. If this argument is supplied, the command performs additional validations, e.g., that WSDL port types referenced in the descriptor are properly declared.|
- |{{-q\|-v\|-vv}}|adjust the verbosity of logging output. See [Logging and Output from Commandline Tools].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`ddfile`|the filename of the [system deployment descriptor].|
+ |`rrfile`|the filename of a [resource repository] containing the root WSDL definitions for the system. If this argument is not supplied, the command only performs schema-level validation of the descriptor. If this argument is supplied, the command performs additional validations, e.g., that WSDL port types referenced in the descriptor are properly declared.|
+ |`-q\|-v\|-vv`|adjust the verbosity of logging output. See [Logging and Output from Commandline Tools].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/faq.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/faq.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/faq.mdtext (original)
+++ ode/site/trunk/content/faq.mdtext Fri Dec 28 11:29:06 2012
@@ -117,7 +117,7 @@ __A.__ ODE uses a number of liberally-li
This section covers frequently asked questions about how ODE related to various web services specifications and initiatives.
__Q.__ _Does ODE supply a SOAP stack?_
-__A.__ Not directly. ODE relies on the [Integration Layer|Architectural Overview#ODEIntegrationLayers] to supply the "physical" communication mechanisms. The [AXIS2 Integration Layer|Architectural Overview#ODEIntegrationLayers] that is part of the ODE distribution uses the AXIS2 SOAP stack. The [JBI Integration Layer|Architectural Overview#ODEIntegrationLayers] relies on external HTTP/SOAP components (e.g. ServiceMix's {{servicemix-http}} component).
+__A.__ Not directly. ODE relies on the [Integration Layer|Architectural Overview#ODEIntegrationLayers] to supply the "physical" communication mechanisms. The [AXIS2 Integration Layer|Architectural Overview#ODEIntegrationLayers] that is part of the ODE distribution uses the AXIS2 SOAP stack. The [JBI Integration Layer|Architectural Overview#ODEIntegrationLayers] relies on external HTTP/SOAP components (e.g. ServiceMix's `servicemix-http` component).
__Q.__ _Can ODE be integrated with third-party web services products such as Apache AXIS, Systinet WASP, or JAXRPC?_
__A.__ Yes, ODE can be integrated into most any stack via the [Integration API](http://incubator.apache.org/ode/javadoc/bpel-api/index.html)
Modified: ode/site/trunk/content/process-contexts.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/process-contexts.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/process-contexts.mdtext (original)
+++ ode/site/trunk/content/process-contexts.mdtext Fri Dec 28 11:29:06 2012
@@ -222,9 +222,9 @@ Context data should be accessible within
<div class="alert alert-info">
- - {{context="*"}} in {{from}}\-specs selects all contexts.
- - {{context="*"}} in {{to}}\-specs replaces existing contexts with context data selected by the {{from}}\-spec.
- - {{context="+"}} in {{to}}\-specs merges existing contexts with context data selected by the {{from}}\-spec.
+ - `context="*"` in `from`\-specs selects all contexts.
+ - `context="*"` in `to`\-specs replaces existing contexts with context data selected by the `from`\-spec.
+ - `context="+"` in `to`\-specs merges existing contexts with context data selected by the `from`\-spec.
</div>
When assigning context data to variables, the variable should be declared to be an instance of the context XSD (see [Contexts section](#contexts.html)). It is also possible to copy only fragments of a context data set by applying an XPath query to the `from`\-spec:
Modified: ode/site/trunk/content/pxe-activate-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/pxe-activate-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/pxe-activate-command.mdtext (original)
+++ ode/site/trunk/content/pxe-activate-command.mdtext Fri Dec 28 11:29:06 2012
@@ -11,15 +11,15 @@ The `pxe-activate` command {excerpt}acti
pxe-activate -h{noformat}
h2. Description
- The {{pxe-activate}} command will activate a deployed system via JMX. The command is idempotent in the sense that if a system is already activated, if has no effect. This command is the inverse of the [{{pxe-deactivate}}|pxe-deactivate Command].
+ The `pxe-activate` command will activate a deployed system via JMX. The command is idempotent in the sense that if a system is already activated, if has no effect. This command is the inverse of the [`pxe-deactivate`|pxe-deactivate Command].
For more information about activation, see [System Lifecycle].
h2. Options
||Option/Argument||Effect||
- |{{ystem}}|the name of the system to activate, as specified in the [PXE System Deployment Descriptor]. This option is required if the {{-all}} option is not specified.|
- |{{-all}}|activate _all_ of the systems in the target domain.|
- |{{-jmxurl url}}|the JMX service URL for the target domain. See the [urlalias Command] for more information about how to set default values and shortcuts.|
- |{{-domain domain}}|the name of the target domain. If this option is not specified, the command will search for PXE domains. If a single domain is located, then the command is applied in that domain, but if multiple domains are located, an error is returned.|
- |{{-q\|-v\|-vv}}|adjust the verbosity of logging output. See [Log and Debug Output from Commandline Tools].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`ystem`|the name of the system to activate, as specified in the [PXE System Deployment Descriptor]. This option is required if the `-all` option is not specified.|
+ |`-all`|activate _all_ of the systems in the target domain.|
+ |`-jmxurl url`|the JMX service URL for the target domain. See the [urlalias Command] for more information about how to set default values and shortcuts.|
+ |`-domain domain`|the name of the target domain. If this option is not specified, the command will search for PXE domains. If a single domain is located, then the command is applied in that domain, but if multiple domains are located, an error is returned.|
+ |`-q\|-v\|-vv`|adjust the verbosity of logging output. See [Log and Debug Output from Commandline Tools].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/pxe-deactivate-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/pxe-deactivate-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/pxe-deactivate-command.mdtext (original)
+++ ode/site/trunk/content/pxe-deactivate-command.mdtext Fri Dec 28 11:29:06 2012
@@ -11,15 +11,15 @@ The `pxe-deactivate` command {excerpt}de
pxe-deactivate -h{noformat}
h2. Description
- The {{pxe-deactivate}} command will deactivate a deployed system via JMX. The command is idempotent in the sense that if a system is already deactivated, if has no effect. This command is the inverse of the [pxe-activate Command].
+ The `pxe-deactivate` command will deactivate a deployed system via JMX. The command is idempotent in the sense that if a system is already deactivated, if has no effect. This command is the inverse of the [pxe-activate Command].
For more information about deactivation, see [System Lifecycle].
h2. Options
||Option/Argument||Effect||
- |{{system}}|the name of the system to deactivate, as specified in the [PXE System Deployment Descriptor]. This option is required if the {{-all}} option is not specified.|
- |{{-all}}|deactivate _all_ of the systems in the target domain.|
- |{{-jmxurl url}}|the JMX service URL for the target domain. See the [urlalias Command] for more information about how to set default values and shortcuts.|
- |{{-domain domain}}|the name of the target domain. If this option is not specified, the command will search for PXE domains. If a single domain is located, then the command is applied in that domain, but if multiple domains are located, an error is returned.|
- |{{-q\|-v\|-vv}}|adjust the verbosity of logging output. See [Log and Debug Output from Commandline Tools].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`system`|the name of the system to deactivate, as specified in the [PXE System Deployment Descriptor]. This option is required if the `-all` option is not specified.|
+ |`-all`|deactivate _all_ of the systems in the target domain.|
+ |`-jmxurl url`|the JMX service URL for the target domain. See the [urlalias Command] for more information about how to set default values and shortcuts.|
+ |`-domain domain`|the name of the target domain. If this option is not specified, the command will search for PXE domains. If a single domain is located, then the command is applied in that domain, but if multiple domains are located, an error is returned.|
+ |`-q\|-v\|-vv`|adjust the verbosity of logging output. See [Log and Debug Output from Commandline Tools].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/pxe-deploy-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/pxe-deploy-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/pxe-deploy-command.mdtext (original)
+++ ode/site/trunk/content/pxe-deploy-command.mdtext Fri Dec 28 11:29:06 2012
@@ -10,19 +10,19 @@ The `pxe-deploy` command {excerpt}deploy
pxe-deploy -h{noformat}
h2. Description
- The {{pxe-deploy}} command will deploys a system in a running domain via JMX. A [system deployment bundle] for the system can either be at a URL that the target domain can access and read (the {{-url}} argument) or in a local [SAR file|SAR File] ({{-sar}} argument).
+ The `pxe-deploy` command will deploys a system in a running domain via JMX. A [system deployment bundle] for the system can either be at a URL that the target domain can access and read (the `-url` argument) or in a local [SAR file|SAR File] (`-sar` argument).
For more information about deployment, see [System Lifecycle].
{info:title=So many ways to deploy...}
- The [{{ModDeployer}}|ModDeployer Kmodule] kmodule polls a directory for [SAR|SAR File] or JAR files to deploy and provides an alternative to the {{pxe-deploy}} command.
+ The [`ModDeployer`|ModDeployer Kmodule] kmodule polls a directory for [SAR|SAR File] or JAR files to deploy and provides an alternative to the `pxe-deploy` command.
{info}
h2. Options
||Option/Argument||Effect||
- |{{-url sarurl}}|the URL, from the perspective of the target domain, containing the [system deployment bundle].|
- |{{-sar file}}|the name of a [SAR file] on the local machine.|
- |{{-jmxurl url}}|the JMX service URL for the target domain. See the [{{urlalias}}|urlalias Command] for more information about how to set default values and shortcuts.|
- |{{-domain domain}}|the name of the target domain. If this option is not specified, the command will search for PXE domains. If a single domain is located, then the command is applied in that domain, but if multiple domains are located, an error is returned.|
- |{{-q\|-v\|-vv}}|adjust the verbosity of logging output. See [Loging and Output for Commandline Tools].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`-url sarurl`|the URL, from the perspective of the target domain, containing the [system deployment bundle].|
+ |`-sar file`|the name of a [SAR file] on the local machine.|
+ |`-jmxurl url`|the JMX service URL for the target domain. See the [`urlalias`|urlalias Command] for more information about how to set default values and shortcuts.|
+ |`-domain domain`|the name of the target domain. If this option is not specified, the command will search for PXE domains. If a single domain is located, then the command is applied in that domain, but if multiple domains are located, an error is returned.|
+ |`-q\|-v\|-vv`|adjust the verbosity of logging output. See [Loging and Output for Commandline Tools].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/pxe-status-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/pxe-status-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/pxe-status-command.mdtext (original)
+++ ode/site/trunk/content/pxe-status-command.mdtext Fri Dec 28 11:29:06 2012
@@ -10,9 +10,9 @@ The `pxe-status` command {excerpt}prints
pxe-status -h{noformat}
h2. Description
- The {{pxe-status}} command prints a list of systems and service providers to the console.
+ The `pxe-status` command prints a list of systems and service providers to the console.
- The prototypical output from {{pxe-status}} is as follows:
+ The prototypical output from `pxe-status` is as follows:
Domain: MyDomain (2 systems, 1 active)
@@ -31,11 +31,11 @@ Domain: MyDomain (2 systems, 1 active)
* The name of the domain is "MyDomain", and it contains two systems, "GeoIp" and "HelloWorld".
* The GeoIp system is deactivated, as denoted by the "-".
* The HelloWorld system is activated, as denoted by the "+", and contains two services, numbered 0 through 1.
- * The URI of the GeoIpService.BpelService is {{uri:bpelProvider}}.
+ * The URI of the GeoIpService.BpelService is `uri:bpelProvider`.
h2. Options
||Option/Argument||Effect||
- |{{-jmxurl url}}|the JMX service URL for the target domain. See the [urlalias Command] for more information about how to set default values and shortcuts.|
- |{{-domain domain}}|the name of the target domain. If this option is not specified, the command will search for PXE domains. If a single domain is located, then the command is applied in that domain, but if multiple domains are located, an error is returned.|
- |{{-q\|-v\|-vv}}|adjust the verbosity of logging output. See [Log and Debug Output from Commandline Tools].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`-jmxurl url`|the JMX service URL for the target domain. See the [urlalias Command] for more information about how to set default values and shortcuts.|
+ |`-domain domain`|the name of the target domain. If this option is not specified, the command will search for PXE domains. If a single domain is located, then the command is applied in that domain, but if multiple domains are located, an error is returned.|
+ |`-q\|-v\|-vv`|adjust the verbosity of logging output. See [Log and Debug Output from Commandline Tools].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/pxe-undeploy-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/pxe-undeploy-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/pxe-undeploy-command.mdtext (original)
+++ ode/site/trunk/content/pxe-undeploy-command.mdtext Fri Dec 28 11:29:06 2012
@@ -11,17 +11,17 @@ The `pxe-undeploy` command {excerpt}unde
pxe-undeploy -h{noformat}
h2. Description
- The {{pxe-undeploy}} command will undeploy a system in a running domain via JMX. This command is the inverse of the [{{pxe-deploy}}|pxe-deploy Command].
+ The `pxe-undeploy` command will undeploy a system in a running domain via JMX. This command is the inverse of the [`pxe-deploy`|pxe-deploy Command].
- {warning}Undeploying a aystem erases information about its state, including any the state of process instances and process completion data. Deactivation via [{{pxe-deactivate}}|pxe-deactivate Command] is preferable unless a system is at the end of its life.{warning}
+ {warning}Undeploying a aystem erases information about its state, including any the state of process instances and process completion data. Deactivation via [`pxe-deactivate`|pxe-deactivate Command] is preferable unless a system is at the end of its life.{warning}
For more information about undeployment, see [System Lifecycle].
h2. Options
||Option/Argument||Effect||
- |{{system}}|the name of the system to undeploy, as specified in the [PXE System Deployment Descriptor]. This option is required if the {{-all}} option is not specified.|
- |{{-all}}|undeploy _all_ of the systems in the target domain.|
- |{{-jmxurl url}}|the JMX service URL for the target domain. See the [urlalias Command] for more information about how to set default values and shortcuts.|
- |{{-domain domain}}|the name of the target domain. If this option is not specified, the command will search for PXE domains. If a single domain is located, then the command is applied in that domain, but if multiple domains are located, an error is returned.|
- |{{-v\|-vv}}|adjust the verbosity of logging output. See [Log and Debug Output from Commandline Tools].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`system`|the name of the system to undeploy, as specified in the [PXE System Deployment Descriptor]. This option is required if the `-all` option is not specified.|
+ |`-all`|undeploy _all_ of the systems in the target domain.|
+ |`-jmxurl url`|the JMX service URL for the target domain. See the [urlalias Command] for more information about how to set default values and shortcuts.|
+ |`-domain domain`|the name of the target domain. If this option is not specified, the command will search for PXE domains. If a single domain is located, then the command is applied in that domain, but if multiple domains are located, an error is returned.|
+ |`-v\|-vv`|adjust the verbosity of logging output. See [Log and Debug Output from Commandline Tools].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/receive.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/receive.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/receive.mdtext (original)
+++ ode/site/trunk/content/receive.mdtext Fri Dec 28 11:29:06 2012
@@ -33,7 +33,7 @@ The `<receive>` activity enables a BPEL
In this sense, the activity can be said to block. For non-deterministic selection (something akin to a POSIX `select`), the `<[pick](pick.html)>` activity should be used.
<div class="alert alert-info">
- The precise timing of message arrival is not important. The message can arrive before the {{<receive>}} activity is activated; ODE will store the message in an internal queue and associate it with the appropriate {{<receive>}} once it is activated.
+ The precise timing of message arrival is not important. The message can arrive before the `<receive>` activity is activated; ODE will store the message in an internal queue and associate it with the appropriate `<receive>` once it is activated.
</div>
If the operation is of a request-response style, the `<[reply](reply.html)>` activity can be used to send the reply.
@@ -56,7 +56,7 @@ If the operation is of a request-respons
-- `part` -- name of the received message part
-- `toVariable` -- the variable in which the part should be saved
<div class="alert alert-note">
- ODE does not yet support the {{<fromPart>}} syntax. Hence, the {{variable}} attribute must be used.
+ ODE does not yet support the `<fromPart>` syntax. Hence, the `variable` attribute must be used.
</div>
Modified: ode/site/trunk/content/rradd-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/rradd-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/rradd-command.mdtext (original)
+++ ode/site/trunk/content/rradd-command.mdtext Fri Dec 28 11:29:06 2012
@@ -11,17 +11,17 @@ The `rradd` command {excerpt}adds one or
rradd -h{noformat}
h2. Description
- The {{rradd}} command adds one or resources to a [ZIP resource repository]. If the target file does not already exist, it is created. As with other repository manipulation commands, the action of {{rradd}} is atomic, so if there is a failure reading one of the URLs, the entire operation is aborted.
+ The `rradd` command adds one or resources to a [ZIP resource repository]. If the target file does not already exist, it is created. As with other repository manipulation commands, the action of `rradd` is atomic, so if there is a failure reading one of the URLs, the entire operation is aborted.
h2. Options
||Option/Argument||Effect||
- |{{-q}}|Suppress complaints about URIs already registered in the repository.|
- |{{-wsdl}}|Treat the specified [URL]s as WSDL and/or XML schema and recursively import any other WSDL and/or schema documents referenced. The import algorithm handles circular references intelligently.|
- |{{url}} ... {{url}}|one or more [URL]s to be imported; the content of the resource at each [URL] will be stored at a [URI] equal to the URL it was loaded from. See the [rralias Command] for information about how to add additional references to an previously stored resource.|
- |{{rrfile}}|the [ZIP resource repository] file to update or create.|
- |{{-v\|-vv}}|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`-q`|Suppress complaints about URIs already registered in the repository.|
+ |`-wsdl`|Treat the specified [URL]s as WSDL and/or XML schema and recursively import any other WSDL and/or schema documents referenced. The import algorithm handles circular references intelligently.|
+ |`url` ... `url`|one or more [URL]s to be imported; the content of the resource at each [URL] will be stored at a [URI] equal to the URL it was loaded from. See the [rralias Command] for information about how to add additional references to an previously stored resource.|
+ |`rrfile`|the [ZIP resource repository] file to update or create.|
+ |`-v\|-vv`|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
+ |`-h`|prints a synopsis to the console and exits.|
- {note:title=Use Care When Adding WSDL or Schema}Without the {{-wsdl}} flag, WSDL and schema documents are handled in a "dumb" fashion.
+ {note:title=Use Care When Adding WSDL or Schema}Without the `-wsdl` flag, WSDL and schema documents are handled in a "dumb" fashion.
- For example, valid use cases for adding WSDL without using the {{-wsdl}} flag include selective replacement of imports.{note}
+ For example, valid use cases for adding WSDL without using the `-wsdl` flag include selective replacement of imports.{note}
Modified: ode/site/trunk/content/rralias-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/rralias-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/rralias-command.mdtext (original)
+++ ode/site/trunk/content/rralias-command.mdtext Fri Dec 28 11:29:06 2012
@@ -11,17 +11,17 @@ The `rralias` command {excerpt}adds an a
rralias -h{noformat}
h2. Description
- The {{rralias}} command adds an additional [URI] reference to a [ZIP resource repository]. As with other repository manipulation commands, the action of {{rralias}} is atomic, so if there is a failure reading one of the URLs, the entire operation is aborted.
+ The `rralias` command adds an additional [URI] reference to a [ZIP resource repository]. As with other repository manipulation commands, the action of `rralias` is atomic, so if there is a failure reading one of the URLs, the entire operation is aborted.
- The most common use case for the {{rralias}} command is when using the [rradd Command] to add multiple resources to the repository but where the URI of one of the resources is different than the URI in the {{<wsdl:import>}} statement. (This occurs frequently with generated WSDL and XML schema documents.)
+ The most common use case for the `rralias` command is when using the [rradd Command] to add multiple resources to the repository but where the URI of one of the resources is different than the URI in the `<wsdl:import>` statement. (This occurs frequently with generated WSDL and XML schema documents.)
- {note:title=Many References, One Resource}A URI reference created by {{rralias}} is indistinguishable from a URI reference added by {{rradd}}, so in effect, a URI is dereferenced at the time that the alias is created. This means that if any of the aliased URIs is rebound at a later time, any alises must be reestablished.{note}
+ {note:title=Many References, One Resource}A URI reference created by `rralias` is indistinguishable from a URI reference added by `rradd`, so in effect, a URI is dereferenced at the time that the alias is created. This means that if any of the aliased URIs is rebound at a later time, any alises must be reestablished.{note}
h2. Options
||Option/Argument||Effect||
- |{{-q}}|Suppress complaints about a {{touri}} that is already registered in the repository.|
- |{{fromuri}}|the URI key of the source resource. This URI must already be registered in the repository, or the command will signal an error.|
- |{{touri}}|the new URI alias.|
- |{{rrfile}}|the [ZIP resource repository] file to which the alias will be added.|
- |{{-v\|-vv}}|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`-q`|Suppress complaints about a `touri` that is already registered in the repository.|
+ |`fromuri`|the URI key of the source resource. This URI must already be registered in the repository, or the command will signal an error.|
+ |`touri`|the new URI alias.|
+ |`rrfile`|the [ZIP resource repository] file to which the alias will be added.|
+ |`-v\|-vv`|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/rrdrop-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/rrdrop-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/rrdrop-command.mdtext (original)
+++ ode/site/trunk/content/rrdrop-command.mdtext Fri Dec 28 11:29:06 2012
@@ -9,8 +9,8 @@ The `rrdrop` command {excerpt}removes on
`rrdrop -h`
<div class="alert alert-note"><h4 class="alert-heading">Compatibility Note</h4>
Command line arguments were normalized in PXE v1.0RC2. Users of PXE v1.0RC1 should use the following syntax:
- {{rrdrop \[-v](-vv\) \[-q\] _uri ... uri rr_}}
- {{rrdrop -h}}
+ `rrdrop \[-v](-vv\) \[-q\] _uri ... uri rr_`
+ `rrdrop -h`
</div>
<a name="rrdropCommand-Description"></a>
@@ -21,8 +21,8 @@ The `rrdrop` command removes one or more
h2. Options
||Option/Argument||Effect||
- |{{-q}}|Suppress complaints about URIs not registered in the repository. Otherwise, a warning message is printed to standard error.|
- |_{{uri}} ... {{uri}}_|one or more [URI]s to be removed.|
- |_{{rr}}_|the path of the [resource repository] to update.|
- |{{-v\|-vv}}|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`-q`|Suppress complaints about URIs not registered in the repository. Otherwise, a warning message is printed to standard error.|
+ |_`uri` ... `uri`_|one or more [URI]s to be removed.|
+ |_`rr`_|the path of the [resource repository] to update.|
+ |`-v\|-vv`|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/rrget-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/rrget-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/rrget-command.mdtext (original)
+++ ode/site/trunk/content/rrget-command.mdtext Fri Dec 28 11:29:06 2012
@@ -18,12 +18,12 @@ rrget -h{noformat}
h2. Description
- The {{rrget}} command extracts a resource from a [resource repository] and streams it to standard out.
+ The `rrget` command extracts a resource from a [resource repository] and streams it to standard out.
h2. Options
||Option/Argument||Effect||
- |{{-q}}|Suppress complaint about a URI not registered in the repository. Otherwise, an error is printed to standard error.|
- |{{uri}}|the [URI] of the resource to be extracted.|
- |{{rrfile}}|the path of the [resource repository] where the resource is found. |
- |{{-v\|-vv}}|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`-q`|Suppress complaint about a URI not registered in the repository. Otherwise, an error is printed to standard error.|
+ |`uri`|the [URI] of the resource to be extracted.|
+ |`rrfile`|the path of the [resource repository] where the resource is found. |
+ |`-v\|-vv`|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/sarcreate-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/sarcreate-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/sarcreate-command.mdtext (original)
+++ ode/site/trunk/content/sarcreate-command.mdtext Fri Dec 28 11:29:06 2012
@@ -3,7 +3,7 @@ Title: sarcreate Command
The `sarcreate` command {excerpt}creates a [system deployment archive](system-deployment-archive.html).{excerpt}
<div class="alert alert-note"><h4 class="alert-heading">Compatibility Note</h4>
- This command is only available in PXE vesion RC1. Starting with RC2, the [{{<pxe-sar>}}|pxe-sar Task] Ant task or the standard Java {{jar}} command should be used.
+ This command is only available in PXE vesion RC1. Starting with RC2, the [`<pxe-sar>`|pxe-sar Task] Ant task or the standard Java `jar` command should be used.
</div>
<a name="sarcreateCommand-Synopsis"></a>
## Synopsis
@@ -13,16 +13,16 @@ The `sarcreate` command {excerpt}creates
h2. Description
- The {{sarcreate}} command builds a [system deployment archive].
+ The `sarcreate` command builds a [system deployment archive].
- For comparison, see the [{{<pxe-sar>}}|pxe-sar Task] Ant task.
+ For comparison, see the [`<pxe-sar>`|pxe-sar Task] Ant task.
h2. Options
||Option/Argument||Effect||
- |{{-sysd ddfile}}|a file containing the [system deployment descriptor] for the bundle. Errors or warnings about the validity of the descriptor will be reported to standard error.|
- |{{-common rrfile}}|a [ZIP resource repository] containing the root WSDL definitions for the system. If this argument is not specified, then the command attempts to parse the system descriptor to and interprets the root WSDL URI as a URL from which to create a temporary resource repository containing the specified WSDL document and its imported WSDL and XML schema documents.|
- |{{file ... file}}|additional files to add to the bundle as resources. Each file is added with its name set to the file name, i.e., {{foo/bar/baz.qux}} is added as a resource with name {{baz.qux}}. If the file has a {{.rr}} extension, it is added to the archive as a resource repository, i.e., {{foo/bar/baz.rr}} is added as a resource repository with name {{baz}}.||
- |{{sarfile}}|the name of the file to write the new archive into.|
- |{{-v\|-vv}}|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`-sysd ddfile`|a file containing the [system deployment descriptor] for the bundle. Errors or warnings about the validity of the descriptor will be reported to standard error.|
+ |`-common rrfile`|a [ZIP resource repository] containing the root WSDL definitions for the system. If this argument is not specified, then the command attempts to parse the system descriptor to and interprets the root WSDL URI as a URL from which to create a temporary resource repository containing the specified WSDL document and its imported WSDL and XML schema documents.|
+ |`file ... file`|additional files to add to the bundle as resources. Each file is added with its name set to the file name, i.e., `foo/bar/baz.qux` is added as a resource with name `baz.qux`. If the file has a `.rr` extension, it is added to the archive as a resource repository, i.e., `foo/bar/baz.rr` is added as a resource repository with name `baz`.||
+ |`sarfile`|the name of the file to write the new archive into.|
+ |`-v\|-vv`|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/sarls-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/sarls-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/sarls-command.mdtext (original)
+++ ode/site/trunk/content/sarls-command.mdtext Fri Dec 28 11:29:06 2012
@@ -12,11 +12,11 @@ The `sarls` command {excerpt}outputs a s
h2. Description
- The {{sarls}} command outputs a summary of the contents of a [system deployment archive]. The summary includes the name of the system, the [URI] of the root WSDL in the common [resource repository], summaries of the contents of the resource repositories in the archive (including the common resource repository), and a list of the other resources in the archive.
+ The `sarls` command outputs a summary of the contents of a [system deployment archive]. The summary includes the name of the system, the [URI] of the root WSDL in the common [resource repository], summaries of the contents of the resource repositories in the archive (including the common resource repository), and a list of the other resources in the archive.
h2. Options
||Option/Argument||Effect||
- |{{sarfile}}|the name of the file containing the archive to summarize.|
- |{{-v\|-vv}}|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`sarfile`|the name of the file containing the archive to summarize.|
+ |`-v\|-vv`|adjust the verbosity of logging output. See [Configuring Commandline Launchers].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/sendsoap-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/sendsoap-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/sendsoap-command.mdtext (original)
+++ ode/site/trunk/content/sendsoap-command.mdtext Fri Dec 28 11:29:06 2012
@@ -10,13 +10,13 @@ The `sendsoap` command {excerpt}uses a l
sendsoap -h{noformat}
h2. 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 PXE or external HTTP services that PXE will interact with, as {{sendsoap}} uses the same client as the [HTTP-SOAP Protocol Adapter].
+ 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 PXE or external HTTP services that PXE will interact with, as `sendsoap` uses the same client as the [HTTP-SOAP Protocol Adapter].
h2. Options
||Option/Argument||Effect||
- |{{url}}|the HTTP URL to post the message to.|
- |{{file}}|a file containing the message to post.|
- |{{-}}|read the message data from standard in instead of a file.|
- |{{-o file}}|sets a file to write the output to; otherwise, output is sent to the console.|
- |{{-q\|-v\|-vv}}|adjust the verbosity of logging output. See [Loging and Output for Commandline Tools].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`url`|the HTTP URL to post the message to.|
+ |`file`|a file containing the message to post.|
+ |`-`|read the message data from standard in instead of a file.|
+ |`-o file`|sets a file to write the output to; otherwise, output is sent to the console.|
+ |`-q\|-v\|-vv`|adjust the verbosity of logging output. See [Loging and Output for Commandline Tools].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/urlalias-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/urlalias-command.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/urlalias-command.mdtext (original)
+++ ode/site/trunk/content/urlalias-command.mdtext Fri Dec 28 11:29:06 2012
@@ -13,18 +13,18 @@ The `urlalias` command {excerpt}manages
urlalias -h{noformat}
h2. Description
- The {{urlalias}} command is used to maintain a mapping between aliases and URLs used by other [Commandline Tools] and [Ant Tasks].
+ The `urlalias` command is used to maintain a mapping between aliases and URLs used by other [Commandline Tools] and [Ant Tasks].
- The list of aliases is stored in a file named {{.pxe.aliases}} in the user's home directory.
+ The list of aliases is stored in a file named `.pxe.aliases` in the user's home directory.
{info:title=Be sure to properly escape URLs on the commandline.}The commandline shells for different operating systems may interpret colons, question marks, and other symbols as part of the command instead of part of the argument, so be sure to properly quote or escape any URLs passed as arguments.{info}
h3. Magic Aliases
Other commands recognize the following "magic" aliases:
- * The {{jmx-default}} alias supplies the default value of the JMX service URL for the system management commands; see [{{pxe-deploy}}|pxe-deploy Command], [{{pxe-undeploy}}|pxe-undeploy Command], [{{pxe-status}}|pxe-status Command], [{{pxe-activate}}|pxe-activate Command], or [{{pxe-deactivate}}|pxe-deactivate Command].
+ * The `jmx-default` alias supplies the default value of the JMX service URL for the system management commands; see [`pxe-deploy`|pxe-deploy Command], [`pxe-undeploy`|pxe-undeploy Command], [`pxe-status`|pxe-status Command], [`pxe-activate`|pxe-activate Command], or [`pxe-deactivate`|pxe-deactivate Command].
h2. Options
||Option/Argument||Effect||
- |{{-v\|-vv}}|adjust the verbosity of logging output. See [Loging and Output for Commandline Tools].|
- |{{-h}}|prints a synopsis to the console and exits.|
+ |`-v\|-vv`|adjust the verbosity of logging output. See [Loging and Output for Commandline Tools].|
+ |`-h`|prints a synopsis to the console and exits.|
Modified: ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext?rev=1426460&r1=1426459&r2=1426460&view=diff
==============================================================================
--- ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext (original)
+++ ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext Fri Dec 28 11:29:06 2012
@@ -35,7 +35,7 @@ Let's assume that such a resource accept
According to the WSDL 1.1 specification, the verb describing the HTTP method has to be at [the binding level](http://www.w3.org/TR/wsdl#A4.3). Which implies that the same HTTP method is used by all operations of a given port type. But RESTful web services leverage HTTP methods as a uniform interface to describe operation on resources. So for instance, if you want to use the following HTTP operations -- GET, POST, PUT, DELETE -- for a given resource, four different bindings would be required. And consequently four port types and four ports. Quite verbose and unusable, isn't it?
So, this extension is to push down the HTTP verb at the operation level. And if an operation does not have its own verb, then the verb defined at the binding level will be used.
- This extension is declared in the namespace: {{http://www.apache.org/ode/type/extension/http}}
+ This extension is declared in the namespace: `http://www.apache.org/ode/type/extension/http`
Please note that ODE supports GET, POST, PUT, DELETE only.
{code:xml}
@@ -61,7 +61,7 @@ Let's assume that such a resource accept
A RESTful service exposed a set of resources, each of them being accessible through a uniform interface: HTTP methods for a web service. So we need a way to define four operations (at most) for a single resource.
- Moreover it's very likely that the resource URI actually describes a set of resources. For instance, the set of posts contained in our imaginary blog: {{http://blog.org/post/\{post_id\}}}.
+ Moreover it's very likely that the resource URI actually describes a set of resources. For instance, the set of posts contained in our imaginary blog: `http://blog.org/post/\{post_id\`}.
HTTP binding offers the [http:operation | http://www.w3.org/TR/wsdl#_http:operation] element to set the path of an operation. While the service address is set in the [http:address](http://www.w3.org/TR/wsdl#_http:address) of the [wsdl:port](http://www.w3.org/TR/wsdl#_ports) element.
So one could imagine splitting the URL this way:
@@ -203,7 +203,7 @@ Let's assume that such a resource accept
|503_SERVICE_UNAVAILABLE|
|504_GATEWAY_TIMEOUT|
- {info:title=Useful Information}Note that 3xx errors should be pretty rare since by default the first hundred redirections are followed. You can tweak this value by setting the property {{http.protocol.max-redirects}} in the [enpoint-configuration.properties|Endpoint Configuration] of your process.{info}
+ {info:title=Useful Information}Note that 3xx errors should be pretty rare since by default the first hundred redirections are followed. You can tweak this value by setting the property `http.protocol.max-redirects` in the [enpoint-configuration.properties|Endpoint Configuration] of your process.{info}
Here what ODE does, if the status code is one of those listed in the next table (500, 501, etc):
# check that the operation has at least one fault in its abstract part, and one fault binding