Contact Us 1-800-596-4880

RMI Transport Reference

Mule Runtime Engine versions 3.5, 3.6, and 3.7 reached End of Life on or before January 25, 2020. For more information, contact your Customer Success Manager to determine how you can migrate to the latest Mule version.

The Java Remote Message Invocation (RMI) transport sends and receives Mule events over Java Remote Method Protocol (JRMP). This transport has a dispatcher that invokes an RMI method and a polling receiver that repeatedly does the same.

You configure the RMI transport as follows:

Note: In the code examples in this guide, spring-beans-current.xsd is a placeholder. To locate the correct version, see http://www.springframework.org/schema/beans/.

The connector looks for the method and methodArgumentTypes. It uses the payload as the argument.

JNP Connector

If you want to use the Java naming protocol to bind to remote objects, you can use the JNP connector instead simply by using the jnp namespace.

Configuration Reference

Connector

Table 1. Attributes of <connector…​>
Name Type Required Default Description

pollingFrequency

long

no

Period (ms) between polling connections.

securityManager-ref

string

no

Bean reference to the security manager that should be used.

securityPolicy

string

no

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

serverClassName

string

no

The target class name.

serverCodebase

string

no

The target method.

Table 2. Child Elements of <connector…​>
Name Cardinality Description

Endpoint

Table 3. Attributes of <endpoint…​>
Name Type Required Default Description

host

string

no

The endpoint host name.

port

port number

no

The port number to use when a connection is made.

object

string

no

The class name of the object that is being invoked over RMI.

method

string

no

The name of the method to invoke.

methodArgumentTypes

string

no

Comma separated argument types of the method to invoke. For example, "java.lang.String".

Table 4. Child Elements of <endpoint…​>
Name Cardinality Description