entrypoint

Home > Books > NetKernel API and Services Reference > Accessor Listing > Entrypoint Management > entrypoint

Syntax

URI

active:entrypoint

Argument	Rules	Description
name	Mandatory	the name of the entrypoint
entrypoints	Mandatory	the XML collection of entrypoints
module	Optional	the URI of the module of the entrypoint
version	Optional	the version of the module

Example Usage

DPML

<instr>
  <type>entrypoint</type>
  <name>ep:myEntrypoint</name>
  <!-- use global entrypoints -->
  <entrypoints>active:entrypoint-list</entrypoints>
  <target>this:response</target>
</instr>

NetKernel Foundation API

req=context.createSubRequest("active:entrypoint");
req.addArgument("name", [resource representation, aspect, or URI] );
req.addArgument("entrypoints", [resource representation, aspect, or URI] );
result=context.issueSubRequest(req);

Purpose

The entrypoint accessor resolves an entrypoint name to the module interface URI which the entrypoint describes. The resolution is performed against the entrypoints list supplied as the entrypoints argument - to resolve against all currently known entrypoint then this argument should be active:entrypoint-list.

If the entrypoint name is globally unique then module and version are not necessary otherwise the first entrypoint with the name will be chosen.

The ep: scheme should be used to specify entrypoint names. For example the URI of the named entrypoint for this guide is ep:doc_entrypoint_ura_resolve.

See the ext_entrypoint guide for more details on entrypoints.