CA Gen Web View assemble step fails for non-default dialect (ARABIC)

book

Article ID: 211016

calendar_today

Updated On:

Products

CA Gen - Workstation Toolset CA Gen

Issue/Introduction

After successful Web View generation from CA Gen Studio and install via Build tool the Assemble step fails for non-default ARABIC dialect:
BUILD FAILED
C:\Users\Administrator\Documents\CA\Gen 8.6\Models\model1.ief\java\assemble.EAR.XML:189: Could not find the file "C:\Users\Administrator\Documents\CA\Gen 8.6\Models\model1.ief\java\\..\WebViewUI\ARABIC\CB001_MAINTAIN_APPLICANT_CL_ARABIC.html"
Often this is caused by failing to select all the source modules for generation.

Gen Studio has created these files in the WebViewUI directory for the DEFAULT dialect:
CB001_MAINTAIN_APPLICANT_CL.Help.html
CB001_MAINTAIN_APPLICANT_CL.html
CB001_MAINTAIN_APPLICANT_CL.js
CB001_MAINTAIN_APPLICANT_CL.style.css

Gen Studio has created these files in the WebViewUI\ARABIC directory for ARABIC dialect and the "_CL_" has been truncated from the PStep name due to 32 character limit in names:
CB001_MAINTAIN_APPLICANT_ARABIC.Help.html
CB001_MAINTAIN_APPLICANT_ARABIC.html
CB001_MAINTAIN_APPLICANT_ARABIC.js
CB001_MAINTAIN_APPLICANT_ARABIC.style.css

Per the error, the Assemble step seems to be unaware of that name truncation and is still looking for a name of "CB001_MAINTAIN_APPLICANT_CL" + "_DIALECT" so for DIALECT=ARABIC that is "CB001_MAINTAIN_APPLICANT_CL_ARABIC.*".

Have previously used the same model successfully for Web Generation without having any problems.

Environment

Release : 8.6
Component : CA Gen Build Tool

Resolution

Gen Engineering has determined that Web View is currently designed to expect the non-default dialect windows to be modeled with the same name as their corresponding default dialect windows with the suffix of '_<DIALECT>.
They understand that this is different from how Web Generation works, but in order to make Web View work like Web Generation, a fix would entail changes to generators, Gen Studio, the Build Tool as well as the Web View runtimes. Due to the size and broad impact of these changes, Engineering believes it will take a significant amount of time before these PTFs could be made available.
In the meantime, the following workaround has been successfully tested:

Rename the non-default dialect windows so that they have the same name as their corresponding default dialect windows and then add '_ARABIC' to the end of their name, then the Web View application Assemble step would not experience the current problem. In the situation where the default dialect window name is too long (maximum length is 31 characters) to add the '_ARABIC' for the non-default window requires the default window name to be shortened (see below).
In the model provided there are three dialect windows that would need to be changed to follow this pattern:

Pstep: CB10_LIST_APPLICANTS_CL
Default: CB10_LIST_APPLICANTS_CL
Dialect:  LIST_APPLICANTS_ARABIC (Change to)-->CB10_LIST_APPLICANTS_CL_ARABIC

Pstep: CB00_LOGON
Default: CB00_LOGON
Dialect:  CB00_LOGON_ARAB (Change to)-->CB00_LOGON_ARABIC

Pstep: CB001_MAINTAIN_APPLICANT_CL
Default: CB001_MAINTAIN_APPLICANT_CL (shorten to)--> CB001_MAINTAIN_APPLICANT  
Dialect:  CB001_MAINTAIN_APPLICANT_ARABIC <<< keep the same

After implementing the above workaround changes and regenerate from Gen Studio, the Build Tool install and Assemble steps are then successful.

Additional Information

The workaround is harder to implement for medium/large models and per previous comments Engineering plans to provide a fix for this problem in the future.