[MGNLCTS-21] Refactor exporter to make it work with blossom dialogs Created: 21/Aug/12  Updated: 27/Sep/12  Resolved: 29/Aug/12

Status: Closed
Project: Content Translation Support
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.1

Type: New Feature Priority: Neutral
Reporter: Zdenek Skodik Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MAGNOLIA-4521 Check for existence of parameter valu... Closed
causality
Template:
Acceptance criteria:
Empty

 Description   

The current NodeDataToTranslateFinder implementations provided out of the box are able to cope just with common dialog definitions. However if a dialog is registered programmatically via blossom module, both exporters can find it, but are not able to retrieve its tab/s in order to parse the dialog definition down and fill i18nAwareProperties up accordingly. This list is returned empty so that the final exported file doesn't contain any content (apart from the columns' titles).

To reproduce:

  • install the blossom sample webapp with enterprise modules
  • allow internationalization for one/more controls by setting i18n=true here or there
  • provide an i18n'ed content via the dialogs updated in the previous step
  • try to export any page updated in the previous step

Generated at Mon Feb 12 00:32:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.