cmr.plugin.jar.types.web.routes — gov.nasa.earthdata/cmr-jar-plugin 0.1.2

plugin-routes clj

(plugin-routes jarfile in-jar-filepath route-keys api-key site-key)

Given a:

• jarfile
• an in-jarfile path to the plugin's configuration file
• the configuration value that points to the route-keys, and
• the configuration values that point to the api-key and site-key perform the actual lookup of the plugin routes in the plugin configuration, and assemble these into a data structure that can later be transformed into a hashmap.

plugins-routes clj

(plugins-routes jarfiles in-jar-filepath route-keys api-key site-key)

Perform the assembly done in plugin-routes over one or more jarfiles, converting the final data structure into a hashmap for easy lookup by the application or service that is managing these plugins.

resolve-routes clj

(resolve-routes routes-symbols)

This function wraps a utility function for resolving fully-qualified function names. What this offers over the utility function is the capability of wrapping multiple functions at ones, and removing any functions that don't resolve.

resolved-routes-fns clj

(resolved-routes-fns plugin-name
                     plugin-type
                     in-jar-filepath
                     route-keys
                     api-key
                     site-key)

(resolved-routes-fns jarfiles
                     plugin-name
                     plugin-type
                     in-jar-filepath
                     route-keys
                     api-key
                     site-key)

This function offers the convenience of locating all of the plugins that had declared themselves of the given name (e.g. 'CMR-Plugin') and type (e.g. 'service-bridge-app'), and once located, performing the function resolution and final data structure creation as done above.

Note: this function has been refactored several times, and the need for this function vs the plugins-routes function above is now questionable, worth determining, and possibly refactoring.