[
https://issues.apache.org/jira/browse/JAMES-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605221#action_12605221
]
Stefano Bagnara commented on JAMES-842:
---------------------------------------
Maybe it would be even better to have a james agnostic component in the
spring-avalon container and then have the filesystem service to use this
component. It just doesn't seem ok to import james services from the spring
container. In a perfect world the avalon-spring container is something not
dependant to james.
Currently the only james-aware class in the spring deployment module is
FileSystemBridge.java.
Any idea? Bernd?
> 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
> 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.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
