A detailed description of a method call in a simple to
visualize text format. Throughout the Framework code is often referenced, like
in configuration files, through an address (host and Queue), ATM, and then
guessed data type parameters. For many scenarios this is fine but sometimes you
will need to specify something out the ordinary, this is where the CallText
format comes in.
Examples of reasons you will need CallText
·
Guessing parameters, guess wrong! You need to send “321” as a
string, not an Int32 that would be guessed. loose coupling needs to know the
correct method parameter datatypes to find a method.
·
Passing arrays. No way to get arrays on a guessed parameters
line, the elements would just be interpreted as separate parameters.
·
Readability. A line of tab delimited parameters without headings
is not that easy to visualize. If you have a lot of parameters, then a list per
line with the names is pretty handy.
·
Constructor Arguments, should be avoided on high level classes.
But if you do have to use them, maybe you just want to quickly test a lower
level method, then you can.
·
Call Flags are required.
There are 2 ways the CallText format is used;
·
Full - contains the entire description of a method call; address,
ATM, parameters, constructor arguments, and CallFlags.
·
Partial – Address and ATM have already been specified, like in
Framework configuration files, and now you want to specify; parameters,
constructor arguments, and CallFlags. In configuration files an at sign ‘@’ in
the parameter means; the following lines are CallText, ending at the next empty
line.
Simple Example to get machine name from host using a web
service call:
Host WSYS-BRAN-APP
Assembly System
Type System.Environment
Method MachineName
Flags ReportResult
You can create CallText for a method easily, by using the
Call page of the Intranet. Select the host, find and select your method using
the search, enter parameters (or leave parameters blank to make a template),
and click the “Make CallText” button.