wormhole

Home > Books > NetKernel API and Services Reference > Accessor Listing > Layer1 > wormhole

Module

The module accessor is exported by the urn:org:ten60:netkernel:ext:layer1 module. Import this module to gain access to the accessor.

Syntax

URI

active:module

Argument	Rules	Description
module	Mandatory	the module to issue a request to directly
version	Optional	the version of the module to issue a request to
resource	Mandatory	the URI to issue on the interface of the module

Example Usage

DPML

<instr>
  <type>module</type>
  <module>urn:org:ten60:netkernel:ext:layer1</module>
  <version>version:1.2.18</version>
  <resource>ffcpl:/entrypoints.xml</resource>
</instr>

NetKernel Foundation API

// beanshell example
main()
{   req=context.createSubRequest("active:module");
    req.addArgument("module","urn:org:ten60:netkernel:ext:layer1");
    req.addArgument("version","version:1.2.18");
    req.addArgument("resource","ffcpl:/entrypoints.xml");
    context.issueAsyncSubRequest(req);
}

Purpose

This accessor should not be used by regular application code. It is better to import a module into your module if that module's functionality is needed.

The wormhole accessor is useful for tools and system utilities which wish to access all deployed modules without needing to import them into their address space. It provides a mechanism for "tunnelling through address hyperspace" a request directly onto the external interface of a module without going though the regular request resolution process. When a generated request enters the target module its super-stack is lost preventing it from seeing where it came from.

The request which passes through the wormhole inherits the properties of the request issued to the wormhole accessor. The URI of the request is taken from the uri argument. The request type (SOURCE/SINK/etc) and required resource aspect class are copied through.