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 "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/12/16 13:11:01 UTC

[jira] Resolved: (JAMES-1150) Remove UsersStore

     [ https://issues.apache.org/jira/browse/JAMES-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Norman Maurer resolved JAMES-1150.
----------------------------------

    Resolution: Fixed

done

> Remove UsersStore
> -----------------
>
>                 Key: JAMES-1150
>                 URL: https://issues.apache.org/jira/browse/JAMES-1150
>             Project: JAMES Server
>          Issue Type: Task
>    Affects Versions: 3.0-M2
>            Reporter: Norman Maurer
>            Assignee: Norman Maurer
>             Fix For: 3.0-M3
>
>
> Remove the UsersStore interface.
> From ml:
> Hi there,
> as we are currently doing last changes in the API before the next
> release I would like to get rid of the UsersStore interface and
> implementation.
> Here some background:
> In previous version of James Server we allowed to configure more then
> one UsersRepository and lookup each by its unique name. We forced the
> User/Dev to specify at least one UsersRepository which need to have
> the name "LocalUsers". This one was used as the "default" which were
> used to back all "local" users. Beside this you could configure a
> second one and use it in some mailets. Anyway most of our code was
> bound to use the "LocalUsers" one to check for valid user etc. So I
> don't see much value to support more the one at the same time. It just
> complicate stuff and needed some ugly hacks to get it workin all the
> way.
> The only "service" which make really use of the UsersStore and so more
> then one UsersRepository is the mailinglist stuff. But I think its
> just plain wrong to use it here. The maillinglist use one
> UsersRepository per mailinglist to store eachs users. Anyway using the
> UsersRepository for this is just a misusage of a component, as it was
> not really designed for that purpose. The mailinglist in fact only
> need some kind of storage which map mail-addresses to the right list.
> Nothing more.
> So I propose to remove UsersStore and just use one UsersRepository.
> For the mailinglist we have two options:
> 1) Remove the mailinglist stuff
> 2) Write some simple store for it.
> I think 1 would be the fastest but maybe users still like to use it.
> I'm in fact never did so I would be ok with removing it too.
> So what others think about it ?
> Bye,
> Norman

-- 
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org