Search: concept

Users only have to deal with Nested Pages, which is hiding the fact that Nested Pages are emulated using Nested Spaces. This is why the concept of Nested Spaces still exists. Migrating to Nested Pages If you're upgrading from a version of XWiki prior to the Nested Pages feature (i.e.

Users only have to deal with Nested Pages, which is hiding the fact that Nested Pages are emulated using Nested Spaces. This is why the concept of Nested Spaces still exists. = Migrating to Nested Pages = If you're upgrading from a version of XWiki prior to the Nested Pages feature (i.e.

{{image reference="syntaxConversionUnsupported.png"/}} {{id name="HWYSIWYGeditingmode"/}} = Setting the page parent = {{version since="7.2"}} The concept of setting the page parent has been deprecated in favor of the [[Nested Pages feature>>Documentation.UserGuide.Features.ContentOrganization.WebHome]].

Understanding resources and representations "An important concept in REST is the existence of resources (sources of specific information), each of which is referenced with a global identifier (e.g., an URI in HTTP).

/jobstatus/{jobId} Request parameters: Name Required Values Default Description Version request no true|false false Return also the job request 9.1RC1 progress no true|false true Return also the job progress 9.1RC1 log no true|false false Return also the job log 9.1RC1 log_fromLevel no error|warn|info|debug|trace Indicate the level from which to return logs 9.1RC1 HTTP Method: GET Media types: application/xml (JobStatus element) Description: status of a job Status codes: 200: If the request was successful. 404: If the job status has not been found /joblog/{jobId} Request parameters: Name Required Values Default Description Version level no error|warn|info|debug|trace Indicate the exact level for which to return logs 7.2M3 fromLevel no error|warn|info|debug|trace Indicate the level from which to return logs 7.2M3 HTTP Method: GET Media types: application/xml (JobLog element) Description: log of a job Status codes: 200: If the request was successful. 404: If the job status has not been found /jobs Request parameters: Name Required Values Default Description Version jobType yes The type of the job to pass to the Job Executor 9.1RC1 async no true|false true If false, return the response only when the job is done 9.1RC1 This API is designed to be a REST clone of the JobExecutor Java API (the only real difference right now being way to deal with asynchronous jobs) documented on http://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module#HUseanexistingjob so the concepts (job type, job request) are the same and the exact information to put in the job request depends on the job you want to run and are usually documented in the extension this job is coming from (extension module, refactoring, etc.).

= Understanding resources and representations = "An important concept in REST is the existence of resources (sources of specific information), each of which is referenced with a global identifier (e.g., an URI in HTTP).

(eg: ##refactoring/delete/11451##). === /jobstatus/{jobId} {{info}}Since 7.2M3{{/info}} === Request parameters: |=Name|=Required|=Values|=Default|=Description|=Version |##request##|no|##true~|false##|##false##|Return also the job request|9.1RC1 |##progress##|no|##true~|false##|##true##|Return also the job progress|9.1RC1 |##log##|no|##true~|false##|##false##|Return also the job log|9.1RC1 |##log_fromLevel##|no|##error~|warn~|info~|debug~|trace##| |Indicate the level from which to return logs|9.1RC1 * **HTTP Method:** GET ** **Media types:** *** application/xml (JobStatus element) ** **Description:** status of a job ** **Status codes:** *** 200: If the request was successful. *** 404: If the job status has not been found === /joblog/{jobId} {{info}}Since 7.2M3{{/info}} === Request parameters: |=Name|=Required|=Values|=Default|=Description|=Version |##level##|no|##error~|warn~|info~|debug~|trace##| |Indicate the exact level for which to return logs|7.2M3 |##fromLevel##|no|##error~|warn~|info~|debug~|trace##| |Indicate the level from which to return logs|7.2M3 * **HTTP Method:** GET ** **Media types:** *** application/xml (JobLog element) ** **Description:** log of a job ** **Status codes:** *** 200: If the request was successful. *** 404: If the job status has not been found === /jobs {{info}}Since 9.1RC1{{/info}} === Request parameters: |=Name|=Required|=Values|=Default|=Description|=Version |##jobType##|yes| | |The type of the job to pass to the Job Executor|9.1RC1 |##async##|no|##true~|false##|##true##|If false, return the response only when the job is done|9.1RC1 This API is designed to be a REST clone of the JobExecutor Java API (the only real difference right now being way to deal with asynchronous jobs) documented on http://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module#HUseanexistingjob so the concepts (job type, job request) are the same and the exact information to put in the job request depends on the job you want to run and are usually documented in the extension this job is coming from (extension module, refactoring, etc

XWiki Classes, Objects, and Properties If you are familiar with object oriented programming, you understand the concept of classes, properties, and objects. The presentation level data model that XWiki exposes is much the same.

= XWiki Classes, Objects, and Properties = If you are familiar with object oriented programming, you understand the concept of classes, properties, and objects. The presentation level data model that XWiki exposes is much the same

This version mainly introduces various ways of customizing users directory and profiles and it also bring all comments features to annotation (answer, threaded annotation, etc.) by merging the two concepts in one comment with optional precise location.

This version mainly introduces various ways of customizing users directory and profiles and it also bring all comments features to annotation (answer, threaded annotation, etc.) by merging the two concepts in one comment with optional precise location

It also introduces the concept of Reference for any entity of the model and the parser/serializer associated.

It also introduces the concept of Reference for any entity of the model and the parser/serializer associated.

It also introduces the concept of Reference for any entity of the model and the parser/serializer associated.

It also introduces the concept of Reference for any entity of the model and the parser/serializer associated.

Page Index Since we have introduced the concept of Nested Spaces we needed to replace the Space column in the LiveTable with a more generic solution.

{{image reference="breadcrumbsTreeNavigation.png"/}} == Page Index == Since we have introduced the concept of Nested Spaces we needed to replace the Space column in the LiveTable with a more generic solution.

This release candidate brings many Flamingo skin improvements to better present Nested Documents on top of the Nested Spaces concept. Similar improvements were made in applications like Solr Search, AWM, FAQ, Activity Stream and the Skin editor in order to be compatible with Nested Spaces.

This release candidate brings many Flamingo skin improvements to better present Nested Documents on top of the Nested Spaces concept. Similar improvements were made in applications like Solr Search, AWM, FAQ, Activity Stream and the Skin editor in order to be compatible with Nested Spaces.

In addition, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find particularly useful in creating XWiki applications.

If you previously chose to use a "Custom creation form" for creating new FAQ entries, follow these steps: Go to FAQ.WebHome Below the "Add a new question" header, enter a question (which will also be used as the document title) in the Document field Click Create this FAQ You can then enter your question in longer form using the Question field on the template, like this: Click Save & View and then you will see the newly created document, like this: Go back to the FAQ.WebHome page (you can use the breadcrumbs) to see the list of existing questions Conclusion This tutorial has taught you how to use the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced the authoring templates and page design sheets.

You can use these basic concepts to build custom applications at the document or presentation layer of XWiki without having to compile or deploy code.

In addition, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find particularly useful in creating XWiki applications.

If you previously chose to use a "Custom creation form" for creating new FAQ entries, follow these steps: * Go to ##FAQ.WebHome## * Below the "Add a new question" header, enter a question (which will also be used as the document title) in the //Document// field * Click //Create this FAQ// * You can then enter your question in longer form using the //Question// field on the template, like this:((( {{image reference="FAQSheetEdit.PNG"/}} ))) * Click //Save & View// and then you will see the newly created document, like this:((( {{image reference="FAQSheetView.PNG"/}} ))) * Go back to the ##FAQ.WebHome## page (you can use the breadcrumbs) to see the list of existing questions((( {{image reference="FAQsWithEntry.png"/}} ))) = Conclusion = This tutorial has taught you how to use the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced the authoring templates and page design sheets.

You can use these basic concepts to build custom applications at the document or presentation layer of XWiki without having to compile or deploy code.