In our Deploy scripts, we create singletons of several large/complex classes to avoid the overhead of creating/destroying/garbage collecting them for each message.
When we Reload Resources, these singletons are (obviously) not updated even though the Reload Resources panel advises you that current channels will be affected.
I believe you should put a Code Template-style notification in the "Rev" column to advise users that they may need to re-deploy channels to fully reflect the reload.
P.S. I don't think it's sufficient to check for a non-empty deploy script either. Someone could just as easily check $gc (or something similar) in the transformer and create/set to a singleton if the value is null.
In our Deploy scripts, we create singletons of several large/complex classes to avoid the overhead of creating/destroying/garbage collecting them for each message.
When we Reload Resources, these singletons are (obviously) not updated even though the Reload Resources panel advises you that current channels will be affected.
I believe you should put a Code Template-style notification in the "Rev" column to advise users that they may need to re-deploy channels to fully reflect the reload.
P.S. I don't think it's sufficient to check for a non-empty deploy script either. Someone could just as easily check
$gc(or something similar) in the transformer and create/set to a singleton if the value is null.Imported Issue. Original Details: Jira Issue Key: MIRTH-4319 Reporter: ambsw Created: 2018-08-23T07:46:32.000-0700