At runtime, gets metadata information about components from the model developed in USoft Definer. This information covers general information about the component, methods, and parameters.
Returns an XML document of the form demonstrated in the Example below.
All parameters are optional. Parameter values that you pass are mapped to parameters by alias name. The '.*DOT NET.*' value in the following example is for architecture-pattern because of the "Architecture" alias:
This results in all components of the "DOT NET", and the "DOT NET INTERNAL" architectures.
(For backward compatibility only, it is possible to supply parameter values by position. Using this syntax, a list of non-aliased values maps to the parameter list in the order stated, with empty values at the end of the list if you supply less than 4 values, and '' (the empty string) as a way of explicitly declaring an empty value.)
Name-pattern is a regular expression that matches zero, one or more component names in the model. The result data is limited to components matching the pattern. If name-pattern is omitted, then result data is not limited in this way.
Architecture-pattern is a regular expression that matches zero, one or more component architectures in the model. The result data is limited to components with architectures matching the pattern. If architecture-pattern is omitted, then result data is not limited in this way. The following are valid component architectures in USoft:
If interfaces-only is set to 'yes', only columns that have Interface = Yes are included. The default of interfaces-only is 'no', meaning that components are in scope regardless of the value of their Interface attribute.
Module-pattern is a regular expression that matches zero, one or more module names in the model. The result data is limited to components within modules matching the pattern. Any components that are consumed from a different module which is filtered out by the regular expression, will show two additional fields 'INTERFACE_FROM_MODULE', which will be 'Y', and 'IMPLEMENTING_MODULE', which will contain the module name where the component originates from. The 'MODULE_NAME' field will in this case contain the name of the module in which the interface was consumed. If module-pattern is omitted, then the result data is not limited in this way.
This example returns component information about any components in the model that have the name 'REGEXP', and are of the 'J2EE' architecture :
The return value of this statement could be: