[
https://issues.apache.org/jira/browse/DIRMINA-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540353
]
Trustin Lee commented on DIRMINA-463:
-------------------------------------
> We need a way to couple IoHandlerTransition and IoHandlerTransitions
> together. I think we can use a special annotation for that:
>
> @TransitionsCombiner(IoHandlerTransitions.class)
> public interface @IoHandlerTransition {
> ...
> }
Does this mean we apply the same technique to IoFilterTransition(s) and
Transition(s)? Then it sounds great to me. Probably we could allow user to
specify either annotation class:
StateMachineFactory.getInstance(IoHandlerTransition.class).create(...) =
StateMachineFactory.getInstance(IoHandlerTransitions.class).create(...)
Does it make a sense?
> Find the best way to specify both MINA and non-MINA events.
> -----------------------------------------------------------
>
> Key: DIRMINA-463
> URL: https://issues.apache.org/jira/browse/DIRMINA-463
> Project: MINA
> Issue Type: Task
> Components: Statemachine
> Reporter: Trustin Lee
> Assignee: Niklas Therning
> Priority: Minor
> Fix For: 2.0.0-M1
>
>
> As discussed here: http://tinyurl.com/2omrl9
> For now, we use String to identify event types, which is somewhat unsafe.
> Using an enum might be useful, but there are a few disadvantages:
> * Wildcard event type cannot be used, which could be extended further (e.g.
> "message*" or "session(Opened|Closed)")
> Probably sticking to String might be the best solution? :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
