You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/09/13 08:10:33 UTC

[jira] Resolved: (JAMES-1044) SpringProtocolHandlerChain does not load handlers correctly when the same handler is used for different ProtocolHandlerChain instances

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

Norman Maurer resolved JAMES-1044.
----------------------------------

    Resolution: Fixed

fixed

> SpringProtocolHandlerChain does not load handlers correctly when the same handler is used for different ProtocolHandlerChain instances
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JAMES-1044
>                 URL: https://issues.apache.org/jira/browse/JAMES-1044
>             Project: JAMES Server
>          Issue Type: Bug
>            Reporter: Norman Maurer
>            Assignee: Norman Maurer
>             Fix For: 3.0-M1
>
>
> After introducing the NioLMTPServer I noticed that SpringProtocolHandlerChain does not load the currect handlers for NioSMTPServer anymore. This is caused because NioLMTPServer reuse many classes for NioSMTPServer and SpringProcolHandlerChain will only use the classname to detect the right Bean to return. 
> We need to make sure that the same classes could be reused b different SpringProtocolHandlerChain instances

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


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org