Description
The current state transition mechanism uses private methods that are annotated with to/from states. It is possible to accidentally define duplicate state transitions. A plugin has no way to know what state transitions may be defined in a base implementation.
We desire to refactor the implementation to make it cleaner.
Attachments
Issue Links
- relates to
-
QPID-7104 [Java Broker] Creating multiple state transition methods on a ConfiguredObject should cause an error
- Closed