Stefano Bagnara wrote:
The second step ( and the harder step) is to make it manageable. This
is only the case for JDBCVirtualUserTable at the moment. I want to add
JMX and RemoteManager support for it to create mappings and delete
them.
>> Yes, BUT ... this should have some more ca
Norman Maurer wrote:
+1
Yes, BUT ... this should have some more careful designing. And we do not
need to rush it. For example, UsersRepositoryVUT should be a higher
priority (IMO), and it already has an administrative interface.
So what you guys prefer ? Deprecate the old methods f
>> +1
>>
>
> Yes, BUT ... this should have some more careful designing. And we do not
> need to rush it. For example, UsersRepositoryVUT should be a higher
> priority (IMO), and it already has an administrative interface.
>
So what you guys prefer ? Deprecate the old methods for adding/
Noel J. Bergman wrote:
Stefano Bagnara wrote:
Norman Maurer wrote:
First off all i want to create and VirtualUserTable service
At the moment i created the XMLVirtualUserTable and
JDBCVirtualUserTable as implementations.
+1
We should also make the DefaultJamesUsersRepository to implement
Stefano Bagnara wrote:
> Norman Maurer wrote:
> > First off all i want to create and VirtualUserTable service
> > At the moment i created the XMLVirtualUserTable and
> > JDBCVirtualUserTable as implementations.
> +1
> We should also make the DefaultJamesUsersRepository to implement this
> new se
Norman Maurer wrote:
First off all i want to create and VirtualUserTable service which can be
used in other classes. At the moment i created the XMLVirtualUserTable
and JDBCVirtualUserTable as implementations.
+1
We should also make the DefaultJamesUsersRepository to implement this
new service
Hi all,
you maybe allready notice that i did some commits for JAMES-582. After
talkln yesterday with Noel, we both agreed that i maybe should write to
mailing list and explain what i try to do and why...
First off all i want to create and VirtualUserTable service which can be
used in other classe
