james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <server-...@james.apache.org>
Subject [jira] Created: (JAMES-842) Inconsistencies in spring integration
Date Sun, 15 Jun 2008 15:50:45 GMT
Inconsistencies in spring integration

                 Key: JAMES-842
                 URL: https://issues.apache.org/jira/browse/JAMES-842
             Project: James
          Issue Type: Bug
    Affects Versions: 3.0
            Reporter: David Jencks

I've found a couple inconsistencies in the spring integration:

in AvalonConfigurationFileProvider InputSource is supplied a systemId for the james config
files whereas in AvalonBeanDefinitionReader it is not.  In my scenario this means that the
entities in james-config.xml don't work because for AvalonConfigurationFileProvider the entities
are resolved relative to the james-config.xml file location whereas for AvalonBeanDefinitionReader
they are resolved relative to some base directory.

There's a FileSystem bean supplied to spring to locate stuff in the file system but it is
not used in AvalonConfigurationFileProvider; AFAICT this means that configuration files must
be in the classpath.

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

View raw message