field to applications descriptors. * XAWM-23: Separate wiki and wiki alias concepts. * XAWM-26

translations are using the same concepts as the XWiki Java Properties except that the translations

Properties translations are using the same concepts as the [[XWiki Java Properties>>||anchor

Continue SOLR implementation EM upgrade of subwikis in farm mode + flavor concept (add Flavor type in EM

in farm mode + flavor concept (add Flavor type in EM/Repository) + leftover from 4.x for EM/DW:((( {{jira

as a dependency. {{/info}} = Concepts = Similar to the [[authorization API>>Extension.Security Module

of the existing XWiki concepts, there is no new implementation of the rights or of their storage. It is fully

), the access rights do endup stored as XWikiRights or XWikiGlobalRights objects, but those concepts

a proof of concept they can take to sign off -simple things like the sections option in confluence is very

would have more people complete a proof of concept they can take to sign off -simple things like

description : {{warning}}This is currently a proof of concept and not yet ready for production.{{/warning}} Inspiration: https://github.com/phillip-kruger/graphql-example It follows the [[Eclipse MicroProfile GraphQL API Specifications>>https://github.com/eclipse/microprofile-graphql/]] using the

. 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>>platform:Features.Applications||queryString="#HFlavors"]]. For those unfamiliar with the concept, a "flavor" is a collection

, etc.) by merging the two concepts in one comment with optional precise location. See [[the full

the concept of Reference for any entity of the model and the parser/serializer associated. For now Wiki, Space

manipulations around documents and attachment names. It also introduces the concept of Reference for any entity