Wiki source code of Writing XWiki Components

Version 66.2 by Vincent Massol on 2017/02/24

version	line-number	content
46.1	1	{{box cssClass="floatinginfobox" title="Contents"}}
	2	{{toc/}}
	3	{{/box}}
1.1	4
52.3	5	This tutorial guides you through the creation of a XWiki component, which is a way to extend or customize the XWiki platform. Indeed the XWiki platform is composed of components and it's possible to replace the default implementations with your own implementations. It's also possible to add new component implementations to extend the platform such as by implementing new [[Rendering Macros>>DevGuide.RenderingMacroTutorial]].
1.1	6
46.1	7	{{info}}
52.3	8	Components replace the older plugin architecture which has been deprecated a while ago.
46.1	9	{{/info}}
28.1	10
37.5	11	You should start by reading the [[Reference document on XWiki Components>>extensions:Extension.Component Module]].
1.1	12
27.1	13	= Let's get started! =
1.1	14
	15	Enough talking, let's see some code!
	16
52.3	17	In the following tutorial we will guide you through writing a simple component, helping you to quickly get oriented in the XWiki components world and explaining how it works.
1.1	18
28.1	19	== Creating a XWiki component using Maven ==
1.1	20
52.3	21	As you've read in the [[XWiki Component Reference>>extensions:Extension.Component Module]] writing a component is a three-steps process (component interface, component implementation and registration of component).
26.1	22
52.3	23	To make it easier for you to get started, we have created a [[Maven Archetype>>http://maven.apache.org/archetype/maven-archetype-plugin/]] to help create a simple component module with a single command.
37.2	24
52.3	25	After you've [[installed Maven>>http://maven.apache.org/]], open a shell prompt an type: {{code language="none"}}mvn archetype:generate{{/code}}.
1.1	26
47.1	27	This will list all archetypes available on Maven Central. If instead you wish to directly use the XWiki Component Archetype, you can directly type (update the version to use the version you wish to use):
	28
	29	{{code language="none"}}
	30	mvn archetype:generate \
	31	-DarchetypeArtifactId=xwiki-commons-component-archetype \
	32	-DarchetypeGroupId=org.xwiki.commons \
53.4	33	-DarchetypeVersion=5.4.4
47.1	34	{{/code}}
	35
28.1	36	Then follow the instructions. For example:
37.2	37
28.2	38	{{code language="none"}}
28.1	39	[INFO] Scanning for projects...
	40	[INFO]
	41	[INFO] ------------------------------------------------------------------------
	42	[INFO] Building Maven Stub Project (No POM) 1
	43	[INFO] ------------------------------------------------------------------------
	44	[INFO]
53.4	45	[INFO] >>> maven-archetype-plugin:2.2:generate (default-cli) @ standalone-pom >>>
28.1	46	[INFO]
53.4	47	[INFO] <<< maven-archetype-plugin:2.2:generate (default-cli) @ standalone-pom <<<
28.1	48	[INFO]
53.4	49	[INFO] --- maven-archetype-plugin:2.2:generate (default-cli) @ standalone-pom ---
28.1	50	[INFO] Generating project in Interactive mode
53.4	51	[INFO] Archetype repository missing. Using the one from [org.xwiki.commons:xwiki-commons-component-archetype:6.1-milestone-1] found in catalog remote
28.1	52	Define value for property 'groupId': : com.acme
53.4	53	Define value for property 'artifactId': : example
28.1	54	Define value for property 'version': 1.0-SNAPSHOT: :
	55	Define value for property 'package': com.acme: :
	56	Confirm properties configuration:
	57	groupId: com.acme
	58	artifactId: example
	59	version: 1.0-SNAPSHOT
	60	package: com.acme
	61	Y: : Y
	62	[INFO] ----------------------------------------------------------------------------
53.4	63	[INFO] Using following parameters for creating project from Archetype: xwiki-commons-component-archetype:5.4.4
28.1	64	[INFO] ----------------------------------------------------------------------------
	65	[INFO] Parameter: groupId, Value: com.acme
47.1	66	[INFO] Parameter: artifactId, Value: example
	67	[INFO] Parameter: version, Value: 1.0-SNAPSHOT
28.1	68	[INFO] Parameter: package, Value: com.acme
47.1	69	[INFO] Parameter: packageInPathFormat, Value: com/acme
	70	[INFO] Parameter: package, Value: com.acme
	71	[INFO] Parameter: version, Value: 1.0-SNAPSHOT
	72	[INFO] Parameter: groupId, Value: com.acme
28.1	73	[INFO] Parameter: artifactId, Value: example
47.1	74	[INFO] project created from Archetype in dir: /private/tmp/example
28.1	75	[INFO] ------------------------------------------------------------------------
	76	[INFO] BUILD SUCCESS
	77	[INFO] ------------------------------------------------------------------------
53.4	78	[INFO] Total time: 25.019s
	79	[INFO] Finished at: Thu May 29 18:49:46 CEST 2014
	80	[INFO] Final Memory: 11M/26M
28.1	81	[INFO] ------------------------------------------------------------------------
28.2	82	{{/code}}
1.1	83
28.2	84	Then go in the created directory (##example## in our example above) and run ##mvn install## to build your component.
1.1	85
29.1	86	== The Component explained ==
27.1	87
29.1	88	Assume, for the following explanations, that the package you used is ##com.acme##
26.1	89
29.1	90	Navigating in the component project folder, you will see the following standard Maven project structure:
26.1	91
30.1	92	{{code language="none"}}
1.1	93	pom.xml
29.1	94	src/main/java/com/acme/HelloWorld.java
	95	src/main/java/com/acme/internal/DefaultHelloWorld.java
33.1	96	src/main/java/com/acme/internal/HelloWorldScriptService.java
19.1	97	src/main/resources/META-INF/components.txt
29.1	98	src/test/java/com/acme/HelloWorldTest.java
26.1	99	{{/code}}
1.1	100
52.3	101	which corresponds to the default files created: the ##HelloWorld## interface (a.k.a component role), its implementation ##DefaultHelloWorld## (component implementation), a test class for this component ##HelloWorldTest##, the component declaration file ##components.txt## and the Maven project ##pom.xml## file. The ##HelloWorldScriptService## file is described below when we explain how to make the component's API available to wiki pages.
26.1	102
52.3	103	If you have a look in ##pom.xml## you'll notice the following dependencies:
26.1	104
30.1	105	{{code language="xml"}}
29.1	106	<dependencies>
1.1	107	<dependency>
44.3	108	<groupId>org.xwiki.commons</groupId>
45.1	109	<artifactId>xwiki-commons-component-api</artifactId>
44.3	110	<version>${commons.version}</version>
1.1	111	</dependency>
29.1	112	<!-- Testing dependencies -->
1.1	113	<dependency>
44.3	114	<groupId>org.xwiki.commons</groupId>
	115	<artifactId>xwiki-commons-test</artifactId>
	116	<version>${commons.version}</version>
1.1	117	<scope>test</scope>
29.1	118	</dependency>
1.1	119	</dependencies>
26.1	120	{{/code}}
27.1	121
46.1	122	The code above defines the dependency on the ##xwiki-core-component-api## in the core which is where XWiki Component notions are defined. There's also a dependency on ##xwiki-core-shared-tests## which provides helper classes to easily test components.
1.1	123
52.3	124	The interface file (##HelloWorld.java##) contains the definition of a regular Java interface and looks like this:
26.1	125
30.1	126	{{code language="java"}}
52.4	127	@Role /* annotation used for declaring the service our component provides */
19.1	128	public interface HelloWorld
	129	{
	130	String sayHello();
	131	}
26.1	132	{{/code}}
1.1	133
29.1	134	Keep in mind that this interface specifies the API that other components can use on your component. In our case, we'll build a polite component that can ##sayHello()##.
27.1	135
42.3	136	Then we have the implementation of the interface, the ##DefaultHelloWorld## class.
23.1	137
46.1	138	{{code language="java"}}
29.1	139	@Component /* annotation used for declaring a component implementation */
44.1	140	@Singleton /* annotation used for defining the component as a singleton */
29.1	141	public class DefaultHelloWorld implements HelloWorld
26.1	142	{{/code}}
19.1	143
59.1	144	Note that optionally, there is a ##@Named## annotation to specify a component //hint//. This is useful especially when we want to distinguish between several implementations for the same type of component. Imagine we had a special HelloWorld implementation taking the greeting message from a database; it could look like:
26.1	145
46.1	146	{{code language="java"}}
44.1	147	@Component
	148	@Named("database")
29.1	149	public class DatabaseHelloWorld implements HelloWorld
26.1	150	{{/code}}
27.1	151
29.1	152	Then the ##sayHello## in ##DefaultHelloWorld## is basic in this example:
26.1	153
30.1	154	{{code language="java"}}
19.1	155	/**
	156	* Says hello by returning a greeting to the caller.
	157	*
	158	* @return A greeting.
	159	*/
	160	public String sayHello()
	161	{
	162	return "Hello world!";
	163	}
26.1	164	{{/code}}
1.1	165
53.1	166	And now, the ##components.txt## file, in which component implementations present in this jar are specified for the ##ComponentManager## to register them.
1.1	167
46.1	168	{{code language="none"}}
	169	com.acme.internal.DefaultHelloWorld
	170	{{/code}}
1.1	171
27.1	172	= How to find my component and use it? =
24.1	173
27.1	174	== From other components ==
1.1	175
57.1	176	To access your component from another component we use the components engine, and specify the dependencies, leaving instantiation and component injection to be handled by the component manager.
27.1	177
58.1	178	In order to use the ##HelloWorld## component, you need a reference to it in the component that uses it. For this, you should use a member variable in the implementation of the using component, for example, a ##Socializer## component will need to be able to say hello to the world:
27.1	179
26.1	180	{{code}}
19.1	181	@Component
44.1	182	@Singleton
30.1	183	public class DefaultSocializer implements Socializer
1.1	184	{
	185	[...]
	186
	187	/** Will be injected by the component manager */
44.1	188	@Inject
1.1	189	private HelloWorld helloWorld;
	190
52.1	191	/** Will be injected by the component manager */
	192	@Inject
	193	@Named("database")
	194	private HelloWorld databaseWorld;
	195
1.1	196	[...]
	197	}
26.1	198	{{/code}}
1.1	199
44.1	200	Note the ##@Inject## annotation, which instructs the component manager to inject the required component where needed.
27.1	201
26.1	202	And that's it, you can now use the ##helloWorld## member anywhere in the ##DefaultSocializer## class freely, without further concerns, it will be assigned by the component manager provided that the ##HelloWorld## component is on the classpath at runtime when the ##Socializer## is used. Such as:
1.1	203
26.1	204	{{code}}
30.1	205	public class DefaultSocializer implements Socializer
1.1	206	{
	207	[...]
	208
	209	public void startConversation()
	210	{
	211	this.helloWorld.sayHello();
	212
	213	[...]
	214	}
	215
	216	[...]
	217	}
26.1	218	{{/code}}
1.1	219
26.1	220	More, note that all through the process of defining a communication path between two components, we never referred components implementations, all specifications being done through //roles// and //interfaces//: the implementation of a service is completely hidden from any code external to the component.
27.1	221
	222	== From non-components java code (e.g. older plugins) ==
1.1	223
31.1	224	For this kind of usages, since we cannot use the component-based architecture advantages and the "magic" of the component manager, the XWiki team has created a helper method that acts like a bridge between component code and non-component code, the ##com.xpn.xwiki.web.Utils.getComponent(String role, String hint)## that gets the specified component instance from the component manager and returns it. As seen in the previous sections, the hint is an optional identifier, additional to ##role##, used to differentiate between implementations of the same interface: the //roles// identify services while the hints help differentiate between implementations. The ##getComponent## function also has a signature without the ##hint## parameter, that uses the default hint.
30.2	225
31.1	226	To use our greetings provider component, we would simply invoke:
27.1	227
26.1	228	{{code}}
31.1	229	HelloWorld greeter = Utils.getComponent(HelloWorld.class);
1.1	230	greeter.sayHello();
52.1	231
	232	HelloWorld databaseGreeter = Utils.getComponent(HelloWorld.class, "database");
	233	greeter.sayHello();
26.1	234	{{/code}}
1.1	235
52.3	236	{{warning}}
	237	Even if the object returned by this function is an instance of the ##DefaultHelloWorld##, you should never declare your object of the implementation type nor cast to implementation instead of interface.
	238	{{/warning}}
27.1	239
52.3	240	A component is represented by its interface, the implementation for such a service can be provided by any code, any class so relying on the implementation type is neither good practice (since the interface contract should be enough for a component), nor safe. In the future, a maven enforcer plugin will be setup in the build lifecycle, so that any reference to component implementations (located in an "internal" subpackage) will cause build errors.
	241
46.1	242	{{info}}
	243	The usage of ##Utils.getComponent()## functions is highly discouraged, reserved for this type of situations, when you need to access a component from non-componentized code. For the componentized code, you should use either dependency declaration at 'compile-time' (as shown before with annotations) or, if you need to resolve components dependencies at runtime, use the ##ComponentManager##, which you can access by implementing the Composable interface as described in the [[Component Module Reference>>extensions:Extension.Component Module]].
	244	{{/info}}
1.1	245
27.1	246	== From wiki pages ==
15.1	247
52.3	248	Components can be made accessible to wiki pages by writing a ##ScriptService## implementation. They can then be accessed using any provided scripting language (velocity, groovy, python, ruby, php, etc).
1.1	249
32.1	250	Let's make our ##sayHello## method accessible:
	251
	252	{{code language="java"}}
44.1	253	@Component
	254	@Named("hello")
	255	@Singleton
32.1	256	public class HelloWorldScriptService implements ScriptService
	257	{
44.1	258	@Inject
32.1	259	private HelloWorld helloWorld;
	260
	261	public String greet()
	262	{
	263	return this.helloWorld.sayHello();
	264	}
	265	}
	266	{{/code}}
	267
53.2	268	Note: We could have also injected the Named component instead, "database" which would look like:
	269
63.3	270	{{code language="java"}}
63.2	271	// Or inject a Named Component
	272	@Inject
	273	@Named("database")
	274	private HelloWorld databaseWorld;
	275	{{/code}}
53.1	276
52.3	277	{{info}}
	278	The component hint used (the ##hello## part in the ##@Component##) is the name under which the script service will be accessible from scripting languages.
	279	{{/info}}
32.1	280
52.3	281	For example to access it in Velocity you'd write: {{code language="velocity"}}$services.hello.greet(){{/code}}.
32.1	282
52.3	283	From Groovy: {{code language="groovy"}}services.hello.greet(){{/code}}.
32.1	284
34.1	285	Now for our script service to work we need to register it as a component and thus add it to the ##META-INF/components.txt## file:
32.1	286
52.3	287	{{code language="none"}}
	288	...
	289	com.acme.internal.HelloWorldScriptService
	290	{{/code}}
	291
33.1	292	We also need to make the Script Service infrastructure available in our classpath. This is done by adding the following in your ##pom.xml## file:
52.3	293
	294	{{code language="xml"}}
	295	<dependency>
44.3	296	<groupId>org.xwiki.commons</groupId>
	297	<artifactId>xwiki-commons-script</artifactId>
	298	<version>${commons.version}</version>
52.3	299	</dependency>
	300	{{/code}}
33.1	301
35.1	302	= Accessing Legacy code =
1.1	303
35.1	304	By legacy we mean old XWiki code that hasn't been moved to components yet.
1.1	305
27.1	306	== The XWiki data model ==
1.1	307
26.1	308	Since the XWiki data model (documents, objects, attachments, etc.) reside in the big, old ##xwiki-core## module, and since we don't want to add the whole core and all its dependencies as a dependency of a simple lightweight component (this would eventually lead to a circular dependency, which is not allowed by maven), the current strategy, until the data model is completely turned into a component, is to use a //bridge// between the new component architecture and the old ##xwiki-core##.
27.1	309
52.3	310	In short, the way this works is based on the fact that implementations for a component don't have to be in the same ##.jar## as the interface, and there is no dependency //from// the component interface //to// the actual implementation, only the other way around. So, we made a few simple components that offer basic access to XWiki documents, and declare the classes in ##xwiki-core## as the default implementation for those components.
27.1	311
60.6	312	If your component needs to access the XWiki data model, it will use the components from the ##xwiki-platform-bridge## module for that. Note that these interfaces are rather small, so you can't do everything that you could with the old model. If you need to add some methods to the bridge, feel free to propose it on the [[mailing list>>dev:Community.MailingLists]].
27.1	313
26.1	314	For example:
1.1	315
26.1	316	{{code}}
19.1	317	@Component
44.1	318	@Singleton
1.1	319	public class DefaultHelloWorld implements HelloWorld
	320	{
	321	/** Provides access to documents. Injected by the Component Manager. */
44.1	322	@Inject
1.1	323	private DocumentAccessBridge documentAccessBridge;
	324
	325	[...]
	326
	327	private String getConfiguredGreeting()
	328	{
	329	return documentAccessBridge.getProperty("XWiki.XWikiPreferences", "greeting_text");
	330	}
26.1	331	{{/code}}
1.1	332
49.1	333	=== Querying the data model ===
	334
	335	Queries can be performed by using an instance of a QueryManager, which can be obtained and used as follows :
	336
	337	{{code}}
	338	QueryManager queryManager = (QueryManager) componentManager.getInstance(QueryManager.class);
	339	Query query = queryManager.createQuery(xwqlstatement,Query.HQL);
	340	List<Object> results = query.execute();
	341	{{/code}}
	342
52.3	343	{{info}}
	344	A reference to a ComponentManager can be obtained through injection, as explained on the [[Component module extension page>>extensions:Extension.Component Module#HGettingaccesstotheComponentManager]].
	345	{{/info}}
51.1	346
27.1	347	== The XWiki context ==
1.1	348
26.1	349	Note that the XWiki context is deprecated. It was an older way of keeping track of the current request, which had to be passed around from method to method, looking like a [[ball and chain>>http://en.wikipedia.org/wiki/Ball_and_chain]] present everywhere in the code.
27.1	350
60.3	351	In the component world, the current request information is held in an {{scm project="xwiki-commons" path="xwiki-commons-core/xwiki-commons-context/src/main/java/org/xwiki/context/ExecutionContext.java"}}Execution Context{{/scm}}. This is actually more powerful than the old XWikiContext, as it is a generic execution context, hold in a ThreadLocal variable, and you can create one anytime you want and use it anyway you want. And you don't have to manually pass it around with all method calls, as execution contexts are managed by the {{scm project="xwiki-commons" path="xwiki-commons-core/xwiki-commons-context/src/main/java/org/xwiki/context/Execution.java"}}Execution{{/scm}} component, which you can use just like any other XWiki component.
27.1	352
48.1	353	In short, if you want to get access to the execution context (which holds context information inserted by the new components), you must declare an injection point on the ##Execution## component (located in the ##xwiki-commons-context## module), and then you can write:
1.1	354
63.1	355	{{code language="java"}}
26.1	356	/** Provides access to the request context. Injected by the Component Manager. */
60.2	357	@Inject
	358	private Execution execution;
	359	...
	360	private void workWithTheContext()
	361	{
	362	ExecutionContext context = execution.getContext();
	363	// Do something with the execution context
	364	}
26.1	365	{{/code}}
1.1	366
60.1	367	All that said, we're still in a transition phase and a lot of information is still available only through the old XWikiContext and has not yet been moved to the ExecutioncContext (the current user for example just to mention one). Thus you may still need to access the old XWiki Context. You can get a reference to it from the Execution Context. If you can you should try to not cast it to an ##XWikiContext##, which would pull the whole ##xwiki-platform-oldcore## as a dependency, but to a ##Map##. Doing it this way, you won't be able to access all the properties, like the current user name or the URL factory, but you can access anything placed in the internal map of the XWikiContext.
26.1	368
63.1	369	{{code language="java"}}
26.1	370	private void workWithTheContext()
60.1	371	{
	372	ExecutionContext context = execution.getContext();
	373	Map<Object, Object> xwikiContext = (Map<Object, Object>) context.getProperty("xwikicontext");
	374	// Do something with the XWiki context
	375	}
26.1	376	{{/code}}
1.1	377
62.1	378	If you need to access typed information then the easiest is to use a Provider the following way:
1.1	379
62.1	380	{{code language="java"}}
60.1	381	@Inject
62.1	382	private Provider<XWikiContext> xwikiContextProvider;
60.1	383	...
62.1	384	XWikiContext xcontext = this.xwikiContextProvider.get();
60.1	385	{{/code}}
	386
62.1	387	which will always provide a usuable XWikiContext (if there is none in the current ExecutionContext it will create one).
61.1	388
62.1	389	Since 7.2 if you just want to get one if there is one (i.e. you don't need to automatically create a new one) you can use the "readonly" XWikiContext Provider as in:
	390
61.1	391	{{code language="java"}}
	392	@Inject
62.1	393	@Named("readonly")
61.1	394	private Provider<XWikiContext> xwikiContextProvider;
	395	...
	396	XWikiContext xcontext = this.xwikiContextProvider.get();
62.1	397	if (xcontext != null) {
	398	...
	399	}
61.1	400	{{/code}}
	401
60.3	402	If you want not just to use the Execution Context, but to make something available in every execution context, you can create an implementation of the {{scm project="xwiki-commons" path="xwiki-commons-core/xwiki-commons-context/src/main/java/org/xwiki/context/ExecutionContextInitializer.java"}}ExecutionContextInitializer{{/scm}} component, and populate newly created execution contexts, just like with [[velocity contexts>>#HFromwikipages]].
60.1	403
27.1	404	== Code outside components ==
1.1	405
26.1	406	You can use external libraries as in any other maven module, just declare the right dependencies in your module's ##pom.xml##.
27.1	407
26.1	408	As a general rule, you should not work with any non-componentized XWiki code, as the way the old code was designed leads to an eventual dependency on the whole ##xwiki-core## module, which we are trying to avoid. If the component you are writing is needed by other modules (which is the case with most components, since a component which isn't providing any usable/used services is kind of useless), then this will likely lead to an eventual cyclic dependency, which will break the whole build.
27.1	409
26.1	410	If you need some functionality from the old core, consider rewriting that part as a new component first, and then use that new component from your code. You should ask first on the [[devs mailing list>>dev:Community.MailingLists]], so that we can design and implement it collaboratively.
27.1	411
1.1	412	If the effort needed for this is too large, you can try creating a bridge component, by writing just the interfaces in a new module, and make the classes from the core the default implementation of those interfaces. Then, since in the end the xwiki-core, the bridge component and your component will reside in the same classpath, plexus will take care of coupling the right classes. Be careful when writing such bridges, as they are short lived (since in the end all the old code will be replaced by proper components), and if the future real component will have a different interface, then you will have to rewrite your code to adapt to the new method names, or worse, the new component logic.
	413
35.1	414	= Deploying the Component =
1.1	415
64.1	416	Now that we have a functioning Component let's build it and deploy it to an XWiki instance. There are 2 ways.
46.1	417
64.1	418	== Manually ==
	419
32.1	420	* To build the component, issue ##mvn install##. This generates a JAR in the ##target## directory of your project.
	421	* To install it into a XWiki Enterprise instance, just copy that JAR file in ##XE_WAR_HOME/WEB-INF/lib## where ##XE_WAR_HOME## is where the XWiki Enterprise WAR is deployed.
	422
64.1	423	== Using the Extension Manager ==
	424
66.2	425	The advantage over the Manual way is that you don't need to regularly start/stop your XWiki instance and thus you don't incur the start wait times.
64.1	426
	427	* Have a running XWiki instance configured with a local Extension Repository pointing to your Maven local Repository. Edit ##xwiki.properties## and make sure you have the following set:(((
64.2	428	{{code language="none"}}
64.1	429	extension.repositories=local:maven:file://${sys:user.home}/.m2/repository
	430	extension.repositories=maven-xwiki:maven:http://nexus.xwiki.org/nexus/content/groups/public
	431	extension.repositories=extensions.xwiki.org:xwiki:http://extensions.xwiki.org/xwiki/rest/
64.2	432	{{/code}}
64.1	433	)))
	434	* Build your component and deploy it in your local Maven repository with ##mvn install##
	435	* Inside your running XWiki instance, go to the Extension Manager in the Admin UI (e.g. ##{{{http://localhost:8080/xwiki/bin/admin/XWiki/XWikiPreferences?editor=globaladmin&section=XWiki.AddExtensions}}}##) and click on Advanced Search and enter your extension's id and version and follow the instructions
	436
	437	{{warning}}
66.1	438	If you want to redeploy an extension and it's already installed with the same version, the Extension Manager won't let you do so. Thus you'll need to uninstall it first using the Extension Manager. You'll also need to remove metadata in memory using the [[Extension Tweak>>extensions:Extension.Extension Tweak]].
64.1	439	{{/warning}}
	440
32.1	441	Your component is now ready for service.
	442
	443	Enjoy!
50.1	444
51.1	445	= See also =
50.1	446
	447	* [[extensions:Extension.Component Module]]
56.2	448	* If you are experiencing problems trying to install the component using Maven, check the [[Building Guide>>dev:Community.Building]].

Wiki source code of Writing XWiki Components

Quick Links

Navigation

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected