[
https://issues.apache.org/jira/browse/JAMES-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677835#action_12677835
]
robertburrelldonkin edited comment on JAMES-893 at 3/1/09 12:42 PM:
----------------------------------------------------------------------
Proposal Overview:
* Use JSR-250 annotations on existing components to replace intrusive Avalon
Framework
* Use Service Locator to loosen coupling to Phoenix blocks
was (Author: robertburrelldonkin):
Proposal:
Use JSR-250 annotations on existing components to replace Av
> JSR250 Replacement For Avalon Framework
> ---------------------------------------
>
> Key: JAMES-893
> URL: https://issues.apache.org/jira/browse/JAMES-893
> Project: JAMES Server
> Issue Type: Wish
> Components: Build System, Deployment Modules, DNSServer,
> Documentation, FetchMail, IMAPServer, James Core, JUnit, Mailet
> Contributions, MailStore & MailRepository, Matchers/Mailets (bundled),
> NNTPServer & Repository, POP3Server, Remote Delivery, Remote Manager,
> SMTPServer, SpoolManager & Processors, UsersStore & UsersRepository
> Affects Versions: 3.0
> Reporter: Robert Burrell Donkin
>
> Background
> ----------------
> James uses the Phoenix container and the Avalon Framework.
> Unfortunately, both are now dead projects. This is now starting to cause
> maintainability issues. Realistically, James will need to start maintaining a
> fork or accept that some features will not work correctly in this container.
> It is also hard to recruit developers willing to learn these obsolete
> technologies.
> Both Avalon and Phoenix take intrusive approaches to IoC. Avalon imposes
> coupling to a number of lifecycle interfaces. Phoenix requires a
> proliferation of finely grained internal interfaces.
> However, these components have many advantages. They are now well tested and
> debugged. Users of James (as opposed to developers) seem happy with them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]