Exception at first start for JDBCDomainList Configuration
---------------------------------------------------------

                 Key: JAMES-990
                 URL: https://issues.apache.org/jira/browse/JAMES-990
             Project: JAMES Server
          Issue Type: Bug
          Components: SpoolManager & Processors
    Affects Versions: Trunk
            Reporter: Eric Charles
            Priority: Minor


Build and deploy current trunk.

Configuration scenario 1:
---------------------------------

- James.xml:
<enableVirtualHosting> true </enableVirtualHosting>

- domainlist.xml : 
   <!-- comment this if you use JDBCDomainList -->
   <!-- 
   <domainnames>
        <domainname>localhost</domainname>
    </domainnames>
   -->
    <!-- uncomment this if you use JDBCDomainList -->
    <repositoryPath>db://maildb/domain</repositoryPath>
    <sqlFile>file://conf/sqlResources.xml</sqlFile>

- springbeans.xml
use the <bean id="domainlist" class="org.apache.james.domain.JDBCDomainList"/>
and not the <bean id="domainlist" 
class="org.apache.james.domain.XMLDomainList"/>

run.sh gives an exception
Caused by: org.apache.commons.configuration.ConfigurationException: Configured 
defaultdomain could not get added to DomainList

run.sh a second time, everything's ok

Configuration scenario 2:
-----------------------------------

Same, but don't comment the domainnames in domainlist.xml
run.sh gives the same exception

run.sh a second time, everything's ok


PS : By the way, with the embedded derby out-of-the-box, could the default 
config be enableVirtualHosting=true and JDBCDomainList.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to