[ http://issues.apache.org/jira/browse/DIRMINA-118?page=all ]
Niklas Therning resolved DIRMINA-118:
-------------------------------------
Resolution: Fixed
When searching for a MessageHandler for a given message object the superclass
will now be searched recursively when no match can be found for the immediate
message class or any of the interfaces implemented by the immediate message
class. For efficiency reasons matches will be cached. The cache is cleared on
calls to addMessageHandler and removeMessageHandler.
> DemuxingIoHandler should look up super classes, too, and cache the lookup
> results.
> ----------------------------------------------------------------------------------
>
> Key: DIRMINA-118
> URL: http://issues.apache.org/jira/browse/DIRMINA-118
> Project: Directory MINA
> Type: Improvement
> Versions: 0.8
> Reporter: Trustin Lee
> Assignee: Niklas Therning
> Priority: Minor
> Fix For: 0.9
>
> Jose Alberto Fernandez wrote:
> Another matter around Demux, is that currently it only looks at
> super-interfaces if a direct match is not found,
> But it does not look at super-classes. This is annoying when you have
> protocols that extend all messages from some particular superclass and you
> want to be able to treat groups of messages the same way (like ignoring them).
> Also, it may be interesting to see if there is a good way to cache the
> resolution of super-interfaces and super-classes in order to make such code
> more efficient. You will just need to make sure that the cache is flushed
> when MessageHandlers are added or removed.
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
