[
https://issues.apache.org/jira/browse/FINERACT-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Vorburger closed FINERACT-1181.
---------------------------------------
Resolution: Fixed
> Fineract does not start unless machine is connected to internet
> ---------------------------------------------------------------
>
> Key: FINERACT-1181
> URL: https://issues.apache.org/jira/browse/FINERACT-1181
> Project: Apache Fineract
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Petri Tuomola
> Assignee: Michael Vorburger
> Priority: Major
> Fix For: 1.5.0
>
>
> If you try to start Fineract on a machine that is not connected to the
> internet, at least I get the following error:
>
> {noformat}org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
> Configuration problem: Failed to import bean definitions from relative
> location [securityContext.xml]
> Offending resource: URL
> [file:/usr/local/Cellar/tomcat/9.0.38/libexec/webapps/fineract-provider/WEB-INF/classes/META-INF/spring/appContext.xml|file:///usr/local/Cellar/tomcat/9.0.38/libexec/webapps/fineract-provider/WEB-INF/classes/META-INF/spring/appContext.xml];
>
> nested exception is
> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
> 223 in XML document from URL
> [file:/usr/local/Cellar/tomcat/9.0.38/libexec/webapps/fineract-provider/WEB-INF/classes/META-INF/spring/securityContext.xml|file:///usr/local/Cellar/tomcat/9.0.38/libexec/webapps/fineract-provider/WEB-INF/classes/META-INF/spring/securityContext.xml]
> is invalid;
> nested exception is org.xml.sax.SAXParseException; lineNumber: 223;
> columnNumber: 63; cvc-complex-type.2.4.c:
> The matching wildcard is strict, but no declaration can be found for element
> 'oauth:authorization-server’.{noformat}
>
> It seems that our JAR/WAR does not include some XSDs needed to validate the
> XML config files. If the machine used is connected to the internet, these are
> downloaded automatically - but if not, Fineract does not start.
>
> Given these are related to Spring Security, I wonder if this will be fixed by
> upgrading the Spring Security JARs?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
