You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Stefano Bagnara (JIRA)" <se...@james.apache.org> on 2006/10/06 15:50:19 UTC
[jira] Created: (JAMES-654) Deprecate AvalonContextUtils/Constants
in favor of a JamesContextService (we only need the getFile now)
Deprecate AvalonContextUtils/Constants in favor of a JamesContextService (we only need the getFile now)
-------------------------------------------------------------------------------------------------------
Key: JAMES-654
URL: http://issues.apache.org/jira/browse/JAMES-654
Project: James
Issue Type: Improvement
Affects Versions: Trunk
Reporter: Stefano Bagnara
Assigned To: Stefano Bagnara
Priority: Minor
Fix For: Trunk
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-654) Remove avalon "Context" usage when
possible: deprecate AvalonContextUtils/Constants in favor of a FileSystem
Service (we only need the getFile now)
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-654?page=all ]
Stefano Bagnara updated JAMES-654:
----------------------------------
Summary: Remove avalon "Context" usage when possible: deprecate AvalonContextUtils/Constants in favor of a FileSystem Service (we only need the getFile now) (was: Deprecate AvalonContextUtils/Constants in favor of a JamesContextService (we only need the getFile now))
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.
was:
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.
Made the issue more generic so to involve more changes.
> Remove avalon "Context" usage when possible: deprecate AvalonContextUtils/Constants in favor of a FileSystem Service (we only need the getFile now)
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JAMES-654
> URL: http://issues.apache.org/jira/browse/JAMES-654
> Project: James
> Issue Type: Improvement
> Affects Versions: Trunk
> Reporter: Stefano Bagnara
> Assigned To: Stefano Bagnara
> Priority: Minor
> Fix For: Trunk
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (JAMES-654) Remove avalon "Context" usage when
possible: deprecate AvalonContextUtils/Constants in favor of a FileSystem
Service (we only need the getFile now)
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-654?page=all ]
Stefano Bagnara resolved JAMES-654.
-----------------------------------
Resolution: Fixed
Applied. Please review.
> Remove avalon "Context" usage when possible: deprecate AvalonContextUtils/Constants in favor of a FileSystem Service (we only need the getFile now)
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JAMES-654
> URL: http://issues.apache.org/jira/browse/JAMES-654
> Project: James
> Issue Type: Improvement
> Affects Versions: Trunk
> Reporter: Stefano Bagnara
> Assigned To: Stefano Bagnara
> Priority: Minor
> Fix For: Trunk
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org