Search: concept

I wonder if we cannot somehow merge the concepts together. I guess I'd need to see some examples for this.

But it works, and its a good proof of concept. If anyone is up to writing a cleaner, more efficient version - please do, and share.

Documents listed here will ne copied in the new wiki but with overloaded contents that include the template wiki one ex : {{code}} #includeInContext("templatewiki:Space.Document") {{/code}} (% style="list-style-type: square" %) * documents to link in place of copy (not used yet) : same concept as include overload at copy but here with a real link.

. == Namespaces == Component API comes with "namespace" concept. The format of the namespaces is ##<type>:<id>##.

It's instantiated in the ##XWikiServletContextListener## class (in the ##xwiki-platform-container-servlet## module). == Accessing components in legacy code == The XWiki project is older that this component concept and sometimes you can find yourself in code which cannot really inject components, you should ideally try to convert it to the components world.

In addition, there are also some [[extra Configuration APIs using platform concepts>>Extension.PlatformConfigurationAPI.WebHome]]. == Configuration Source API == {{code language='java'}} @Role public interface ConfigurationSource { /** * @param <T> the value type * @param key the property key for which we want the value * @param defaultValue the value to use if the key isn't found * @return the property value is found or the default value if the key wasn't found * @since 2.0M1 */ <T> T getProperty(String key, T defaultValue); /** * @param <T> the value type * @param key the property key for which we want the value * @param valueClass the type of object that should be returned.