You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2009/03/23 11:51:50 UTC

[jira] Assigned: (DIRMINA-237) Improve Spring integration

     [ https://issues.apache.org/jira/browse/DIRMINA-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashish Paliwal reassigned DIRMINA-237:
--------------------------------------

    Assignee: Ashish Paliwal

> Improve Spring integration
> --------------------------
>
>                 Key: DIRMINA-237
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-237
>             Project: MINA
>          Issue Type: Improvement
>    Affects Versions: 0.9.4
>            Reporter: Niklas Therning
>            Assignee: Ashish Paliwal
>            Priority: Minor
>             Fix For: 3.0.0-M1
>
>
> The Spring integration module is in need of an overhaul. There are some things that aren't that simple to configure like the default IoService config. Also, Spring 2.0 is due to be released very soon. We should add support for the custom XML configuration feature introduced with Spring 2.0. That would let users write things like (just brainstorming here):
> <mina:acceptor type="socket" tcpNoDelay="true" reuseAddress="true" threadPoolMaxSize="20" threadPoolKeepAlive="30000">
>   <mina:bind address=":23" handler="telnetHandler"/>
>   <mina:bind address=":80" handler="httpHandler"/>
>   <mina:bind address=":443" handler="httpHandler">
>     <mina:filter ref="sslFilter"/>
>   </mina:binding>
> </mina:acceptor>
> Of course, we should still support and make life easier for people who don't use Spring 2.0.
> I'd like to know what people using the Spring integration think should be made to make it easier to use. Please add your comments to this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.