Hi,
yes, this is correct and intended, but it is missing the original idea
and thus it is probably not necessary.
The reload of the script needs to be supported for some special use
cases like changing the rules during the pipeline processing. The
additional analysis engine are however directly specified in the
configuration parameters and should only be changed with reconfigure().
Does this cause problems? I would not change it right now because I am
also thinking about removing these parameters at all in a next major
release since they are redundant and could be induced using the script
files. The objects could be cached, but the initialize is normally the
expensive part.
Best,
Peter
Am 30.01.2016 um 23:33 schrieb Miguel Alvarez:
Hi Peter,
I have another question about external engines :- ) When the reloadScript
parameter is set to false only one instance of the external engine is
created and the initialize method is invoked only once before processing all
the CASes. This is what I was expecting. But when the reloadScript is set to
true the initialize method of the external engines is invoked once per CAS,
as the documentation indicates, but it looks like a new instance of the
external engine is created for each CAS too. Is this the expected behaviour?
I was expecting for RUTA to create just once instance of the engine, and
then on that instance invoke the initialize method once per CAS, but I
couldn't find any information about this on the documentation.
Thanks again.
Cheers,
Miguel
