Author: vanto
Date: Mon Dec 31 15:49:17 2012
New Revision: 1427156
URL: http://svn.apache.org/viewvc?rev=1427156&view=rev
Log:
formatting tweaks.
Modified:
ode/site/trunk/content/direct-process-to-process-communication.mdtext
ode/site/trunk/content/endpoint-references.mdtext
ode/site/trunk/content/extensions/wsdl-11-extensions-for-rest.mdtext
ode/site/trunk/content/instance-data-cleanup.mdtext
ode/site/trunk/content/ode-jbi-and-axis2-properties-overview.mdtext
ode/site/trunk/content/wsdl-11-http-binding-support.mdtext
Modified: ode/site/trunk/content/direct-process-to-process-communication.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/direct-process-to-process-communication.mdtext?rev=1427156&r1=1427155&r2=1427156&view=diff
==============================================================================
--- ode/site/trunk/content/direct-process-to-process-communication.mdtext
(original)
+++ ode/site/trunk/content/direct-process-to-process-communication.mdtext Mon
Dec 31 15:49:17 2012
@@ -1,2 +1,5 @@
Title: Direct Process-to-Process Communication
-ODE automatically optimizes all process-to-process communication such that all
message exchanges happen directly inside the engine and do not go through the
integration layer (e.g. Axis2, JBI, ...).
+Category: documentation
+
+# P2P Communication
+ODE automatically optimizes all process-to-process (P2P) communication such
that all message exchanges happen directly inside the engine and do not go
through the integration layer (e.g. Axis2, JBI, ...).
Modified: ode/site/trunk/content/endpoint-references.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/endpoint-references.mdtext?rev=1427156&r1=1427155&r2=1427156&view=diff
==============================================================================
--- ode/site/trunk/content/endpoint-references.mdtext (original)
+++ ode/site/trunk/content/endpoint-references.mdtext Mon Dec 31 15:49:17 2012
@@ -1,11 +1,13 @@
Title: Endpoint References
+Category: documentation
+
<a name="EndpointReferences-Introduction"></a>
-### Introduction
+## Introduction
An endpoint reference holds information to call a service. The simplest
endpoint reference is usually an URL but it can also be much more complex such
as holding a message id, a reply-to address or custom properties.
In BPEL, endpoint references (aka EPRs) are modeled as partner link roles.
When defining a partner link, two roles maybe defined, `myRole` and
`partnerRole`:
-
+ :::xml
<partnerLink name="responderPartnerLink"
partnerLinkType="test:ResponderPartnerLinkType"
myRole="main" partnerRole="responder"
initializePartnerRole="yes"/>
@@ -13,10 +15,10 @@ In BPEL, endpoint references (aka EPRs)
Both `partnerRole` and `myRole` represent EPRs. So when assigning partner link
roles or invoking partners, you are using EPRs behind the scene.
<a name="EndpointReferences-ODEandEndpointReferences"></a>
-### ODE and Endpoint References
+## ODE and Endpoint References
<a name="EndpointReferences-TypesofEPRs"></a>
-#### Types of EPRs
+### Types of EPRs
The ODE runtime supports 4 types of EPRs:
@@ -116,7 +118,7 @@ Normally BPEL requires wrapping EPRs wit
You can just as well assign EPRs to/from variables to pass them around and
enable more dynamic communication patterns.
<a name="EndpointReferences-PassingEndpointReferences"></a>
-### Passing Endpoint References
+## Passing Endpoint References
To pass endpoint references around and manipulate them, you usually need to
assigne them to variables. The EPR can then be sent in a message and reassigned
to another partner link. This lets you model complex scenarii where you don't
know the address of your partner beforehand or where you select one partner
among many others.
Modified: ode/site/trunk/content/extensions/wsdl-11-extensions-for-rest.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/extensions/wsdl-11-extensions-for-rest.mdtext?rev=1427156&r1=1427155&r2=1427156&view=diff
==============================================================================
--- ode/site/trunk/content/extensions/wsdl-11-extensions-for-rest.mdtext
(original)
+++ ode/site/trunk/content/extensions/wsdl-11-extensions-for-rest.mdtext Mon
Dec 31 15:49:17 2012
@@ -1,4 +1,5 @@
Title: WSDL 1.1 Extensions for REST
+Category: documentation
## Overview
Modified: ode/site/trunk/content/instance-data-cleanup.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/instance-data-cleanup.mdtext?rev=1427156&r1=1427155&r2=1427156&view=diff
==============================================================================
--- ode/site/trunk/content/instance-data-cleanup.mdtext (original)
+++ ode/site/trunk/content/instance-data-cleanup.mdtext Mon Dec 31 15:49:17 2012
@@ -1,8 +1,9 @@
Title: Instance Data Cleanup
+Category: documentation
+
<a name="InstanceDataCleanup-Rational"></a>
## Rational
-
During its execution, a process instance can accumulate a significant amount
of data. The running process itself isn't that much of an issue, when the
instance is done there's nothing left to execute. But the process data can be
rather big, mostly because of the messages it received and sent and its own
variables. All of these are XML documents and in some cases, sizable ones.
<a name="InstanceDataCleanup-Levelsofcleanup"></a>
@@ -11,9 +12,10 @@ During its execution, a process instance
<a name="InstanceDataCleanup-Cleanuponcompletion"></a>
### Cleanup on completion
-{panel}
-This feature is only available in ODE 1.3 or later
-{panel}
+<div class="alert alert-info">
+ <h4 class="alert-heading">ODE Version</h4>
+ This feature is only available in ODE 1.3 or later
+</div>
The easiest approach to get started is simply to wait until the instance
execution is finished and then cleanup everything that's related to it. That
would include the instance state with its variables, scopes and correlation,
but also all the messages it has received and sent. Execution events should
also be disposed of. So this description defines 5 different categories:
instance, messages and events. We should be able to turn on and off each level
separately.
@@ -23,40 +25,39 @@ The easiest approach to get started is s
* correlations: ODE_CORRELATION_SET, ODE_CORSET_PROP
* events: ODE_EVENTS
-<a name="InstanceDataCleanup-dtd"></a>
-#### dtd
+<div class="caption">DTD</div>
- <xs:element name="cleanup" minOccurs="0" maxOccurs="3"
type="dd:tCleanup" />
-
- <xs:complexType name="tCleanup">
- <xs:sequence>
- <xs:element name="category" default="all" minOccurs="0"
maxOccurs="unbounded">
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration
value="instance" />
- <xs:enumeration
value="variables" />
- <xs:enumeration
value="messages" />
- <xs:enumeration
value="correlations" />
- <xs:enumeration value="events"
/>
- <xs:enumeration value="all" />
- </xs:restriction>
- </xs:simpleType>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="on" use="required">
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value="success" />
- <xs:enumeration value="failure" />
- <xs:enumeration value="always" />
- </xs:restriction>
- </xs:simpleType>
- </xs:attribute>
- </xs:complexType>
+ <xs:element name="cleanup" minOccurs="0" maxOccurs="3" type="dd:tCleanup"
/>
+
+ <xs:complexType name="tCleanup">
+ <xs:sequence>
+ <xs:element name="category" default="all" minOccurs="0"
maxOccurs="unbounded">
+ <xs:simpleType>
+ <xs:restriction base="xs:string">
+ <xs:enumeration value="instance" />
+ <xs:enumeration value="variables" />
+ <xs:enumeration value="messages" />
+ <xs:enumeration value="correlations" />
+ <xs:enumeration value="events" />
+ <xs:enumeration value="all" />
+ </xs:restriction>
+ </xs:simpleType>
+ </xs:element>
+ </xs:sequence>
+ <xs:attribute name="on" use="required">
+ <xs:simpleType>
+ <xs:restriction base="xs:string">
+ <xs:enumeration value="success" />
+ <xs:enumeration value="failure" />
+ <xs:enumeration value="always" />
+ </xs:restriction>
+ </xs:simpleType>
+ </xs:attribute>
+ </xs:complexType>
<a name="InstanceDataCleanup-examples"></a>
-#### examples
+## Examples
1. no instance data cleanup
@@ -135,7 +136,7 @@ The easiest approach to get started is s
<a name="InstanceDataCleanup-FutureDevelopments"></a>
-### Future Developments
+## Future Developments
WS-BPEL makes heavy use of scopes, those could be another hook in the
execution lifecycle for the cleanup to take place. So instead of waiting until
the instance is finished and clean up the whole state, we could proceed by
smaller increments and delete the state scope by scope. For short running
processes (say less than a few days) the advantages of this approach are
minimal but for long running processes (say months), there's potentially a lot
of unused state that's just sitting there and will never be used anymore.
Modified: ode/site/trunk/content/ode-jbi-and-axis2-properties-overview.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/ode-jbi-and-axis2-properties-overview.mdtext?rev=1427156&r1=1427155&r2=1427156&view=diff
==============================================================================
--- ode/site/trunk/content/ode-jbi-and-axis2-properties-overview.mdtext
(original)
+++ ode/site/trunk/content/ode-jbi-and-axis2-properties-overview.mdtext Mon Dec
31 15:49:17 2012
@@ -1,4 +1,6 @@
-Title: ODE Jbi and Axis2 properties overview
+Title: ODE JBI and Axis2 properties overview
+Category: documentation
+
<a name="ODEJbiandAxis2propertiesoverview-Introduction"></a>
## Introduction
ode-axis2.properties and ode-jbi.properties are used for engine configuration.
@@ -7,7 +9,7 @@ ode-axis2.properties and ode-jbi.propert
## Common properties
Here, ode-jbi prefix is used. However for axis2, you need to replace it into
ode-axis2.
-
+ :::properties
# Database Mode ("INTERNAL", "EXTERNAL", "EMBEDDED")
# What kind of database should ODE use?
# * "EMBEDDED" - ODE will create its own embbeded database (Derby)
@@ -84,7 +86,7 @@ Here, ode-jbi prefix is used. However fo
## ode-axis2.properties
To configure those properties, please put ode-axis2.properties file in
webapps/ode/WEB-INF/conf directory.
-
+ :::properties
# HTTP connection pool used to invoke external services
ode-axis2.http.connection-manager.max-per-host=100
ode-axis2.http.connection-manager.max-total=100
@@ -107,7 +109,7 @@ To configure those properties, please pu
For JBI distribution, those properties are zipped into Service Assembly.
For SMX4 OSGi bundle distribution, those are in
SMX4/etc/org.apache.ode.jbi.cfg file.
-
+ :::properties
# Process Identifier Namespace [QNAME]
# Namespace for processes created using the JBI integration.
# This will be the namespace of the process identifiers (PIDs)
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=1427156&r1=1427155&r2=1427156&view=diff
==============================================================================
--- ode/site/trunk/content/wsdl-11-http-binding-support.mdtext (original)
+++ ode/site/trunk/content/wsdl-11-http-binding-support.mdtext Mon Dec 31
15:49:17 2012
@@ -1,4 +1,7 @@
Title: WSDL 1.1 HTTP Binding Support
+Category: documentation
+
+## HTTP Binding
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:
