Search: concept

. Example to illustrate formentioned concepts. Ex: Ajax request to add and init an object

comment : The combination of *actions* (like <tt>save</tt>) and *request parameters* (like <tt>xredirect</tt>) obviously is a very powerful means to work with XWiki documents. Is there any documentation on that? Where do these concepts belong to in the first place, Struts, XWiki, Velocity or another technology?

", or "1" {table} 1.1 Sample use cases TBD. Example to illustrate formentioned concepts. Ex: Ajax

content : With the release of [[9.5.1>>Download.DownloadVersion||queryString="projectVersion=9.5.1"]] we have dropped the XWiki Enterprise distribution and instead we exposed the [[Flavor mechanism>>xwiki:Documentation.UserGuide.Features.Applications||queryString="#HFlavors"]]. For those unfamiliar with the concept, a "flavor" is a collection

of installed applications to the "Flavors" concept. In XWiki, a flavor is simply a bundle of extensions

this new concept. For more informations, do not hesitate to check out [[Caty's blog post>>Blog.XWiki

resources and representations "An important concept in REST is the existence of resources (sources

://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module#HUseanexistingjob so the concepts (job type, job request

and representations = "An important concept in REST is the existence of resources (sources of specific information

/xwiki/bin/view/Extension/Job+Module#HUseanexistingjob so the concepts (job type, job request

="HWYSIWYGeditingmode"/}} = Setting the page parent = {{version since="7.2"}} The concept of setting the page parent

using Annotations as explained above. == Namespaces == Component API comes with "namespace" concept

== The XWiki project is older that this component concept and sometimes you can find yourself in code

reading ~-~- what a concept (I'm impatient sometimes). Tom