| Namespace | http://www.mulesoft.org/schema/mule/pubsubhubbub |
|---|---|
| Schema Location | http://www.mulesoft.org/schema/mule/pubsubhubbub/3.2/mule-pubsubhubbub.xsd |
| Version | 3.2 |
| Minimum Mule Version | 3.2 |
Allows Mule to act as a PubSubHubbub (aka PuSH) hub. Pubsubhubbub is a simple, open, web-hook-based pubsub protocol &
open source reference implementation.
This module implements the PubSubHubbub Core 0.3 -- Working Draft
specification, except 7.5 Aggregated
Content Distribution.
| Configuration | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Configure an instance of this module
| |||||||||||
| Message Processors | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Handle all hub requests.
| |||||||||||
To use the this module within a flow the namespace to the module must be included. The resulting flow will look similar to the following:
<mule xmlns="http://www.mulesoft.org/schema/mule/core"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:pubsubhubbub="http://www.mulesoft.org/schema/mule/pubsubhubbub"
xsi:schemaLocation="
http://www.mulesoft.org/schema/mule/core
http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/pubsubhubbub
http://www.mulesoft.org/schema/mule/pubsubhubbub/3.2/mule-pubsubhubbub.xsd">
<!-- here goes your flows and configuration elements -->
</mule>
This module is configured using the config element. This element must be placed outside of your flows and at the root of your Mule application. You can create as many configurations as you deem necesary as long as each carries its own name.
Each message processor, message source or transformer carries a config-ref attribute that allows the invoker to specify which configuration to use.
| Attributes | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Type | Name | Default Value | Description | Optional. Give a name to this configuration so it can be later referenced. | |||||||
| 604800 | Optional. The default lease time in milliseconds. | ||||||||||
| Any implementation of PartitionableObjectStore can be used as a back-end for the hub. | |||||||||||
| 12 | Optional. The retry count. | ||||||||||
| 300000 | Optional. The retry frequency in milliseconds. | ||||||||||
Handle all hub requests.
INCLUDE_ERROR
| Optional. Specify which configuration to use. | ||
| The message payload |
||
| The outbound/response headers |
| MuleException |
|
| DecoderException | |
| MuleException |