Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| docs:3500:0500 [2023/04/05 05:52] – removed - external edit (Unknown date) 127.0.0.1 | docs:3500:0500 [2025/06/12 02:35] (current) – Rename to AwareIM aware_support3 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | {{tag> | ||
| + | [< | ||
| + | ====== Adding function libraries ====== | ||
| + | |||
| + | This section describes what programmers have to do to add new function libraries to // | ||
| + | |||
| + | Function libraries contain functions that can be used in the Rule Language (see [[docs: | ||
| + | |||
| + | Note that unlike processes functions are not supposed to communicate with the rest of the // | ||
| + | |||
| + | Functions are organized in libraries. The grouping of functions in a library is up to the designer of the library. The name of the function must be unique across all libraries, so it is generally a good idea to start the name of the function with a prefix uniquely identifying the library that the function belongs to. | ||
| + | |||
| + | To add a new function library to // | ||
| + | |||
| + | - Write the code for the component that will implement functions of the library (see [[docs: | ||
| + | - Compile the source code of your function library component and package it in a jar file(s). Make sure that the jar file resides in the '' | ||
| + | - Add a definition of the new function library to the '' | ||
| + | |||
| + | If everything has been done correctly the name of the new functions must appear in the list of functions displayed by the Rule Language [[docs: | ||
| + | |||
| + | {{simplenavi>: | ||
| + | |||