complexType "baseServiceType"
Namespace:
http://www.mulesoft.org/schema/mule/core
Content:
complex, 2 attributes, attr. wildcard, 8 elements
Defined:
globally in mule.xsd; see XML source
Includes:
definitions of 1 attribute, 7 elements
Used:
at 2 locations
Content Model Diagram
XML Representation Summary
<...
   
name
 = 
 (xsd:string)
initialState
 = 
 ("started" | "stopped" | "paused") : "started"
    {any attribute with non-schema namespace}
    >
   
Content: 
 annotations?, description?, inbound?, abstract-component?, outbound?, async-reply?, legacy-abstract-exception-strategy?, abstract-message-info-mapping?
</...>
Content Model Elements (8):
abstract-component, abstract-message-info-mapping, annotations, async-reply, description, inbound, legacy-abstract-exception-strategy, outbound
Known Direct Subtypes (2):
customServiceType, sedaServiceType
All Direct / Indirect Based Elements (2):
custom-service, service
Known Usage Locations
Annotation
Base support for a model-based wrapper around the POJO service (SEDA, Streaming, etc.)
Type Definition Detail
Type Derivation Tree
annotatedType (extension)
  abstractServiceType (extension)
      baseServiceType
XML Source (w/o annotations (8); see within schema source)
<xsd:complexType name="baseServiceType">
<xsd:complexContent>
<xsd:extension base="abstractServiceType">
<xsd:sequence>
<xsd:element minOccurs="0" name="description" type="descriptionType"/>
<xsd:element minOccurs="0" name="inbound" type="inboundCollectionType"/>
<!-- minOccurs="0" to allow for <forwarding-router/> and/or default component -->
<xsd:element minOccurs="0" ref="abstract-component"/>
<xsd:element minOccurs="0" name="outbound" type="outboundCollectionType"/>
<xsd:element minOccurs="0" name="async-reply" type="asyncReplyCollectionType"/>
<xsd:element minOccurs="0" ref="legacy-abstract-exception-strategy"/>
<xsd:element minOccurs="0" ref="abstract-message-info-mapping"/>
</xsd:sequence>
<xsd:attribute default="started" name="initialState">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="started"/>
<xsd:enumeration value="stopped"/>
<xsd:enumeration value="paused"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Attribute Detail (all declarations; defined within this component only; 1/3)
initialState
Type:
anonymous simpleType (restriction of xsd:NMTOKEN)
Use:
optional
The initial state of the service. Usually a service is started automatically ("started"), but this attribute can be used to disable initial startup ("stopped") or start the service in a paused state ("paused").
Attribute Value
enumeration of xsd:NMTOKEN
Enumeration:
 "started", "stopped", "paused"
Default:
"started"
Anonymous simpleType
Type Derivation Tree
xsd:NMTOKEN (restriction)
  simpleType
Derivation:
restriction of xsd:NMTOKEN
Facets:
enumeration:
"started", "stopped", "paused"
XML Source (w/o annotations (1); see within schema source)
<xsd:attribute default="started" name="initialState">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="started"/>
<xsd:enumeration value="stopped"/>
<xsd:enumeration value="paused"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
Content Element Detail (all declarations; defined within this component only; 7/8)
abstract-component
Type:
abstractComponentType, complex content
Abstract:
(may not be used directly in instance XML documents)
Subst.Gr:
affiliated to substitution group abstract-message-processor; may be substituted with 16 elements
The service component that is invoked when incoming messages are received. If this element is not present, the service simply bridges the inbound and outbound using a pass-through component.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" ref="abstract-component"/>
abstract-message-info-mapping
Type:
abstractMessageInfoMappingType, empty content
Abstract:
(may not be used directly in instance XML documents)
Subst.Gr:
may be substituted with 2 elements
The message info mapper used to extract key bits of the message information, such as Message ID or Correlation ID. these properties are used by some routers and this mapping information tells Mule where to get the information from in the current message.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" ref="abstract-message-info-mapping"/>
async-reply
Type:
asyncReplyCollectionType, complex content
The elements within 'async-reply' describe how asynchronous replies are handled.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="async-reply" type="asyncReplyCollectionType"/>
description
Type:
descriptionType, mixed content
This can hold any kind of documentation related to the service. It is intended to be "human readable" only and is not used by the system.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="description" type="descriptionType"/>
inbound
Type:
inboundCollectionType, complex content
The elements within 'inbound' describe how a service receives messages.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="inbound" type="inboundCollectionType"/>
legacy-abstract-exception-strategy
Type:
exceptionStrategyType, complex content
Abstract:
(may not be used directly in instance XML documents)
Subst.Gr:
may be substituted with 7 elements
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="legacy-abstract-exception-strategy"/>
outbound
Type:
outboundCollectionType, complex content
The elements within 'outbound' describe how a service sends or dispatches messages.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="outbound" type="outboundCollectionType"/>
XML schema documentation generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.0 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.