Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -16,7 +16,7 @@
16	16
17	17	{{image reference="solrSearchFilters.png"/}}
18	18
19		-The new engine has it's own index, separate from the Lucene one, which is stored by default in the ##<permanent directory>/solr## folder. In the same folder you can also access Solr's configuration files together with the index's schema.xml which you can tweak to achieve better results. To change this folder's location, you can either pass the ##-Dsolr.solr.home## system property when you start the application container (tomcat/jetty/etc.) or you can set the ##search.solr.home## property in ##WEB-INF/xwiki.preferences##.
	19	+The new engine has it's own index, separate from the Lucene one, which is stored by default in the ##<permanent directory>/solr## folder. In the same folder you can also access Solr's configuration files together with the index's schema.xml which you can tweak to achieve better results. To change this folder's location, you can either pass the ##-Dsolr.solr.home## system property when you start the application container (tomcat/jetty/etc.) or you can set the ##search.solr.home## property in ##WEB-INF/xwiki.properties##.
20	20
21	21	For now, indexing is done only __manually__ by using the Search Administration UI. Because of this, in order to get any search results, you have to go to ##Administration > Applications > Search## and index/reindex the wiki. Any changes in the content of the wiki will not be searchable until you manually reindex. This limitation will be removed in future versions, once the feature matures.
22	22
...	...	@@ -94,7 +94,7 @@
94	94
95	95	== Easy creation of new XClass property types ==
96	96
97		-It's now possible to create your own [[XClass property types>>platform:DevGuide.DataModel||anchor="HXWikiClasses2CObjects2CandProperties"]] without having to patch XWiki's old core. [[Adding a new property type>>platform:DevGuide.CreatingNewXClassPropertyTypes]] is as easy as implementing a component. This means you can extend the [[class editor>>platform:Features.PageEditing||anchor="HClasseseditingmode"]] and even the [[App Within Minutes>>extensions:Extension.App Within Minutes Application||anchor="HFieldTypes"]].
	97	+It's now possible to create your own [[XClass property types>>platform:DevGuide.DataModel||anchor="HXWikiClasses2CObjects2CandProperties"]] without having to patch XWiki's old core. [[Adding a new property type>>platform:DevGuide.CreatingNewXClassPropertyTypes]] is as easy as implementing a component. This means you can extend the [[class editor>>platform:Features.PageEditing||anchor="HClasseseditingmode"]] and even the [[App Within Minutes>>extensions:Extension.App Within Minutes Application||anchor="HFieldPalette-1"]].
98	98
99	99	== Execution context property declarations ==
100	100
...	...	@@ -156,7 +156,29 @@
156	156
157	157	* The methods setUrlPatternMatcher and getUrlPatternMatcher have been removed from the core class com.xpn.xwiki.XWiki. The underlying URLPatternMatcher could not really be used as a singleton instance and was causing irregular failures in the basic authentication method. Thus these methods cannot be meaningfully relied upon and have therefore been removed.
158	158	* When setting the value using setValue (or setList) on a list field in an XWiki object, the list will now be copied. To be able to update the list, you must call getValue (or getList) and update the returned list. This is due to {{jira style="enum" url="http://jira.xwiki.org"}}XWIKI-8398{{/jira}}.
	159	+* The behaviour of ##com.xpn.xwiki.api.PropertyClass#getClassType()## (public API) and ##com.xpn.xwiki.objects.classes.PropertyClass#getClassType()## (protected API) has changed. They don't return the canonical Java class name of the property implementation anymore but an implementation hint. Here's the code:(((
	160	+{{code language="java"}}
	161	+/**
	162	+ * Each type of XClass property is identified by a string that specifies the data type of the property value (e.g.
	163	+ * 'String', 'Number', 'Date') without disclosing implementation details. The internal implementation of an XClass
	164	+ * property type can change over time but its {@code classType} should not.
	165	+ * <p>
	166	+ * The {@code classType} can be used as a hint to lookup various components related to this specific XClass property
	167	+ * type. See {@link com.xpn.xwiki.internal.objects.classes.PropertyClassProvider} for instance.
	168	+ *
	169	+ * @return an identifier for the data type of the property value (e.g. 'String', 'Number', 'Date')
	170	+ */
	171	+public String getClassType()
	172	+{
	173	+ // By default the hint is computed by removing the Class suffix, if present, from the Java simple class name
	174	+ // (without the package). Subclasses can overwrite this method to use a different hint format.
	175	+ return StringUtils.removeEnd(getClass().getSimpleName(), "Class");
	176	+}
	177	+{{/code}}
159	159
	179	+This means that instead of returning ##com.xpn.xwiki.objects.classes.DBListClass## these methods now return ##DBList##. This is due to {{jira style="enum" url="http://jira.xwiki.org"}}XWIKI-8355{{/jira}}.
	180	+)))
	181	+
160	160	== API Breakages ==
161	161
162	162	The following APIs were modified since 4.2: