Last modified by Thomas Mortagne on 2017/03/24

From version 5.1
edited by Artem Melentyev
on 2008/09/11
Change comment: update QueryManager section
To version 7.1
edited by Vincent Massol
on 2008/09/12
Change comment: Improved (less technical - they need to be user-oriented) explanations for Query Manager changes

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.amelentev
1 +XWiki.VincentMassol
Content
... ... @@ -13,13 +13,10 @@
13 13  
14 14  * New experimental support for other syntaxes (Confluence, JSPWiki, Creole, MediaWiki, TWiki and XHTML), including a new XWiki Syntax v2.0 (work in progress, see [XWiki Syntax 2.0 Draft>dev:Drafts.XWikiSyntax20]).#info("To start entering page content using the new syntaxes, you must be logged with admin rights, go to the page you wish to edit and change the Syntax for the page to the one you wish to use. Note that all syntaxes except the XWiki 1.0 and XWiki 2.0 ones have important limitations (like links not working).")
15 15  * New experimental WYSIWYG editor (Work In Progress)#info("The look & feel is not the final one. Please look at the [new WYSIWYG Design page>dev:Design.NewWysiwygEditorInterface] to see what it'll look like (except for the colors which will be different). To activate the new editor you must be logged with admin rights, go to the page you wish to edit, change the Syntax of the page to <tt>XWiki 2.0</tt> (right panel in edit mode), save. From then on when you edit with the WYSIWYG editor you'll be using the new editor. For some details about the new syntax please see the [XWiki Syntax 2.0 Draft>dev:Drafts.XWikiSyntax20]. Again this is work in progress but we'd like *as much feedback as possible*. Known issues with the editor:\\- Heading doesn't work in IE6/7.\\- Nested lists does not work.\\- Switching from any heading level to normal leaves the id that was previously associated with that heading.\\- Editing in wiki mode and then switching to wysiwyg may determine an unexpected behavior from the wysiwyg (like being unable to un-bold the text).")
16 -* New experimental XWiki Query Language. #info("More about the language in [XWQL design page>dev:Design.XWikiQueryLanguage]. Main syntax and translator to hql are implemented. It requre programming rights to use in scripts now. The current xwql syntax is not the final one. We'd like some feedback to improve it. The language will fully replace current $xwiki.search methods in XE 1.7.")
17 -* Various changes in Query Manager.
18 -** Query Manager was added since 1.6M1. The purpose of Query Manager is easy to use multiple languages and manage them.
19 -** Changes:
20 -*** Added ability to use positional parameters in Query (only named parameters supported earlier)
21 -*** Moved to separate maven module (core/xwiki-query/manager/)
22 -*** New language is now added via introducing its QueryExecutor component instead of hardcoded in QueryManager. This allows to add a new language just by adding jar with configured QueryExecutor component implementation. (XWIKI-2643)
16 +* New experimental XWiki Query Language. #info("More about the language in [XWQL design page>dev:Design.XWikiQueryLanguage]. Main syntax and translator to hql are implemented. It requre programming rights to use in scripts now. The current xwql syntax is not the final one. We'd like some feedback to improve it. The language will fully replace current $xwiki.search methods in XE 1.7. Language is accessible via QueryManager. Example: $xwiki.xWiki.store.queryManager.createQuery('from doc.object(XWiki.XWikiUsers) as user', 'xwql').execute()")
17 +* Improvement of Query Manager which was introduced in 1.6M1. The purpose of the Query Manager is to allow using multiple Query Languages and manage them (HQL is one such language). The changes are:
18 +** Ability to use positional parameters in Query (only named parameters supported earlier).
19 +** Ability to add a new Query Language easily simply by adding a JAR to the Classpath.
23 23  
24 24  Other changes:
25 25  

Get Connected