Hello team,
I am meeting a query at startup of my xwiki (3.1) which takes more than three minutes.
delete from xwikiproperties where xwp_name like 'editbox_%' and xwp_classtype='com.xpn.xwiki.objects.LongProperty'
I don't find where that query is made anymore, Google is becoming worse and worse to search for XWiki things, but I vaguely remember something about it.
Do you all agree it is useless a delete?
Should I create an SQL index just for that?
thanks in advance
paul
Hi devs,
XWiki is planning to participate in this year's Google Summer of Code [1].
The organization registration period has already started and the deadline
is the 9th of March [2] (a bit more than one week).
1. We need to provide by then a list of proposals and assign mentors for
the students that are going to implement them.
I would like to ask everybody that wants to participate as a mentor from
the XWiki organization to review the proposals [3] list (that is currently
empty) and add as many interesting proposals as possible.
The proposals can be either new, or they can be revived from previous year
proposals. Just navigate to the previous years, find the proposal you like
and know about, go to its proposal page (click it) and press the "Clone to
this year" link. Now you can assign yourself as lead for that project,
update it's description if needed and wait for the student applications to
start pouring :)
2. We also need to submit the actual application [4] of the XWiki
organization to participate to the GSoC 2012 project so I would also like
to ask you to review it so that we have a better chance of being selected
into the program.
Thanks for your help,
Eduard
----------
[1] http://www.google-melange.com/gsoc/homepage/google/gsoc2012
[2] http://www.google-melange.com/gsoc/events/google/gsoc2012
[3]
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/#HProposedProjects28…
[4]
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/OrganizationApplicat…
Hi devs,
Right now renaming a key is a pain if we don't want to loose the
existing translations associated to it. Basically it require to rename
the key in all languages and reimport all of them on l10n.xwiki.org.
We already have a section in the translation file to indicate which
translations are deprecated. The idea is to indicate what is the new
name of a deprecated translation key directly in the translation file
so that l10n.xwiki.org can automatically copy the translation to the
new key when it find a new deprecated key while importing default
translation file.
For that we need to decide a syntax to indicate what is the new name of the key.
I propose to do something similar to java and indicate it in a comment
like the following:
new.key.name=Default translation
#@deprecated new.key.name
old.key.name=Default translation
Here are some other alternatives to "deprecated":
* replacedBy
* new
others ?
Here is my +1 for "deprecated", more intuitive for Java developers and
it's clear it's a deprecated translation key.
Thanks,
--
Thomas Mortagne
Hi devs,
>From the start Extension Manager has been designed to be usable
outside of XWiki. I would like to make this effective by moving it
into commons.
Here is the detail of the operation:
= Not moved
* UI of Extension Manager
* Xar handler
* Server side module and UI of XWiki Repository (but the client will
be moved to commons since a generic REST protocol has been designed
for it which could be implemented by anything)
* Clustering module
* Script service module
* An ExecutionContextInitializer which is responsible for switching
the current Thread classloader for each new request with the one
linked to the current wiki (so that everything loading classes like
script macros do it from the proper classloader)
That means that the commons version of Extension Manager will support
everything the current one supports except for the thing that don't
make sense outside of XWiki (XAR packages, wiki pages UI, etc.).
= Dependencies to move
* ClassLoader module: even more than Extension Manager (and like other
stuff that will follow in other mails) this module is ready to be
moved as it is except for the attachment based support which is
already in a separated module and will stays in platform obviously.
= Extracted from Extension Manager
* Job Manager: encapsulate background task into a job providing
progress and status informations as well as logging isolation. In it's
own module.
* ClassLoader Manager: namespace based organization for classloaders
(like we have for Component Managers). In the existing classloader
module.
WDYT ?
Here is my +1
--
Thomas Mortagne
Hi Thomas,
I'm having problems with the cache tests for infinispan. They take a very long time to execute locally and some fail:
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.xwiki.cache.infinispan.InfinispanCacheTest
Tests run: 10, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 103.143 sec <<< FAILURE!
Running org.xwiki.cache.infinispan.InfinispanConfigTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.044 sec
Running org.xwiki.cache.infinispan.InfinispanLocalCacheTest
Tests run: 10, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 102.152 sec <<< FAILURE!
Results :
Failed tests: testCreateAndDestroyCacheLRUMaxEntries(org.xwiki.cache.infinispan.InfinispanCacheTest): No value has been evicted from the cache
testCreateAndDestroyCacheLRUTimeToLive(org.xwiki.cache.infinispan.InfinispanCacheTest)
testCreateAndDestroyCacheLRUAll(org.xwiki.cache.infinispan.InfinispanCacheTest)
testCreateAndDestroyCacheLRUMaxEntries(org.xwiki.cache.infinispan.InfinispanLocalCacheTest): No value has been evicted from the cache
testCreateAndDestroyCacheLRUTimeToLive(org.xwiki.cache.infinispan.InfinispanLocalCacheTest)
testCreateAndDestroyCacheLRUAll(org.xwiki.cache.infinispan.InfinispanLocalCacheTest)
Tests run: 21, Failures: 6, Errors: 0, Skipped: 0
Any idea?
Thanks
-Vincent
Is there a way in XWiki's velocity to process an XML document? I want
to parse a SPARQL Query Results XML document [1] returned by a custom
script service.
Thanks!
[1] http://www.w3.org/TR/rdf-sparql-XMLres/
--
Mark Wallace
Principal Engineer, Semantic Applications
Modus Operandi, Inc., FL, USA