- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] [GSOC] [REMINDER] Today is the student application deadline
by Eduard Moraru 06 Apr '12

06 Apr '12

Hello interested GSoC students, I`d like to remind you that, according to the GSoC timeline [1], today at 19:00 GMT/UTC is the final day when you can apply as a GSoC student. After that, students can no longer apply or modify their application's details. Please make sure that you don`t miss this deadline and that your application is in final state to be reviewed by our mentors. Also, if you have worked on any existing Jira issue, please make sure to include that in the application so that we know about it and make sure you publish (pull request or attached patch file) your work so we can review it. Otherwise, if you have posted a link (github repository) with any past coding that you have done that you would like us to see, please make sure to include it in the application together with any references that can certify that the code is yours. Code samples that were uploaded very recently (like 1 week ago) will not be considered. Thanks, Eduard ---------- [1] http://www.google-melange.com/gsoc/events/google/gsoc2012

1 0

[xwiki-devs] GSOC-2012 LDAP Server Implementation
by Sai Teja Jammalamadaka 06 Apr '12

06 Apr '12

Hello. My name is Sai Teja Jammalamadaka. I'm a Student of Computer Science and Engineering (B.Tech.) at Vishnu Institute of Technology, Bhimavaram, India. I am interested to participate in GSOC this year. I've taken a look at the ideas page, and I see that you are wanting to develop a LDAP server using XWiki. To be frank, I have never worked on an open source project before. I have worked on Java based web projects which I've submitted for Competitions like Oracle's ThinkQuest International Competition and IBM's The Great Mind Challenge. I created a small side scrolling java game using the JGame Java Library. So I do have a good exposure to the Java Language. But I've never channeled my time into working with a public open source project, as of yet. What I've understood from discussing on IRC is that the project is to implement an XWiki LDAP as a backend for user registration and groups for XWiki. I think that it will provide me with a good challenge and at the same time allow me to learn more about java, since I am a java programmer at heart. One of my strong points is that I can analyse pieces of java code with ease, so I feel that I will be able to get a good understanding of XWiki during the community bonding period in May before the actual coding starts. I would like your advice and feedback. I mean is there scope for you to select a project related to the LDAP compared to other projects? And since I've never worked before on open source projects, will that affect my chance of getting accepted? What else can I do to overcome that drawback? Eagerly Awaiting Your Reply, Sai Teja Jammalamadaka, Student of Computer Science and Engineering, Vishnu Institute of Technology, Bhimavaram, 534204 Andhra Pradesh INDIA Link to CV: https://docs.google.com/open?id=0B3KNacfHUN6OamJwWGFuQ0FULWlmLUxab25yejhaQQ Website: www.saiteja.in (undergoing maintenance) Email: audiodevelop(a)gmail.com IRC Nick: audiodevelop

4 8

[xwiki-devs] GSOC 2012
by savitha sundaramurthy 05 Apr '12

05 Apr '12

Dear Team XWiki I'm Savitha doing my MS in Computer science at Arizona State University. I'm really excited to contribute to open source community through XWiki GSOC 2012. I'm interested in the project *SOLR search component*. I have worked in lot of Java Projects and have a good standing in it. I've downloaded and built the Xwiki source code as per the instructions. Right now I'm going through the documentation of SOLR and trying to play around with XWiki Enterprise . Looking forward to this opportunity. -- Thanks, Savitha

4 17

[xwiki-devs] XWiki chat authentication
by Fabio Mancinelli 05 Apr '12

05 Apr '12

Hi everybody, I've added the support for XWIki authentication to the chat prototype. Now, XMPP connections are authenticated using the XWiki authentication service. To make the integration seamless, BOSH connections are authenticated using XWiki cookies. So if you connect from an XWiki page where you are already logged in, you will be automatically authenticated. Otherwise you must provide actual XWiki usernames and passwords (e.g., if you login from Pidgin) Everything works quite well, though I think that some code review is needed because accessing the AuthService from outside a real HTTP request is quite tricky and I don't know if what I did has potential issues. There are 2 places where I can perform authentication: 1) In the XWikiUserAuthorization class. This code is called by the Vysper server when it needs to authenticate a request. Here we are outside the HTTP/Servlet realm because calls to the verifyCredentials method could come also from the TCP/IP endpoint (the one used by Pidgin, for example). What I did here is to create fake HTTP/Servlet request/response to build an XWiki context and access to the AuthService. I've adapted the code from XWikiContextInitializationFilter and it looks like this: https://github.com/xwiki-contrib/xwiki-platform-chat/blob/master/xwiki-plat… (called from here: https://github.com/xwiki-contrib/xwiki-platform-chat/blob/master/xwiki-plat…) 2) In the XWikiBoshHandler class. Here I have basically overridden Vysper's Bosh process method that processes XMPP Stanzas. I intercept AUTH stanzas and I try to authenticate the request from where these stanzas come from using cookies. Here we are in the HTTP/Servlet realm and I use the Execution object to retrieve the XWiki context which is available because I associated a XWikiContextInitializationFilter to the Bosh servlet. The code is here: https://github.com/xwiki-contrib/xwiki-platform-chat/blob/master/xwiki-plat… (pretty standard) Comments are welcome. Thanks, -Fabio

1 0

[xwiki-devs] XWiki chat
by Fabio Mancinelli 05 Apr '12

05 Apr '12

Hi everybody, one of the research projects we are involved in is about realtime collaboration. One of the aspects we wanted to investigate was the integration of a chat system within XWiki. I've been working on this lately and I've built a prototype that uses an embedded XMPP server for handling all the communication. I still have to cleanup a bit the code before committing it, but I took a video of how things work. You can find it here: http://youtu.be/0Gwtpu3iVwo (it's FullHD, so make sure to change the video quality and to switch to fullscreen) There are several things we need to address (authentication is one of them), but I think we could have a functional extension pretty soon. It's 1:30am right now, so I will give you more details in a next mail :) Enjoy. Thanks, Fabio

7 16

[xwiki-devs] [ANN] XWiki Enterprise and XWiki Enterprise Manager 4.0 Milestone 2 Released
by Thomas Mortagne 05 Apr '12

05 Apr '12

The XWiki development team is proud to announce the availability of XWiki Commons, XWiki Rendering, XWiki Platform, XWiki Enterprise and XWiki Enterprise Manager 4.0 Milestone 2. This version mainly introduces: * various ways of customizing users directory and profiles * comments and annotation merge * LDAP administration UI See the full release notes at http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris… for more details. Thanks -The XWiki dev team

1 0

[xwiki-devs] [PROPOSAL] Change component role from Class to Type
by Thomas Mortagne 05 Apr '12

05 Apr '12

Hi devs, I recently modified component manager internals and changed the role used as key in the map from Class to Type so that it properly make a difference between Provider<Toto> and Provider<Titi> without the need to generate a special hint. For the one not aware of what Type is lets say it's what Class is extending. Among other things Type is also extended by ParameterizedType which is interesting here because it basically contain a Class with it's generic parameters (it also indicate if the type in included in another one but we don't care in our case ;)). To summarize: * Provider is a Class * Provider<String> is ParameterizedType and both are Type That said I would like to change the whole ComponentManager and related descriptors APIs to use Type as role instead of Class. = What it bring What it means is that it makes possible to cleanly represent a Provider in which the generic type is meaningful right in the ComponentDescriptor (right now the generic type is extract from the implementation class when the provider is registered which is pretty crappy) and simplify a lot the current implementation. But it also mean we could use this new "feature" for other components. For example right now we have things like: @Component public class DefaultStringDocumentReferenceResolver implements DocumentReferenceResolver<String> and @Component @Named("default/reference") public class DefaultReferenceDocumentReferenceResolver implements DocumentReferenceResolver<EntityReference> and injected by @Inject DocumentReferenceResolver<String> resolver; and @Inject @Named("default/reference") DocumentReferenceResolver<EntityReference> resolver; Having Type used as role means that we could have: @Inject DocumentReferenceResolver<String> resolver; and @Inject DocumentReferenceResolver<EntityReference> resolver; = What it breaks So what's the catch ? Basically it would break any code that currently programmatically register or unregister Provider since It would remove the current hack to discover the Provider parameter (assuming that the ComponentDescriptor now provide the complete role). But that's OK IMO given that Provider support is very recent and I doubt it's a common use case. We would obviously keep and deprecate all the existing APIs based on Class which are pretty easy to implement since Class extends Type. Even if removing them would not cause any issue when you build it's not binary compatible since it's not the same method signature. So WDYT ? Here is my +1 and since we are starting a new major version it sounds a good occasion so introduce such change. -- Thomas Mortagne

7 17

[xwiki-devs] GSOC XWiki Android proposal WYSIWYG Editor
by sasinda rukshan 05 Apr '12

05 Apr '12

Dear* Thomas,* I think it will take the same time with android. No difference. I am also thinking that it is easy to propose but hard to make. I will lower the set of requirements to a doable set. I will almost complete the proposal by today night. Thanks for frequently checking out. Regards, Sasinda Rukshan,

2 8

[xwiki-devs] [GSOC] A basic search implementation with SOLR
by savitha sundaramurthy 04 Apr '12

04 Apr '12

Hi Paul , Eduard and Sergiu, I went through Fabio Mancinelli's code and with the help of few inputs from there , I have implemented a basic search functionality using solr. It also fixes the issue http://jira.xwiki.org/browse/XWIKI-6226 . I have indexed the page in English, french and Spanish. I have implemented these main functionality: 1) Simple text search using solr. 2) Used *Extended Dismax Parser *to customize search relevancy using boost index. 3) Hit highlighting for English. Below is the link to the source code https://github.com/savis/xwiki-platform-search XWiki front end , HTML and Velocity code https://gist.github.com/2295648 I wanted to send a pull request but I was playing around when renaming my username and deleted the forked repository and I'm having difficulty forking it again. So I have created a new repository and shared the code above. I have taken few screen shots and have attached the document. I'm working on my application and it should be done today. Thanking You, Savitha

2 1

[xwiki-devs] [Proposal] Supported Databases Strategy
by Vincent Massol 04 Apr '12

04 Apr '12

Hi devs, In the same spirit as what we have done for Browsers (see http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for Databases since we don't have a clear strategy ATM. I propose that by "supporting" we mean: - issues created for these DBs in jira are not closed as won't fix and we make a best effort to fix them - we include these DBs in our tests (be them automated or manual) - when we create new features or modify existing features we make a best effort to verify that they work on the supported list of DBs Proposal: * HSQLDB: only support the version bundled in the standalone zip * MySQL: We officially support the last major version, i.e. 5.0+ ATM * PostgreSQL: We officially support the last major version, i.e. 9.0+ ATM * Oracle: We officially support the last major version, i.e. 11g ATM * DB2: We don't officially support it. This means that we don't test against it, we don't ensure that new feature work on it but if someone raises an issue in jira and it's easy to fix (or if someone provides a patch) then we fix it. * Derby: Same as DB2 * Microsoft SQL Server: Same as DB2 * H2: Same as DB2 for the moment (it would change if we decide to replace HSQLDB by H2 one day) * Others: Same as DB2 I also propose that in the Release notes for each version of XWiki we mention the list of DBs we have tested against and that we "support". Here's my +1 Thanks -Vincent

9 16