Hi Patrik, you can enable the "executionmetadata=true" option when sending requests.
from the documentation [1] - - - executionmetadata=true/false: Allows the include of execution metadata in the enhancement metadata of the response. Such data include also the execution plan used to enhance the parsed content. This information is typically only useful to clients that want to know how the parsed content was processed by the enhancer. NOTE that the execution metadata can also be requested by using the multi-part content item API described below. - - - The documentation of the Execution Metadata can be found at [2] Hope this answers your question best Rupert [1] http://stanbol.apache.org/docs/trunk/components/enhancer/enhancerrest.html [2] http://stanbol.apache.org/docs/trunk/components/enhancer/executionmetadata.html On Thu, Mar 12, 2015 at 11:08 AM, Patrick Kirsch <[email protected]> wrote: > Hey list, > > is there any debugging/development best practices for debugging a enhancer > chain available? > > Here is my current situation: > - I have enabled geonames enhancer engine, it is configured within > chain 'default' and 'all active'. Geonames 'mvn test' passes and a valid > api.geonames.org account is configured and known working. > > - Now if I use the enhancer chain e.g. via webfrontend geonames > with query "New Zealand" geonames.impl.LocationEnhancementEngine gets > executed. > > - But if I try "Bad Düben" /1/ the > geonames.impl.LocationEnhancementEngine is not executed. > > > So my question is, what is the best way to debug the enhancer chain, to > check why certain enhancers do not get executed? > > > /1/ Small town in Germany with German Umlaute. > > Thanks > Patrick > -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen | REDLINK.CO .......................................................................... | http://redlink.co/
