Defining External Objects

This document is deprecated, for more information refer to External object

External Objects

• Web Services - WSDL (Web Services Description Language)
• Plattform classes
  • .Net Assemblies .Net
  • Java classes

External objects can be defined in two ways. Using the External Object Editor or using "Inspectors".

External Object Editor

When using the External Object Editor you have to provide, depending on your external application, the following items:

Note: As of Rocha Beta 2, you can define only one mapping for each external data type. In future versions it is expected that you can define one set of mappings for each environment (Java, .Net, etc.).

Inspectors

Using "Inspectors" is usually simpler than manually describing an external object. They inspect the external application for you and create / populate the External Object.

When creating an External Object, you can choose which inspector to use; this defines the external object to import and it is valid for webservices or Platform classes 

Import

Import is produced in two steps:

1. Choose the Webservice Description WSDL or Native File .
2. Pressing the Import button the SDT`s and service or classes description are imported.

In the case of  Webservices the inspector dialog have two areas. The area having a tree exposes service definitions and the structures that they use. In another area, the information of the selected element of the tree is shown.

Once, for example, a WSDL is selected, the tree has two elements: the first one contains the service definition; the other one, the scheme definition. To select any scheme element, you will be able to see the structure of the XML file.

The object is imported with the web service definition. This object have a user selected name. In addition a SDT by each structure used by the methods is imported. This SDT´s are created with the  

In the case of  a Native Object the inspector dialog displays a tree structure where the different classes are shown.

Using external objects in GeneXus

Samples

 Sample .NET Native

Considerations

Native Classes

-  The native classes have to be copied into the Application directory. 

Net Native Classes

 
      [return: MarshalAs(UnmanagedType.U1)]
      public unsafe bool AppendFile(string localFilename, string remoteFilename)
      {
        bool flag;
       ...
      }

    public static int multiplicar(int a, int b)
    {
     return a * b;
    }

     public void method(...) throws IOException {
        ......
       throw new IOException(...);
      ....
      }

WebServices (WSDL)