8 Jan
2009
8 Jan
'09
3:47 p.m.
On Jan 8, 2009, at 2:39 PM, Jerome Velociter wrote:
Vincent Massol wrote:
This is not a problem. The problem is that you need to move existing
configuration data to the new xwiki.properties file and change the
code that uses this data. Unless your use case is for new params in
which case the only question is under what name you want your
configuration component to be made visible for velocity.
Technical detail: we have a VelocityContextInitializer interface for
making components visible to velocity. We don't have the future
velocity bridge but that shouldn't be a showstopper.
-Vincent
+0 (I'm not a big fan of it though since
it's overloading even more
our XWiki API) since we have it in XWiki.java but provided you fix
the
param names:
* prefname --> preferenceName
* fallback_param --> fallbackPropertyName
Note: that what's even better is to use the new configuration module
which supports this use case in a much nicer way.
Yes but we don't have a velocity bridge to make it public, do we? Jerome.
>
> On Jan 8, 2009, at 2:24 PM, Jerome Velociter wrote:
>
>> The signature would be :
>>
>> public String getXWikiPreference(String prefname, String
>> fallback_param,
>> String default_value);
>>
>> The underlaying method already exists in the non API XWiki.java (was
>> added for http://jira.xwiki.org/jira/browse/XWIKI-2569).
>>
>> What this method exactly do is : "Obtain a preference value for the
>> wiki, looking up first in the XWiki.XWikiPreferences document, then
>> fallbacking on a config parameter when the first lookup gives an
>> empty
>> string, then returning the default value if the config parameter
>> returned itself an empty string."
>>
>> My +1:
>>
>> +1
>>
>> Jerome.
>>
>> PS: I've created a JIRA for it: http://jira.xwiki.org/jira/browse/XWIKI-3086