Project resolving

There is RulesProjectResolverthat resolves all OpenL projects inside the workspace, Resolver just list all folders in workspace and tries to detected OpenL project by some predefined strategy. Most easy wayto init RulesProjectResolveris to use static method loadProjectResolverFromClassPath() that will use project-resolver-beans.xml from classpath(this is usual Spring beans config that defines all resolving strategies and their order).

Make sure that resolving strategies are in the right order: some projects may be matched by several resolving strategies. By default resolving strategies are in the following order:

Project Descriptor resolving strategy

This resolving strategy is the strictest resolving strategy. This strategy based on the descriptor file (see above).

Eclipse based resolving strategy

Previously default resolving strategy that checks that it contains “openlbuilder” section in “.project” file (eclipse project description file) and search all wrappers that will represent module.

By default wrappers will be searched in gen folder among the java classes with ending “Wrapper.java”. But you can change this defaults by setting system properties:

org.openl.rules.wrapper.dir – list of directories to search wrappers separated by ", "

org.openl.rules.wrapper.suffixes - list of wrapper endings separated by ", "

Excel file resolving strategy

This is the resolving strategy for the simplest OpenL project which contains only Excel files in root without wrappers and descriptor. Each Excel file represents module.