james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <server-...@james.apache.org>
Subject [jira] Commented: (JAMES-842) Inconsistencies in spring integration
Date Fri, 11 Jul 2008 16:18:31 GMT

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

Stefano Bagnara commented on JAMES-842:
---------------------------------------

Hi David, 

I slightly modified JAMES-842-2.patch and applied it.

Please note that I created now a new module in james for the bridge code, and the James specific
AvalonApplicationContext is now named JamesApplicationContext (you probably want to override
this one).

I also warn you that the check for file.exists() you have in GeronimoAvalonApplicationContext
may not be appropriate because we may have code that try to get File references even if they
don't exists.
I don't remember now but I know I had to remove the check from our resource loader in order
to run James.

Do you think JamesApplicationContext should be factored to expose a protected method for you
to override only the file:// lookup?

> 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