[
https://issues.apache.org/jira/browse/QPID-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387408#comment-15387408
]
Lorenz Quack commented on QPID-7104:
------------------------------------
One example where this currently happens is {{AbstractVirtualHost}} the state
transition {{ERRORED -> ACTIVE}} is defined twice:
{code}@StateTransition(currentState = {State.UNINITIALIZED, State.ERRORED},
desiredState = State.ACTIVE)
private ListenableFuture<Void> onActivate()
{...}
@StateTransition( currentState = { State.STOPPED, State.ERRORED }, desiredState
= State.ACTIVE )
private ListenableFuture<Void> onRestart()
{...}{code}
> [Java Broker] Creating multiple state transition methods on a
> ConfiguredObject should cause an error
> ----------------------------------------------------------------------------------------------------
>
> Key: QPID-7104
> URL: https://issues.apache.org/jira/browse/QPID-7104
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.32, qpid-java-6.0
> Reporter: Lorenz Quack
> Fix For: qpid-java-7.0.0
>
>
> Currently nothing prevents one from annotating several methods with the same
> @StateTransition. However, the behaviour is not well defined.
> Ideally, we would catch this during compile-time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
