[
https://issues.apache.org/jira/browse/TORQUE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923213#comment-17923213
]
Thomas Vandahl commented on TORQUE-371:
---------------------------------------
Turbine uses Avalon as its service framework. Avalon has some similarities to
Spring IoC. That means that services take part in a lifecycle that is managed
by a service container. In the Torque case, the TorqueComponent is is such a
service. It extends TorqueInstance and is instantiated, configured, started,
stopped and properly disposed by the Avalon Container. So this allows Torque to
be properly shut down and restarted, something which the static Torque accessor
doesn't provide. You can see the different lifecycle phases in the Avalon
interfaces that TorqueComponent implements. The lifecycle itself is documented
here: https://excalibur.apache.org/framework/lifecycle.html
HTH
Suggestions and discussions should take place on the dev mailing list. This is
its main purpose.
> Remove Avalon
> -------------
>
> Key: TORQUE-371
> URL: https://issues.apache.org/jira/browse/TORQUE-371
> Project: Torque
> Issue Type: Task
> Components: Runtime
> Reporter: Max Philipp Wriedt
> Priority: Minor
>
> As Avalon and its successor seem to be gone. We might also remove Avalon?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
