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