Hi Andrej,
thanks for pointing this out. This is really a bug in the code rather than a documentation
error.
I created
https://hibernate.onjira.com/browse/HSEARCH-1118 to track the issue. There will
be a 4.1.1 release shortly which will include a fix for the issue.
Out of interest though, what is your use case for a custom scope and what is your custom
implementation doing?
--Hardy
On May 6, 2012, at 11:43 PM, Andrej Golovnin wrote:
Hi all,
I'm in process to migrate an application from an old Hibernate Search version
to the latest one. We have been used own implementation of Worker.
In the old Hibernate Search version it was possible to define own implementation
of Worker using the property "hibernate.search.worker.scope". But it seems not
possible to do it in the latest version although the Hibernate Search Guide suggest
to use this property.
After studying the sources of Hibernate Search I have found that the property
to be used is "worker.scope". This change was introduced with the work on
the issue HSEARCH-761.
Could you please verify what is the right property name and either correct the
Hibernate Search Guide or change the property name in the Environment
class to the old one.
Thanks in advance!
Best regards
Andrej Golovnin
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev