Search: concept

For now I think I'm going to kick back and do some reading ~-~- what a concept (I'm impatient sometimes). Tom

Last but not least this release contains a first implementation of the "Supported By" extension concept for administrators. The release also includes lots of bug fixes and security fixes, with the highest severity being 9.1/10.

Last but not least this release contains a first implementation of the "Supported By" extension concept for administrators. The release also includes lots of bug fixes and security fixes, with the highest severity being 9.1/10.

Last but not least this release contains a first implementation of the "Supported By" extension concept for administrators. The release also includes lots of bug fixes and security fixes, with the highest severity being 9.1/10.

Last but not least this release contains a first implementation of the "Supported By" extension concept for administrators. The release also includes lots of bug fixes and security fixes, with the highest severity being 9.1/10.

summary : Extensions now have the concept of supporters and support plans. The goal is to replace the very vague concept of //Recommended// we currently have for a very explicit pledge of organizations and individuals (**Supporters**) to support an extension, and to which extent (**Support Plans**).

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

However, spreadsheets enforce a view of the world that consists mostly of tables and numbers rather than the domain concepts users have in mind. We are using wikis as a platform for empowering end-users to perform computational tasks of their choice.

However, spreadsheets enforce a view of the world that consists mostly of tables and numbers rather than the domain concepts users have in mind. We are using wikis as a platform for empowering end-users to perform computational tasks of their choice.

Job Logs XWiki has the concept of jobs (e.g. when you install or upgrade an Extension or when you delete pages, they all execute in a job).

. == Job Logs == XWiki has the concept of [[jobs>>extensions:Extension.Job Module.WebHome]] (e.g. when you install or upgrade an Extension or when you delete pages, they all execute in a job).

XWiki 7.2 has introduced the concept of Nested Spaces. With this new concept it's legitimate to ask oneself what are the differences between using a (sub)wiki or using Nested Pages.

XWiki 7.2 has introduced the concept of Nested Spaces. With this new concept it's legitimate to ask oneself what are the differences between using a (sub)wiki or using Nested Pages

Starting with this version we introduce the concept of "request effective author". By default, the currently authenticated user is the request effective author, but XWiki extensions can overwrite this based on the request data and their own logic by setting a ##UserReference## as the value of a request attribute named ##com.xpn.xwiki.web.XWikiRequest#effectiveAuthor##.

It is a great pleasure for me keeping my knowledge in my all-available, all-accessible xwiki and every release is like birthday. 23 February 2012, from Yannick Loth: #XWiki is a great tool once you understand its concepts and how it works! You may be proud, XWiki team!

/yannickloth/status/172641714576687104]]:((( > #XWiki is a great tool once you understand its concepts and how it works! You may be proud, XWiki team!