Got it! The code must be modified to invoke I_Info.get instead of pluginInfo.getParameters().getProperty(key, def) to force the expansion.
Thanks a lot. Cheers from Sunny Western Australia, Christian -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michele Sent: Monday, August 18, 2008 6:29 PM To: [email protected] Subject: Re: [xmlblaster] Variable substitution in xmlBlasterPlugins.xml Salut Christian, you are right, as it looks like now there is currently no replacement of such variables in the plugins. One fast solution would be to let your plugin extend the GlobalInfo (which is a base class for plugins in the contrib package). This way the transformation would be done implicitly. If you do that, you should move your init(...) Code to doInit(...) (and make sure not to overwrite the init method). Cheers Michele christian chevalley wrote: > > Hi Guys, > > I am not sure I have missed something here, but it seems to me that > configuration variable substitution is not implemented for attributes > in xmlBlasterPlugins.xml. This is working fine with the properties > file (xmlBlaster.properties) but doesn't work as described in > engine.runlevel. I have tried various possibilities but no luck so far: > > -Dxcare.partition.base=${PARTITION_BASE} on the command line followed by : > > <plugin id='JobScheduler' create='true' className='.'> > > <attribute > id='config'>${xcare.partition.base}/profiles/jobs.xml</attribute> > > . > > </plugin> > > In xmlBlasterPlugins.xml. 'xcare.partition.base' Is not substituted. > The same is true whenever using ${java.io.tmpdir} or other java > environment variable. > > Is it the plugin's responsibility to perform the variable substitution? > > Cheers -- Christian >
