lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shad Storhaug (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENENET-572) Make Lucene.Net.Expressions Configurable via Dependency Injection
Date Sun, 23 Apr 2017 22:46:04 GMT

     [ https://issues.apache.org/jira/browse/LUCENENET-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shad Storhaug updated LUCENENET-572:
------------------------------------
    Affects Version/s:     (was: Lucene.Net 5.0 PCL)
                       Lucene.Net 4.8.0
        Fix Version/s:     (was: Lucene.Net 5.0 PCL)
                       Lucene.Net 4.8.0

> Make Lucene.Net.Expressions Configurable via Dependency Injection
> -----------------------------------------------------------------
>
>                 Key: LUCENENET-572
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-572
>             Project: Lucene.Net
>          Issue Type: Improvement
>    Affects Versions: Lucene.Net 4.8.0
>            Reporter: Shad Storhaug
>             Fix For: Lucene.Net 4.8.0
>
>
> Lucene.Net.Expressions currently reads its function data from a configuration file using
Support.Configuration classes. We should aim to "push" the configuration down from the consuming
application rather than "pull" it from a source that the consuming application does not control.
> In Java, the initial list of functions was in an embedded text file, and it could be
extended by passing in a ClassLoader (which is roughly equivalent to .NET's Assembly class).
For some reason, the .NET implementation has some auto-generated wrapper code, and it is unclear
what auto-generated it and if it can be re-generated. We need to investigate why the implementation
is so different, and make it Dependency Injection friendly.
> After this task is complete the Support.Configuration namespace should be deleted. All
configuration should be supplied directly by the consuming application, not pulled from configuration
files.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message