[
https://issues.apache.org/jira/browse/CONNECTORS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874035#action_12874035
]
Karl Wright commented on CONNECTORS-37:
---------------------------------------
I am not happy with the idea of configuration living in both the database and
in an XML file. The idea that you can somehow read the XML configuration "just
once" the first time LCF is started seems rife with potential problems. Far
from improving the user experience, I think that the proposed design would
instead create enormous confusion.
Perhaps the problem is that Mr. Krupansky is attempting to do too much with a
single configuration file here. It would be perfectly reasonable to introduce
a "read setup information" command that would read what is effectively a
sequence of commands from an XML file. However, that command file would be an
"execute once" kind of affair - although it could be coded in such a way as to
ignore the definition of entities that already exist in the database.
Nevertheless, such a file would have a very different usage pattern than the
configuration file as it exists today, so I'd have a lot of concern using the
same configuration file for both purposes.
> LCF should use an XML configuration file, not the simple name/value config
> file it currently has
> ------------------------------------------------------------------------------------------------
>
> Key: CONNECTORS-37
> URL: https://issues.apache.org/jira/browse/CONNECTORS-37
> Project: Lucene Connector Framework
> Issue Type: Improvement
> Components: Framework core
> Reporter: Karl Wright
>
> LCF's configuration file is limited in what it can specify, and XML
> configuration files seem to offer more flexibility and are the modern norm.
> Before backwards compatibility becomes an issue, it may therefore be worth
> converting the property file reader to use XML rather than name/value format.
> It would also be nice to be able to fold the logging configuration into the
> same file, if this seems possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
