[CONF] Apache Camel > Netty

[confluence]

Netty Page edited by Ashwin Karpe Netty Component Available as of Camel 2.3 See also the Apache Mina component The netty component in Camel is a socket communication component, based on the JBoss Netty community offering (available under an Apache 2.0 license). Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. Netty greatly simplifies and streamlines network programming such as TCP and UDP socket server. This camel component supports both producer and consumer endpoints. The netty component has several options and allows fine-grained control of a number of TCP/UDP communication parameters (buffer sizes, keepAlives, tcpNoDelay etc) and facilitates both In-Only and In-Out communication on a Camel route. Maven users will need to add the following dependency to their pom.xml for this component: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-netty</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> URI format The URI scheme for a netty component is as follows netty:tcp://localhost:99999[?options] netty:udp://remotehost:99999/[?options] This component supports producer and consumer endpoints for both TCP and UDP. You can append query options to the URI in the following format, ?option=value&option=value&... Options Name Default Value Description keepAlive true boolean setting to ensure socket is not closed due to inactivity tcpNoDelay true boolean setting to improve TCP protocol performance broadcast false boolean setting to choose Multicast over UDP connectTimeoutMillis 10 seconds time to wait for a socket connection to be available receiveTimeoutMillis 10 seconds time to wait for a response to be received on a connection reuseAddress true boolean setting to facilitate socket multiplexing sync false boolean setting to set endpoint as one-way or request-response ssl false boolean setting to specify whether SSL encrytion is applied to this endpoint sendBufferSize 65536 bytes the TCP/UDP buffer sizes to be used during outbound communication receiveBufferSize 65536 bytes tthe TCP/UDP buffer sizes to be used during inbound communication corePoolSize 10 threads the number of allocated threads at component startup. Defaults to 10 maxPoolSize 100 threads the maximum number of threads that may be allocated to this endpoint. Defaults to 100 Registry based Options Codec Handlers and SSL Keystores can be set via a JNDI Registry that is associated with the Camel Context. The values that could be passed in, are the following Name Description passphrase password setting to use in order to encrypt/decrypt payloads sent using SSH keyStoreFile Client side certificate keystore to be used for encryption trustStoreFile Server side certificate keystore to be used for encryption sslHandler Reference to a class that could be used to return an SSL Handler encoder A custom Handler class that can be used to perform special marshalling of outbound payloads. Must override org.jboss.netty.channel.ChannelDownStreamHandler decoder A custom Handler class that can be used to perform special marshalling of inbound payloads. Must override org.jboss.netty.channel.ChannelUpStreamHandler handler A custom Handler class that can be used to perform custom processing of Netty events triggered during communication. Must override org.jboss.netty.channel.SimpleChannelHandler Sending Messages to/from a Netty endpoint Netty Producer In Producer mode, the component provides the ability to send payloads to a socket endpoint using either TCP or UDP protocols (with optional SSL support). The producer mode supports both one-way and request-response based operations. Netty Consumer In Consumer mode, the component provides the ability to listen on a specified socket using either TCP or UDP protocols (with optional SSL support), receive requests on the socket using text/xml, binary and serialized object based payloads and send them along on a route as message exchanges. The consumer mode supports both one-way and request-response based operations. Usage Samples Example 1: A UDP based Netty consumer endpoint supporting Request-Reply communication and serialized Object payload RouteBuilder builder = new RouteBuilder() { public void configure() { from("netty:udp://localhost:5155?sync=true") .process(new Processor() { public void process(Exchange exchange) throws Exception { Poetry poetry = (Poetry) exchange.getIn().getBody(); poetry.setPoet("Dr. Sarojini Naidu"); exchange.getOut().setBody(poetry); } } } }; Example 2: A TCP based Netty consumer endpoint supporting One-way communication RouteBuilder builder = new RouteBuilder() { public void configure() { from("netty:tcp://localhost:5150") .to("mock:result"); } }; Example 3: An SSL/TCP based Netty consumer endpoint supporting Request-Reply communication JndiRegistry registry = new JndiRegistry(createJndiContext()); registry.bind("password", "changeit"); registry.bind("keyStoreFile", new File("src/test/resources/keystore.jks")); registry.bind("trustStoreFile", new File("src/test/resources/keystore.jks")); context.createRegistry(registry); context.addRoutes(new RouteBuilder() { public void configure() { from("netty:tcp://localhost:5150sync=true&ssl=true&passphrase=#password&keyStoreFile=#ksf&trustStoreFile=#tsf") .process(new Processor() { public void process(Exchange exchange) throws Exception { exchange.getOut().setBody("When You Go Home, Tell Them Of Us And Say, For Your Tomorrow, We Gave Our Today."); } } } }); Change Notification Preferences View Online | View Change | Add Comment