Do we need both developer and classic-pe profiles ... that's the question. So, here is a request to all module leads: In order to ascertain whether or not we need a new profile called developer profile in addition to the old classic-pe profile, we need some data in following format. We need to find out if the "default" value for a setting is different from the setting that is available in the PE domain.xml or any other config file. An example: The http-access-logging property for the virtual-server is not defined in domain.xml and its default value is "enabled", thus making it mandatory for the developers to modify the property to be set to false, so that access logging is disabled. All in all, I am looking for all such settings whose defaults on PE domain.xml (or other file) are different from what developers would like. If we have too many such differences, then only would it make sense to have two separate profiles like: classic-pe and developer.
The domain.xml settings (add a row)
| item |
default or the current domain.xml value |
value that makes sense for developers |
| http access logging |
true |
false |
| sso-enabled |
true |
false |
| secure ports |
enabled |
disabled (saves some time (~350 ms) during startup) |
| http-file-caching |
enabled (does not immediately reflect the static content) |
disabled (immediately reflect) |
| acceptor-threads |
1 |
2 |
| thread-count |
5 |
20 |
|
