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 2006/11/10 11:53:38 UTC

[jira] Resolved: (JAMES-415) Dynamic reload for some configuration of main services (e.g: servernames)

     [ http://issues.apache.org/jira/browse/JAMES-415?page=all ]

Norman Maurer resolved JAMES-415.
---------------------------------

    Resolution: Fixed

Reloading of servernames is now possible when using VUT

> Dynamic reload for some configuration of main services (e.g: servernames)
> -------------------------------------------------------------------------
>
>                 Key: JAMES-415
>                 URL: http://issues.apache.org/jira/browse/JAMES-415
>             Project: James
>          Issue Type: New Feature
>          Components: James Core
>    Affects Versions: 2.2.0
>            Reporter: Stefano Bagnara
>         Assigned To: Norman Maurer
>            Priority: Minor
>             Fix For: Next Major
>
>
> We probably could try to reload most of the config.xml by implementing and handling the Reconfigurable interface and running in a compliat container (maybe latest excalibur, merlin or even loom).

-- 
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


Re: [jira] Resolved: (JAMES-415) Dynamic reload for some configuration of main services (e.g: servernames)

Posted by Stefano Bagnara <ap...@bago.org>.
Bernd Fondermann wrote:
> On 11/11/06, Stefano Bagnara <ap...@bago.org> wrote:
>> The XMLDomainList is manageable but dynamic changes are not persisted.
>>
>> There is no management code yes, but it should be feasible to add the
>> management bean and the relative remotemanager "extension" via the
>> ManageableDomainList interface.
> 
> is this JIRA really ready to be closed then, given the headline and
> commit log comment?

You're right. We have not implemented what is described by the subject 
of the issue but only solved in a different way the main goal of that issue.

Maybe we should close it as won't fix and create a more specific issue 
for the DomainList service  or rename the subject. I would follow the 
first, but the commits already used the JAMES-415 "tag" in the comment 
and would be much more trackable if we simply change the title of this 
issue...

Stefano


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


Re: [jira] Resolved: (JAMES-415) Dynamic reload for some configuration of main services (e.g: servernames)

Posted by Norman Maurer <nm...@byteaction.de>.
Stefano Bagnara schrieb:
> Bernd Fondermann wrote:
>> On 11/11/06, Stefano Bagnara <ap...@bago.org> wrote:
>>> The XMLDomainList is manageable but dynamic changes are not persisted.
>>>
>>> There is no management code yes, but it should be feasible to add the
>>> management bean and the relative remotemanager "extension" via the
>>> ManageableDomainList interface.
>>
>> is this JIRA really ready to be closed then, given the headline and
>> commit log comment?
>
> You're right. We have not implemented what is described by the subject
> of the issue but only solved in a different way the main goal of that
> issue.
>
> Maybe we should close it as won't fix and create a more specific issue
> for the DomainList service  or rename the subject. I would follow the
> first, but the commits already used the JAMES-415 "tag" in the comment
> and would be much more trackable if we simply change the title of this
> issue...
>
> Stefano
>

+1
Norman




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


Re: [jira] Resolved: (JAMES-415) Dynamic reload for some configuration of main services (e.g: servernames)

Posted by Bernd Fondermann <be...@googlemail.com>.
On 11/11/06, Stefano Bagnara <ap...@bago.org> wrote:
> Bernd Fondermann wrote:
> > Just out of curiosity, how is this done? Simply by going to the DB
> > everytime?
> >
> > There is no management command for this, right?
>
> We currently have 4 implementations of the DomainList service:
>
> DomainList
> |- JDBCVirtualUserTable
> |- XMLVirtualUserTable
> '- ManageableDomainList
>     |- JDBCDomainList
>     '- XMLDomainList
>
> By default we use XMLDomainList for backward compatibility.
>
> JDBC based implementations run a direct query on db every time a
> contains(domain) is called. The is no cache at this time, but it should
> not be difficult to manage it.

ok.

>
> The XMLDomainList is manageable but dynamic changes are not persisted.
>
> There is no management code yes, but it should be feasible to add the
> management bean and the relative remotemanager "extension" via the
> ManageableDomainList interface.

is this JIRA really ready to be closed then, given the headline and
commit log comment?

> Are you the man for this? ;-)
> I just created this: https://issues.apache.org/jira/browse/JAMES-687

maybe, but not at the moment. I am already overcommitted. :-)

>
> > (There is no SVN log attached to the JIRA, I briefly browsed svn but
> > probably overlooked this.)
> >
> >  Bernd
>
> I think there is something broken with the svn/jira integration since
> they moved the servers.

ah right, I read something somewhere...

  Bernd

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


Re: [jira] Resolved: (JAMES-415) Dynamic reload for some configuration of main services (e.g: servernames)

Posted by Stefano Bagnara <ap...@bago.org>.
Bernd Fondermann wrote:
> Just out of curiosity, how is this done? Simply by going to the DB 
> everytime?
> 
> There is no management command for this, right?

We currently have 4 implementations of the DomainList service:

DomainList
|- JDBCVirtualUserTable
|- XMLVirtualUserTable
'- ManageableDomainList
    |- JDBCDomainList
    '- XMLDomainList

By default we use XMLDomainList for backward compatibility.

JDBC based implementations run a direct query on db every time a 
contains(domain) is called. The is no cache at this time, but it should 
not be difficult to manage it.

The XMLDomainList is manageable but dynamic changes are not persisted.

There is no management code yes, but it should be feasible to add the 
management bean and the relative remotemanager "extension" via the 
ManageableDomainList interface.

Are you the man for this? ;-)
I just created this: https://issues.apache.org/jira/browse/JAMES-687

> (There is no SVN log attached to the JIRA, I briefly browsed svn but
> probably overlooked this.)
> 
>  Bernd

I think there is something broken with the svn/jira integration since 
they moved the servers.

Stefano


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


Re: [jira] Resolved: (JAMES-415) Dynamic reload for some configuration of main services (e.g: servernames)

Posted by Norman Maurer <nm...@byteaction.de>.
<SNIP>
>> (There is no SVN log attached to the JIRA, I briefly browsed svn but
>> probably overlooked this.)
>>
>>  Bernd
>
> I think there is something broken with the svn/jira integration since 
> they moved the servers.
>
> Stefano
>

I opened a jira issue about that if someone want follow it ;-)

http://issues.apache.org/jira/browse/INFRA-1036


bye
Norman


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


Re: [jira] Resolved: (JAMES-415) Dynamic reload for some configuration of main services (e.g: servernames)

Posted by Bernd Fondermann <be...@googlemail.com>.
Just out of curiosity, how is this done? Simply by going to the DB everytime?

There is no management command for this, right?

(There is no SVN log attached to the JIRA, I briefly browsed svn but
probably overlooked this.)

  Bernd

On 11/10/06, Norman Maurer (JIRA) <se...@james.apache.org> wrote:
>      [ http://issues.apache.org/jira/browse/JAMES-415?page=all ]
>
> Norman Maurer resolved JAMES-415.
> ---------------------------------
>
>     Resolution: Fixed
>
> Reloading of servernames is now possible when using VUT
>
> > Dynamic reload for some configuration of main services (e.g: servernames)
> > -------------------------------------------------------------------------
> >
> >                 Key: JAMES-415
> >                 URL: http://issues.apache.org/jira/browse/JAMES-415
> >             Project: James
> >          Issue Type: New Feature
> >          Components: James Core
> >    Affects Versions: 2.2.0
> >            Reporter: Stefano Bagnara
> >         Assigned To: Norman Maurer
> >            Priority: Minor
> >             Fix For: Next Major
> >
> >
> > We probably could try to reload most of the config.xml by implementing and handling the Reconfigurable interface and running in a compliat container (maybe latest excalibur, merlin or even loom).
>
> --
> 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
>
>

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