From: Kyle G. <kyl...@kl...> - 2006-04-26 16:03:57
|
First of all thanks for the quick reply! <snip> > <if expr="STAXResult != 0"> > <message>'local: Failed to set STAF variables:\n'</message> > <else> > <sequence> > <stafcmd> > <location>'local'</location> > <service>'var'</service> > <request>'resolve string {KW/FooBar}'</request> > </stafcmd> > <message>STAFResult</message> > </sequence> > </else> > </if> > > The message output will be 'foobar'. > This works, (thanks). But, now I have another question, If I use 'local' for the machine name when using STAXUtilExportSTAFVars why doesn't the variable show up when I do a variable list from the command line on that machine? If I use another machine name 'machA' for example I can then list the variables on 'machA' from the command line and the variable {KW/FooBar} is listed. Why is the variable {KW/FooBar} only accessible via the VAR service on the 'local' machine? > Regarding the use of system/shared/handle, it really depends on how you > want to manage your variables. See section "2.4 Variables" of the STAF > User's Guide (http://staf.sourceforge.net/current/STAFUG.htm) for more > information on the different types of variables, I read the above section just _after_ I sent my email... sigh. The question that I still have is there a 'best practices' guide as to the best way to manage variables? <snip> > > <function name="Main"> > <sequence> > <script> > staxUtilDir = '{STAF/Config/STAFRoot}/services/stax/libraries' > </script> > <import machine="'local'" file="'%s/STAXUtil.xml' % staxUtilDir"/> > <script> > foobar = "foobar" > </script> > <call function="'STAXUtilExportSTAFVars'"> > [ > { > 'foobar' : 'KW/FooBar', > }, > [ 'local' ] > ] > </call> > <if expr="STAXResult != 0"> > <message>'local: Failed to set STAF variables:\n'</message> > <else> > <message>'{KW/FooBar}'</message> > </else> > </if> > > </sequence> > </function> <snip> |