[
https://issues.apache.org/jira/browse/TORQUE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922796#comment-17922796
]
Max Philipp Wriedt commented on TORQUE-371:
-------------------------------------------
So, I still don't quite get Avalon as the documentation is pretty old, so maybe
someone might need to explain to me how it's used in Turbine.
If I understand this correctly, Avalon is in general something like the Spring
Framework?
At the time I am still getting into the concepts the Spring Framework provides
to Java, so i would not be of much help at the time implementing it and I don't
know about competitors of Spring. In Spring Framework Hibernate currently seems
to be the ORM of choice. So I don't think it would be useful as replacement for
Torque but Torque as part of Turbine might also work when replace by some
Spring components?
On the other hand, marketing Torque as compatible to Spring might get some
attention to the project as spring seems to be a de-facto standard in java
development?
At my job I am currently trying to take a more than 20 years old Torque
Integration to the web (rest-api/jakarta-rs) using whatever i need (which seems
to be some parts of Spring at this time, but we are still starting). Maybe the
experience gain will help here in the future.
Another thing i would like to suggest/open for discussion: switching torque
from svn to git (as dbcp and pool are there already) -> should i open an
issue/improvement for that, or is the dev mailing list the way to go?
> 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]
