All Element Summary | ||||||||||||
connector |
|
|||||||||||
endpoint |
|
|||||||||||
inbound-endpoint |
|
|||||||||||
outbound-endpoint |
|
Complex Type Summary | ||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
Attribute Group Summary | ||||||||||
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/rmi" xmlns="http://www.mulesoft.org/schema/mule/rmi" 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.mulesoft.org/schema/mule/core" schemaLocation="http://www.mulesoft.org/schema/mule/core/3.3/mule.xsd"/> <xsd:import namespace="http://www.mulesoft.org/schema/mule/schemadoc" schemaLocation="http://www.mulesoft.org/schema/mule/schemadoc/3.3/mule-schemadoc.xsd"/> <xsd:annotation> <xsd:documentation> The RMI transport can be used to send and receive Mule events over JRMP. This transport has a dispatcher that invokes an RMI method and a polling receiver that repeatedly does the same. </xsd:documentation> <xsd:appinfo> <schemadoc:short-name>RMI</schemadoc:short-name> <schemadoc:page-title>RMI Transport</schemadoc:page-title> <schemadoc:transport-features dispatchEvents="true" receiveEvents="true" requestEvents="true" streaming="false" transactions="false"> <schemadoc:MEPs default="request-response" supported="one-way, request-response"/> </schemadoc:transport-features> </xsd:appinfo> </xsd:annotation> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:complexContent> <xsd:annotation> <xsd:documentation> Period (ms) between polling connections. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Bean reference to the security manager that should be used. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The security policy (file name) used to enable connections. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The target class name. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> <!-- is this correct?! serverCodebase is an odd name to identify a method! --> The target method. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="inbound-endpoint" substitutionGroup="mule:abstract-inbound-endpoint" type="inboundEndpointType"/> <xsd:complexContent> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="outbound-endpoint" substitutionGroup="mule:abstract-outbound-endpoint" type="outboundEndpointType"/> <xsd:complexContent> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="endpoint" substitutionGroup="mule:abstract-global-endpoint" type="globalEndpointType"/> <xsd:complexContent> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:annotation> <xsd:documentation> The endpoint host name. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The port number to use when a connection is made. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The class name of the object that is being invoked over RMI. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The name of the method to invoke. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Comma separated argument types of the method to invoke. For example, "java.lang.String". </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:attributeGroup> </xsd:schema> |
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. |