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:21:12 UTC
svn commit: r1426457 - in /ode/site/trunk/content: assign.mdtext faq.mdtext
management-api.mdtext pxe-deploy-command.mdtext receive.mdtext
sendsoap-command.mdtext wsdl-11-extensions-for-rest.mdtext
wsdl-11-http-binding-support.mdtext
Author: vanto
Date: Fri Dec 28 11:21:12 2012
New Revision: 1426457
URL: http://svn.apache.org/viewvc?rev=1426457&view=rev
Log:
more conversions of conluence links to markdown links.
Modified:
ode/site/trunk/content/assign.mdtext
ode/site/trunk/content/faq.mdtext
ode/site/trunk/content/management-api.mdtext
ode/site/trunk/content/pxe-deploy-command.mdtext
ode/site/trunk/content/receive.mdtext
ode/site/trunk/content/sendsoap-command.mdtext
ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext
ode/site/trunk/content/wsdl-11-http-binding-support.mdtext
Modified: ode/site/trunk/content/assign.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/assign.mdtext?rev=1426457&r1=1426456&r2=1426457&view=diff
==============================================================================
--- ode/site/trunk/content/assign.mdtext (original)
+++ ode/site/trunk/content/assign.mdtext Fri Dec 28 11:21:12 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)}}
Modified: ode/site/trunk/content/faq.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/faq.mdtext?rev=1426457&r1=1426456&r2=1426457&view=diff
==============================================================================
--- ode/site/trunk/content/faq.mdtext (original)
+++ ode/site/trunk/content/faq.mdtext Fri Dec 28 11:21:12 2012
@@ -79,7 +79,7 @@ __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.
Modified: ode/site/trunk/content/management-api.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/management-api.mdtext?rev=1426457&r1=1426456&r2=1426457&view=diff
==============================================================================
--- ode/site/trunk/content/management-api.mdtext (original)
+++ ode/site/trunk/content/management-api.mdtext Fri Dec 28 11:21:12 2012
@@ -3,13 +3,13 @@ ODE has a complete management API to che
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/pxe-deploy-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/pxe-deploy-command.mdtext?rev=1426457&r1=1426456&r2=1426457&view=diff
==============================================================================
--- ode/site/trunk/content/pxe-deploy-command.mdtext (original)
+++ ode/site/trunk/content/pxe-deploy-command.mdtext Fri Dec 28 11:21:12 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/receive.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/receive.mdtext?rev=1426457&r1=1426456&r2=1426457&view=diff
==============================================================================
--- ode/site/trunk/content/receive.mdtext (original)
+++ ode/site/trunk/content/receive.mdtext Fri Dec 28 11:21:12 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/sendsoap-command.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/sendsoap-command.mdtext?rev=1426457&r1=1426456&r2=1426457&view=diff
==============================================================================
--- ode/site/trunk/content/sendsoap-command.mdtext (original)
+++ ode/site/trunk/content/sendsoap-command.mdtext Fri Dec 28 11:21:12 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/wsdl-11-extensions-for-rest.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/wsdl-11-extensions-for-rest.mdtext?rev=1426457&r1=1426456&r2=1426457&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:21:12 2012
@@ -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}
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=1426457&r1=1426456&r2=1426457&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:21:12 2012
@@ -4,7 +4,7 @@ Actually only the following [MIME types]
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).