NetKernel registers a protocol handler java.net.ContentHandler for the scheme of internal which enables technologies which rely on the java.net.URLConnection to locate resources by URL.

URLConnections used to retrieve resources differ from the NetKernel resource resolution infrastructure in these important ways:

• Only an java.io.InputStream can gained to pull bytes from the resource. Therefore no higher level datatypes (Aspects) can be retrieved.
• The context of the current module cannot be used to locate the resource as URLConnections are assumed to be global. Therefore URL are passed to the NetKernel Internal Transport in a similar way to the operation of NetKernel in co-processor deployment mode.

For a technology to use NetKernel to resolve a resource it should prefix internal:, for example internal:ffcpl:/mymodule/myresource.txt

For the integration of new technologies at is generally best not to use this mechanism for retrieving resources but to use the NKF APIs.