[JAMES-654] Remove avalon "Context" usage when possible: deprecate AvalonContextUtils/Constants in favor of a FileSystem Service (we only need the getFile now)

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.0
• Assignee: Stefano Bagnara
• Reporter: Stefano Bagnara
• Created: 06/Oct/06 13:49
• Updated: 06/Oct/06 17:48
• Resolved: 06/Oct/06 17:48

Description

We should remove the AvalonContextUtils that we currently use only to retrieve files stored in the apps folder.
If we introduce a new Service for that we can also remove many uses of Context/Contextualizable and make the whole thing less Avalon-ized.
—
In James.initialize (or initializeServernamesAndPostmaster in trunk) we create a new DefaultContext that we store in a field, but we never use it.

We could remove it and remove the constants currently used only by that call.

This unused variable seems to be there unchanged since 2.2.0: it is referenced in UsersLDAPRepository but it never worked at least since 2.2.0 so we should remove it and eventually create the service chain needed to service the usersldaprepository.
—
In the remaining James we use the context almost only to access a file in the context: if we introduce this service we can remove Context/Contextualizable from James.

Issue Links

• blocks: JAMES-493 Refactor James components/services to simplify their usage in other IoC containers (SDI)