About User Exits

Edit online

User exits perform functions that the translator does not perform during typical translation. For example, user exits can:

  • Access a database table to perform cross-references or lookups.
  • Perform complex pricing calculations that enable different prices to be calculated for multiple customers, where the seller is located, or where the product is sold.

User exits are extended rules that enable Java™™ objects to be created and accessed. With user exits you can create custom Java classes or use third-party Java classes. User exits can create objects, access properties, or start methods.

The Map Editor does not inspect Java classes to verify the correctness of method and property names during map compilation.

Note: Extended rules cannot compare property or method results because property and method types are unknown prior to compilation. Also, extended rules cannot catch Java exceptions and Java methods called by extended rules cannot throw exceptions.

To handle an exception, you must create a user exit containing a wrapper class that calls the real class and handles the exception. Also, the Java class needs a constructor with a string argument. For more information on using constructor with a string argument, see Creating an Object.

Long Keyword

The keyword “long” is supported after a parameter is passed to a user exit method. This keyword is used for integers only and indicates a 64-bit integer.

This function is backward-compatible; the translator assumes that user exits used with versions of the Sterling B2B Integrator Map Editor prior to the implementation of this functionality refer to 32-bit integers.