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] Updated: (JAMES-842) Inconsistencies in spring integration
Date Mon, 07 Jul 2008 23:38:33 GMT

     [ 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-3.patch

I tried the approach of removing the user of ResourceLoaderAware and that seems to work ok
in geronimo also, see the attached patch.  I don't know to what extent spring uses ResourceLoaderAware
but since I ran into problems with it using the AvalonApplicationContext instead of explicitly
configured ResourceLoaders I think that the JAMES-842-2.patch solution is safer since everything
is sure to get the ApplicationContext implemented ResourceLoader.  I think it's unfortunate
that Spring has combined these functions in the same class.

I think that for both patchs changes to the xml config files will be necessary.

> 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-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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message