Schema "mule-ejb.xsd"

Target Namespace:

http://www.mulesoft.org/schema/mule/ejb

Defined Components:

4 global elements, 1 complexType

Default Namespace-Qualified Form:

Local Elements: qualified; Local Attributes: unqualified

Schema Location:

http://www.mulesoft.org/schema/mule/ejb/3.3/mule-ejb.xsd; see XML source

Imports Schemas (4):

mule-rmi.xsd [src], mule-schemadoc.xsd [src], mule.xsd [src], xml.xsd [src]

Imported by Schema:

_mule-all-included.xsd

Annotation

The EJB transport allows EJB session beans to be invoked as part of an event flow. Components can be given an EJB outbound endpoint, which will invoke the remote object and optionally return a result. The Javadoc for this transport can be found {javadoc:mule/transport/ejb}here{javadoc}.

All Element Summary

connector

The Mule EJB Connector provides connectivity for EJB beans.

Type:	ejbConnectorType
Content:	complex, 13 attributes, attr. wildcard, 8 elements
Subst.Gr:	may substitute for element mule:abstract-connector
Defined:	globally; see XML source
Used:	never

endpoint

Type:	rmi:globalEndpointType
Content:	complex, 16 attributes, attr. wildcard, 16 elements
Subst.Gr:	may substitute for element mule:abstract-global-endpoint
Defined:	globally; see XML source
Used:	never

inbound-endpoint

Type:	rmi:inboundEndpointType
Content:	complex, 16 attributes, attr. wildcard, 16 elements
Subst.Gr:	may substitute for element mule:abstract-inbound-endpoint
Defined:	globally; see XML source
Used:	never

outbound-endpoint

Type:	rmi:outboundEndpointType
Content:	complex, 16 attributes, attr. wildcard, 16 elements
Subst.Gr:	may substitute for element mule:abstract-outbound-endpoint
Defined:	globally; see XML source
Used:	never

Complex Type Summary

ejbConnectorType

Content:	complex, 13 attributes, attr. wildcard, 8 elements
Defined:	globally; see XML source
Includes:	definitions of 5 attributes
Used:	at 1 location

XML Source

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/ejb" xmlns="http://www.mulesoft.org/schema/mule/ejb" xmlns:mule="http://www.mulesoft.org/schema/mule/core" xmlns:rmi="http://www.mulesoft.org/schema/mule/rmi" 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:import namespace="http://www.mulesoft.org/schema/mule/rmi" schemaLocation="http://www.mulesoft.org/schema/mule/rmi/3.3/mule-rmi.xsd"/>

<xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>

<xsd:annotation>

<xsd:documentation>

The EJB transport allows EJB session beans to be invoked as part of an event flow. Components can be given an EJB outbound endpoint, which will invoke the remote object and optionally return a result.

The Javadoc for this transport can be found {javadoc:mule/transport/ejb}here{javadoc}.

</xsd:documentation>

<xsd:appinfo>

<schemadoc:short-name>EJB</schemadoc:short-name>

<schemadoc:page-title>EJB 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>

<schemadoc:additional-documentation where="before-specific-elements">

h2. Using the EJB Connector

EJB endpoints are configured the same way as [RMI endpoints|RMI Transport]. Note that only outbound endpoints can use the EJB transport. For a given endpoint, you must provide the following information:

- registry host
- registry port
- remote home name
- remote method name

These values will be used to establish the dispatcher connection. For example:
{code:xml}
<ejb:endpoint host="localhost" port="1099" object="SomeService" method="remoteMethod"/>
{code}

Alternatively, you could use URI-based configuration:
{code:xml}
<outbound-endpoint address="ejb://localhost:1099/SomeService?method=remoteMethod"/>
{code}

If the method can take one or more input arguments, you configure their types as a comma-separated list using the methodArgumentTypes attribute. Multiple arguments are passed in as an array of objects as the payload of the Mule event.

h2. Transformers

There are no specific transformers required for EJB.

</schemadoc:additional-documentation>

</xsd:appinfo>

</xsd:annotation>

<xsd:element name="connector" substitutionGroup="mule:abstract-connector" type="ejbConnectorType">

<xsd:annotation>

<xsd:documentation>

The Mule EJB Connector provides connectivity for EJB beans.

</xsd:documentation>

</xsd:annotation>

</xsd:element>

<xsd:complexType name="ejbConnectorType">

<xsd:complexContent>

<xsd:extension base="mule:jndiConnectorType">

<xsd:attribute name="pollingFrequency" type="mule:substitutableLong">

<xsd:annotation>

<xsd:documentation>

Period (ms) between polling connections.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="securityManager-ref" type="xsd:NMTOKEN">

<xsd:annotation>

<xsd:documentation>

Bean reference to the security manager that should be used.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="securityPolicy" type="xsd:string">

<xsd:annotation>

<xsd:documentation>

The security policy (file name) used to enable connections.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="serverClassName" type="xsd:NMTOKEN">

<xsd:annotation>

<xsd:documentation>

The target class name.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="serverCodebase" type="xsd:string">

<xsd:annotation>

<xsd:documentation>

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="rmi:inboundEndpointType"/>

<xsd:element name="outbound-endpoint" substitutionGroup="mule:abstract-outbound-endpoint" type="rmi:outboundEndpointType"/>

<xsd:element name="endpoint" substitutionGroup="mule:abstract-global-endpoint" type="rmi:globalEndpointType"/>

</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.