james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Bagnara <apa...@bago.org>
Subject avalon-spring-library (Was: [jira] Commented: (JAMES-842) Inconsistencies in spring integration)
Date Wed, 02 Jul 2008 08:57:51 GMT
Bernd Fondermann (JIRA) ha scritto:
>     [ https://issues.apache.org/jira/browse/JAMES-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609623#action_12609623
> Bernd Fondermann commented on JAMES-842:
> ----------------------------------------
> Great work, Stefano! Thanks for taking care (also for 841 & 840).

Thank you :-)

Should we move the "non-james-specific" spring-avalon bridge to an 
"avalon-spring-library" and just keep the 
FileSystemBridge+configurations in the spring-deployment module?


>> 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
>>            Assignee: Stefano Bagnara
>>             Fix For: 3.0
>>         Attachments: JAMES-842.patch
>> 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.

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

View raw message