Hi devs,
Just wanted to share my vision of how we should tackle migrating to the new Model. I see the following steps:
* Step 1: Define new model interfaces (status: in progress)
* Step 2: Implement a "bridged" version which uses the oldcore (status: in progress).
* Step 3: Start moving code to use the new API as the new API and its implementation progress. Note: we should start using the produce of step1 and step2 ASAP to tune the details (status: not started)
* Step 4: At the same time, start a new implementation based on a RDBMS (probably hibernate-based, to be decided) (status: not started). I'd also like that we start other implementations not based on a RDBMS just to prove that it works with other storages. Ideally I'd like some NoSQL impl (Caleb maybe?) and I'd also like to try a Git-based implementation (using jgit)
* Step 5: Deprecate all our search apis located in XWikiHibernateStore and make everyone use the new QueryManager module. This needs some tuning on the QueryManager for missing stuff but that's doable (I need to send some proposal on missing stuff). (status: in progress). The idea here is to decouple search from storage. Note that we'll need to write some translator from HQL to XWQL or the new search query language.
* Step 6: As we progress in step 2, 3, 4, introduce a configuration parameter to decide which implementation to use ("bridged", etc) so that users can start playing with new implementations (status: not started)
* Step 7: Rewrite a new Importer/Exporter that exports everything (all the data in the current DB) + all configuration files/data. To see what we are currently not exporting, see http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Backup#HUsingtheXWikiEx… This new exporter should probably be based on the XWiki Streams module being developed here: https://github.com/xwiki-contrib/wiki-stream (status: in progress but not active)
* Step 8: When users want to migrate from one implementation ("bridged" for ex) to a new implementation they export their wiki, set the new implementation in the configuration file and reimport. (status: not started)
For me Step3 can almost begin (I probably need one or 2 more weeks to be ready to have some use cases implemented and I'll send a vote to merge my work in feature-newmodel branch in master - Would be good if you guys start looking at it and give comments to be ready for this).
Then we need volunteer for Step 4 for:
* new RDBMS implementation. Who?
* noSQL impl. Cassandra? other? Who?
* git implementation. Vincent
WDYT about the plan?
In term of time required it's probably going to take us about a year to have a first working version for all the steps by working at a leisurely pace.
Thanks
-Vincent
Hello devs,
we are having a very very weird bug: the two nodes of our cluster are made of A and B and saved objects sync into B when written on A but fail to do sync into A when written on B.
What could be the cause?
thanks in advance
Paul
Hi devs,
We've been talking about this for a long time already. We've even seen what Jenkins does (go to http://ci.xwiki.org and click on the bottom left link).
Today I've seen an article showing a cool new plugin for JIRA to help localize JIRA:
http://blogs.atlassian.com/2012/09/inproduct-translation-plugin-beta/
Since XWiki allows overriding translation in wiki pages we have almost the same features OOB as those touted on the JIRA plugin page:
* "Access Management: control which groups can translate JIRA". We have that too with wiki right management
* "Instant updates: translations are saved automatically and appear immediately for all users". Same for us
• "Mouse-hover: items turn green to let you know they are translatable". This is the cool part we're missing. It would be awesome to be able to do this. We should brainstorm about how to be able to do that.
* "Translate Page: select from your username drop-down". We don't have that either and it would be cool to write/bundle in XE a Translation app to let users write translations in their wiki and then to contribute them with one click to l10n.xwiki.org (we'd need to put l10n on SCM too at the same time).
WDYT? Any idea about how to do the "mouse-over" feature? Anyone interested by this topic?
Thanks
-Vincent
Is it possible to have a page in the Xwiki visible and viewable to the
"public" that is not under the control of the custom authentication class
defined in the config?
Currently, I have a JSP file that collects user credentials that are placed
in the HTTP session used for login. However, when the user is authenticated
and redirected to the /xwiki web application those session values are no
longer there so the Xwiki just loops back to the JSP file looking for
credentials.
What I would like to do is have something like /xwiki/public/login where the
user is prompted to enter their credentials which is then processed by the
custom authentication and sends the user to /xwiki/private.
By setting the xwiki.authentication.authclass to a custom authentication
class... it seems like it is an all or nothing approach to where I cannot
have a subset of pages open to the public.
--
View this message in context: http://xwiki.475771.n2.nabble.com/Public-pages-within-a-secured-private-Xwi…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
My instance of Xwiki is using custom authentication. I have a new
requirement to add Yubikey based authentication now. I believe in order to
pull it off, I need to set a session attribute in the Xwiki context with a
value defined in a JSP file.
I tried to set it in the current HTTP session, with the code below but it is
not showing up in the Xwiki context session when the checkAuth method is
called
...
session.setAttribute("okc_sso_username", username);
...
public XWikiUser checkAuth(XWikiContext context) throws XWikiException
{
....
String okc_sso_username =
(String)context.getRequest().getSession().getAttribute("okc_sso_username");
....
}
Any idea on how to bind the two to make a JSP session variable available in
the XwikiContext?
--
View this message in context: http://xwiki.475771.n2.nabble.com/Setting-a-session-variable-in-the-Xwiki-C…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hello,
I'm trying to update our semantic extension for xwiki from 3.1 to 4.2 to
be able to release this as an open-source finally. Now, it looks like
something inbetween 3.1 and 4.2 changed in xwiki-platform-oldcore's
com.xpn.xwiki.objects* since my current 4.2 setup complains a lot with a
message like:
Wrapped Exception: Error number 7006 in 7: Cannot find property class
com.xpn.xwiki.objects.classes.SPARQListClass in MetaClass object
The SPARQListClass is our implementation of the list class which
provides dynamic list based on the supplied SPARQ query and which was of
course working well on top of 3.1. I'm looking into all the classes in
4.2's com.xpn.xwiki.objects subdirectory but so far I'm not able to
distill what change between 3.1 and 4.2 breaks our SPARQList.
Any idea what's going wrong or where should I have a look is highly
appreciated.
Thanks!
Karel
Hi devs,
When we release a new version we publish the announcement in several places (wikimatrix, freshmeat, wikipedia). I'd like to propose that we add DZone too.
For example I've just seen that GateIn 3.4 has been announced there: http://www.dzone.com/links/gatein_34_is_released.html
DZone is very well know and I think it would help spread the word even more about XWiki.
So here's my +1 to add DZone to the list of sites to update when we release.
Thanks
-Vincent
The XWiki development team is proud to announce the availability of XWiki
Enterprise 4.2 Milestone 3. This is the third and final milestone of the
XWiki Enterprise 4.2 version. This release brings new and improved UIs for
file upload, logging configuration, an applications panel and the
experimental install/upgrade wizard. For developers this release introduces
many features: a new file upload widget, minor improvements of the
attachment picker and documents macros, the ability to add skin extensions
located in JAR files, a new field (mime-type) to index attachments by, an
extension of the xar format and an experimental UI extension mechanism.
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/ReleaseNotesXWikiEnterprise
42M3
Thanks
-The XWiki dev team