[
https://issues.apache.org/jira/browse/QPID-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241172#comment-15241172
]
Keith Wall commented on QPID-7104:
----------------------------------
Impose a model validation (at start-up time) that ensures that no method
annotated with @StateTransition has either a sibling method (within the same
class) or a state transition method on a parent class that has a:
# non empty intersection of start state
# equality on end state
If the invariant is broken, the Broker must faill to start.
> [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-6.1
>
>
> 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]
