The XWiki development team is proud to announce the availability of XWiki
Enterprise 4.1.4.
This is probably the last bugfix release for the 4.1 series. It provides 30
bug fixes, mainly in the Extension Manager, including important fixes for
extensions that provide components or script services (see XCOMMONS-231
andXCOMMONS-232). It also improves the large data migration introduced in
4.0, in particular to support MS-SQL, and fixes an important issue that
cause the migration of annotations to be unintentionally skipped.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris…
Thanks
-The XWiki dev team
Hi devs,
I'm going to be the RM for 4.1.4 and I'd like to release it ASAP starting
right now.
If you are working on something that needs to be included in 4.1.4 please
reply to this mail immediately. There is currently only one minor bug that
I will postpone to 4.2.
XWIKI-8057: IllegalArgumentException on annotation creation and deletion
when content is using a verbatim block
Any else ?
Please vote quickly, thanks.
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
Hi Alexandru Loredan,
Since the build is failing (don't know why, problem with attached emulator?
) , I want to notify you that the module
<module>xwiki-android-test-fixture-setup</module> starts a local xwiki
server instance and it won't be shut down unless you run
<module>xwiki-android-test-fixture-teardown</module> or manually shut it
down.
Regards.
Sasinda.
Hi all, I'm test driving this sweet new Solr integration with xwiki, and I am sure I've done something wrong... Am I supposed to remove the LucenePlugin?
The LucenePlugin in the xwiki.cfg has to be commented out for me or else all pages end up with a 500 error, and a ClassNotFound for org.apache.lucene.queryParser.QueryParser.
(import org.apache.lucene.queryParser.QueryParser;)
I have moved out some jars, and put in some new ones, and somewhere along the way I removed it.
I'm running the 4.2-milestone-2 version of xwiki, mostly. I also have the BETA solr & lucene jars. The lib looks like this (extra removed)
Solr:
08/06/2012 07:50 PM 16,670 apache-solr-analysis-extras-4.0.0-BETA.jar
08/06/2012 07:50 PM 29,834 apache-solr-cell-4.0.0-BETA.jar
08/06/2012 07:50 PM 50,461 apache-solr-clustering-4.0.0-BETA.jar
08/06/2012 07:50 PM 1,853,274 apache-solr-core-4.0.0-BETA.jar
08/06/2012 07:50 PM 214,355 apache-solr-dataimporthandler-4.0.0-BETA.jar
08/06/2012 07:50 PM 31,084 apache-solr-dataimporthandler-extras-4.0.0-BETA.jar
08/06/2012 07:50 PM 766,460 apache-solr-langid-4.0.0-BETA.jar
08/06/2012 07:50 PM 362,101 apache-solr-solrj-4.0.0-BETA.jar
08/06/2012 07:50 PM 86,185 apache-solr-test-framework-4.0.0-BETA.jar
08/06/2012 07:50 PM 38,879 apache-solr-uima-4.0.0-BETA.jar
08/06/2012 07:50 PM 22,281 apache-solr-velocity-4.0.0-BETA.jar
Lucene (tried with and without the 3.4 jars):
08/06/2012 10:42 PM 1,525,477 lucene-analyzers-common-4.0.0-BETA.jar
08/06/2012 10:42 PM 84,283 lucene-analyzers-icu-4.0.0-BETA.jar
08/06/2012 10:42 PM 4,553,550 lucene-analyzers-kuromoji-4.0.0-BETA.jar
08/06/2012 10:42 PM 19,976 lucene-analyzers-morfologik-4.0.0-BETA.jar
08/06/2012 10:42 PM 22,853 lucene-analyzers-phonetic-4.0.0-BETA.jar
08/06/2012 10:42 PM 3,598,820 lucene-analyzers-smartcn-4.0.0-BETA.jar
08/06/2012 10:42 PM 516,896 lucene-analyzers-stempel-4.0.0-BETA.jar
08/06/2012 10:42 PM 26,933 lucene-analyzers-uima-4.0.0-BETA.jar
08/06/2012 10:42 PM 253,578 lucene-benchmark-4.0.0-BETA.jar
08/06/2012 10:42 PM 2,410,540 lucene-core-4.0.0-BETA.jar
08/06/2012 10:42 PM 28,235 lucene-demo-4.0.0-BETA.jar
08/06/2012 10:42 PM 61,327 lucene-facet-4.0.0-BETA-examples.jar
08/06/2012 10:42 PM 307,800 lucene-facet-4.0.0-BETA.jar
08/06/2012 10:42 PM 164,624 lucene-grouping-4.0.0-BETA.jar
08/06/2012 10:42 PM 99,764 lucene-highlighter-4.0.0-BETA.jar
08/06/2012 10:42 PM 53,820 lucene-join-4.0.0-BETA.jar
08/06/2012 10:42 PM 36,801 lucene-memory-4.0.0-BETA.jar
08/06/2012 10:42 PM 50,939 lucene-misc-4.0.0-BETA.jar
08/06/2012 10:42 PM 194,333 lucene-queries-4.0.0-BETA.jar
01/03/2012 05:14 PM 309,353 lucene-queryparser-3.4.0.jar
08/06/2012 10:42 PM 384,388 lucene-queryparser-4.0.0-BETA.jar
08/06/2012 10:42 PM 45,389 lucene-sandbox-4.0.0-BETA.jar
08/25/2012 11:05 AM 67,616 lucene-spatial-4.0-SNAPSHOT.jar
08/06/2012 10:42 PM 67,481 lucene-spatial-4.0.0-BETA.jar
08/06/2012 10:42 PM 120,106 lucene-suggest-4.0.0-BETA.jar
08/06/2012 10:42 PM 6,133,261 lucene-test-framework-4.0.0-BETA.jar
Xwiki:
08/07/2012 08:55 AM 41,472 xwiki-commons-classloader-api-4.2-milestone-2.jar
08/07/2012 08:55 AM 24,961 xwiki-commons-classloader-protocol-jar-4.2-milestone-2.jar
08/07/2012 08:56 AM 16,349 xwiki-commons-component-observation-4.2-milestone-2.jar
08/07/2012 08:56 AM 20,027 xwiki-commons-configuration-api-4.2-milestone-2.jar
08/07/2012 08:56 AM 18,826 xwiki-commons-context-4.2-milestone-2.jar
08/07/2012 09:01 AM 36,575 xwiki-commons-diff-api-4.2-milestone-2.jar
08/07/2012 09:01 AM 30,658 xwiki-commons-diff-display-4.2-milestone-2.jar
08/07/2012 09:01 AM 17,210 xwiki-commons-diff-script-4.2-milestone-2.jar
08/07/2012 08:57 AM 13,549 xwiki-commons-environment-api-4.2-milestone-2.jar
08/07/2012 08:58 AM 17,469 xwiki-commons-environment-common-4.2-milestone-2.jar
08/07/2012 08:58 AM 15,256 xwiki-commons-environment-servlet-4.2-milestone-2.jar
08/07/2012 08:59 AM 318,005 xwiki-commons-extension-api-4.2-milestone-2.jar
08/07/2012 08:59 AM 22,033 xwiki-commons-extension-handler-jar-4.2-milestone-2.jar
08/07/2012 08:59 AM 37,274 xwiki-commons-extension-repository-maven-4.2-milestone-2.jar
08/07/2012 09:00 AM 25,967 xwiki-commons-extension-repository-xwiki-4.2-milestone-2.jar
08/07/2012 09:00 AM 19,499 xwiki-commons-groovy-4.2-milestone-2.jar
08/07/2012 08:58 AM 43,356 xwiki-commons-job-4.2-milestone-2.jar
08/07/2012 09:01 AM 55,008 xwiki-commons-legacy-component-api-4.2-milestone-2.jar
08/07/2012 09:02 AM 56,371 xwiki-commons-legacy-component-default-4.2-milestone-2.jar
08/07/2012 09:02 AM 14,277 xwiki-commons-legacy-configuration-4.2-milestone-2.jar
08/07/2012 08:58 AM 21,812 xwiki-commons-logging-api-4.2-milestone-2.jar
08/07/2012 08:58 AM 19,927 xwiki-commons-logging-logback-4.2-milestone-2.jar
08/07/2012 09:00 AM 14,978 xwiki-commons-management-4.2-milestone-2.jar
08/07/2012 08:56 AM 25,020 xwiki-commons-observation-api-4.2-milestone-2.jar
08/07/2012 08:58 AM 21,259 xwiki-commons-observation-local-4.2-milestone-2.jar
08/07/2012 08:58 AM 40,449 xwiki-commons-properties-4.2-milestone-2.jar
08/07/2012 09:00 AM 18,673 xwiki-commons-repository-api-4.2-milestone-2.jar
08/07/2012 09:00 AM 37,281 xwiki-commons-repository-model-4.2-milestone-2.jar
08/07/2012 08:56 AM 20,553 xwiki-commons-script-4.2-milestone-2.jar
08/07/2012 08:55 AM 14,708 xwiki-commons-text-4.2-milestone-2.jar
08/07/2012 09:01 AM 56,597 xwiki-commons-velocity-4.2-milestone-2.jar
08/07/2012 09:01 AM 74,884 xwiki-commons-xml-4.2-milestone-2.jar
08/07/2012 09:36 AM 56,309 xwiki-platform-activitystream-4.2-milestone-2.jar
08/07/2012 09:35 AM 62,000 xwiki-platform-annotation-core-4.2-milestone-2.jar
08/07/2012 09:37 AM 44,751 xwiki-platform-annotation-io-4.2-milestone-2.jar
08/07/2012 09:37 AM 27,470 xwiki-platform-annotation-maintainer-4.2-milestone-2.jar
08/07/2012 09:37 AM 21,042 xwiki-platform-annotation-reference-4.2-milestone-2.jar
08/07/2012 09:37 AM 53,944 xwiki-platform-annotation-rest-4.2-milestone-2.jar
08/07/2012 09:37 AM 20,152 xwiki-platform-annotation-scripting-4.2-milestone-2.jar
08/07/2012 09:38 AM 63,731 xwiki-platform-application-manager-api-4.2-milestone-2.jar
08/07/2012 09:20 AM 27,409 xwiki-platform-bridge-4.2-milestone-2.jar
08/07/2012 09:22 AM 27,645 xwiki-platform-cache-api-4.2-milestone-2.jar
08/07/2012 09:23 AM 26,579 xwiki-platform-cache-infinispan-4.2-milestone-2.jar
08/07/2012 09:22 AM 23,647 xwiki-platform-captcha-4.2-milestone-2.jar
08/07/2012 09:39 AM 51,062 xwiki-platform-chart-macro-4.2-milestone-2.jar
08/07/2012 09:39 AM 128,851 xwiki-platform-chart-plugin-4.2-milestone-2.jar
08/07/2012 09:21 AM 31,890 xwiki-platform-chart-renderer-4.2-milestone-2.jar
08/07/2012 09:22 AM 17,262 xwiki-platform-classloader-protocol-attachmentjar-4.2-milestone-2.jar
08/07/2012 09:40 AM 15,015 xwiki-platform-classloader-xwiki-4.2-milestone-2.jar
08/07/2012 09:24 AM 17,675 xwiki-platform-component-multi-4.2-milestone-2.jar
08/07/2012 09:40 AM 15,138 xwiki-platform-component-script-4.2-milestone-2.jar
08/07/2012 09:20 AM 25,955 xwiki-platform-configuration-default-4.2-milestone-2.jar
08/07/2012 09:20 AM 23,481 xwiki-platform-container-api-4.2-milestone-2.jar
08/07/2012 09:20 AM 20,192 xwiki-platform-container-portlet-4.2-milestone-2.jar
08/07/2012 09:25 AM 33,024 xwiki-platform-container-servlet-4.2-milestone-2.jar
08/07/2012 09:40 AM 62,663 xwiki-platform-crypto-4.2-milestone-2.jar
08/07/2012 09:25 AM 20,677 xwiki-platform-csrf-4.2-milestone-2.jar
08/07/2012 09:41 AM 38,540 xwiki-platform-dashboard-macro-4.2-milestone-2.jar
08/07/2012 09:21 AM 31,287 xwiki-platform-display-api-4.2-milestone-2.jar
08/07/2012 09:41 AM 19,286 xwiki-platform-display-macro-4.2-milestone-2.jar
08/07/2012 09:36 AM 22,063 xwiki-platform-eventstream-4.2-milestone-2.jar
08/07/2012 09:41 AM 18,840 xwiki-platform-extension-cluster-4.2-milestone-2.jar
08/07/2012 09:41 AM 64,692 xwiki-platform-extension-handler-xar-4.2-milestone-2.jar
08/07/2012 09:41 AM 56,733 xwiki-platform-extension-script-4.2-milestone-2.jar
08/07/2012 09:42 AM 20,336 xwiki-platform-formula-macro-4.2-milestone-2.jar
08/07/2012 09:23 AM 30,682 xwiki-platform-formula-renderer-4.2-milestone-2.jar
08/07/2012 09:25 AM 15,179 xwiki-platform-groovy-4.2-milestone-2.jar
08/07/2012 09:33 AM 87,639 xwiki-platform-gwt-api-4.2-milestone-2.jar
08/07/2012 09:49 AM 20,108 xwiki-platform-jodatime-4.2-milestone-2.jar
08/07/2012 10:11 AM 15,049 xwiki-platform-legacy-annotation-4.2-milestone-2.jar
08/07/2012 10:11 AM 31,820 xwiki-platform-legacy-model-4.2-milestone-2.jar
08/07/2012 10:11 AM 19,997 xwiki-platform-legacy-observation-4.2-milestone-2.jar
08/07/2012 10:12 AM 90,793 xwiki-platform-legacy-office-importer-4.2-milestone-2.jar
08/07/2012 10:11 AM 2,750,601 xwiki-platform-legacy-oldcore-4.2-milestone-2.jar
08/07/2012 09:46 AM 20,251 xwiki-platform-linkchecker-api-4.2-milestone-2.jar
08/07/2012 09:50 AM 39,589 xwiki-platform-mailsender-4.2-milestone-2.jar
08/07/2012 09:50 AM 19,620 xwiki-platform-messagestream-4.2-milestone-2.jar
08/07/2012 09:20 AM 70,038 xwiki-platform-model-4.2-milestone-2.jar
08/07/2012 09:19 AM 36,346 xwiki-platform-observation-remote-4.2-milestone-2.jar
08/07/2012 09:51 AM 18,595 xwiki-platform-office-macro-4.2-milestone-2.jar
08/07/2012 09:51 AM 26,673 xwiki-platform-office-viewer-4.2-milestone-2.jar
08/07/2012 09:24 AM 370,794 xwiki-platform-query-jpql-parser-4.2-milestone-2.jar
08/07/2012 09:23 AM 33,694 xwiki-platform-query-manager-4.2-milestone-2.jar
08/07/2012 09:25 AM 33,449 xwiki-platform-query-xwql-4.2-milestone-2.jar
08/07/2012 09:23 AM 24,822 xwiki-platform-refactoring-4.2-milestone-2.jar
08/07/2012 09:52 AM 18,823 xwiki-platform-rendering-macro-cache-4.2-milestone-2.jar
08/07/2012 09:45 AM 28,090 xwiki-platform-rendering-macro-code-4.2-milestone-2.jar
08/07/2012 09:40 AM 21,410 xwiki-platform-rendering-macro-container-4.2-milestone-2.jar
08/07/2012 09:22 AM 17,590 xwiki-platform-rendering-macro-context-4.2-milestone-2.jar
08/07/2012 09:24 AM 17,396 xwiki-platform-rendering-macro-gallery-4.2-milestone-2.jar
08/07/2012 09:25 AM 16,624 xwiki-platform-rendering-macro-groovy-4.2-milestone-2.jar
08/07/2012 09:42 AM 20,713 xwiki-platform-rendering-macro-include-4.2-milestone-2.jar
08/07/2012 09:52 AM 15,256 xwiki-platform-rendering-macro-python-4.2-milestone-2.jar
08/07/2012 09:51 AM 22,142 xwiki-platform-rendering-macro-rss-4.2-milestone-2.jar
08/07/2012 09:22 AM 38,122 xwiki-platform-rendering-macro-script-4.2-milestone-2.jar
08/07/2012 09:51 AM 18,113 xwiki-platform-rendering-macro-useravatar-4.2-milestone-2.jar
08/07/2012 09:25 AM 26,498 xwiki-platform-rendering-macro-velocity-4.2-milestone-2.jar
08/07/2012 09:42 AM 38,315 xwiki-platform-rendering-wikimacro-api-4.2-milestone-2.jar
08/07/2012 09:43 AM 35,001 xwiki-platform-rendering-wikimacro-store-4.2-milestone-2.jar
08/07/2012 09:21 AM 28,066 xwiki-platform-rendering-xwiki-4.2-milestone-2.jar
08/07/2012 09:32 AM 63,918 xwiki-platform-rest-model-4.2-milestone-2.jar
08/07/2012 09:33 AM 178,239 xwiki-platform-rest-server-4.2-milestone-2.jar
08/07/2012 09:35 AM 39,959 xwiki-platform-scheduler-api-4.2-milestone-2.jar
09/03/2012 02:39 PM 42,661 xwiki-platform-search-api-1.0-SNAPSHOT.jar
08/26/2012 04:29 PM 45,742 xwiki-platform-search-lucene-4.0.0.jar
08/07/2012 09:46 AM 62,331 xwiki-platform-search-lucene-4.2-milestone-2.jartamarut
09/03/2012 02:39 PM 53,639 xwiki-platform-search-solrj-1.0-SNAPSHOT.jar
08/07/2012 09:39 AM 85,974 xwiki-platform-security-api-4.2-milestone-2.jar
08/07/2012 09:53 AM 41,169 xwiki-platform-security-bridge-4.2-milestone-2.jar
08/07/2012 09:21 AM 22,235 xwiki-platform-sheet-api-4.2-milestone-2.jar
08/07/2012 09:23 AM 13,549 xwiki-platform-skin-api-4.2-milestone-2.jar
08/07/2012 09:27 AM 67,671 xwiki-platform-skin-skinx-4.2-milestone-2.jar
08/07/2012 09:19 AM 13,591 xwiki-platform-store-api-4.2-milestone-2.jar
08/07/2012 09:54 AM 17,076 xwiki-platform-store-filesystem-4.2-milestone-2.jar
08/07/2012 09:54 AM 74,988 xwiki-platform-store-filesystem-attachments-4.2-milestone-2.jar
08/07/2012 09:53 AM 19,863 xwiki-platform-store-locks-4.2-milestone-2.jar
08/07/2012 09:54 AM 20,605 xwiki-platform-store-serialization-4.2-milestone-2.jar
08/07/2012 09:53 AM 24,828 xwiki-platform-store-transaction-4.2-milestone-2.jar
08/07/2012 09:54 AM 26,218 xwiki-platform-tag-api-4.2-milestone-2.jar
08/07/2012 09:20 AM 18,079 xwiki-platform-url-api-4.2-milestone-2.jar
08/07/2012 09:21 AM 14,488 xwiki-platform-url-container-4.2-milestone-2.jar
08/07/2012 09:21 AM 26,470 xwiki-platform-url-default-4.2-milestone-2.jar
08/07/2012 09:19 AM 14,778 xwiki-platform-velocity-webapp-4.2-milestone-2.jar
08/07/2012 09:55 AM 59,952 xwiki-platform-watchlist-api-4.2-milestone-2.jar
08/07/2012 09:32 AM 80,783 xwiki-platform-webdav-server-4.2-milestone-2.jar
08/07/2012 09:56 AM 64,381 xwiki-platform-wiki-manager-api-4.2-milestone-2.jar
08/07/2012 09:56 AM 26,337 xwiki-platform-workspace-api-4.2-milestone-2.jar
08/07/2012 09:31 AM 516,948 xwiki-platform-wysiwyg-client-4.2-milestone-2-shared.jar
08/07/2012 09:32 AM 67,222 xwiki-platform-wysiwyg-server-4.2-milestone-2.jar
08/07/2012 10:10 AM 15,593 xwiki-platform-xml-script-4.2-milestone-2.jar
08/07/2012 09:20 AM 23,672 xwiki-platform-xmlrpc-model-4.2-milestone-2.jar
08/07/2012 10:10 AM 22,964 xwiki-platform-zipexplorer-4.2-milestone-2.jar
08/07/2012 09:13 AM 235,566 xwiki-rendering-legacy-api-4.2-milestone-2.jar
08/07/2012 09:10 AM 19,267 xwiki-rendering-macro-box-4.2-milestone-2.jar
08/07/2012 09:10 AM 15,067 xwiki-rendering-macro-comment-4.2-milestone-2.jar
08/07/2012 09:10 AM 20,521 xwiki-rendering-macro-footnotes-4.2-milestone-2.jar
08/07/2012 09:10 AM 23,215 xwiki-rendering-macro-html-4.2-milestone-2.jar
08/07/2012 09:11 AM 16,068 xwiki-rendering-macro-id-4.2-milestone-2.jar
09/02/2012 06:41 PM 28,796 xwiki-rendering-macro-jira-4.2-SNAPSHOT.jar
08/07/2012 09:11 AM 18,202 xwiki-rendering-macro-message-4.2-milestone-2.jar
08/07/2012 09:10 AM 20,549 xwiki-rendering-macro-toc-4.2-milestone-2.jar
08/07/2012 09:09 AM 15,063 xwiki-rendering-syntax-confluence-4.2-milestone-2.jar
08/07/2012 09:08 AM 14,989 xwiki-rendering-syntax-creole-4.2-milestone-2.jar
08/07/2012 09:08 AM 18,174 xwiki-rendering-syntax-docbook-4.2-milestone-2.jar
08/07/2012 09:08 AM 28,112 xwiki-rendering-syntax-doxia-4.2-milestone-2.jar
08/07/2012 09:09 AM 15,172 xwiki-rendering-syntax-html-4.2-milestone-2.jar
08/07/2012 09:08 AM 15,011 xwiki-rendering-syntax-jspwiki-4.2-milestone-2.jar
08/07/2012 09:09 AM 16,050 xwiki-rendering-syntax-markdown-4.2-milestone-2.jar
08/07/2012 09:09 AM 15,042 xwiki-rendering-syntax-mediawiki-4.2-milestone-2.jar
08/07/2012 09:06 AM 21,777 xwiki-rendering-syntax-plain-4.2-milestone-2.jar
08/07/2012 09:08 AM 17,460 xwiki-rendering-syntax-tex-4.2-milestone-2.jar
08/07/2012 09:09 AM 15,033 xwiki-rendering-syntax-twiki-4.2-milestone-2.jar
08/07/2012 09:06 AM 33,201 xwiki-rendering-syntax-wikimodel-4.2-milestone-2.jar
08/07/2012 09:07 AM 67,930 xwiki-rendering-syntax-xhtml-4.2-milestone-2.jar
08/07/2012 09:11 AM 105,736 xwiki-rendering-syntax-xwiki10-4.2-milestone-2.jar
08/07/2012 09:07 AM 45,002 xwiki-rendering-syntax-xwiki20-4.2-milestone-2.jar
08/07/2012 09:07 AM 24,797 xwiki-rendering-syntax-xwiki21-4.2-milestone-2.jar
08/07/2012 09:11 AM 19,737 xwiki-rendering-transformation-icon-4.2-milestone-2.jar
08/07/2012 09:12 AM 29,538 xwiki-rendering-transformation-linkchecker-4.2-milestone-2.jar
08/07/2012 09:07 AM 49,581 xwiki-rendering-transformation-macro-4.2-milestone-2.jar
08/07/2012 09:11 AM 15,511 xwiki-rendering-transformation-wikiword-4.2-milestone-2.jar
08/07/2012 09:06 AM 749,988 xwiki-rendering-wikimodel-4.2-milestone-2.jar
________________________________
This communication (including all attachments) is intended solely for
the use of the person(s) to whom it is addressed and should be treated
as a confidential AAA communication. If you are not the intended
recipient, any use, distribution, printing, or copying of this email is
strictly prohibited. If you received this email in error, please
immediately delete it from your system and notify the originator. Your
cooperation is appreciated.
Hello GSoC students and mentors,
Today is the firm pencils down deadline (in about 3 hours). What does
this mean?
First, your success regarding the GSoC project is supposed to be judged
on the work done so far, and you're supposed to send to Google all the
code that you wrote up until this date. (code submission will begin on
August 31)
Second, both students and mentors have to submit the final evaluations
before Friday, 19:00 UTC. Without the evaluations, the project will be
automatically considered failed, so don't forget to submit them on time,
ideally as soon as possible, not right before the deadline.
In general, I feel that all the projects have been successful, and are
good candidates for integration into the platform shortly. So, even if
the GSoC coding period is officially over, don't forget that one of the
main goals of the program is to introduce students to open source
communities on the long term. Thus, I'd be more than happy to see you
continue to be members of the XWiki open source community, hoping that
we made a good impression and made you feel welcome here. A project is
never "done", there's always room for improvements, new features,
maintenance, bug fixing, documentation and so on.
So, congratulations on your work, I hope you liked doing it, and that
you enjoyed the interaction with your mentors and with the XWiki community.
How to get out the code that you wrote?
Go to your local Git repository, and execute the following command (use
your own name for the --author parameter):
git log --patch "--before=2012-08-20T19:00z" --author=sergiu >
SergiuDumitriu-xwiki.patch
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi devs,
I'd need to access an instance of ExecutionContext from a Servlet within
XWiki in order to perform XWiki operations from there (query, storage
etc.). So far I tried to follow the same approach as the one I found in
the XWikiRestetServlet :
- XWikiRestletServlet.java http://bit.ly/TDcoQz
- Utils.java http://bit.ly/UfNWa6
i.e. something like this:
ComponentManager componentManager = (ComponentManager)
getServletContext().getAttribute("org.xwiki.component.manager.ComponentManager");
Execution execution = componentManager.getInstance(Execution.class);
ExecutionContext ec = execution.getContext();
XWikiContext xwikiContext = (XWikiContext) ec.getProperty("xwikicontext");
XWiki xwiki = xwikiContext.getWiki();
Unfortunately, while a proper Execution object is obtained indeed, the
returned ExecutionContext remains desperately null. Do you see any
configuration or annotation that may be missing ?
Another option I guess would be to lookup dedicated components for
performing the queries and storage directly without going through an
XWikiContext instance, but then what would be the proper way to discover
all the components that are available from the ComponentManager (esp.
query / storage) ?
Regards,
Stéphane
--
Ubimix - Give a new life to your content!
http://ubimix.com
Twitter: @ubimix
Hi devs,
We've identified yesterday one scenario when the doc cache can become corrupted. By corrupted I mean having a document in it which is empty and has isNew set to true.
Here it is:
* Imagine we're doing a hibernate query calling XHS.execute() (executeRead()/executeWrite()). We're thus in a hibernate session/transaction
* Now imagine that in the doInHibernate callback we start another request.
* Also imagine that the first query was executed in the "wiki1" wiki (setDatabase has been called and the DB is positionned in this wiki)
* Now imagine that the second nested query is done on a different wiki (for example asking to get the user doc from the main wiki)
* The result will be that the doc will not be found by hibernate and loadXWikiDoc will return a new doc with isNew set to true
* The doc cache will save this new doc in the cache
* Subsequent calls for this document will return the invalid document (with isNew = true)
This is what was happening for http://jira.xwiki.org/browse/XWIKI-8160, the problem being that HqlQueryExecutor was doing 2 nested queries. JV is fixing this today.
I'm reporting this here because it's important not to do nested queries like. We're going to generate an exception when we do to try to locate them if there are any more.
Thanks
-Vincent
Hi devs,
I need to have some Velocity macros in the file system because one use
case where I need them is when the database is empty. So I put them in
a new Velocity template file under /templates folder. I didn't want to
add them to macros.vm because they are very specific and not used very
often. Plus, I don't like the idea of putting all the macros in one
single file.
I then tried to include these macros in my other template and some
wiki page using #template. It didn't work. Surprisingly, when I
attached the template with the macros to the skin it worked.
By looking at the code I noticed that #template calls
XWiki#evaluateTemplate which (if I understood correctly) registers the
Velocity macros under
* '' (global) namespace if the template is part of a skin
* template name namespace if the template is not part of the skin.
Both seem wrong:
* in the first case, once you include the template the Velocity macros
become available globally
Hi Savitha,
I've started reviewing quickly the SOLR code in preparation for an integration in the platform and I have some questions which I have jotted down below as I was reviewing the code. Sorry for the terse format, I actually wrote the questions to myself and then decide to send them as is :)
General:
* Need an architecture diagram showing the main modules and threads and how they interact with the platform
Search-api:
* Is the Search API supposed to be independent of SOLR?
* Search interface is strange, it has implementation details such as: getImplementation(), initialize(),
* It also has other concerns such as getStatus(), getStatusAsJson(), getVelocityUtils(), getSearchRequest()
* Why do we need a Search interface? Why not instead use the Query module and introduce a new query type? (note return List from Query.execute() probably needs to be clarified). Replace SearchRequest with Query impl
* Naming of interfaces are a bit strange. For example: BuildIndex; should it be IndexBuilder instead? What about DeleteIndex, should it be IndexDeleter?
* I don't think we need deleteDocumentIndex(), deleteWikiIndex(), deleteSpaceIndex(), etc. We need a single deleteEntity(EntityReference reference, EntityType type). Same for IndexBuilder.
* Why is there a DocumentIndexer interface? Why is a Document different from other entities? For ex I can see DocumentIndexer.deleteIndex() why not IndexDeleter.deleteEntity(documentRef)?
* Why is there a need for RebuildIndex (which I assume is IndexRebuilder) and why cannot we use the IndexBuilder?
* Why the need for SearchIndex?
Search-solrj:
* solrj server in embedded mode is used.
* Shouldn't use system property but the xwiki configuration instead for the solrj home (see below in misc)
* EmbeddedSolrServer depends on Servlet API? "Also, if using EmbeddedSolrServer, keep in mind that Solr depends on the Servlet API. " from http://wiki.apache.org/solr/Solrj
* EmbeddedSolrServer should be started by listening to the app started event instead of lazily in Initializable IMO
* Since we use EmbeddedSolrServer how do we handle clustering? One instance per wiki instance? How do they reconcile their indexes? Need an architecture diagram for our solution for heavy loads.
Misc:
* all API to review and improve/stabilize
* typos to fix
* licenses to fix
* pom to fix
* missing class javadoc (eg BuildIndex, DeleteIndex, etc)
* exception handling to verify (ex: SolrjSearchEngine)
* Remove unneeded javadoc when @override
* Need to use the XWiki Permanent Directory for storing SOLR configuration data (the solr home) - Need to move data currenty in solr/ in a solr-configuration jar module which gets used as a fallback if the data doesn't exist in the solr home dir.
* Idea: use solr JMX to provide admin features (http://wiki.apache.org/solr/SolrJmx)
* TODO: Think about how to migrate users to use SOLR instead of Lucene or DB Searches. Need a plan.
Thanks!
-Vincent
Hello to everyone,
My company has been using XWiki for a while and we have always been able
to solve all problems by ourselves.
This time, it's a bug so weird we need some help from you.
Unfortunately, it is also quite urgent.
Let's begin with a short description of the problem:
- We use the latest XWiki development release, 4.2-milestone-2.
- We use Basic Authentication.
- We connect with a particular administrator to a particular subwiki (it
does not happen with other admiministrators or in other subwikis).
- We open XWikiPreferences once, all is fine.
- We open XWikiPreferences once again, we get a login prompt.
- Any subsequent call to any page gets us a login prompt.
As you may know, with Basic Authentication, a login prompt is an
impossible situation unless the user has been deactivated/removed or the
server does not receive the logged-in username.
But we dumped the JVM heap, and we found that the user object is still
there and the server receives the logged-in username.
After a lot of debugging, we discovered that the user document object
used to retrieve the user object has no references to its objects.
In other words, xObjects is an empty collection within the used instance
of XWikiDocument.
If you would like to help us just read the whole JIRA issue, it contains
much more information. And thank you very much!
http://jira.xwiki.org/browse/XWIKI-8160
--
Martino Dell'Ambrogio
Security Auditor
Web: http://www.tillo.ch/
Email: tillo(a)tillo.ch
Hi devs,
The {{velocity}} macro has a nice filter that removes the whitespace
from the start of each line. This allows us to format (indent) the
Velocity code without generating whitespace garbage.
Recently I had to move some Velocity macros from a wiki page to a
Velocity template file and the absence of this filter turned out to be
a pita. Even if my macros were generating HTML, consecutive
whitespaces were collapsed into a single one which was still visible,
breaking my layout a little. Some of my macros were generating Strings
which now contained a lot of whitespace. I had to update my functional
tests to trim the actual text taken from the UI whenever asserting
something.
WDYT about applying the same filter when parsing Velocity templates?
Do you see any problems with ignoring the whitespace at the start of
the line?
Thanks,
Marius
Hi guys,
I would like to modify a bit the Maven XAR plugin to add in the
package.xml some extension related informations like the extension id
and version at the very least.
The idea is to be able to know what a XAR is exactly like we have the
pom.xml packaged with the jar file for example.
Among other things it will cover the following use cases:
* when someone import a XAR with the standard UI, automatically
register it in the extension index if it happen to be an extension
(i.e. if we find extension informations in its package.xml)
* wiki manager and workspaces can properly register actual extension
when creating their default template from a XAR the first time (this
is for example required to be able to upgrade a farm with EM where
pretty much all the wiki as been created from this default template)
In both cases the idea is to support as much current behaviours as we
can and still be able to use the full power of Extension Manager.
There should not be any backward compatibility issue here since it
does not really change anything in the XAR structure.
WDYT ?
Here is my +1
Thanks,
--
Thomas Mortagne
Hi,
I have received numerous complains that simple users have problems in
editing the content and title of the Welcome block ("Welcome to you wiki"
gadget) from the homepage.
There are multiple factors that influence the editing of that particular
gadget and that make the job especially harder for beginners.
One of these factors is that the gadget used to display the Welcome content
is an "include" gadget. Without some custom actions for the gadget that
would let the user navigate to the included page or without some
auto-redirect mechanism, the simple users have difficulties in
understanding where the welcome content is coming from and what actions
they need to do in order to edit that content.
Also the "include" macro has a lot of advanced properties that can be scary
and confusing for users (context, reference, section, type, etc.).
My proposal is to create a new "text" gadget. This gadget will be very-very
simple and will contain just the gadget's title and the gadget's content.
Its only purpose will be to let users add textual information inside a
dashboard.
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/EditingWelcomeMess…
Right now we have specialized gadgets for HTML content, velocity content,
code in general, boxes, success messages, etc. but no way to put just a
simple text inside the dashboard.
Let me know what you think.
Thanks,
Caty
Hi devs,
Me and Thomas are late on the work for making an XWiki farm upgradable
through the Extension Manager in a few minutes and JV just committed
two new modules, wiki components and UI extensions, in the platform
and they need some time to be tested and stabilised. Thus I'm
proposing to delay the 4.2M3 release by one week and reduce the 4.2RC1
by one week so that the final release date for 4.2 stays the same:
* 4.2M3: 3 September
* 4.2RC1: 10 September
* 4.2 final: 17 September
Here's my +1.
Thanks,
Marius
Hi devs,
Do you have unfinished work that needs to be included in this release?
I know JV has to move the wiki components module from contrib to
platform. Anything else? Also, are there any blocking issues?
Otherwise, I'd like to start the maven release in the afternoon. I'll
take care of the failing tests in the mean time.
Thanks,
Marius
Hi,
I've been working on UI extensions lately and those extensions are
implemented as components.
To be able to have components both defined from java code and from
wiki documents I've worked on the xwiki-platform-component-wiki module
started by Jerome a while ago.
The initial design is described here:
http://dev.xwiki.org/xwiki/bin/view/Design/WikiComponents
In addition the module allows other modules to easily synchronize java
components with content coming from XObjects.
To do so you need to implement WikiComponent [1] and
WikiComponentBuilder [2]. Then a manager will automatically
unregister/register your components whenever it's required: when the
wiki starts, when a document is updated, deleted, etc.
In order to commit the UI extension module I need
xwiki-platform-component-wiki to be moved to platform.
Here's my +1
[1] : https://github.com/xwiki-contrib/xwiki-platform-component-wiki/blob/master/…
[2] : https://github.com/xwiki-contrib/xwiki-platform-component-wiki/blob/master/…
--
Jean-Vincent Drean,
XWiki.
Thank you Mr. Mortagne! Keep up the great work.
I will go with the 2nd option and use the REST api.
________________________________
This communication (including all attachments) is intended solely for
the use of the person(s) to whom it is addressed and should be treated
as a confidential AAA communication. If you are not the intended
recipient, any use, distribution, printing, or copying of this email is
strictly prohibited. If you received this email in error, please
immediately delete it from your system and notify the originator. Your
cooperation is appreciated.
Hello Jerome, Vincent, friends
Good idea. The extension page is here:
http://extensions.xwiki.org/xwiki/bin/view/Extension/xorange
wdyt?
Thanks again,
Jonathan Solichin
> On Tue, Aug 21, 2012 at 11:43 AM, Jonathan Solichin <jssolichin(a)gmail.com>wrote:
>
>> Hello Sergiu, friends,
>>
>> First of all, thank you once again for this wonderful opportunity to work
>> with the xwiki team. It has been a learning experience that will no doubt
>> change my future in programming and open source. Like Sasinda said, all the
>> support and help throughout the project have been enormous. I think all of
>> us GSOC students will agree that it was one of the most interesting and
>> useful summer we ever had.
>>
>> Thank you for the reminders to submit the code and evaluation.
>>
>> The XWiki team made a great impression, and in my opinion, a very good
>> face for the open source community. I hope to be able to contribute more
>> and continue support/development on the skin as it comes up. Like Sasinda I
>> will definitely try to come back in my free time
>>
>> Status:
>> The overall design and implementation goals of the skin is, in my
>> opinion, achieved (note: as planned we did not use foundation as the base
>> of our skin as the GSOC proposal stated). The skin works on a plethora of
>> browsers (tested in ie7-9, opera, ffx, chrome, and safari. devices: g2x,
>> nokia 710, nexus7, bb curve) and responds to size changes. Due to the
>> limitation of some browser, there will be slight deviations, but none
>> should impact the function of the skins.
>>
>> There are some minor differences than those of the design plan. For
>> example the apps are not skinned as they were designed in the design plans.
>> After working on the skin, I did not think that was priority since there
>> are so many apps, that it wouldn't be the most fruitful use of the gsoc
>> time to skin one. I'll try to work on these in my free time. The idea to
>> create a 2nd configuration page for the skin was scraped since it was
>> deemed to not be efficient.
>>
>> In general, the skin is usable and "complete". I think to truly complete
>> the skin, we would need users to try and use the skins since I did not have
>> the time, and I think XWiki is too expansive for me to test every use case
>> scenario anyway. Future explorations would be how to make the skin
>> functions more efficient.
>>
>> Thank you once again for the opportunity, do let me know of anything you
>> would like me to do. Thanks Asiri for dropping by and dropping us the hint
>> ahaha.
>> Thank you for all those involved in making GSOC happen, from Caty,
>> Eduard, Sergiu, Vincent, Thomas and anyone who I missed. Finally, last but
>> not least, Thank you especially to Jerome, for mentoring me through out
>> this time.
>>
>> Best,
>> Jonathan Solichin
>>
>
>
Hello Sergiu, friends,
First of all, thank you once again for this wonderful opportunity to work
with the xwiki team. It has been a learning experience that will no doubt
change my future in programming and open source. Like Sasinda said, all the
support and help throughout the project have been enormous. I think all of
us GSOC students will agree that it was one of the most interesting and
useful summer we ever had.
Thank you for the reminders to submit the code and evaluation.
The XWiki team made a great impression, and in my opinion, a very good face
for the open source community. I hope to be able to contribute more and
continue support/development on the skin as it comes up. Like Sasinda I
will definitely try to come back in my free time
Status:
The overall design and implementation goals of the skin is, in my opinion,
achieved (note: as planned we did not use foundation as the base of our
skin as the GSOC proposal stated). The skin works on a plethora of browsers
(tested in ie7-9, opera, ffx, chrome, and safari. devices: g2x, nokia 710,
nexus7, bb curve) and responds to size changes. Due to the limitation of
some browser, there will be slight deviations, but none should impact the
function of the skins.
There are some minor differences than those of the design plan. For example
the apps are not skinned as they were designed in the design plans. After
working on the skin, I did not think that was priority since there are so
many apps, that it wouldn't be the most fruitful use of the gsoc time to
skin one. I'll try to work on these in my free time. The idea to create a
2nd configuration page for the skin was scraped since it was deemed to not
be efficient.
In general, the skin is usable and "complete". I think to truly complete
the skin, we would need users to try and use the skins since I did not have
the time, and I think XWiki is too expansive for me to test every use case
scenario anyway. Future explorations would be how to make the skin
functions more efficient.
Thank you once again for the opportunity, do let me know of anything you
would like me to do. Thanks Asiri for dropping by and dropping us the hint
ahaha.
Thank you for all those involved in making GSOC happen, from Caty, Eduard,
Sergiu, Vincent, Thomas and anyone who I missed. Finally, last but not
least, Thank you especially to Jerome, for mentoring me through out this
time.
Best,
Jonathan Solichin
Hi all!
I was trying to build XWiki from sources (xwiki-commons) with a fresh new
Maven installation (empty local repository) and found a problem with the *
org.restlet.ext.jaxrs* artifact (2.0.14).
This was the build error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
(default-compile) on project xwiki-commons-extension-repository-xwiki:
Compilation failure: Compilation failure:
[ERROR]
/data/Repository/XWiki/xwiki-commons/xwiki-commons-core/xwiki-commons-extension/xwiki-commons-extension-repositories/xwiki-commons-extension-repository-xwiki/src/main/java/org/xwiki/extension/repository/xwiki/internal/XWikiExtensionRepository.java:[38,23]
package org.restlet.data does not exist
[ERROR]
/data/Repository/XWiki/xwiki-commons/xwiki-commons-core/xwiki-commons-extension/xwiki-commons-extension-repositories/xwiki-commons-extension-repository-xwiki/src/main/java/org/xwiki/extension/repository/xwiki/internal/XWikiExtensionRepository.java:[116,47]
package MediaType does not exist
A little above it i saw this:
Downloading:
http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest…
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
97d021087f5852baf8cc9deca20825b1bf42bbaf for
http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest…
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
97d021087f5852baf8cc9deca20825b1bf42bbaf for
http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest…
Downloaded:
http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest…
KB at 1.6 KB/sec)
[WARNING] The POM for org.restlet.jse:org.restlet.ext.jaxrs:jar:2.0.14 is
invalid, transitive dependencies (if any) will not be available, enable
debug logging for more details
Downloading:
http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest…
Downloaded:
http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest…
KB at 47.0 KB/sec)
It seems the org.restlet's repository was down for maintenance at the time
Nexus fetched the files.
The POM (
http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest…)
has this inside:
You caught us doing a little maintenance. We're sorry that you can't
access your community right now.
...
With a problem like this, would something like adding the org.restlet's
repository to my settings.xml do the work?
I'm in no hurry anyway, i can wait for the repository... ;)
If there's anything else i can do, just drop me a message!
Thanks,
Fernando
Hi devs,
Each java module has a current TPC level (Test Percentage Coverage), be it 5% of 90%.
As part of improving XWiki's quality, the idea is that future commits in this module shouldn't lower the module's quality.
One easy way to ensure this is to measure the current TPC level and make the build fail whenever the build is under this TPC threshold.
This means that if you commit code that has less tests average than what currently exists then the build will fail.
Here's one way to implement it:
<!-- Fail the build if the test coverage is below a given value.
Note: Since this takes a bit of time to execute we only run this when the integration-tests profile is active -->
<profiles>
<profile>
<id>integration-tests</id>
<build>
<plugins>
<plugin>
<groupId>com.atlassian.maven.plugins</groupId>
<artifactId>maven-clover2-plugin</artifactId>
<configuration>
<targetPercentage>86.9%</targetPercentage>
</configuration>
<executions>
<execution>
<id>clover-check</id>
<phase>verify</phase>
<goals>
<goal>instrument-test</goal>
<goal>check</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
So this proposal is about the following strategy:
* Allow committers to modify module's pom.xml to fail the build when then TPC is under the current threshold
* Since oldcore is really difficult to test, maybe we should not set build failing for oldcore. OTOH oldcore is an important module. WDYT?
* If for some reason a committer wants to lower the TPC threshold for a module he needs to get the agreement from the other committers (vote). There might be valid reasons like fixing an important bug quickly for a release and writing a test is just too complex so the writing of the test is to be delayed for after the release, etc.
* I'd like to consider this as an experiment and see how it goes
Note: This is about unit test TPC which is different from the TPC that includes functional tests.
WDYT?
Here's my +1 to try this out and see how it goes.
Thanks
-Vincent
I have the BulletinBoard plugin installed into Xwiki to use as a forum. The
forum works fine if it is accessed directly. However, I have a page in the
Xwiki that includes a menu and a particular section of the forum. I can see
content, I am just unable to add new topics via the page that contains a
menu. When accessing the forum directly under the same section I am able to
add new topics. The problem is that the site navigational menu must be
included so this "middle man" page is necessary.
The page that includes references to the menu and the forum section is
written as:
(% style="margin-top: -2em;" %)
(((
|(% style="vertical-align: top; position: relative; top: -1.0em; left:
-0.4em; border:0;" %)(((
{{include document="CTAs.Menu"/}}
)))|(% style="width: 100%; border-width: medium; border-style: none;
border-color: -moz-use-text-color; vertical-align: top;" %)(((
(% style="margin-top: -0.7em; margin-left: -0.25em" %)
(((
{{include document="BulletinBoard.CTAENS" context="new"/}}
)))
)))
)))
Where CTAs.Menu is the menu I need to include and the BullentinBoard.CTAENS
is the section of the forum I need to display.
The page displays fine, however the link "Add new topic" is not functional.
The error that seems to be generated due to this action is....
012-08-21 12:32:33,548 [/xwiki/bin/view/CTAs/ens_forum] ERROR
rnal.DefaultObservationManager - Fail to send event
[org.xwiki.observation.event.ActionExecutionEvent@373aa5] to listener
[com.xpn.xwiki.stats.impl.XWikiStatsServiceImpl@110bc5c]
java.lang.NullPointerException
at
com.xpn.xwiki.stats.impl.XWikiStatsServiceImpl.onEvent(XWikiStatsServiceImpl.java:190)
at
org.xwiki.observation.internal.DefaultObservationManager.notify(DefaultObservationManager.java:278)
at
org.xwiki.observation.internal.DefaultObservationManager.notify(DefaultObservationManager.java:247)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:316)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:117)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:129)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:152)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:218)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:775)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:704)
at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:897)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:662)
--
View this message in context: http://xwiki.475771.n2.nabble.com/Unable-to-add-new-topics-under-Xwiki-Bull…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Dear XWiki community,
The Advanced Search features, Administration
module is almost complete in Solr Search component.
The link to the running instance is given below.
http://savitha.hoplahup.net/xwiki/bin/view/Main/AdvancedSearch
Link to the Set Up Documentation and the features Page
Set Up Doc and Feature
Page<http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SolrSearchApplication>
Progress Page<http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SOLRsearchcomponent>
Work remaining to be able to commit the component in platform :
1. Fix checkstyle errors
2. Auto Suggest feature
3. Admin UI
4. Minor bugs in Facet search to be fixed
5. Search calibration
6. Unit test cases and Functional test cases.
Planning to do the following this week
1. Fix checkstyle errors
2. Auto Suggest feature
3. Fix the minor bugs.
4. Search calibration
5. Complete the documentation.
--
Thanks,
Savitha
Hi devs,
Trying to address http://jira.xwiki.org/browse/XWIKI-6228 I noticed
today a big problem with the way translations work.
$xwiki.getDocument('Main.Welcome').getTranslatedDocument('fr').plainTitle
No matter what language I request, the title will always be displayed in
English. This is caused by the fact that for all translations, the title
is actually $msg.get("xe.dashboard.wiki.welcome"), and $msg uses the
context language, not the document language. This means that getting the
right title of the document is almost impossible.
Given that we've separated the displayers from the oldcore and the main
rendering engine, we could change their behavior so that document
translations would work better. Whenever displaying some information
from a document, we should temporarily change the context language to be
the same as the document's language, if any. This would be a
backwards-incompatible change, but IMO it's a change for the better.
WDYT?
--
Sergiu Dumitriu
http://purl.org/net/sergiu/