<?xml version="1.0" encoding="UTF-8" standalone="no"?> <xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/atom" xmlns="http://www.mulesoft.org/schema/mule/atom" xmlns:beans="http://www.springframework.org/schema/beans" xmlns:mule="http://www.mulesoft.org/schema/mule/core" xmlns:schemadoc="http://www.mulesoft.org/schema/mule/schemadoc" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:import namespace="http://www.springframework.org/schema/beans" schemaLocation="http://www.springframework.org/schema/beans"/> <xsd:import namespace="http://www.mulesoft.org/schema/mule/core" schemaLocation="http://www.mulesoft.org/schema/mule/core/3.1/mule.xsd"/> <xsd:import namespace="http://www.mulesoft.org/schema/mule/schemadoc" schemaLocation="http://www.mulesoft.org/schema/mule/schemadoc/3.1/mule-schemadoc.xsd"/> <xsd:annotation> <xsd:documentation> The Mule ATOM support makes it possible to integrate easily with Atom feeds and Atom Publishing Protocol servers via the Apache Abdera project. </xsd:documentation> <xsd:appinfo> <schemadoc:short-name>ATOM</schemadoc:short-name> <schemadoc:page-title>ATOM Module</schemadoc:page-title> <schemadoc:transport-features dispatchEvents="true" receiveEvents="true" requestEvents="true" streaming="true" transactions="false"> <schemadoc:MEPs default="one-way" supported="one-way"/> </schemadoc:transport-features> </xsd:appinfo> </xsd:annotation> <xsd:annotation> <xsd:documentation> Allows ATOM requests to be filtered by request path and HTTP verb. The route attribute defines a type of URI Template loosely based on Ruby on Rails style Routes. For example: "feed" or ":feed/:entry". For reference, see the Ruby On Rails routing http://guides.rubyonrails.org/routing.html </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexContent> <xsd:annotation> <xsd:documentation> The URI request path made for an ATOM request. This matches against the path of the request URL. The route attribute defines a type of URI Template loosely based on Ruby on Rails style Routes. For example: "feed" or ":feed/:entry". For reference, see the Ruby On Rails routing http://guides.rubyonrails.org/routing.html </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> A comma-separated list of HTTP verbs that will be accepted by this filter. By default all verbs are accepted. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="entry-last-updated-filter" substitutionGroup="mule:abstract-filter" type="entryLastUpdateFilterType"> <xsd:annotation> <xsd:documentation> Will filter ATOM entry objects based on their last update date. This is useful for filtering older entries from the feed. This filter works only on Atom Entry objects not Feed objects. Typically it is better to set the lastUpdated attribute on an inbound ATOM endpoint rather than use this filter, however, this filter can be used elsewhere in a flow. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexContent> <xsd:annotation> <xsd:documentation> The date from which to filter events from. Any entries that were last updated before this date will not be accepted. The date format is The format for the date is is: yyyy-MM-dd hh:mm:ss, for example 2008-12-25 13:00:00. If only the date is important you can omit the time part. You can set the value to 'now' to set the date and time that the server is started. Do not set this attribute if you want to receive all available entries then any new entries going forward. This is the default behaviour and suitable for many scenarios. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Whether an entry should be accepted if it doesn't have a Last Update date set. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="feed-last-updated-filter" substitutionGroup="mule:abstract-filter" type="feedLastUpdateFilterType"> <xsd:annotation> <xsd:documentation> Will filter the whole ATOM Feed based on its last update date. This is useful for processing a feed that has not been updated since a specific date. This filter works only on Atom Feed objects. Typically it is better to set the lastUpdated attribute on an inbound ATOM endpoint with splitFeed=false rather than use this filter, however, this filter can be used elsewhere in a flow. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexContent> <xsd:annotation> <xsd:documentation> The date from which to filter events from. Any entries that were last updated before this date will not be accepted. The date format is The format for the date is is: yyyy-MM-dd hh:mm:ss, for example 2008-12-25 13:00:00. If only the date is important you can omit the time part. You can set the value to 'now' to set the date and time that the server is started. Do not set this attribute if you want to receive all available entries then any new entries going forward. This is the default behaviour and suitable for many scenarios. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Whether a Feed should be accepted if it doesn't have a Last Update date set. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:annotation> <xsd:documentation> Represents an Abdera component. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="feed-splitter" substitutionGroup="mule:abstract-intercepting-message-processor" type="mule:baseSplitterType"> <xsd:annotation> <xsd:documentation> Will split the entries of a feed into single entry objects. Each entry will be a separate message in Mule. By default the inbound endpoint will split the feed automatically. The only time this splitter will be useful is when you explicitly request that the feed is not split, but then you want to split it later in the flow or if the endpoint serving the feed is not an Atom endpoint, for example receiving a feed over JMS. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexContent> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:attributeGroup> <xsd:element name="entry-builder-transformer" substitutionGroup="mule:abstract-transformer" type="entryBuilderTransformerType"> <xsd:annotation> <xsd:documentation> A transformer that uses expressions to configure an Atom Entry. The user can specify one more expressions that are used to configure properties on the bean. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexContent> <xsd:sequence maxOccurs="unbounded" minOccurs="1"> <xsd:complexType> <xsd:annotation> <xsd:documentation> The name of the atom property </xsd:documentation> </xsd:annotation> <xsd:simpleType> <xsd:enumeration value="content"/> <xsd:enumeration value="summary"/> <xsd:enumeration value="id"/> <xsd:enumeration value="title"/> <xsd:enumeration value="draft"/> <xsd:enumeration value="updated"/> <xsd:enumeration value="published"/> <xsd:enumeration value="edited"/> <xsd:enumeration value="author"/> <xsd:enumeration value="contributor"/> <xsd:enumeration value="link"/> <xsd:enumeration value="category"/> <xsd:enumeration value="rights"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> <xsd:annotation> <xsd:documentation> An optional expression means that if the expression evaluates to null, it will continue to the next expression without error. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="inbound-endpoint" substitutionGroup="mule:abstract-inbound-endpoint" type="inboundEndpointType"/> <xsd:complexContent> <xsd:annotation> <xsd:documentation> Whether the feed entries should be split before routing the data. If split the service component will be invoked for each entry in the feed. Otherwise the feed itself will be used as the data for the message. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Allows the endpoint to filter out any feed entries before the given date/time. This is only used if the feed is split. The format for the date is is: yyyy-MM-dd hh:mm:ss, for example 2008-12-25 13:00:00. If only the date is important you can omit the time part You can set the value to 'now' to set the date and time that the server is started Do not set this attribute if you want to receive all available entries then any new entries going forward. This is the default behaviour and suitable for many scenarios. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The frequency in milliseconds to check the feed for new entries. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:schema> |
XML schema documentation generated with DocFlex/XML SDK 1.8.1b6 using DocFlex/XML XSDDoc 2.2.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration. |