NetKernel 3.3.1 includes a new feature in the Resource Request Trace Tool which, combined with a simple configuration, provides
an easy way to build and verify portions of an application.
The Resource Request Tool is available from the Developer tab in the NetKernel management interface. This tool allows you to specify a resource address and to make a request with the source verb delivered to either the module''s external interface or the inner private address space.
You may choose the "Resolve" button, which only performs the address resolution phase of request processing, to confirm that the module address mappings are set up correctly. Or you may choose the "Resolve and Execute" button to also cause the resolved-to Endpoint to receive the request. New in NetKernel 3.3.1 is the "Display Representation" button which will display in the browser the representation returned for the request.
The tip is to set up a rewrite rule in the mapping section of your module''s module.xml file to map the address
to the portion of the application or the service you are developing. For example:
Then you simply request the URI ffcpl:/test and select the "inner" option and your request will be mapped to the program you are working on. You can quickly verify that the mappings are correct, run the program and see the result without setting up a separate path from a browser through a fulcrum, the modules export section and rewrite sections.
In a refinement of this approach you could use a mapper with a links.xml resource to define the mapping between ffcpl:/test and the code you are developing. By using a mapper you avoid the need to hot-restart your module each time you make a change and you could develop a family of test mappings such as ffcpl:/test/program1, ffcpl:/test/program2 if you are developing a set of capabilities.
The Resource Request Tool is available from the Developer tab in the NetKernel management interface. This tool allows you to specify a resource address and to make a request with the source verb delivered to either the module''s external interface or the inner private address space.
You may choose the "Resolve" button, which only performs the address resolution phase of request processing, to confirm that the module address mappings are set up correctly. Or you may choose the "Resolve and Execute" button to also cause the resolved-to Endpoint to receive the request. New in NetKernel 3.3.1 is the "Display Representation" button which will display in the browser the representation returned for the request.
The tip is to set up a rewrite rule in the mapping section of your module''s module.xml file to map the address
ffcpl:/test |
|
<rewrite>
<match>ffcpl:/test</match> <to>active:dpml+operand@ffcpl:/resources/programs/myProg.idoc</to> </rewrite> |
Then you simply request the URI ffcpl:/test and select the "inner" option and your request will be mapped to the program you are working on. You can quickly verify that the mappings are correct, run the program and see the result without setting up a separate path from a browser through a fulcrum, the modules export section and rewrite sections.
In a refinement of this approach you could use a mapper with a links.xml resource to define the mapping between ffcpl:/test and the code you are developing. By using a mapper you avoid the need to hot-restart your module each time you make a change and you could develop a family of test mappings such as ffcpl:/test/program1, ffcpl:/test/program2 if you are developing a set of capabilities.
