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

[xwiki-devs] about XWiki XEclipse Restification

by Jun Han

Dear all, First of all, I am very glad that I can participate in the GSOC project and thanks a lot for giving this great oppotunity. During the Community bonding period, I will look at the JIRA issues about XEclipse. However, I have several questions about XEclipse development: 1. Now the whole XWiki project is moving to github, where would XEclipse project be hosted, in SVN or git? I searched for XEclipse in github, and do not find a related entry. 2. what is the build method, using maven, Tycho or just in Eclipse IDE? This is related to XEclipse-150 issue In JIRA, which requires the whole XEclipse project to be built from maven and Tycho. I can already run XEclipse from Eclipse IDE. But if maven is to be used, I think I will learn some maven as well. Best regards Jun Han

14 years, 4 months

5
12
0 0

[xwiki-devs] RPC Client Issue

by Uday Ghattamaneni

Hello, I am working on developing RPC client for Xwiki3.0 and got the below exception Failed to invoke method getObject in class com.xpn.xwiki.xmlrpc.XWikiXmlRpcApiImpl: [Page 'UserSpace.UserTestPage' cannot be accessed] I got the error when I am trying to retrieve objects as mentioned in the code below. My main problem is the code is working fine with some pages, I am getting actual values for some pages, but some pages return the above error message, I checked the privileges for those two pages, they are all same for the working one and for the page which I am getting this error. . .. ... XWikiXmlRpcClient rpc = new XWikiXmlRpcClient(url); rpc.login(username, password); XWikiObjectSummary xosum = new XWikiObjectSummary(); xosum.setClassName("XWiki.XWikiRights"); xosum.setPageId(page.getId()); XWikiObject xwo = *rpc.getObject(xosum);* ...... ... .. Also, I am having problems with the RPC client functionality I tried using Apache XML-RPC Client ,Client-side Proxy for Java and also native Swizzle API for RPC , all of them provide limited functions where all the functions listed in Remote API specifications<http://confluence.atlassian.com/display/CONFDEV/Remote+API+Specification>are not supported by any of these mainly some of such functions which I tried to implement is getPagePermissions(String token, String pageId) , I got an exception *org.codehaus.swizzle.confluence.ConfluenceException: No such handler: confluence1.getPagePermissions* while I tried to use Apache XML-RPC Client , I don't have any issue with some of the functions like getPages() etc. Is there any specific way where we could make all the functions listed in the Remote API specifications<http://confluence.atlassian.com/display/CONFDEV/Remote+API+Specification>work as specified, if any one could send me a sample working program or any document related would be helpful. Thanks in advance, Uday

14 years, 4 months

2
1
0 0

[xwiki-devs] [investigation] XWiki 5 minutes Experience - Need users' help

by LD

Hi, We are launching an investigations called "XWiki 5 minutes experience" (for those who don't know, an investigation is the work before we actively work on a new development). In this case, the objective is to identify and simplify all the common things that admins and users are doing in their first five minutes of XWiki usage. The first step to this investigation is to identify all the actions they are doing and which issues they struggle with. This is where we need the help of our fellow XWiki users. Please come on this page: http://dev.xwiki.org/xwiki/bin/view/Design/XWiki5minutesExperienceMostCommo… and help us find out all the common actions (and problems with these actions) that users (actually admins and then normal users) are trying to do the first time they use XWiki. The listing of all actions and problems with be followed by studying the solutions we can implement to fix the situations reported. Some solutions might be very easy to implement and we will push then in the next release cycle, while some others will require more work and will be proposed as new work for the future release cycles. Make you voice heard as this can have a big impact on the XWiki ease of use. Ludovic

14 years, 4 months

2
1
0 0

[xwiki-devs] [Performance] Livetable calls to DB

by Vincent Massol

Hi devs, Since we can now change the log levels at runtime I was trying to set "org.hibernate.SQL" to "debug". It works well ;) I reload the AllDocs page and was surprised to see that we have 5 requests to the DB: 2011-05-13 08:53:51,524 [http://localhost:8080/xwiki/bin/view/Main/AllDocs] DEBUG o.h.SQL - select top ? distinct xwikidocum0_.XWD_WEB as col_0_0_, xwikidocum0_.XWD_NAME as col_1_0_, xwikidocum0_.XWD_DATE as col_2_0_ from xwikidoc xwikidocum0_ where (xwikidocum0_.XWD_HIDDEN<>1 or xwikidocum0_.XWD_HIDDEN is null) and 1=1 and xwikidocum0_.XWD_AUTHOR='XWiki.Admin' order by xwikidocum0_.XWD_DATE desc 2011-05-13 08:53:52,134 [http://localhost:8080/xwiki/bin/get/XWiki/LiveTableResults?outputSyntax=pla…] DEBUG o.h.SQL - select list3_.XWL_VALUE as col_0_0_ from xwikiobjects baseobject0_, xwikilists dbstringli1_ inner join xwikiproperties dbstringli1_1_ on dbstringli1_.XWL_ID=dbstringli1_1_.XWP_ID and dbstringli1_.XWL_NAME=dbstringli1_1_.XWP_NAME, xwikilistitems list3_, xwikidoc xwikidocum2_ where dbstringli1_.XWL_ID=list3_.XWL_ID and dbstringli1_.XWL_NAME=list3_.XWL_NAME and baseobject0_.XWO_CLASSNAME='XWiki.TagClass' and baseobject0_.XWO_ID=dbstringli1_.XWL_ID and dbstringli1_.XWL_NAME='tags' and xwikidocum2_.XWD_FULLNAME=baseobject0_.XWO_NAME and 1=1 2011-05-13 08:53:52,136 [http://localhost:8080/xwiki/bin/get/XWiki/LiveTableResults?outputSyntax=pla…] DEBUG o.h.SQL - select list3_.XWL_VALUE as col_0_0_ from xwikiobjects baseobject0_, xwikilists dbstringli1_ inner join xwikiproperties dbstringli1_1_ on dbstringli1_.XWL_ID=dbstringli1_1_.XWP_ID and dbstringli1_.XWL_NAME=dbstringli1_1_.XWP_NAME, xwikilistitems list3_, xwikidoc xwikidocum2_ where dbstringli1_.XWL_ID=list3_.XWL_ID and dbstringli1_.XWL_NAME=list3_.XWL_NAME and baseobject0_.XWO_CLASSNAME='XWiki.TagClass' and baseobject0_.XWO_ID=dbstringli1_.XWL_ID and dbstringli1_.XWL_NAME='tags' and xwikidocum2_.XWD_FULLNAME=baseobject0_.XWO_NAME and 1=1 2011-05-13 08:53:52,137 [http://localhost:8080/xwiki/bin/get/XWiki/LiveTableResults?outputSyntax=pla…] DEBUG o.h.SQL - select top ? distinct xwikidocum0_.XWD_WEB as col_0_0_, xwikidocum0_.XWD_NAME as col_1_0_, xwikidocum0_.XWD_NAME as col_2_0_ from xwikidoc xwikidocum0_ where (xwikidocum0_.XWD_HIDDEN<>1 or xwikidocum0_.XWD_HIDDEN is null) and 1=1 order by xwikidocum0_.XWD_NAME asc 2011-05-13 08:53:52,138 [http://localhost:8080/xwiki/bin/get/XWiki/LiveTableResults?outputSyntax=pla…] DEBUG o.h.SQL - select count(distinct xwikidocum0_.XWD_FULLNAME) as col_0_0_ from xwikidoc xwikidocum0_ where (xwikidocum0_.XWD_HIDDEN<>1 or xwikidocum0_.XWD_HIDDEN is null) and 1=1 Is that the best we can do? For example there are 2 requests that come one after another that are the same (the ones starting with "select list3"). Do you know why this is so? Couldn't we do only one such request? Thanks -Vincent

14 years, 4 months

1
0
0 0

[xwiki-devs] wysiwyg editor test errors

by 许凌志(Jamesxu)

Hi, I run all the test under xwiki-enterprise-test-wysiwyg again, still got 2 failures and 22 errors, I upload it to google doc: https://docs.google.com/document/pub?id=1kh5emfmiMlcEkNUKOfxyZSyj9rRV0EjR8y… There are a lot of "com.thoughtworks.selenium.Wait$WaitTimedOutException: The specified tree node, Blog, is not present!" errors, anyone can tell me why -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

14 years, 4 months

2
3
0 0

[xwiki-devs] Test for xwiki-enterprise

by 许凌志(Jamesxu)

Thanks for Marius to teach me how to run selenium test for wysiwyg editor when I fixed a bug. Today I tried to use "mvn clean install" under xwiki-enterprise-test-wysiwyg dir to fun all the tests, but results showed that there are 2 failures and 44 errors, the source codes are the newest one. Anyone can tell me why some of the test were failed? -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

14 years, 4 months

1
0
0 0

[xwiki-devs] [VOTE] Use SLF4J directly instead of inventing xwiki-commons-logging

by Vincent Massol

Hi devs, After progressing on the new logging implementation I've come to the conclusion that we don't need our own facade in xwiki-commons-logging. I started doing the facade and then hit the issue that we need a facade for the MDC feature too (Mapped Diagnostic Context) so that would be one more class to add. If you follow in the direction what will happen is that we will, in the end, completely copy the slf4j-api sources, just under a different name. So my proposal is that we standardize on the SLF4J API and use it directly without any facade. The rationale is: * The SLF4J API is in a single jar (slf4j-api.jar) which is a minimal JAR weighting 23KB (small) * The SLF4J API can be implemented over all existing logging systems. There are currently implementation for at least log4j, jdk14 logging, commons logging, logback and more. So it's ensured that if we wanted we would be able to write our own implementation of it for whatever log system that can come up. * That's one more thing that we don't have to maintain * It's very mature since the guy who wrote it (Ceki) has gone through the log4j experience Here's my +1 Thanks -Vincent

14 years, 4 months

6
6
0 0

[xwiki-devs] [Proposal] Switch from Commons Logging/Log4j to SLF4J/Logback

by Vincent Massol

Hi, I'd like to propose switching from Commons Logging/Log4j to SLF4J/Logback for the following reasons: * slf4j was written to solve the issues with commons logging (memory leaks under some circumstances). http://www.google.fr/search?aq=f&sourceid=chrome&ie=UTF-8&q=slf4j+vs+common… * logback is the successor of log4j and addresses the following when compared to lgog4j: http://logback.qos.ch/reasonsToSwitch.html * New stuff happens in logback and not in log4j * I'd also like to switch to logback since it has full-fledged JMX support which allows us to easily change logging configuration at runtime (changing log levels for example): http://logback.qos.ch/manual/jmxConfig.html Note that migrating a log4j.properties file is easy: http://logback.qos.ch/translator/ In addition if a user wants to stay on log4j it would be possible and easy: simply remove the logback jar and replace it with the slf4j-log4j one. WDYT? Thanks -Vincent

14 years, 4 months

6
10
0 0

[xwiki-devs] Problem with badly formed pom.xml in saaj-api-1.3.jar

by Karel Gardas

Hello, I'm trying to build xwiki enterprise from the source tree (git) I kind of succeed in having the ./xwiki-enterprise/xwiki-enterprise-web/target/xwiki-enterprise-web-3.1-SNAPSHOT.war compiled/packaged. Now I'd like to deploy it to freshly installed tomcat 7.0.12 but while tomcat starts it complains about: 2011-05-11 13:50:23,435 [Thread-2] ERROR DefaultCoreExtensionRepository - Failed to parse descriptor [jar:file:/var/tmp/xwiki/xwiki-dev-apache/apache-tomcat-7.0.12/webapps/xwiki-enterprise-web-3.1-SNAPSHOT/WEB-INF/lib/saaj-api-1.3.jar!/META-INF/maven/javax.xml.soap/saaj-api/pom.xml] org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected START_TAG or END_TAG not TEXT (position: TEXT seen ...</organization>`\r\n <d... @41:5) at org.codehaus.plexus.util.xml.pull.MXParser.nextTag(MXParser.java:1095) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2247) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4088) and the xwiki is not installed or run on it. I've unpacked the problematic saaj-api-1.3.jar file and found that the problem is probably with this line typo: 37 <organization> 38 <name>Sun Microsystems, Inc</name> 39 <url>http://www.sun.com/</url> 40 </organization>` 41 <dependencies> See "`" at the end of 40 line. Now my question is how to fix this issue properly? My guess is that this file does not come from XWiki project... Thanks! Karel

14 years, 4 months

3
12
0 0

[xwiki-devs] About jira issue-5560

by 许凌志(Jamesxu)

I am trying to fix the issue-5560, thanks for the comments of Marius on the jira issue-5560 page, it made me know the reason to cause the bug. I think out a way as folloing to sovle the problem: First, I find the js code for saving wiki pages whether using shortcuts or by clicking the buttons. According to the analysis of Marius' comments, he suggest to use editor.getSourceText(onSuccess, onFailure) to get the content from the wysiwyg editor(I find when in source mode, the editor change to an plain textarea_ "<textarea class="xPlainTextEditor" style="height: 492px;"></textarea>".) I think it is a good way to get the content dirctly from wysiwyg editor, so I searched all the js file to find the editor.getSourceText method, finnally I found it in js file under xwe, it is the js code which is generated by GWT. Cause the js file under xwe aer compressed, I did not find a good way to use this method out of GWT, so anyone can give me some help to explain the usage of method editor.getSourceText(onSuccess, onFailure), and tell me how can I use it outside GWT. -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

14 years, 4 months

2
3
0 0

[xwiki-devs] [Proposal] Switch to injecting Loggers

by Vincent Massol

Hi, I'd like to commit @Inject injection of Loggers at the same time as I do the switch to SLF4J/Logback (I have it mostly done on my machine). The idea is to move from: public MyComponent implements LogEnabled, MyComponentRole { ... } to: public MyComponent implements MyComponentRole { @Inject private Logger logger; ... } Rationale: * More consistent with how we inject dependencies * Makes it easier to move to another DI framework later on (CDI, Guice, etc) since the way to implement this with them is to use the JSR299 @Producer annotation on a class that produces Loggers. * Allows to keep the current logging behavior unchanged for backward compatibility (we juste deprecate it). WDYT? Thanks -Vincent

14 years, 4 months

6
6
0 0

[xwiki-devs] [Proposal] Introduce user management configuration in virtual mode

by Jean-Vincent Drean

Hi Devs, I'd like to introduce a new configuration property that would define at which level users should be handled in a farm. See the proposition about the new entry in xwiki.properties, it should be self-explanatory: --------------------------------8<-------------------------------- #-# [Since 2.5M1] #-# Define at which level users and groups should be handled in the farm. Available modes: #-# #-# mixed (default): #-# - user registration available in the main wiki and local wikis #-# - users from the current wiki and the main wiki will be displayed in the rights interface and user suggests #-# - user administration is present in all the wikis #-# #-# local: #-# - user registration available in the main wiki and local wikis #-# - only users from the current wiki will be displayed in the rights interface and user suggests #-# - user administration is present in all the wikis #-# #-# global: #-# - user registration available in the main wiki only, the register link in local wikis will point to the main wiki #-# - only users from the main wiki will be displayed in the rights interface and user suggests #-# - user administration is present in the main wiki only core.virtual.users=mixed -------------------------------->8-------------------------------- More details are available here: http://dev.xwiki.org/xwiki/bin/view/Design/UsersModule WDYT ? Thanks, JV.

14 years, 4 months

12
32
0 0

[xwiki-devs] Adding a "more" button to the Activity Stream

by Ludovic Dubost

Hi, Is there any reason why there is not a "more" button in the Activity Stream on the home page ? I've made a simple change to add it and it seems to work. Shouldn't we add it ? It's quite usefull to go beyond the first set of changes. Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

14 years, 4 months

5
4
0 0

[xwiki-devs] [vote] Split XE/XEM Home Page Investigation in XWIki in 5 minutes / XEM-Workspaces investigations

by Ludovic Dubost

Hi, After having a bit of thought about the XE/XEM Home Page investigations, I don't think the "home page" investigation is relevant. I'd like to propose to split this investigation into 2 investigations: 1/ "XWiki in the first 5 minutes" investigation How to improve XWiki's User Experience in the first 5 minutes with simple or more complex changes in the home page but for all initial actions that are made by a user/administrator when he starts with XWiki. The objective of this investigation would be to list small changes that could be implemented in the coming releases and list larger work that would need their own investigation. 2/ XEM/Workspaces investigation This investigation is about the next generation Multi-Wiki management including creation of Workspaces with the management of application. New features would be part of that as well as a redesign of the Wiki creation and management UI. On this matter there is already work in the Wiki 3.0 project with a prototype delivered of this work, which is a great basis for discussion, in which we need to bring some guidelines about the objective of these features as well as User Experience proposals by Cati. WDYT ? -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

14 years, 4 months

7
6
0 0

[xwiki-devs] [Proposal] [UX] [Iteration] Extension Manager

by Ecaterina Moraru (Valica)

Hi, Please take a look at the proposal http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ExtensionManagerPr… Prototype: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ExtensionManagerPr… Thanks, Caty Other links: Incubator Extension Manager Homepage: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ExtensionManager [Investigation] [UX] Extension Manager: http://xwiki.markmail.org/thread/zu4v7pfz4kbaupdq

14 years, 4 months

7
10
0 0

[xwiki-devs] Enhancing Static/Dynamic List type property by custom code/SPARQ query

by Karel Gardas

Hello, I'm currently in a need to have a dynamically created list in authoring template. The list will be generated by SPARQ query which will run against Jena's SDB storage. Sidenote: we have loosely integrated XWiki and Jena to provide some kind of semantic XWiki. This is done by custom macros w/o any special kind of syntax. This is perhaps some of later steps to do. Now, we would like to come with special forms/templates for creating pages for customer defined constructs. Since some of the constructs properties depends on another constructs properties, ideally I'd like to either enhance dynamic or static list (if static is an option here) or write another dynamic list with a support for executing custom groovy code or even SPARQ query directly. My question is: what do you think is the easiest way (whole our project is still at the prototype level) to achieve this functionality? Also where exactly shall I go inside the source code to find the required code? Thanks a lot for any hint! Karel

14 years, 4 months

1
0
0 0

[xwiki-devs] [VOTE] Remove distribution (war) from xwiki-platform

by Vincent Massol

Hi devs, We've decided with the new reorg following the move to github that xwiki-platform was a collection of libraries/resources that work together (and released together) that can be used by top level projects (XE for example) to build a running application. We've also implicitly decided that we didn't have a notion of "core" and that all libs/resources were at the same level (all in xwiki-platform-core/). As a consequence it doesn't really make sense for xwiki-platform to release a WAR since we wouldn't know what to put in it (since there's no notion of core). Right now it's a bit a mess with no logic (for example the watchlist is not in it but other modules are). I'm thus proposing to transform xwiki-platform-web in 1 or 2 modules instead (resources and templates) that generate a zip/jar that only contains resources, and that it's up to the top level projects (like XE) to build their own distribution by pulling in whatever libs/resources they want from xwiki-platform. Note that this solves an issue we currently have with Maven. If a top level project depends on the platform web but also on other modules that transitively depend on artifacts bundled in the platform war then we can get duplicate jars in the resulting war since maven sees the war artifact as a blob and doesn't know about the dependencies that were included in it. Here's my +1 Thanks -Vincent

14 years, 4 months

5
5
0 0

[xwiki-devs] XWiki Enterprise 3.1 Milestone 1 Released.

by Caleb James DeLisle

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The XWiki development team is proud to announce the release of XWiki Enterprise 3.1 Milestone 1. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This is the first milestone in the 3.1 development cycle, you can review the changes made and bugs fixed since 3.0 by going to: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris… Thanks - -The XWiki development team If you would like to download the new release now, you can using these links: - ---- XWiki Enterprise for Servers ---- xwiki-enterprise-web-3.1-milestone-1.war SHA1: 599b25607b6023d4c744e096147cf58e67e708d1 http://forge.ow2.org/project/download.php?group_id=170&file_id=16638 xwiki-enterprise-wiki-3.1-milestone-1.xar SHA1: d947bb06cb94d53d56b4777854e7e1d428f1a2b1 http://forge.ow2.org/project/download.php?group_id=170&file_id=16640 - ---- XWiki Enterprise Standalone ---- xwiki-enterprise-installer-windows-3.1-milestone-1.exe SHA1: 537fceefd6c31005f521a6c68b8410e18fcb3761 http://forge.ow2.org/project/download.php?group_id=170&file_id=16636 xwiki-enterprise-jetty-hsqldb-3.1-milestone-1.zip SHA1: 84f5714cda15f548145f168e6e4e407fc0841d4e http://forge.ow2.org/project/download.php?group_id=170&file_id=16637 xwiki-enterprise-installer-generic-3.1-milestone-1-standard.jar SHA1: 444809f9b172b156dfda970c66e2c3ce5ac4abad http://forge.ow2.org/project/download.php?group_id=170&file_id=16639 - ---- XWiki Manager for Servers ---- xwiki-manager-web-3.1-milestone-1.war SHA1: d9783635b1453ea53edd43f6d7bb8b72a58a03ee http://forge.ow2.org/project/download.php?group_id=170&file_id=16641 xwiki-manager-wiki-administrator-3.1-milestone-1.xar SHA1: 790ae398b9f21a3013bb21956692df4b7e543ed4 http://forge.ow2.org/project/download.php?group_id=170&file_id=16642 - ---- XWiki Manager Standalone ---- xwiki-manager-jetty-mysql-3.1-milestone-1.zip SHA1: 2fb9b0417a54dfaaa6be3af1221c2890ec3a0ad1 http://forge.ow2.org/project/download.php?group_id=170&file_id=16643 - ---- XWiki Manager Extension for XWiki Enterprise Installations ---- xwiki-manager-application-xem-3.1-milestone-1.xar SHA1: 4c3cefce42cc99dd8e0000f54e3adc3eb5b183f5 http://forge.ow2.org/project/download.php?group_id=170&file_id=16644 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBAgAGBQJNwC0qAAoJECYAmptlsgnWEIEP/R99nxJ3M1hVGutXGt96PnQs oDWxWiCfxpHO80249FCcehvB1iG12gRe8ZN4Wzg002ZSHoMLyJfS3EIMOqXYoo7R cFbOK4zEXJCFQvKGCVqpF/J8OF/E3gg0PGwmOOzjtApPcyQxw2RWFw5DaZ4rcFRp zIC6RjZfU03qSpKJhXamHZ5B1B/iZb177s1YQ7R8OQ+oUYugYn2VQSGfVA9+DpkY 1Te0bwtvzz6SyxbAQaYLy0OoAzYcvQnl5+USXt+HExhiurnGLJMZ6UETAb+HglB1 KvjEra5LQYQGO3gF7IZjAl85xHoGGUCtdNzO1CEQLxYwKELq9ItZNlisRuIrV6LN Fmx9tcVJW2LCorx4J8ShR5pbSFZADcMpLH9r1saghRZCP7ZwsQ88b9V2H699veRw NjM1hULEW2oSOX159k3H/JehTJ1kJCJaJIB07A2P6w+iMQEb5iPVImXeLzDpr3QX 0hE+Hz4Ih3ezju0fm5yTNrgZWdm/1mjqEM+QOVoEWt2Uto5PTqVMZPJz9B/H56z9 whGSbbmbVea6HbLcXPYsM2YVxOY0BcSrbf+CW2zbjMw/YsExWxIuB/F8el1tA2Kr BrmWXGr7hC0/wiDlJJby3wNsV9aWWkiba0CZGU5z02fI55uUOPO19uhMKLR0KhFM A5bXf65wAQZ7yEBkJxq2 =/xXw -----END PGP SIGNATURE-----

14 years, 4 months

1
0
0 0

Re: [xwiki-devs] [xwiki-users] XWiki.war + JBoss AS6 + MySQL

by Sergiu Dumitriu

On 05/03/2011 09:40 AM, Vincent Massol wrote: > > On May 3, 2011, at 9:39 AM, Vincent Massol wrote: > >> Hi Andy, >> >> On Apr 27, 2011, at 1:25 PM, andyp wrote: >> >>> Hi all, >>> >>> I'm trying to install the XWiki war file on a Ubuntu virtual machine (KVM) >>> but as yet with no success. I've installed and configured java, jboss and >>> mysql using all the information I could find from your website: >> >> [snip] >> >>> 01:36:10,087 WARN [ClassLoaderManager] Unexpected error during load >>> of:org.apache.jackrabbit.core.query.lucene.WildcardQuery$WildcardQueryWeight: >>> java.lang.IncompatibleClassChangeError: Implementing class >> >> [snip] >> >>> 01:36:10,936 WARN [ClassLoaderManager] Unexpected error during load >>> of:org.apache.jackrabbit.core.query.lucene.MatchAllWeight: >>> java.lang.IncompatibleClassChangeError: Implementing class >> >> [snip] >> >> As you can see in the error above the problem is an incompatible version. JBoss uses Jackrabbit in a given version and XWiki users another version of Jackrabbit. >> >> It's the role of the appserver to isolate classloader so that a webapp can use whatever version it wants in WEB-INF/lib. >> >> You need to configure JBoss to provide this isolation. You need to check Jboss's doc for that. > > I just googled it quickly and found > http://community.jboss.org/wiki/ClassLoadingConfiguration Should we create a jboss-web.xml configuration file as well? We recently added a sun-web.xml file to fix another classloading problem, this time for GlassFish. > Hope it helps, > -Vincent > >> >> Alternatively you could remove xwiki'ds jackrabbit version from WEB-INF/lib (make sure the version used by jboss is greater than the one used by xwiki). >> >> Thanks >> -Vincent >> >>> Can anyone see what I'm doing wrong? All the information on the web seems a >>> little old – I'm using JBoss 6. I would be grateful if anyone could help >>> shed any light on this issue. >>> >>> Cheers, >>> Andy -- Sergiu Dumitriu http://purl.org/net/sergiu/

14 years, 4 months

2
1
0 0

[xwiki-devs] XWiki 3 .XAR decompression bug

by Alain Renaud

Hi, Not sure I'm using the right channel but here is the deal. We were looking for a Tomcat-based Wiki and XWiki seemed to fit the bill (and in addition work with PostgreSQL that we also use). Unfortunately, this product, although I'm sure it's serious and works under certain strict contingencies, seems to have a very blocking bug under some other circumstances, so we will have to dig a bit more for something else, at least until your XWiki is more sturdy. But at least, having put a couple hours on it without results, we will report on our test: we installed version 3.1 (and then did the same test with version 3.0 with the same outcome). We installed the .war on Tomcat as documented in your web pages and configured it accordingly. In the end, that seemed to work in the sense that when we asked for the default page in a browser, we got an answer and also we saw that 41 tables were created in the database. As suggested, we then downloaded the official .xar file (we tried version 3.0 and then version 2.7 also) and uploaded it in the Import page. Then when we clicked on the link of the filename at the lower-left, the upper-right displayed: Archive xwiki-enterprise-wiki-3.0.xarDescription My packageVersion 1.0.0Author XWikiLicence LGPLselect none, all as expected, BUT THE GREY INNER FRAME THAT SHOULD DISPLAY A LIST OF CONTENT IN THE XAR IS... EMPTY, YES TOTALLY EMPTY. So clicking on the Import button will yield a message about selecting something but there's nothing to select. We tested the same in Firefox, IE and Chrome. There are no error message in HTML or JavaScript, nor anything special in any of the Tomcat logs or PostgreSQL log. The .xar files are valid in the sense that they can be fully decompressed by WinZip/WinRAR. Our hypothesis is that some XWiki code (probably the compression library) silently traps an exception and is so far incompatible with either Tomcat version 7 or Java version 6 or Windows 7 or Intel 64-bit. Sorry for you and good luck. A. R.

14 years, 4 months

2
2
0 0

[xwiki-devs] [Discussion] What title behavior do we want in the future?

by Vincent Massol

Hi devs, This is a thread to discuss what kind of title behavior we want in the future. I've listed some topics I consider open below. Could you give me your opinion about them? 1) Should we force titles to be mandatory by default 2) Should we merge page names and titles in the UI (ie only expose titles and compute page names based on it) 3) Do we want titles to be generated from content if the title is empty or not. If 1) is agreed then there'll always be a title set so this is probably not needed 4) Should we allow wiki syntax in the title field and make that field a textarea rather than a single line string (to allow scripts to generate titles, this is useful for applications for example). Note that currently the title field can only contain velocity and no wiki syntax AFAIK. Any other topic to discuss related to titles? Thanks -Vincent

14 years, 4 months

4
3
0 0

[xwiki-devs] About "Auto Completion in Content Editors" GSoC Project

by 许凌志(Jamesxu)

Hi, First of all, I am very excited that Xwiki Community accepted my proposal "Auto Completion in Content Editors", and thanks for everyone that helped me a lot during the application time. Second, I will talk about something I have done these days, and then talk about the problems that confuse me. 1. I have setted up an Linux(Ubuntu 11.04)+Git+maven(2.2.1) environment for developing Xwiki projects. Everything goes well in this step. 2. And I have downloaded the source code of xwiki-enterprise from github, build it up, and got xwiki-enterprise-jetty-hsqldb-3.1-SNAPSHOT.zip file under distribution folder, unzip it and run the start_xwiki.sh, and visit http://localhost:8080, it is successful to see the xwiki page. 3. I have searched some issues related to WYSIWYG editors, and I finnally chose two for optionals:http://jira.xwiki.org/jira/browse/XWIKI-4471 and http://jira.xwiki.org/jira/browse/XWIKI-4179. Problems: 1.Building XE takes a long time about more than half an hour, if I am working on XE, for example fix some bugs of it, and want to compile and run it as soon as possible to see the results, have an hour would be a very long time for waiting each time. I know maybe the second time for building XE will be much faster than the first time, but it still take some time to build the whole codes, it must slow down the efficiency to debug my code. So anyone can tell me how should I do, or is there any best prictices for debuging and compling the code based on XE. 2. About the selected two issues, one is to add a small new feature, and the other one is to fix a bug, I want to ask for some advices about which issue would be ok, and could you give me some more informations for these two issues. -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

14 years, 4 months

2
3
0 0

[xwiki-devs] Android Client for XWiki

by Chamika Weerasinghe

Hi, First of all I would like to thank XWiki for selecting me to the Google Android Client for XWiki project through the GSOC. As a beginning I'm currently studying on building XWiki public repositories like xwiki-enterprise, xwiki-manager, xwiki-platform etc. so that I can get the domain knowledge. I hope to fix some jira issues in these repositories. Can anybody tell me some other way to get proper understanding in XWiki appropriate to this Android project? Thank you, Chamika Weerasinghe

14 years, 4 months

2
2
0 0

[xwiki-devs] Comments on github

by Vincent Massol

Hi devs, I have a small issues with the comments on github: they are invisible to the xwiki dev team right now. We used to comment on commit mail diffs which made the comments available to everyone (including non developers) following the notifications/devs lists. Right now we have started using github for commenting but this means I don't see anymore when stuff get commented. I have to go to github specifically and look out for comments. Is there a better way combining our lists + github to keep the open collaboration aspect of reviews? Thanks -Vincent

14 years, 4 months

3
5
0 0

[xwiki-devs] YUI compressor 2.4.6

by Vincent Massol

fyi: http://feedly.com/k/fZWfhP Exceprt from the release notes: Highlights include: • Fixed numerous bugs that break the compressor and/or the resulting minified files. • Added documentation on what exactly the minifier does and also which CSS hacks it tolerates. • There’s a JavaScript port of CSS min in case it’s more suitable for your build process.Here’s also a test web UI that uses the JavaScript port, where you can experiment with the minifier. • A significant number of new tests added (but you can add even more). • Safe handling of some CSS features that are getting more adoption such as media queries and CSS3 transforms. We could upgrade maybe. Thanks -Vincent

14 years, 4 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs