[JAMES-842] Inconsistencies in spring integration

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.0
• Assignee: Stefano Bagnara
• Reporter: David Jencks
• Created: 15/Jun/08 15:49
• Updated: 13/Jul/08 20:33
• Resolved: 29/Jun/08 17:02

Description

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.

Issue Links

• relates to: JAMES-845 Geronimo - JAMES Server integration