Use the workbench module to try out DPML, scripting, prototype application components etc - it is fully expanded in the [install]/modules/workbench/ directory.

Click here to go to the workbench index page.

Address Space

The workbench module is configured to export the external address space /workbench/. All paths above workbench are rewritten to the root internal address space. Hence this resource has external address ffcpl:/workbench/index.html but internally it is located at ffcpl:/index.html.

The workbench module is mounted into the frontend fulcrum which presents itself on a HTTP server on port 8080.

The workbench module performs some file extension mapping for various language runtimes:

extension	language runtime
.idoc	Declarative Markup Language Runtime (DPML)
.bsh	Scripted Java (Beanshell)
.js	Javascript
.python	Jython (Python)
.groovy .gy	Groovy

If you create a directory called 'myDir' in the workbench module it will be externally available as http://localhost:8080/workbench/myDir/.

If you create a groovy script '/myDir/index.gy' in the workbench module the result of its execution will be made available as http://localhost:8080/workbench/myDir/index.gy.

Transports

The workbench module is imported into the Front-End Fulcrum - which hosts an HTTP transport running on port 8080. Therefore services in the workbench are exported as web-applications over the HTTP transport. This is convenient for rapid development but there is nothing which limits the scope of applications or services to being Web-apps. NetKernel is completely flexible and services may be externally exposed over a wide variety of transports or even just called as a "sub-process" from a Java application using the embedded API.