On 5/1/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
Not sure about this; the main documentation, in the section 1.5.1 in
tutorials / user guides on the "contract" says
reconfigure
This method is never called by the framework, unless
an application calls it on the Engine object – in which
case it the framework propagates it to all
annotators contained in the Engine.
Its purpose is to signal that the configuration
parameters have changed. A default implementation
of this calls destroy, followed by initialize. This
is the only case where initialize would be called
more than once. Users should implement whatever
logic is needed to return the annotator to an initialized
state, including re-reading the configuration parameter
data.
So this change sounds like a change in the contract for reconfigure?
Technically, that section of the document is only about the contract
for Annotators, not Collection Readers. We're a lot more vague about
the contract for Collection Readers. :)
Basically I want some way to tell a Collection Reader to "reset" back
to the beginning of the collection. I agree if we use reconfigure()
to do that then the right thing to do is to we should say so in the
documentation for the Collection Reader interface.
Also I could go along with using destroy() followed by initialize() as
the trigger for this, if you think that is better than reconfigure().
The CollectionReaderAdapter allows a CollectionReader to be used as a
CAS Multiplier. This is useful because we have said that
CollectionReader is just a specialization of CAS Multiplier that
ignores its input CAS. However since CAS Multipliers can receive
multiple input CASes we have to figure out what to do on the second
input CAS. I think the logical thing to do is to restart from the
beginning of the collection, so I'm looking for some way to do that.
-Adam
