[
https://issues.apache.org/jira/browse/ISIS-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1247:
------------------------------
I can't reproduce this, and looking at the code it's not obvious how there
could be an interaction between i18n and layout.json; the method below, in
LayoutMetadataReaderFromJson, does the reading:
{code}
private LayoutMetadata readMetadata(final Class<?> domainClass) {
final String content;
if(blacklisted.contains(domainClass)) {
return null;
}
final String resourceName = domainClass.getSimpleName() +
".layout.json";
try {
content = ClassExtensions.resourceContentOf(domainClass,
resourceName);
} catch (IOException | IllegalArgumentException ex) {
blacklisted.add(domainClass);
final String message = String .format(
"Failed to locate file %s (relative to %s.class); ex: %s)",
resourceName, domainClass.getName(), ex.getMessage());
LOG.debug(message);
return null;
}
{code}
I've improved the error logging, but need a case to reproduce.
> .layout.json file not found if i18n is enabled ... uses the translated name
> to lookup the file.
> -----------------------------------------------------------------------------------------------
>
> Key: ISIS-1247
> URL: https://issues.apache.org/jira/browse/ISIS-1247
> Project: Isis
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.10.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: 1.11.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
