ResourceService web.xml

webapps/resourceService/WEB-INF/web.xml

    <context-param>
            <param-name>OrgDataSource</param-name>
        <param-value>com.acme.datastore.orgdata.AcmeDataSourceImpl</param-value>
        <description>
                The name of the class (an extension of 'DataSource') which is used
            as the 'data translation layer' between the ResourceService and a source
            of organisational data. The default YAWL implementation is the
            'HibernateImpl' class. NOTE: For external data sources, the fully qualified
            name of the class is required (e.g. com.example.myDataSource)
        </description>
    </context-param>

    <context-param>
        <param-name>ExternalPluginsPath</param-name>
        <param-value>/usr/local/tomcat/acme-jars</param-value>
        <description>
            Sets the path(s) to search for external 'plugin' classes (i.e. codelets,
            allocators, filters, constraints, data sources, dynamic form attributes).
            Each path must refer to a location on the local disk, for example:
            "C:\yawlplugins". Several paths can be provided, separated by semi-colons,
            for example: "C:\yawlplugins;C:\some\other\place".

            Each path and its sub-directories will be searched for classes, or jar files
            that contain classes, that extend from the corresponding base class. Class
            files must be arranged in their package structure. For example, if the
            'ExternalPluginsPath' is set 'C:\yawlplugins' and there is a codelet file
            called 'MyCodelet.class' and it has a package 'com.example.yawl.codelets'
            then its file path is expected to be:
            'C:\yawlplugins\com\example\yawl\codelets\MyCodelet.class'.

            If there are no external plugins, then this param can be commented out or
            the param-value can be left blank.
        </description>
    </context-param>