Hello all,
I have a request to make. Can we make sure to not put Service Configuration
properties files in the src/main/resources directories? The reason is that
it gets bundled with the jar making it impossible to use the following to
set defaults
module.on(JdbmConfiguration.class).to().file().set(jdbmFileName());
I had my jdbm entity store working, then because of this change all the data
all of a sudden went away. I had to fight this same battle with the
JettyService. The reason this is important to me is that it doesn't seem
like qi4j should dictate what these defaults are and it makes it impossible
to use any other method to configure the services. The way that I want to
configure my services is to have a simple application.properties file that I
can use to set things like what the port is that jetty runs on, the
directories where the jdbm store and rdf repository are stored, etc. (really
I just have an application.home directory set in the application.properties
and then all the data lives under that directory).
Anyways, the point is that shipping Service Configuration properties files
limits the way the application developer can choose to configure their
application.
Thanks,
Rich
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
