Re: making schema.xml nicer to read/use

2006-08-23 Thread Bertrand Delacretaz
On 8/22/06, Yonik Seeley [EMAIL PROTECTED] wrote: ...So you would say LowerCaseFilter instead of LowerCaseFilterFactory... I like the idea, as long as it's made sufficiently transparent. For example by logging a warning when a Factory is not found and the component is created by reflection.

Re: making schema.xml nicer to read/use

2006-08-23 Thread Chris Hostetter
: - if no factory can be found, an attempt will be made to construct : one dynamically (easiest would be to create a generic factory that : works via reflection). People could use simple filters w/o creating a : factory for it. I think i mentioned this before ... my opinion depends on what the

making schema.xml nicer to read/use

2006-08-22 Thread Yonik Seeley
What do people thing of leaving off Factory from tokenizers and token filters in schema.xml. Let the user say what filter they want, not necessarily how to get it. So you would say LowerCaseFilter instead of LowerCaseFilterFactory. Implementation details: - Specification of a Factory would

Re: making schema.xml nicer to read/use

2006-08-22 Thread Mike Klaas
On 8/22/06, Yonik Seeley [EMAIL PROTECTED] wrote: What do people thing of leaving off Factory from tokenizers and token filters in schema.xml. Let the user say what filter they want, not necessarily how to get it. So you would say LowerCaseFilter instead of LowerCaseFilterFactory.