lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler" <>
Subject RE: ResourceLoaderAware inform() before or after init()
Date Mon, 13 Aug 2012 19:02:34 GMT
Hi David,

there is currently an issue open in Lucene (LUCENE-4256) handling the issues
with using AnalyzerFactories outside Solr. We are planning to refactor this
and move init args + Resource loader to the constructor (with signature
enforced by SPI loader), so factories can init themselves completely in ctor
and make all their fields/settings final. As this is now moved out of Solr,
the original plugin init requirements are no longer necessarily followed in
the same way as before for analysis factories.

Until we fix this, just make it working. But init() is in all cased called
before inform(), currently.


Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen

> -----Original Message-----
> From: Smiley, David W. []
> Sent: Monday, August 13, 2012 8:39 PM
> To: Dev
> Subject: ResourceLoaderAware inform() before or after init()
> Hi folks.
> I am wondering what the expected initialization sequence of the analysis
> factories are with respect to init() and ResourceLoaderAware.inform().  At
> judging from some tests, it seems that inform() is called afterwards.  I
> expecting the other way around, so that init() can do all the init stuff
it needs to
> do, instead of it being broken up between init() & inform().  In any case,
> should be documented.  I'm working on LUCENE-4303 and I hoped to lookup
> class names in the init() method and have inform() be a simple setter for
> loader.
> ~ David
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: For additional
> commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message