this information). I'm sure that your class concept is really easy to use and useful to do this in an online

for using this class concept but I just see the results. The way of realisation (the codes and steps behind

in using your concept are: How do I assign a document type (class) to a web so that every new document

profile : * Java proficiency * Familiar with unit testing concepts and best practices * Familiar with functional testing concepts and best practices ** Experience with Selenium and the [[Page Objects>>url:https://code.google.com/p/selenium/wiki/PageObjects]] pattern is preferred * Familiar with web technologies: HTML/CSS

="ctag:label" content="$detail.getLabel()"><a class="tag-concept-link" href='$detail.getUri()'>$detail.getLabel

.tag-delete').each(this.ajaxTagDelete); // [semtag] concept list for each tag $$('.doc-tags .tag-list-activator').each(this.ajaxTagConcepts); // [semtag] end concept list for each tag

. 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

volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english

translation application. The concept seems to work by application version. We need to verity

concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation

on launchpad.net there is a quite extensively developed translation application. The concept seems to work

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

rather than the domain concepts users have in mind. We are using wikis as a platform for empowering end

that consists mostly of tables and numbers rather than the domain concepts users have in mind. We are using

adopted the "nested pages" paradigm. It means that you will no longer find the "space" concept in the UI

summary : Proof of concept for XML based api

good proof of concept. If anyone is up to writing a cleaner, more efficient version - please do, and