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] Commented: (JAMES-842) Inconsistencies in spring integration
Date Fri, 11 Jul 2008 17:26:31 GMT

    [ https://issues.apache.org/jira/browse/JAMES-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612936#action_12612936
] 

David Jencks commented on JAMES-842:
------------------------------------

After fixing the build problems I had in james these changes appear to work fine with geronimo,
as far as I can tell.

I have GeronimoAvalonApplicationContext directly overriding AvalonApplicationContext and implementing
the ResourceLoader methods directly.  I think this solution is fine.

I still don't know how to do an actual test of the geronimo-james plugin to see if the file.exists()
check is reasonable.

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


Mime
View raw message