The config file

The following is the default config.xml file packaged in meso.jar. If there is no custom config file provided to the runtime, this file will be used instead. You can use this as a template for your custom config file:

<meso>

   <!-- enables the plugin for the meso: type scheme  -->
   <plugin class="meso.core.lang.MesoPlugin">
      <!--
         The path for loading *.meso source code.
         The path value should be in OS's native format, such as C:\foo\bar
         or /home/foo/bar.  Do not put trailing slashes.

         Use separate <src path="..." /> element for each path value.
      -->
      <src path="." />
   </plugin>

   <!--  enables the plugin for the java: type scheme -->
   <plugin class="meso.plugin.java.JavaPlugin">

      <!--
         Use the following element to add additional locations to the
         system's classpath for loading java classes from Meso.
         This URL is passed verbatim to URLClassLoader.  A tailing slash
         means that it is a directory, otherwise it is a jar file.
         For example:

              <src url="file:///home/foo/bar/" />

         Use separate <src url="..." /> element for each location.
      -->

   </plugin>

   <!--
     Enables the plugin for the imop: type scheme.

      Put allowProxy='false' attribute in this plugin element to disallow
      IMOP requests proxying through this host.  Enable proxy is necessary
      if this host want to serve clients behind a firewall.
      The default value is 'true'.
   -->
   <plugin class="meso.plugin.imop.ImopPlugin">

      <!--
         Use the following element to open a listener.
         Omit the host name (such as ":9900") to listen to all host names
         the specified port.  Omit the port number (such as "foo.com") to
         listen to IMOP's default port 90.

         <listener address="localhost:9900" />
      -->

      <!--
         Use the following element to setup host aliases.
         All requests to the "from" address will be redirected to the "to"
         address.  This might be necessary in development environment in that
         new programs have not been hosted on their production site yet.

         <alias from='api.org' to='localhost:9900'/>
      -->

      <!--
         The path for loading *.imop source code.
         The path value should be in OS's native format, such as C:\foo\bar
         or /home/foo/bar.  Do not put trailing slashes.

         Use separate <src path="..." /> element for each path value.
      -->
      <src path="." />

   </plugin>

</meso>

Note that even if you remove the plugin element for meso.core.lang.MesoPlugin, the meso: scheme will still be enabled as literals (such as 123 or "foobar") still associate with types in the scheme. However, the runtime will not be able to load any user-defined data type for the meso: scheme, because there is no root path defined for the scheme to search the source code from.

Use the -cf config_file_name argument to start the Meso runtime with a custom config file:

java -jar meso.jar -cf config_file_name main_UTL