Integrating Apache MINA with Spring
So far we have seen Apache MINA code samples in standalone form. Apache MINA can be nicely integrated into DI frameworks like Spring. Lets see how to integrate a simple MINA application with Spring
This is how our application is structure. To see details of this application, please refer to the post Implementing Trap Receiver in 30 minutes using Apache MINA
To integrate with Spring, we need to do following
- One Handler
- Two Filter – Logging Filter and a ProtocolCodec Filter
- NioDatagram Socket
This is how our code looks like for the standalone application
// Create an Acceptor NioDatagramAcceptor acceptor = new NioDatagramAcceptor(); // Add Handler acceptor.setHandler(new ServerHandler()); acceptor.getFilterChain().addLast("logging", new LoggingFilter()); acceptor.getFilterChain().addLast("codec", new ProtocolCodecFilter(new SNMPCodecFactory())); // Create Session Configuration DatagramSessionConfig dcfg = acceptor.getSessionConfig(); dcfg.setReuseAddress(true); logger.debug("Starting Server......"); // Bind and be ready to listen logger.debug("Server listening on "+DEFAULT_PORT); }
To integrate with Spring, we need to do following
- Set the IO handler
- Create the Filters and add to the chain
- Create the Socket and set Socket Parameters
NOTE: The latest MINA releases doesn’t have the package specific to Spring, like its earlier versions. The package is now named Integration Beans, to make the implementation work for all DI frameworks.
Lets see the Spring xml file. Please see that I have removed generic part from xml and have put only the specific things needed to pull up the implementation. This example has been derived from Chat example shipped with MINA release.
Now lets pull things together
- Lets set the IO Handler
- Lets create the Filter chain
- Lets complete the last part of creating the Socket and completing the chain

Here, we create instance of our IoFilter. See that for the ProtocolCodec factory, we have used Constructor injection. Logging Filter creation is straight forward. Once we have defined the beans for the filters to be used, we now create the Filter Chain to be used for the implementation. We define a bean with id “FilterChainBuidler” and add the defined filters to it. We are almost ready, and we just need to create the Socket and call bind
Now we create our ioAcceptor, set IO handler and Filter Chain. Now we have to write a function to read this file using Spring and start our application. Here’s the code
new ClassPathXmlApplicationContext("trapReceiverContext.xml"); }
We just call this method from main, and this shall initialize our MINA application. Will try to write a post using some other DI framework like Google Guice.
Reference:


Thanks for this example. It was invaluable in porting my mina-1.1.7 spring configuration over to 2.0.
Hi Ashish,
Thanks for the example. One question that has been vexing me for the past while that you may know the answer to. Do you know why the reuseAddress session config parameter no longer exposed when configuring an NioDatagramConnector/Acceptor ? Of course it is possible to set it programmatically by getting a hold of the DatagramSessionConfig from the acceptor/connector once created, however it makes it awkward from a spring config point of view.
Thanks,
Declan.
To be true, I don’t have an answer right now. Let me check and get back to you.
Hi Ashish
We need the chain filters in a certain order, so a Map is not appropriate !
By.
@serge
You don’t need to worry about this – Spring uses a LinkedHashMap implementation for map definitions by default which does retain definition order.
- Les
@Declan and Ashish,
Spring supports nested property configuration by using OGNL path expressions. For example, if you wanted to change the ‘tcpNoDelay’ property of the NioSocketAcceptor’s nested SessionConfig instance:
…
…
Naturally the default,no-arg constructor of whatever bean you’re instantiating must ensure that any beans referenced via a OGNL expression are non-null (the NioSocketAcceptor does indeed ensure this for its internal SessionConfig instance). No coding necessary
Using the nested property technique above, I think you can easily satisfy almost all of your Mina Spring-configuration needs.
Here is the Spring doco reference:
http://static.springsource.org/spring/docs/2.5.x/reference/beans.html#beans-compound-property-names
Regards,
Les
Oops – my XML example didn’t show correctly. Let’s try again with brackets instead:
[bean class="org.apache.mina.transport.socket.nio.NioSocketAcceptor"
init-method="bind" destroy-method="unbind"/]
…
[property name="sessionConfig.tcpNoDelay" value="true"/]
…
[/bean]
Ashish, please feel free to edit/consolidate my comments so this shows proper XML if you have the ability to do so.
Regards,
Les
I see this is an old post but nevertheless, would it be possible to provide a simple example how to integrate mina app with webbap using guice so it would run on tomcat? Webapp already uses guice and as author suggested he could write a howto – I would very much appreciate just the vital example of it.
Regards,
A good suggestion. Its been on my to-do list for long, let me see how soon can I make it to MINA User Guide
I was wondering if it might be possible to integrate the above code into a Spring based MVC webapp running on Tomcat or websphere
Great article. Thanks.
Is it possible to use spring security while TCP/IP commnuication using MINA, if yes then how ? please help me.
I have no clue how this can be done. Probably you need to implement a IoFilter that does the job for you, by integrating with Spring security API’s. Or look at existing integrations and tweak them to use your IoFilter.
Please do share your findings.
Good Luck !
Hi,
I am unable to find example with SocketConnector with Spring. What would it look like?
Kind regards,
-Vid-