Please read my reply describing the detailed consequences of this change. The behaviour only changes n a corner case, which only exists since our latest version 1.2.20, wihch is not very old. everything that was possible with JkEnvVar before 1.2.20 neither changed in 1.2.20 not due to this patch.
Regards, Rainer Jim Jagielski schrieb: > > On Feb 19, 2007, at 9:44 AM, Mladen Turk wrote: > >> [EMAIL PROTECTED] wrote: >>> /* env_name is mandatory, default_value is optional. >>> - * No value means set the variable to an empty string. >>> + * No value means send the attribute only, if the env var is set >>> during runtime. >>> */ >> >> Think this will break any existing configuration. >> Something like that cannot be part of the 1.2.x branch thought. >> > > If it does break existing configs, and therefore > introduces a regression, then -1 on the patch. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
