Always use the short name (Identifier) when plugging components into the Visual LANSA Framework
|Date:||14 May 2013|
|Product/Release:||Visual LANSA Framework - V13|
|Abstract:||In V13, always use the Identifier when specifying which component or function to use as filters, command handlers and imbedded interface points|
|Submitted By:||LANSA Technical Support|
In V12, LANSA components have a single name.
The version of the Visual LANSA Framework shipped with V13 utilizes and showcases the new features in LANSA Version 13, including Long name support. Long names have been introduced in V13 to enable 3rd party integration and descriptive names.
In LANSA V13, instead of a single name, components have two names:
- Name (which may be long)
- Identifier (which is restricted to the length of the Version 12 name)
When working with the Visual LANSA Framework in a V13 environment, it is important to always use the Identifier (the short name) when specifying which components or functions to use as filters, command handlers, imbedded interface points, etc. The reason for this comes down to the way Visual LANSA works, and it is not specific to the Visual LANSA Framework.
Internally, the Visual LANSA Framework uses components like this:
#OBJECTNAME := ‘MYOBJECT’
SET_REF #REFERENCE (*CREATE_FROM #OBJECTNAME)
#REFERENCE.DoSomeTask Parm1(xxxx) Parm2(yyyyyy) … etc…
This dynamically loads up an object called MYOBJECT for execution and invokes its DoSomeTask method.
The SET_REF command can only load objects using their short names – it cannot load objects by their long name.
Note: At run time the Visual LANSA Framework is unable to translate a long name into a short name, and so must always have the short name (identifier) available.
At design time in the Visual LANSA Framework, however, you can still prompt and search for plug in components using their long name. When you select a component its short name will be returned, and that is what will be saved in the XML schema.