[CAUSEWAY-1221] JSON Format Layouts not recognized with i18n translations in Wicket Viewer

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9.0
• Fix Version/s: 1.11.0
• Component/s: Viewer Wicket
• Environment: Windows Server, HSQLDB
• Assignee: Unassigned
• Reporter: Cesar Lugo
• Created: 27/Oct/15 23:30
• Updated: 02/Jan/16 05:53
• Resolved: 22/Dec/15 16:03

Description

I am working with Apache Isis Wicket viewer 1.9.0, and I have some form layout json files to define the layout for some domain objects. I also added a translation file (i18n) with some translations. When running the application in the browser, when I am in “writing translations” mode it shows the object form with the layout defined in the json file (ok), but when I switch to “reading translations”, it goes back to the “default” layout, ignoring the layout defined in the json file.

In regards to those modes, I am referring to the Apache wicket viewer menu which, in prototype mode, has a "Prototyping" menu, which has an option "Switch to Reading Translations". When you select that option and keep using the application is when it loses the layouts defined in the json layout files.

Issue Links

• duplicates: CAUSEWAY-1247 [DUPLICATE] .layout.json file not found if i18n is enabled ... uses the translated name to lookup the file.