[CONF] Apache Camel > RMI

[confluence]

RMI Page edited by willem jiang RMI Component The rmi: component binds PojoExchanges to the RMI protocol (JRMP). Since this binding is just using RMI, normal RMI rules still apply regarding what methods can be invoked. This component supports only PojoExchanges that carry a method invocation from an interface that extends the Remote interface. All parameters in the method should be either Serializable or Remote objects. Maven users will need to add the following dependency to their pom.xml for this component: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-rmi</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> URI format rmi://rmi-regisitry-host:rmi-registry-port/registry-path[?options] For example: rmi://localhost:1099/path/to/service You can append query options to the URI in the following format, ?option=value&option=value&... Options Name Default Value Description method null As of Camel 1.3, you can set the name of the method to invoke. Using To call out to an existing RMI service registered in an RMI registry, create a route similar to the following: from("pojo:foo").to("rmi://localhost:1099/foo"); To bind an existing camel processor or service in an RMI registry, define an RMI endpoint as follows: RmiEndpoint endpoint= (RmiEndpoint) endpoint("rmi://localhost:1099/bar"); endpoint.setRemoteInterfaces(ISay.class); from(endpoint).to("pojo:bar"); Note that when binding an RMI consumer endpoint, you must specify the Remote interfaces exposed. See Also Configuring Camel Component Endpoint Getting Started Change Notification Preferences View Online | View Change | Add Comment