In order to fix a problem with the cache, I would like to add a pointer type to the storage api.
The problem with the cache is there are multiple names which, when asked of the persistent store,
return the same document. There is no effective way to know what all names which will return that
document. When a document is modified, it is removed from the cache but the only version removed is it's
"real" name. All of the other names for it linger in the cache eating up memory and threatening to
provide someone stale data.
Instead of caching the document, we could cache a pointer to the document and when it became stale,
the pointer could be set to null and then any other name under which that document was cached would look
up a null pointer and the cache logic could remove it.
I would like to add it to xwiki-platform-store-api module and it will look roughly like this:
package org.xwiki.store;
public final class Pointer<T>
{
/** The thing which this pointer points to. */
public T target;
}
WDYT?
Caleb
Hi devs,
Could each of you update the status of the Roadmap items for XE 3.2 to know where we stand. Be as precise as possible please. If you have any doubt about whether you'll be able to implement something in due time please raise it so that we can discuss and try to find solutions (reduce scope, get some help, etc).
As a reminder we have one more milestone (3.2M3) before the RC. Here are the dates again:
* 3.2M3: 12 Sep 2011
* 3.2RC1: 26 Sep 2011
* 3.2 Final: 10 Oct 2011
Roadmap items:
• UI for extension manager + backend extension manager (continued, especially nice XAR upgrades). Thomas + Jean-Vincent
• Search improvements and especially scoring, French support and wildcard issues (continued from 3.1). Sergiu
• App Within Minutes. Marius
• XE-923: Implement user dashboard. Anca
• XWIKI-6504: Convert Panels application into syntax 2.0. Sergiu
• XWIKI-6676 (UI does not report failed delete actions of attachments) and XWIKI-6623 (Attachment upload failure gives no feedback to user). Sergiu
• Fix issues with Oracle support. Specifically XWIKI-6682 and XWIKI-6683. Vincent + Sergiu + Sorin
• Fixes for HTTPS support. Specifically XWIKI-6690, XWIKI-4489 and XWIKI-5771. Sergiu to help
• XWIKI-6687 Be able to delete a space from the UI. Marius
• Stats module improvements (Commit code from client projects without changes). Marius
• LDAP Admin UI (commit Jerome work without changes)
• XWIKI-5037: Clustering bug preventing a node from restarting. Vincent + Thomas
• XWIKI-6684 Use a predefined Space Template like Dashboard, Livetable when creating a new space. Anca
• XWIKI-6073 Change stylesheet and javascript extension filename when a modification is done on those
• Rest improvements (Restlet upgrade + re-organization of the rest module - already started). Jerome
• Suggest widget improvements and bug fixes (better highlighting, better performance, new options - already started as well). Jerome
• Cache improvements, namely: XWIKI-6170, XWIKI-6173 and XWIKI-6169. Caleb
• Fix functional tests to work with CSRF protection: XWIKI-5465. Alex
• Performance tests. Marius
• Selenium 1 to Selenium 2 move for the WYSIWYG functional tests. Marius
• Integrate some Wiki 3.0 workspace features into XEM. Eduard
Thanks
-Vincent
Hello,
I have a XWiki object of a class where one property is defined as a
list. During the page creation of this object (by using appropriate
template provider) I'm setting several values from the list of possible
values for the property. My problem is that although I've set several
values I still get just one value when I look at the object properties
in appropriate sheet class. E.g.
I do have BookClass which besides other props defines property `kind'
where kind might have `fantasy', `drama', or `novel' value. It also
might have several values -- well, not good example but I hope this
illustrates what I'm doing here.
And now when I create new page as a book I set several kinds (for
example fantasy & drama) then when I see the page I see only fantasy as
the book kind.
I'm using XWiki 3.1 snapshot as of May 27 2011. My question is it a
known bug, am I doing anything wrong or was it already fixed (in case of
bug)?
Thanks a lot!
Karel
Dear all,
I am on the way of replacing the xmlrpc implementation of
RemoteXWikiDataStorage implements IDataStorage {}.
One question is about how to implement login and logout functionality
via REST API.
From REST API document, users can be authenticated via something like:
1. XWiki session
2. HTTP Basic Auth.
HTTP basic auth can be implemented via adding HTTP header to the HTTP
request, then XEclipse can display Xwiki Resources by parsing the response.
Therefore, do we need to implement login and logout methods?
Best regards
Jun Han
Hi all,
I've finished development of the XWiki Android Client. I also finished XWiki
REST library unit tests and instrumentation tests for the UI components will
be added soon.
Here is a demo of the application.(This demo is captured using the Android
emulator which may result slow response than an actual device)
( http://www.youtube.com/watch?v=aiEM0iNMnTE )
Please give me your feedback so that I can improve the project.
Thank you,
Best Regards,
Chamika Weerasinghe
Hi, Last week I have done following things:
1. Refine the link autosuggestion functions according to the code review of
Marius
2. Clean the code and wrote the README file for link autosuggestion
functions, including:
a. Introduction to link autosuggestion functions, describing its
features;
b. Report the added files and the modified files
c. Installation instructions
3. Testing it in Firefox, chrome, safari and ie6, ie7, ie8. Currently:
a. Firefox works fine in both linux and windows. Not test in IOS
b. Suggestion box can not be shown in the right place in chrome, I have
found the problem, and I am fixing it now.
c. Safari works fine in windows. not test in linux and IOS.
d. Haven't test in ie6, ie7 and ie8
In next week, I will do the following thingsï¼›
1. Continue testing it in
a. Safari in Linux.
b. fix the bug found for chrome
c. test it in ie6, ie7 and ie8.
2. Write jasmine tests for link autosuggestions.
--
Best wishes,
许凌志(Jame Xu)
MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University
Department of Computer Science and Technology, Xi’an Jiaotong University
Hi devs,
I'd like to propose adding the Ivy JAR to our Platform/XE distributions.
The reason is simple: it makes it possible to use the Groovy @Grab directive which makes it real easy to extend XWiki using Groovy script.
Several advantages:
- not having to manually hunt for transitive dependencies
- not needing to stop/restart XWiki (since this is what you need to do if your groovy script needs to use some third party jars).
Here's a good usage example:
{{cache}}
{{groovy}}
@Grab(group='org.codehaus.groovy.modules.http-builder', module='http-builder', version='0.5.1')
import groovyx.net.http.RESTClient
github = new RESTClient( 'http://github.com/api/v2/json/' )
println "|=Project|=Description|=Use Wiki?|=Use Issues?"
def response = github.get( path : 'repos/show/xwiki' )
response.data.repositories.each() { repo ->
println "|[[${repo.name}>>http://github.com/xwiki/${repo.name}]]|${repo.description}|${repo.has_wiki}…"
}
{{/groovy}}
{{/cache}}
If you try to do this without the grab directive you'll find yourself hunting down more than 30 jars which you'll need to put in your WEB-INF/lib directory, whereas here it's a single line directive. It's really powerful.
Here's my +1 to make it easy for users to use Groovy scripts.
Thanks
-Vincent
Hi devs,
Since 1) we are currently testing only on one browser (FF 3.6 right now) and 2) since FF 6 is now the mainstream version and since 3) we have an issue with latest selenium2 and FF 3.7 (see http://code.google.com/p/selenium/issues/detail?id=2320), I propose to update our agents to use FF 6.0.
I'm going to proceed so shout if you don't agree.
Thanks
-Vincent