element <java-interface-binding> (local)
Namespace:
http://www.mulesoft.org/schema/mule/scripting
Type:
mule:pojoBindingType
Content:
complex, 2 attributes, 1 element
Defined:
locally witnin scriptComponentType complexType in mule-scripting.xsd; see XML source
Content Model Diagram
XML Representation Summary
<java-interface-binding
   
interface
 = 
 (xsd:string | xsd:string)
method
 = 
 xsd:anySimpleType
    >
   
Content: 
 mule:abstract-outbound-endpoint+
</java-interface-binding>
Content model elements (1):
mule:abstract-outbound-endpoint
Included in content model of elements (1):
component
May contain elements by substitutions (25):
mule:outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, outbound-endpoint, servlet-outbound-endpoint
Annotation
A binding associates a Mule endpoint with an injected Java interface (this is like using Spring to inject a bean, but instead of calling a method on the bean a message is sent to an endpoint). Script bindings will only work with Java-based scripting languages. Right now there is no validation on when languages support Java bindinngs because there are so many scripting languages.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="java-interface-binding" type="mule:pojoBindingType"/>
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.