JNDI Repository

["QO) <rsanchez@qualityobjects.com>" <Roberto>]

Hi, 
I'm developing a new user repository, JNDIUsersRepository, for my own use. I have made a new class, I haven't used LDAPUsersRepository because it has too many problems to solve. I thought it was better do a new one, in addition the class "LDAPUsersRepository" has a inappropriate name, this is my opinion. 
My users back-end is a LDAP (OpenLDAP). This new repository is about to be ready, it only needs encrypt passwords (SHA, SSHA, etc) for new Users. 

I never have participated in an apache project, but I would like. I have read the pages: http://james.apache.org/contribute.html and http://jakarta.apache.org/site/source.html but I'm not sure about the process for adding new code.
How to decide if it is correct to add a new class or modify an existing one ?
How I know that there is no another person doing the same task ?
Who assigns each task to a developer ? nobody ?
...

In a future release It would be interesting to manage users groups, but for this it is necessary to modify "UserRepository" interface and to add new commands in "RemoteManager", what do yo think about this ?

Could anybody help me ?.

Thanks in advance.

PD: My english it is not perfect, please be patient with me. ;-)

Re: JNDI Repository

["QO) <rsanchez@qualityobjects.com>" <Roberto>]

> Roberto,
>
> This is good, and we welcome contributions, but you should know that Alex
> Zhukov has also already done a similar thing.  Have you looked at it?

Yes, I saw de Alex Zhukov's LDAP repository, but it supposed several things
that did not fit well with my "production server", for example:
    - The login to access POP3 account is the mail itself, I need the
userid, that is, attribute "uid" of my LDAP.
    - Adding a new user implies to modify a group in LDAP server, but it is
supossed the user already exists, I need create the user.
    - To check if a user is a local user, it searches in the group where the
users are included in the adding process. For me a local user it is a user
that is stored under a specific "Base DN" in my LDAP.
    - etc.

I don't say the the Alex work is wrong, but it's not what I need, at least
in this moment. On the other hand his implementation of a maildir repository
is interesting but I need the inbox in MySQL not on filesystem. It is
possible that the version I saw was obsolete. Where can I see the last
version of this software ?, perhaps in
http://cvs.apache.org/viewcvs.cgi/james-server/src/ ?

>
> > In a future release It would be interesting to manage users groups, but
> > for this it is necessary to modify "UserRepository" interface and to
> > add new commands in "RemoteManager", what do yo think about this ?
>
> It is possible that once we start to integrate with JNDI that the entire
> user repository area will change.

OK, I would like to help in this task, if it is possible. Where is the forum
to discuss about the new architecture, in the Wiki ?

>
> --- Noel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

Re: JNDI Repository

["QO) <rsanchez@qualityobjects.com>" <Roberto>]

>
> ROberto,
>
> Noel wrote
> > It is possible that once we start to integrate with JNDI that the entire
> > user repository area will change.
>
> I would encourage you to make your JNDI work as independant as possible of
James, so that it can more easily be used when we change the way James
handles users.

It's reasonable,  No problem ;-)

>
>
> I want to see James use JNDI for user and mail repositories, and other
services.
>
> James makes great use of "programing by contract" and often seems to be
more interface than code, I believe this is one of James' strengths.
> It is not bad to create new interfaces and show us how to use them in
place of ones we already use, or to suggest changes to the existing ones. If
your changes are big make a new one and extend (inherit) the old one, if
they are small change the old one.

That's right. I'm thinking about a new interface UsersGroupsRepository that
extends of UsersRepository and similar solutions.
On the other hand the telnet interface is a good idea, but, at this moment,
the functionality supported is limited, It would be interesting an interface
more interactive, at least in a few important commandas like "ADD", I need
more data for a User, Complete Name, Address, Telephone, etc. and manage
groups.
I know these changes implies much work, but I say before I would like to
help in the project although I don't know very clearly how to do it. It's my
"first time" ;-), I talk about to take part in a project at "world-wide"
level, normally work with people groups whom every day I see.

I hope that you understand to me, I need to practice my "Written English",
these mails are a good exercise for that.

Bye.

>
> d.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

RE: JNDI Repository

[Danny Angus <da...@apache.org>]

ROberto, 

Noel wrote
> It is possible that once we start to integrate with JNDI that the entire
> user repository area will change.

I would encourage you to make your JNDI work as independant as possible of James, so that it can more easily be used when we change the way James handles users.


I want to see James use JNDI for user and mail repositories, and other services.

James makes great use of "programing by contract" and often seems to be more interface than code, I believe this is one of James' strengths. 
It is not bad to create new interfaces and show us how to use them in place of ones we already use, or to suggest changes to the existing ones. If your changes are big make a new one and extend (inherit) the old one, if they are small change the old one.

d.



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

RE: JNDI Repository

["Noel J. Bergman" <no...@devtech.com>]

Roberto,

This is good, and we welcome contributions, but you should know that Alex
Zhukov has also already done a similar thing.  Have you looked at it?

> In a future release It would be interesting to manage users groups, but
> for this it is necessary to modify "UserRepository" interface and to
> add new commands in "RemoteManager", what do yo think about this ?

It is possible that once we start to integrate with JNDI that the entire
user repository area will change.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org