[
http://mifosforge.jira.com/browse/MIFOS-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
keithwoodlock resolved MIFOS-2922.
----------------------------------
Resolution: Fixed
Fixed in trunk build https://ci.mifos.org:8843/hudson/job/trunk/1263
the file path must be passed into spring configurations and not just the name.
How did this ever work before within SpringUtil.getConfigFiles i am not sure.
> Shamim D not picking up mifosBeanConfig.custom.xml file
> -------------------------------------------------------
>
> Key: MIFOS-2922
> URL: http://mifosforge.jira.com/browse/MIFOS-2922
> Project: mifos
> Issue Type: Bug
> Components: Configuration
> Affects Versions: Shamim D
> Reporter: Kay Chau
> Assignee: keithwoodlock
> Priority: Critical
> Fix For: Shamim D
>
> Attachments: localhost.2009-11-09.log, mifosBeanConfig.custom.xml
>
>
> Upgrade to trunk with a previous mifosBeanConfig.custom.xml that was working
> in 1.5 yields error in attached log. From Keith W on the mailing list:
> the problem here is that it isnt actually finding the file within the
> 'classpath'..
> MifosSpringContextListener was created to support what was previously done in
> SpringUtil.getConfigFiles which is to support this extra custom file that may
> or may not be part of the applicationContext.
> 1.5 may not be using MifosSpringContextListener but instead using SpringUtil
> approach.
> ----
> this should work in Shamim D
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
