Community
Participate
Working Groups
The default web.xml created by the war-product tooling contains two init-params with param-name commandline. In this configuration it is not (yet) a problem because the first one is disabled / commented out, but as soon as s.o. removes the xml comments from the first one the OSGi console doesn't start and the parameter seems to be ignored: <!-- <init-param> <param-name>commandline</... <param-value>-console</... ... --> <init-param> <param-name>commandline</... <param-value>-registryMultiLanguage</... ... One solution could be to put both command line parameters into one attribute, e.g. <param-value>-console -registryMultiLanguage</...
I see your point and a while ago I ran into the same problem. So, the console param should be disabled by default. Maybe one solution can be to inline it like this: <init-param> <param-name>commandline</param-name> <param-value>-registryMultiLanguage <!-- -console --></param-value> </init-param> What do you think about this?
I agree that enabling the OSGi console is not the expected default behaviour ;-) Your suggestion looks good to me, but it should be well documented in the web.xml file what steps someone needs to do in order to activate the console.
Fixed in CVS HEAD.
