[
https://issues.apache.org/jira/browse/JAMES-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated JAMES-842:
-------------------------------
Attachment: JAMES-842-2.patch
Oops, here's the correct patch (I hope :-)
Another note..... this method of using the ApplicationContext as the
ResourceLoader leads to much cleaner code in the geronimo integration since we
have a single point where we can directly supply the necessary geronimo
services. With the other approach I have to supply the geronimo services via
static fields in the ResourceLoader implementation or do something like a
singleton lookup. Direct dependency injection, possible with this patch, seems
like a much cleaner approach.
> 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-840-2.patch, JAMES-842-2.patch, JAMES-842-3.patch,
> 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]
