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:11:23 UTC
svn commit: r1426454 - /ode/site/trunk/content/
Author: vanto
Date: Fri Dec 28 11:11:22 2012
New Revision: 1426454
URL: http://svn.apache.org/viewvc?rev=1426454&view=rev
Log:
conversion of conluence links to markdown links.
Modified:
ode/site/trunk/content/ambiguousreceive.mdtext
ode/site/trunk/content/assign.mdtext
ode/site/trunk/content/endpoint-references.mdtext
ode/site/trunk/content/faq.mdtext
ode/site/trunk/content/http-soap-protocol-adapter.mdtext
ode/site/trunk/content/management-api.mdtext
ode/site/trunk/content/message-exchange.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-sar-task.mdtext
ode/site/trunk/content/pxe-undeploy-command.mdtext
ode/site/trunk/content/receive.mdtext
ode/site/trunk/content/rrdrop-command.mdtext
ode/site/trunk/content/sendsoap-command.mdtext
ode/site/trunk/content/soap-11.mdtext
ode/site/trunk/content/source-code.mdtext
ode/site/trunk/content/ws-bpel-20.mdtext
ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext
ode/site/trunk/content/wsdl-11-http-binding-support.mdtext
ode/site/trunk/content/wsdl-11.mdtext
ode/site/trunk/content/xpath-extensions.mdtext
ode/site/trunk/content/xquery-extensions.mdtext
Modified: ode/site/trunk/content/ambiguousreceive.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/ambiguousreceive.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/ambiguousreceive.mdtext (original)
+++ ode/site/trunk/content/ambiguousreceive.mdtext Fri Dec 28 11:11:22 2012
@@ -5,7 +5,7 @@ Title: ambiguousReceive
<a name="ambiguousReceive-Description"></a>
### Description
-This fault is thrown when two (or more) inbound message activities (i.e. `<[pick](pick.html)>`, `<[receive]>`, etc...) are in a position to consume the same message. This can occur if two (or more) inbound activities using the same partnerLink and operation (but different correlationSets) are activate at the same time and a message arrives that matches more two or more of the activities. In other words, this fault is thrown when there is a race between two activities to consume the same message. The [following section|#examples] provides an example.
+This fault is thrown when two (or more) inbound message activities (i.e. `<[pick](pick.html)>`, `<[receive]>`, etc...) are in a position to consume the same message. This can occur if two (or more) inbound activities using the same partnerLink and operation (but different correlationSets) are activate at the same time and a message arrives that matches more two or more of the activities. In other words, this fault is thrown when there is a race between two activities to consume the same message. The [following section](#examples) provides an example.
<div class="alert alert-note">
ODE does not currently throw this fault. Instead, one of the inbound message activitie will "win" and consume the message.
Modified: ode/site/trunk/content/assign.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/assign.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/assign.mdtext (original)
+++ ode/site/trunk/content/assign.mdtext Fri Dec 28 11:11:22 2012
@@ -21,7 +21,7 @@ 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]}}
@@ -30,12 +30,12 @@ Title: assign
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?
+ - {{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?
@@ -49,8 +49,8 @@ Title: assign
-- {{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])
+ -- {{<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.
{note}
Modified: ode/site/trunk/content/endpoint-references.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/endpoint-references.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/endpoint-references.mdtext (original)
+++ ode/site/trunk/content/endpoint-references.mdtext Fri Dec 28 11:11:22 2012
@@ -20,10 +20,10 @@ Both `partnerRole` and `myRole` represen
The ODE runtime supports 4 types of EPRs:
-* A simple URL or a URL in the location attribute of the binding. See [soap:address](http://www.w3.org/TR/wsdl#_soap:address) and [http:address|http://www.w3.org/TR/wsdl#_http:address] WSDL 1.1 binding.
-* A [WS-Addressing](http://www.w3.org/TR/ws-addr-core/) [EndpointReference|http://www.w3.org/TR/ws-addr-core/#eprinfomodel].
-* A [WSDL 1.1](http://www.w3.org/TR/wsdl) [service element|http://www.w3.org/TR/wsdl#_services].
-* A [WSDL 2.0](http://www.w3.org/TR/wsdl20/) [endpoint element|http://www.w3.org/TR/wsdl20/#Endpoint].
+* A simple URL or a URL in the location attribute of the binding. See [soap:address](http://www.w3.org/TR/wsdl#_soap:address) and [http:address](http://www.w3.org/TR/wsdl#_http:address) WSDL 1.1 binding.
+* A [WS-Addressing](http://www.w3.org/TR/ws-addr-core/) [EndpointReference](http://www.w3.org/TR/ws-addr-core/#eprinfomodel).
+* A [WSDL 1.1](http://www.w3.org/TR/wsdl) [service element](http://www.w3.org/TR/wsdl#_services).
+* A [WSDL 2.0](http://www.w3.org/TR/wsdl20/) [endpoint element](http://www.w3.org/TR/wsdl20/#Endpoint).
We recommend the two first solutions to interact with the engine. The first one is just the easiest and for the case where you need more robustness, WS-Addressing is the most popular second choice.
Modified: ode/site/trunk/content/faq.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/faq.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/faq.mdtext (original)
+++ ode/site/trunk/content/faq.mdtext Fri Dec 28 11:11:22 2012
@@ -79,10 +79,10 @@ __Q.__ _Which operating systems does ODE
__A.__ ODE is written entirely in Java and can run on any operating system supporting the required Java environment. ODE has been tested and is known to run on Windows 2000, Windows XP, Linux, MacOS X, Solaris, and AIX.
__Q.__ _Does ODE require a database? Which databases and versions does ODE support?_
-__A.__ ODE does not depend directly on any specific database or persistence mechanism. Instead, ODE relies on a set of data access object ("DAO") interfaces that encapsulate the behaviors of a persistence layer. The ODE distribution includes a DAO implementation for JDBC databases built using [OpenJPA|http://openjpa.apache.org]. This DAO implementation can support most common relational databases. Schemas suitable for [MySQL|http://www.mysql.com] and [Derby|http://db.apache.org/derby/] are provided. Relational databases lacking transaction or binary large object ("BLOB") capabilities are not supported. The DAO interfaces can readily be implemented to support alternative persistence mechanisms (e.g. JDO), XML datastores, or direct filesystem-based persistence.
+__A.__ ODE does not depend directly on any specific database or persistence mechanism. Instead, ODE relies on a set of data access object ("DAO") interfaces that encapsulate the behaviors of a persistence layer. The ODE distribution includes a DAO implementation for JDBC databases built using [OpenJPA](http://openjpa.apache.org). This DAO implementation can support most common relational databases. Schemas suitable for [MySQL|http://www.mysql.com] and [Derby|http://db.apache.org/derby/] are provided. Relational databases lacking transaction or binary large object ("BLOB") capabilities are not supported. The DAO interfaces can readily be implemented to support alternative persistence mechanisms (e.g. JDO), XML datastores, or direct filesystem-based persistence.
__Q.__ _Does ODE require a J2EE application server?_
-__A.__ The core ODE components do not require a J2EE application server. ODE relies on a [Integration API|http://svn.apache.org/repos/asf/ode/trunk/bpel-api/src/main/java/org/apache/ode/bpel/iapi/] that allows ODE to be embedded in most any environment that can supply the required facilities. An [AXIS2 Integration] is provided that permits ODE to be installed on a J2EE application server, or in a "dumb" Servlet container via a WAR file. A [JBI Integration] integration is also provided that permits ODE to be installed in a JBI container.
+__A.__ The core ODE components do not require a J2EE application server. ODE relies on a [Integration API](http://svn.apache.org/repos/asf/ode/trunk/bpel-api/src/main/java/org/apache/ode/bpel/iapi/) that allows ODE to be embedded in most any environment that can supply the required facilities. An [AXIS2 Integration] is provided that permits ODE to be installed on a J2EE application server, or in a "dumb" Servlet container via a WAR file. A [JBI Integration] integration is also provided that permits ODE to be installed in a JBI container.
__Q.__ _Is there a stand-alone ODE integration?_
__A.__ No, the standard ODE distributions require either an application server, Servlet container, or JBI container.
@@ -107,7 +107,7 @@ __Q.__ _Can ODE interact directly (i.e.,
__A.__ This is currently supported in the [JBI Integration] via standard JBI mechanisms. It is currently not supported in the [AXIS2 Integration] but will be in the future.
__Q.__ _Can ODE integrate with Middleware X? Can ODE integrate with Legacy system Y? Can ODE integrate with Enterprise Application Z? How is this accomplished?_
-__A.__ The generic answer is "Yes," although it requires some work on the part of the integrator. The primary extension point for integrating with external systems is the [Integration API|http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/ProcessManagement.html], which can be used to embed ODE in most any environment.
+__A.__ The generic answer is "Yes," although it requires some work on the part of the integrator. The primary extension point for integrating with external systems is the [Integration API](http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/ProcessManagement.html), which can be used to embed ODE in most any environment.
__Q.__ _Does ODE rely on any third-party or open source libraries?_
__A.__ ODE uses a number of liberally-licensed (i.e., non-GPL) open source libraries, some integral and some not. These are enumerated in the [reference|Required Third-Party Libraries].
@@ -120,7 +120,7 @@ __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).
__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]
+__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/http-soap-protocol-adapter.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/http-soap-protocol-adapter.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/http-soap-protocol-adapter.mdtext (original)
+++ ode/site/trunk/content/http-soap-protocol-adapter.mdtext Fri Dec 28 11:11:22 2012
@@ -10,7 +10,7 @@ The HTTP-SOAP Protocol Adapter is a [PXE
PXE [services](service.html) deployed on this protocol adapter behave as proxies.
-Contrary to what one might expect, this service provider does not actually implement an HTTP "server". Instead it relies on an external SOAP stack to relay messages to it through its [JCA interface ](com.fs.jlo.adapters.httpsoap.httpsoapinteraction@pxedocs.html). This facilitates efficient integration into existing SOAP processing pipelines and permits leveraging the capabilities of the SOAP stack in the areas such as security, addressing, and management. For integration with a Servlet-based HTTP server, a Servlet (`[HttpSoapServlet|com.fs.jlo.adapters.httpsoap.HttpSoapServlet@pxedocs]`) that performs the relaying function is included.
+Contrary to what one might expect, this service provider does not actually implement an HTTP "server". Instead it relies on an external SOAP stack to relay messages to it through its [JCA interface ](com.fs.jlo.adapters.httpsoap.httpsoapinteraction@pxedocs.html). This facilitates efficient integration into existing SOAP processing pipelines and permits leveraging the capabilities of the SOAP stack in the areas such as security, addressing, and management. For integration with a Servlet-based HTTP server, a Servlet (`[HttpSoapServlet](com.fs.jlo.adapters.httpsoap.HttpSoapServlet@pxedocs)`) that performs the relaying function is included.
<a name="HTTP-SOAPProtocolAdapter-"></a>
####
Modified: ode/site/trunk/content/management-api.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/management-api.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/management-api.mdtext (original)
+++ ode/site/trunk/content/management-api.mdtext Fri Dec 28 11:11:22 2012
@@ -1,15 +1,15 @@
Title: Management API
-ODE has a complete management API to check which processes are deployed, running and completed instances, variables values and more. To see which methods are available, have a look at the [ProcessManagement](http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/ProcessManagement.html) and [InstanceManagement|http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/InstanceManagement.html] interfaces, the javadoc is pretty comprehensive.
+ODE has a complete management API to check which processes are deployed, running and completed instances, variables values and more. To see which methods are available, have a look at the [ProcessManagement](http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/ProcessManagement.html) and [InstanceManagement](http://ode.apache.org/javadoc/org/apache/ode/bpel/pmapi/InstanceManagement.html) interfaces, the javadoc is pretty comprehensive.
These two interfaces are available as web services on the Axis2-based distribution. The corresponding WSDL can be found [here](http://svn.apache.org/repos/asf/ode/trunk/axis2/src/main/wsdl/pmapi.wsdl).
-To invoke these two services, any web service client should work (in a perfect interoperable world). To ease the invocation when using an Axis2 client, a helper class is bundled in ode-axis2.jar: [ServiceClientUtil](http://ode.apache.org/javadoc/axis2/org/apache/ode/axis2/service/ServiceClientUtil.html). Usage examples are also available in test classes [InstanceManagementTest|http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/InstanceManagementTest.java] and [ProcessManagementTest|http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/ProcessManagementTest.java]. Here is a short example demonstrating the invocation of the _listAllProcesses_ operation:
+To invoke these two services, any web service client should work (in a perfect interoperable world). To ease the invocation when using an Axis2 client, a helper class is bundled in ode-axis2.jar: [ServiceClientUtil](http://ode.apache.org/javadoc/axis2/org/apache/ode/axis2/service/ServiceClientUtil.html). Usage examples are also available in test classes [InstanceManagementTest](http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/InstanceManagementTest.java) and [ProcessManagementTest|http://svn.apache.org/repos/asf/ode/trunk/axis2/src/test/java/org/apache/ode/axis2/management/ProcessManagementTest.java]. Here is a short example demonstrating the invocation of the _listAllProcesses_ operation:
{code:java}
ServiceClientUtil client = new ServiceClientUtil();
OMElement root = client.buildMessage("listAllProcesses", new String[](.html) {}, new String[](.html) {});
OMElement result = client.send(msg, "http://localhost:8080/ode/processes/ProcessManagement");
- We're using [XMLBeans|http://xmlbeans.apache.org/] to serialize and deserialize the returned values from/to XML so in the previous example. So if you'd like to have objects instead of an [Axiom|http://ws.apache.org/commons/axiom/index.html] structure in the previous example, just add the following lines of code:
+ We're using [XMLBeans](http://xmlbeans.apache.org/) to serialize and deserialize the returned values from/to XML so in the previous example. So if you'd like to have objects instead of an [Axiom|http://ws.apache.org/commons/axiom/index.html] structure in the previous example, just add the following lines of code:
{code:java}
ScopeInfoDocument scopeIndoDoc = ScopeInfoDocument.Factory.parse(result.getXMLStreamReader());
Modified: ode/site/trunk/content/message-exchange.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/message-exchange.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/message-exchange.mdtext (original)
+++ ode/site/trunk/content/message-exchange.mdtext Fri Dec 28 11:11:22 2012
@@ -1,4 +1,4 @@
Title: message exchange
-*message exchange* --- {excerpt}a communication between the ODE engine and a _[partner](partner.html)_ {excerpt}. Essentially, a message exchange is a web service invocation. Each message exchanges is associated with a WSDL _[port type]_ and _operation_. There are two types of message exchanges: _my role message exchanges_ and _partner role message exchanges_. The former represents invocations _on_ the server, while the latter represents invocations _by_ the server (this is BPEL terminology, so a look at the [spec|xxx] may be helpful).
+*message exchange* --- {excerpt}a communication between the ODE engine and a _[partner](partner.html)_ {excerpt}. Essentially, a message exchange is a web service invocation. Each message exchanges is associated with a WSDL _[port type]_ and _operation_. There are two types of message exchanges: _my role message exchanges_ and _partner role message exchanges_. The former represents invocations _on_ the server, while the latter represents invocations _by_ the server (this is BPEL terminology, so a look at the [spec](xxx) may be helpful).
Modified: ode/site/trunk/content/pxe-activate-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/pxe-activate-command.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/pxe-activate-command.mdtext (original)
+++ ode/site/trunk/content/pxe-activate-command.mdtext Fri Dec 28 11:11:22 2012
@@ -7,7 +7,7 @@ The `pxe-activate` command {excerpt}acti
<a name="pxe-activateCommand-Synopsis"></a>
## Synopsis
- pxe-activate [-v|-vv] [-jmxurl url] [-domain domain] -all
+ pxe-activate [-v](-vv) [-jmxurl url] [-domain domain] -all
pxe-activate -h{noformat}
h2. Description
Modified: ode/site/trunk/content/pxe-deactivate-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/pxe-deactivate-command.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/pxe-deactivate-command.mdtext (original)
+++ ode/site/trunk/content/pxe-deactivate-command.mdtext Fri Dec 28 11:11:22 2012
@@ -7,7 +7,7 @@ The `pxe-deactivate` command {excerpt}de
<a name="pxe-deactivateCommand-Synopsis"></a>
## Synopsis
- pxe-deactivate [-v|-vv] [-jmxurl url] [-domain domain] -all
+ pxe-deactivate [-v](-vv) [-jmxurl url] [-domain domain] -all
pxe-deactivate -h{noformat}
h2. Description
Modified: ode/site/trunk/content/pxe-deploy-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/pxe-deploy-command.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/pxe-deploy-command.mdtext (original)
+++ ode/site/trunk/content/pxe-deploy-command.mdtext Fri Dec 28 11:11:22 2012
@@ -6,7 +6,7 @@ The `pxe-deploy` command {excerpt}deploy
<a name="pxe-deployCommand-Synopsis"></a>
## Synopsis
- pxe-deploy [-q|-v|-vv] -sar file [-jmxurl url] [-domain domain]
+ pxe-deploy [-q|-v](-vv) -sar file [-jmxurl url] [-domain domain]
pxe-deploy -h{noformat}
h2. Description
Modified: ode/site/trunk/content/pxe-sar-task.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/pxe-sar-task.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/pxe-sar-task.mdtext (original)
+++ ode/site/trunk/content/pxe-sar-task.mdtext Fri Dec 28 11:11:22 2012
@@ -7,7 +7,7 @@ The `<pxe-sar>` Ant task is used to {exc
## Synopsis
<pxe-sar sar="sarfile" descriptor="descriptor" [commonrr="filename"]
- [failOnError="yes|no"] >
+ [failOnError="yes](no") >
<resource [name="handle"] file="filename" />*
<rr [name="handle"] file="filename" />*
</pxe-sar>
Modified: ode/site/trunk/content/pxe-undeploy-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/pxe-undeploy-command.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/pxe-undeploy-command.mdtext (original)
+++ ode/site/trunk/content/pxe-undeploy-command.mdtext Fri Dec 28 11:11:22 2012
@@ -7,7 +7,7 @@ The `pxe-undeploy` command {excerpt}unde
<a name="pxe-undeployCommand-Synopsis"></a>
## Synopsis
- pxe-undeploy [-v|-vv] [-jmxurl url] [-domain domain] -all
+ pxe-undeploy [-v](-vv) [-jmxurl url] [-domain domain] -all
pxe-undeploy -h{noformat}
h2. Description
Modified: ode/site/trunk/content/receive.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/receive.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/receive.mdtext (original)
+++ ode/site/trunk/content/receive.mdtext Fri Dec 28 11:11:22 2012
@@ -23,7 +23,7 @@ Title: receive
</receive>
-*throws* `[bpel:ambiguousReceive](#ambiguousreceive.html)`, `[bpel:conflictingReceive|#conflictingReceive]`, `[bpel:conflictingRequest|#conflictingRequest]`, `[bpel:correlationViolation|#correlationViolation]`, `[bpel:invalidVariables|#invalidVariables]`, `[bpel:uninitializedPartnerRole|#uninitializedPartnerRole]`,
+*throws* `[bpel:ambiguousReceive](#ambiguousreceive.html)`, `[bpel:conflictingReceive](#conflictingReceive)`, `[bpel:conflictingRequest|#conflictingRequest]`, `[bpel:correlationViolation|#correlationViolation]`, `[bpel:invalidVariables|#invalidVariables]`, `[bpel:uninitializedPartnerRole|#uninitializedPartnerRole]`,
`[bpel:uninitializedVariable](#uninitializedvariable.html)`
<a name="receive-Description"></a>
Modified: ode/site/trunk/content/rrdrop-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/rrdrop-command.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/rrdrop-command.mdtext (original)
+++ ode/site/trunk/content/rrdrop-command.mdtext Fri Dec 28 11:11:22 2012
@@ -9,7 +9,7 @@ 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 \[-v](-vv\) \[-q\] _uri ... uri rr_}}
{{rrdrop -h}}
</div>
Modified: ode/site/trunk/content/sendsoap-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/sendsoap-command.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/sendsoap-command.mdtext (original)
+++ ode/site/trunk/content/sendsoap-command.mdtext Fri Dec 28 11:11:22 2012
@@ -6,7 +6,7 @@ The `sendsoap` command {excerpt}uses a l
<a name="sendsoapCommand-Synopsis"></a>
## Synopsis
- sendsoap [-q|-v|-vv] [-o outfile] url -
+ sendsoap [-q|-v](-vv) [-o outfile] url -
sendsoap -h{noformat}
h2. Description
Modified: ode/site/trunk/content/soap-11.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/soap-11.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/soap-11.mdtext (original)
+++ ode/site/trunk/content/soap-11.mdtext Fri Dec 28 11:11:22 2012
@@ -1,4 +1,4 @@
Title: SOAP 1.1
-*SOAP 1.1* --- {excerpt}version 1.1 of the (unfortunately named) Simple Object Access Protocol [note](http://www.w3.org/TR/2000/NOTE-SOAP-20000508/) from the [W3C|http://www.w3c.org]{excerpt}.
+*SOAP 1.1* --- {excerpt}version 1.1 of the (unfortunately named) Simple Object Access Protocol [note](http://www.w3.org/TR/2000/NOTE-SOAP-20000508/) from the [W3C](http://www.w3c.org){excerpt}.
Modified: ode/site/trunk/content/source-code.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/source-code.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/source-code.mdtext (original)
+++ ode/site/trunk/content/source-code.mdtext Fri Dec 28 11:11:22 2012
@@ -4,7 +4,7 @@ Category: contributing
<a name="SourceCode-Overview"></a>
# Overview
-ODE uses [Subversion](http://subversion.tigris.org/) to manage its source code. Instructions on Subversion use can be found [here|http://svnbook.red-bean.com].
+ODE uses [Subversion](http://subversion.tigris.org/) to manage its source code. Instructions on Subversion use can be found [here](http://svnbook.red-bean.com).
<a name="SourceCode-Mainrepository"></a>
## Main repository
Modified: ode/site/trunk/content/ws-bpel-20.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/ws-bpel-20.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/ws-bpel-20.mdtext (original)
+++ ode/site/trunk/content/ws-bpel-20.mdtext Fri Dec 28 11:11:22 2012
@@ -1,5 +1,5 @@
Title: WS-BPEL 2.0
-*WS-BPEL 2.0* --- {excerpt}the first official version of the BPEL specification released by the [OASIS](http://www.oasis-open.org) [technical committee|http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsbpel]{excerpt}.
+*WS-BPEL 2.0* --- {excerpt}the first official version of the BPEL specification released by the [OASIS](http://www.oasis-open.org) [technical committee](http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsbpel){excerpt}.
The specification has been finalized and can be found [here](http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html). To learn more about it check the webinars produced by the technical committee:
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=1426454&r1=1426453&r2=1426454&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:11:22 2012
@@ -32,7 +32,7 @@ Let's assume that such a resource accept
h3. One verb per operation
- 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?
+ 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}}
@@ -63,7 +63,7 @@ Let's assume that such a resource accept
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.
+ 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:
{code:xml}
@@ -91,7 +91,7 @@ Let's assume that such a resource accept
However, here 3 issues show up:
# the location is not accessible from the End Point Reference. _=> ODE cannot process it before invoking the external service._
- # [http:urlReplacement|http://www.w3.org/TR/wsdl#_http:urlReplacement] is only accepted for GET _=> what about the uniform interface?!_
+ # [http:urlReplacement](http://www.w3.org/TR/wsdl#_http:urlReplacement) is only accepted for GET _=> what about the uniform interface?!_
# http:urlReplacement requires all parts of the operation input message to be mentioned in the operation location. Meaning that:
#* => the resource id (in the present example) must be a part of the message.
#* => no parts may be stored in the HTTP body. this conflicts with a PUT operation for instance. With a PUT you would like to set the id in the url and the resource data in the HTTP request body.
@@ -160,7 +160,7 @@ Let's assume that such a resource accept
</definitions>
{code}
- For every HTTP response, in addition to HTTP response headers, the [Status-Line|http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1] is passed as a message header. To save some painful XPath string manipulations, the Status-line is already parsed into the following structure:
+ For every HTTP response, in addition to HTTP response headers, the [Status-Line](http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1) is passed as a message header. To save some painful XPath string manipulations, the Status-line is already parsed into the following structure:
{code:xml}
<Status-Line>
<HTTP-Version>HTTP/1.1</HTTP-Version>
@@ -192,8 +192,8 @@ Let's assume that such a resource accept
h3. Fault Support
- Another domain completely neglected by WSDL 1.1 HTTP Binding is Fault management. The word is not even mentioned in the [HTTP Binding section|http://www.w3.org/TR/wsdl#_http].
- ODE allows you to bind a fault with HTTP Binding. If a [4xx or a 5xx|http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4] is returned, the following logic is applied:
+ Another domain completely neglected by WSDL 1.1 HTTP Binding is Fault management. The word is not even mentioned in the [HTTP Binding section](http://www.w3.org/TR/wsdl#_http).
+ ODE allows you to bind a fault with HTTP Binding. If a [4xx or a 5xx](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4) is returned, the following logic is applied:
A failure is thrown if the code is one of these:
|| Status-Codes triggering a Failure ||
Modified: ode/site/trunk/content/wsdl-11-http-binding-support.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/wsdl-11-http-binding-support.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/wsdl-11-http-binding-support.mdtext (original)
+++ ode/site/trunk/content/wsdl-11-http-binding-support.mdtext Fri Dec 28 11:11:22 2012
@@ -1,10 +1,10 @@
Title: WSDL 1.1 HTTP Binding Support
-Since version [1.2](getting-ode.html), ODE supports [HTTP Binding|http://www.w3.org/TR/wsdl#_http]. ODE is almost fully compliant with the WSDL 1.1 spec. The few limitations are related to MIME types.
+Since version [1.2](getting-ode.html), ODE supports [HTTP Binding](http://www.w3.org/TR/wsdl#_http). ODE is almost fully compliant with the WSDL 1.1 spec. The few limitations are related to MIME types.
Actually only the following [MIME types](http://www.iana.org/assignments/media-types/) are supported:
1. Media types that represent [XML MIME entities](http://www.rfc-editor.org/rfc/rfc3023.txt). Basically any types matching `"text/xml"`, `"application/xml"` and `"\*+xml"`.
1. Non-XML types will be processed as Text, thus Text Media Types comes de facto but they may have a very limited set of usages.
-[mime:multipartRelated](http://www.w3.org/TR/wsdl#_mime:multipartRelated), [mime:soap:body|http://www.w3.org/TR/wsdl#_mime:soap:body] and [mime:mimeXml|http://www.w3.org/TR/wsdl#_mime:mimeXml] are not supported.
+[mime:multipartRelated](http://www.w3.org/TR/wsdl#_mime:multipartRelated), [mime:soap:body](http://www.w3.org/TR/wsdl#_mime:soap:body) and [mime:mimeXml|http://www.w3.org/TR/wsdl#_mime:mimeXml] are not supported.
Considering how unsuitable WSDL 1.1 HTTP Binding is for a large majority of services -- especially RESTful services -- a set of extensions is available.
All the details you want to know are [here](wsdl-1.1-extensions-for-rest.html).
Modified: ode/site/trunk/content/wsdl-11.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/wsdl-11.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/wsdl-11.mdtext (original)
+++ ode/site/trunk/content/wsdl-11.mdtext Fri Dec 28 11:11:22 2012
@@ -1,4 +1,4 @@
Title: WSDL 1.1
-*WSDL 1.1* --- {excerpt}version 1.1 of the Web Services Description Language [specification](http://www.w3.org/TR/wsdl) from the [W3C|http://www.w3c.org]{excerpt}. Following the [WS-I Basic Profile 1.1], PXE uses the WSDL schema located at [http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd].
+*WSDL 1.1* --- {excerpt}version 1.1 of the Web Services Description Language [specification](http://www.w3.org/TR/wsdl) from the [W3C](http://www.w3c.org){excerpt}. Following the [WS-I Basic Profile 1.1], PXE uses the WSDL schema located at [http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd].
Modified: ode/site/trunk/content/xpath-extensions.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/xpath-extensions.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/xpath-extensions.mdtext (original)
+++ ode/site/trunk/content/xpath-extensions.mdtext Fri Dec 28 11:11:22 2012
@@ -1,5 +1,5 @@
Title: XPath Extensions
-Apache ODE extends the default XPath coverage provided by the [WS-BPEL](-ws-bpel-20.html) specification mostly by adding support for [XPath 2.0|http://www.w3.org/TR/xpath20/] and by offering a few utility extension functions to make some assignments easier.
+Apache ODE extends the default XPath coverage provided by the [WS-BPEL](-ws-bpel-20.html) specification mostly by adding support for [XPath 2.0](http://www.w3.org/TR/xpath20/) and by offering a few utility extension functions to make some assignments easier.
<a name="XPathExtensions-XPath2.0"></a>
### XPath 2.0
Modified: ode/site/trunk/content/xquery-extensions.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/xquery-extensions.mdtext?rev=1426454&r1=1426453&r2=1426454&view=diff
==============================================================================
--- ode/site/trunk/content/xquery-extensions.mdtext (original)
+++ ode/site/trunk/content/xquery-extensions.mdtext Fri Dec 28 11:11:22 2012
@@ -3,7 +3,7 @@ Title: XQuery Extensions
XQuery is available only in ODE 1.3 or later
</div>
-Apache ODE goes above and beyond the [WS-BPEL](-ws-bpel-20.html) specification by allowing the use of [XQuery 1.0|http://www.w3.org/TR/xquery/] in queries and expressions.
+Apache ODE goes above and beyond the [WS-BPEL](-ws-bpel-20.html) specification by allowing the use of [XQuery 1.0](http://www.w3.org/TR/xquery/) in queries and expressions.
Unless specified otherwise, WS-BPEL considers XPath 1.0 to be the query/expression language, which is denoted by the default value of the "queryLanguage" and "expressionLanguage" attributes, viz. "urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0". In addition, we have out-of-the-box support for XPath 2.0.