[
https://issues.apache.org/jira/browse/ISIS-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-1455.
-------------------------------
Resolution: Fixed
> Improve metamodel invalid exception handling
> --------------------------------------------
>
> Key: ISIS-1455
> URL: https://issues.apache.org/jira/browse/ISIS-1455
> Project: Isis
> Issue Type: Improvement
> Components: Core, Core: Viewer: Wicket
> Affects Versions: 1.12.2
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: 1.13.0
>
>
> At the moment the MMV error handling works only "by accident":
> - if an validation failure is found then the remaining initialization of
> authentication manager and persistence is skipped.
> - attempting to go to the login causes a null pointer exception
> - this exception is caught and then the MMV thrown
> This also raises an issue for implementations of - say - the ThemeProvider
> that want to make database queries, eg via Settings service. The todoapp
> does this.
> So, instead, we should always do the complete initialization even if there is
> a metamodel validation exception, but then intercept any such exceptions and
> route the MmvErrorPage thereafter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
