Alexey, I think what you are really asking is whether the generated configuration should have the default values (if user didn't select them). Right?
My intuition would be mostly No - we do not need to include all of the default values into configuration, as you would have to include 100s of redundant properties there. However, I think that for the main configuration properties, e.g. cache-mode, atomicity, number of backups, etc. you should still generate them even if the values are defaults. Would be interesting to see what others think. Also, do we have a test instance for the web-control-center running somewhere? If so, it would be useful to provide a link here, so others could play with it and provide feedback. D. On Thu, Jul 30, 2015 at 8:21 AM, Alexey Kuznetsov <[email protected]> wrote: > Igniters, > > I'm working on Ignite Web Control Center (IGNITE-843 > https://issues.apache.org/jira/browse/IGNITE-843). > > One of its features is a XML / java code generation. > User select in UI different properties and get generated XML or java code > for cluster configuration. > > So the question: should I generate property that user select in UI if user > select default value for that property? > > For example. User select in combobox cache mode: PARTITIONED. > This is default mode for cache and could be omitted. > But somehow I feel that this will confuse users... > > What do you think? > > May be I should add an option on summary screen "Omit defaults"? > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com >
