Re: [ptp-dev] JAXB Launch Configuration Manipulation: relinkConfiguratio

["Albert L. Rossi" <arossi@xxxxxxxxxxxxx>]

relinkConfigurationProperties() is called whenever there is an update (e.g., through Apply) initiated in the UI component (Launch Tab).  What it does is to grab internal variables that are not exposed to the user but are necessary for the normal performance of PTP (resource manager), and hold on to them; since the UI's internal map is rebuilt and then rewritten to the configuration each time (in order to provide for sub-tabs having different environments), it is important these not be lost.   When the job is actually launched, the resource manager control then looks at the LaunchConfiguration passed in to it from the UI component and sets its own map from it.  

I am not sure where ETFW interposes itself, but if it intervenes on the LaunchConfiguration before the Resource Manager submit command is called, then the RM will just use the values substituted by ETFW for those common properties as it would have the originals.  

Not sure this answers your question, though,

Al
----- Wyatt Spear <wspear@xxxxxxxxxxxxxx> wrote:
> Greetings,
> The ETFW needs to switch up the application being launched sometimes (e.g.
> to insert 'valgrind' before the user's app).  This is normally done by
> changing the config value
> of IPTPLaunchConfigurationConstants.ATTR_EXECUTABLE_PATH to the desired
> utility.
> 
> It looks like the JAXB launch manager uses a different set of configuration
> values, set in relinkConfigurationProperties, when launching a job.
>  (e.g. JAXBControlConstants.EXEC_PATH).  My current approach is to have ETFW
> swap those out as it does for the usual PTP configuration values.
>  Everything gets switched back in cleanup after the job runs.
> 
> Since it looks like these values may also be used for some deeper purpose
> within the JAXB system, if anyone has any knowledge of side-effects or
> issues this swapping may introduce, please let me know.
> 
> Thanks,
> Wyatt