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

[xwiki-devs] [VOTE] Marius Florea as a XWiki core commiter

by Jerome Velociter

Hello, I would like to propose voting Marius Florea as a core committer. Marius has already sent a lot of patches (see http://tinyurl.com/67wa9a, in particular the patches on XE statistics, JodaTime plugin, and the new RSS mechanism in the feed plugin). Marius patches are clean, well documented and comes with tests. Marius is now working for a few months already on the rewrite of the WYSIWYG editor in GWT, and at some point soon he will need to start integrating his work with the platform. Thus, I propose Marius applies his own patches from now on. Here is my +1 for this. Note: For full disclosure, Marius is working for XWiki SAS, the company behind the creation of XWiki. FWIW, out of the 21 committers (http://dev.xwiki.org/xwiki/bin/view/Community/HallOfFame), 10 are working for XWiki SAS. Note that we're running XWiki as a meritocratic project (trying to follow the Apache rules as much as possible) and thus anyone can become a committer (see http://dev.xwiki.org/xwiki/bin/view/Community/Committership). The more the merrier! Regards, Jerome.

17 years, 1 month

10
10
0 0

[xwiki-devs] Urgent Regarding Xwiki building

by Deepak24 S

Dear, we Downloaded your xwiki from www.xwiki.org, its an very nice free source code software. But we need to do some addition ,details required as folows: 1.I have got nothing about about the java files.which i need to update specialy admin java files. 2.Our specific requirement is to bypass the user login and password ,as that user already done at our application main page. Please send back some solution and if possible id or mail contact of person to whom i can discuss my problem in detail. Thanks and regards, Deepak Sharma Assistant Software Engineer-T Tata Consultancy Services Cell:- 9911502444 Mailto: deepak24.s(a)tcs.com Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Outsourcing ____________________________________________ =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

17 years, 1 month

2
1
0 0

[xwiki-devs] [Discussion] New WYSIWYG GUI Propositions

by Guillaume Lerouge

Hi fellow XWikiers, I've been spending some time thinking about the new User Interface we might want to build for the new WYSIWYG editor. I've posted the ideas I gathered so far on this page : http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorInterface . I'd be glad to get some feedback either on the list or in comments right on the page in order to see whether any given approach clinches or clashes with your own conceptions of a great rich text editor. Please bear in mind that I'll probably be adding content to the page on a regular basis in days to come in order to account for the feedback received - if any. In case of an absence of feedback, well, I guess we'll be able to assume safely that the new WYSIWYG editor doesn't matter that much in the end and stop its development altogether ;-) Looking forward hearing from you guys (and girls), Guillaume

17 years, 1 month

9
14
0 0

[xwiki-devs] XWIKI - Export PDF Fails

by Prathap Pandian

Hi, While exporting the page to PDF format i got this error. And not able to export the page. Kindly any one tell me what's this error. And how to solve this problem. Error number 11015 in 11: Exception while exporting Wrapped Exception: Error number 12003 in 12: XSL Transformation Failed Wrapped Exception: Premature end of file. com.xpn.xwiki.XWikiException: Error number 11015 in 11: Exception while exporting Wrapped Exception: Error number 12003 in 12: XSL Transformation Failed Wrapped Exception: Premature end of file. at com.xpn.xwiki.web.ExportAction.render(ExportAction.java:64) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:189) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) -- Prathap

17 years, 1 month

2
1
0 0

[xwiki-devs] About Space / Page names.

by Asiri Rathnayake

Hi Devs, Do we have a specific format for a space name or a page name ? A regex may be .... :P Thanks. - Asiri

17 years, 1 month

4
6
0 0

[xwiki-devs] [GSoC]question about the office document "view as html"

by Wang Ning

Hi, Though office converter can convert office documents to many format, I think only some conversion is useful: 1). convert office document to html (view attachment as html) 2). export a page to office document(MS Word, OpenOffice odt), as influence do. 3). export a page to pdf, but this have been done with fop. I don't think xwiki should have two way to export pdf. 4). convert office document to html then parse to xwiki syntax. (this is the most important goal, but I still be learn how to) I can product the low level interface for multi format conversion, but now I only focus on the 1), 4), 2) fuctions. Actually, I'm working on the "view as html". My step: 1. add a method in XWiki Util or Office converter plugin(Which is better) "boolean canViewAsHTML(OfficeDocumenType)" to check if the attachment can view as a html. 2. add a action "viewashtml" to xwiki action map. to handle the "view as html" request 3. modify the attachmentinline.vm. use "$doc.getAttachmentURL("${attach.filename}", "viewashtml", "xredirect=${redirect}")" as "view as html" link. WDYT? Thanks. Wang Ning

17 years, 1 month

1
0
0 0

[xwiki-devs] [GSoC]Use the office converter application

by Wang Ning

Hi, I have finished the office converter application for xwiki. How to use the application: 1. install the office converter plugin reference: http://dev.xwiki.org/xwiki/bin/view/Design/OfficeConverter#HQuickStart 2. install offcie converter application XE <=1.4.1 http://dev.xwiki.org/xwiki/bin/download/Design/OfficeConverter/Import.xar XE 1.5 use: http://dev.xwiki.org/xwiki/bin/download/Design/OfficeConverter/Import%2Dfor… After installation, visit http://.../bin/view/Import/ Select the file in your local file system, input the target page space and page name, click the convert button. Done. It's more easy then the usage of raw office converter plugin. Thanks, Wang Ning

17 years, 1 month

1
0
0 0

[xwiki-devs] [GSOC]Velocity syntax support for XE

by malaka ekanayake

Hi all, Now I've completed (committed to the sandbox) the syntax colouring for most of the Velocity syntax. The colours used are not yet finalized. We are yet to develop colour scheme for both Xiki and Velocity syntax. Your suggestions for appropriate colours are welcome. I've identified following tasks which are to be completed. 1) support for user defined macros in Velocity 2) Enhance the Xwiki content assistance. 3) Implement the Velocity content assistance 4) Implement the Xwiki and Velocity error handling AFAIS, for the 4th task we have to integrate Xwiki and Velocity parsers to get the error messages and to find the excat location of the error. Your comments are welcom on this. I would like to suggest following changes to the existing package sturcture of xeclipse plugin. Now this editor plugin supports different languages, I think refactoring of the package stucture is needed. For the moment, I've included Velocity related classes under the following package name. org.xwiki.eclipse.ui.editors.velocity.* And also several other classes has been modified provide syntax coloring for Velocity. So my suggetion is to put all the Xwiki related classes under the following package name. org.xwiki.eclipse.ui.editors.xwiki.* Then the common classes can be put in the org.org.xwiki.eclipse.ui.editors and org.xwiki.eclipse.ui.editors.util packages. WDYT? Thanks Malaka

17 years, 1 month

3
3
0 0

Re: [xwiki-devs] [xwiki-notifications] r394 - in xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/officeconverter: . filter

by Vincent Massol

On Jul 28, 2008, at 5:12 PM, daning (SVN) wrote: > Author: daning > Date: 2008-07-28 17:12:52 +0200 (Mon, 28 Jul 2008) > New Revision: 394 > > Modified: > xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/DefaultOfficeConverter.java > xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/OfficeServerConnection.java > xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/Util.java > xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/filter/Filter.java > Log: > XSANDBOX-32: > > Modified: xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/ > plugin/officeconverter/DefaultOfficeConverter.java > =================================================================== > --- xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/DefaultOfficeConverter.java 2008-07-28 12:23:27 UTC > (rev 393) > +++ xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/DefaultOfficeConverter.java 2008-07-28 15:12:52 UTC > (rev 394) > @@ -135,6 +135,7 @@ > document = new JDomSerializer(props, true).createJDom(node); > > Element root = document.getRootElement(); > + > // TODO more filter to be added > > XHTMLPinLiFilter pinLiFilter = new XHTMLPinLiFilter(); > > Modified: xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/ > plugin/officeconverter/OfficeServerConnection.java > =================================================================== > --- xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/OfficeServerConnection.java 2008-07-28 12:23:27 UTC > (rev 393) > +++ xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/OfficeServerConnection.java 2008-07-28 15:12:52 UTC > (rev 394) > @@ -7,6 +7,11 @@ > > public class OfficeServerConnection > { > + /** > + * This component's role, used when code needs to look it up. > + */ > + String ROLE = OfficeServerConnection.class.getName(); > + The ROLE should be in the interface or maybe you're planning to transform this into an interface? Thanks -Vincent > private static final OfficeServerConnection instance = new > OfficeServerConnection(); > > public static final String DEFAULT_HOST = "localhost"; > > Modified: xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/ > plugin/officeconverter/Util.java > =================================================================== > --- xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/Util.java 2008-07-28 12:23:27 UTC (rev 393) > +++ xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/Util.java 2008-07-28 15:12:52 UTC (rev 394) > @@ -97,5 +97,8 @@ > } > } > } > - > + > + public static boolean canViewAsHtml(OfficeDocumentType > documentType) { > + return false; > + } > } > > Modified: xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/ > plugin/officeconverter/filter/Filter.java > =================================================================== > --- xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/filter/Filter.java 2008-07-28 12:23:27 UTC (rev 393) > +++ xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/ > officeconverter/filter/Filter.java 2008-07-28 15:12:52 UTC (rev 394) > @@ -4,6 +4,10 @@ > > public interface Filter > { > + /** > + * This component's role, used when code needs to look it up. > + */ > + String ROLE = Filter.class.getName(); > void doFilter(Element element); > String getName(); > void setName(String filterName);

17 years, 1 month

2
1
0 0

[xwiki-devs] [VOTE] SVN reorganization proposal

by Vincent Massol

Hi, We need to better organize our SVN repos. Some current needs/issues: * Curriki needs its own svn location outside of main xwiki devs * Chrono is currently outside of the main svn repo. Same for Sandbox. * We'd like to offer a forge for xwiki -related project (for example for the xlet project) We had a discussion before and I think we agreed to have a single SVN repo vs one for each project. See http://tinyurl.com/69c4bx for more details. Hence I propose the following new structure: https://svn.xwiki.org/svnroot/xwiki |_ platform/ |_ curriki/ |_ sandbox/ |_ enterprise/ |_ enterprise-manager/ |_ watch/ |_ workspaces/ |_ xeclipse/ |_ xlet/ (or whatever name we choose for it) The idea is: * Top level directories are projects. * As such they get their wikis on xwiki.org (<project>.xwiki.org), they are identified by the Committers group in that wiki. * They also get a mailing list (they can use an existing mailing list though) Thus we remove the notion of extensions and products and we replace it with the notion of projects which can be anything. This is more scalable and in line with a forge idea. If we're ok I'll work with Raff to set this up and to modify all web pages which have the SVN URLs (like ohloh, freshmeat, etc). Developers will need to perform a new co. Here' s my +1 Thanks -Vincent

17 years, 1 month

7
10
0 0

[xwiki-devs] [Proposal/New Rendering] HTML in Velocity macro

by Vincent Massol

Hi, Contrary to what is described here http://dev.xwiki.org/xwiki/bin/view/Design/NewRenderingArchitecture#HA6Intr… I'd like to propose instead to use a nested {xhtml} macro whenever you want your velocity script to generate XHTML. So the example would be transformed into: {velocity}{xhtml} <div> <h1>Hello $customer.Name!</h1> <table> #foreach( $mud in $mudsOnSpecial ) #if ( $customer.hasPurchased($mud) ) <tr> <td> * [link>$flogger.getPromo( $mud )] </td> </tr> #end #end </table> </div> {/xhtml}{/velocity} It seems to me much more logical to do it this way, especially since we allow nested macros. Note1: that it'll work because the velocity macro supports wiki syntax and {xhtml} is wiki syntax. Note2: This is not equivalent to writing {xhtml}{velocity}... since the xhtml macro only accepts valid XHTML. This is valid though: {xhtml} <div> <a href="...">{somemacro/}</a> </div> {/xhtml} WDYT? Is it ok with you? Thanks -Vincent

17 years, 1 month

4
3
0 0

[xwiki-devs] [Proposal] XWiki Watch publicly available on xwiki.org

by Anca Paula Luca

Hi devs, As it has been already mentioned a couple of times, I strongly believe that XWiki Watch should be accessible in a sandbox on xwiki.org, for everyone to try it out and explore its features and for us to get an open real-life test of it. There is a document dedicated to the issues that might prevent this at http://watch.xwiki.org/xwiki/bin/view/Development/XWatchOnXWikiOrg , please fill it in with any opinions you have! Here's my +1 for having an installation of XWatch publicly available on xwiki.org, WDYT? Happy coding, Anca P.S: Sorry for the duplicate email, I forgot the subject in the previous one and I thought it's important enough to deserve duplicating.

17 years, 1 month

4
23
0 0

[xwiki-devs] [ANN] XWiki Enterprise Manager 1.3 Release Candidate 1 released

by Thomas Mortagne

The XWiki development team is pleased to announce the release of XWiki Enterprise Manager 1.3 Release Candidate 1. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download First release candidate for the 1.3 version. The main changes are: * Upgrade XE/Core dependency from 1.4.1 to 1.5 * Improve wiki descriptor editor For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM13RC1 Thanks -The XWiki dev team

17 years, 1 month

1
0
0 0

[xwiki-devs] [GSoC]how to implement a class as a plexus component

by Wang Ning

Hi, I want to change some class to plexus component. I see some code of xwiki. I have 2 questions. 1. Only adding "String ROLE = **.class.getName()" in a class, can change a normal class to plexus component? Should I write some plexus config file in somewhere? 2. How to get a plexus components? Use a componentManagement.getComponent(ROLE) can get a component, but I don't know how to get the componentManagement. Forget me if those two question is too stupid. Thanks. Wang Ning

17 years, 1 month

2
1
0 0

[xwiki-devs] [VOTE] XWiki 2.0 formal syntax definition - Bold & Link

by Vincent Massol

Hi, I think I've finished enough in the new rendering implementation so that we should now start defining formally the new XWiki 2.0 syntax. However before we do that let me highlight one important limitation due to the underlying frameworks we use (wikimodel in this case): Wikimodel is using a JavaCC grammar and thus is not able to do look ahead and backtracking (ANTLR can do it, but even if JavaCC could do it it would still be too expensive to use). This means that wikimodel is not able to support the following example: This is a * that is not a bold. When wikimodel sees one of XWiki's special char (like the star for bold) it'll put everything that comes after as bold, till it find another star or till the end of the document. There are 2 solutions out of this: * We don't allow users to enter non-escaped star for example. * Or better we change our syntax for bold so that it uses a 2 chars. For example **. It's less likely people will use 2 stars in their content and this is the reason most wikis use 2 chars. This is also consistent with our other syntaxes for underline, strikethrough, italics, etc. Note that this is also inline with the creole syntax: http://www.wikicreole.org/ The same problem exists for links. We're currently using single brackets which means people cannot use brackets in their text. I'd also propose to use double brackets for links as in: [[This is a link]]. Again this is consistent with the rest. There are several other topics to address but let's start with Bold and Link syntaxes right now. Once we agree on them, I'll do the following: * Create a XWiki 2.0 syntax page on xwiki.org and put Bold and Linkj syntax there * Send change requests to wikimodel for the changes we decide * Adapt the new rendering module code * Send other emails for remaining syntax elements To summarize the vote here is about: * Using ** for bold in the new XWiki 2.0 syntax * Using [[ for links in the new XWiki 2.0 syntax Here's my +1 to both. Thanks -Vincent

17 years, 1 month

7
9
0 0

[xwiki-devs] [XEM][VOTE] Release XEM 1.3RC1

by Thomas Mortagne

Hi all, As XE 1.5 just been released I would like to follow with XEM 1.3. It's mainly XE dependency upgrade fro 1.4.1 to 1.5 and wiki descriptor editor improvements. You can see complete release note at http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM13RC1 Here is my +1 -- Thomas Mortagne

17 years, 1 month

5
5
0 0

[xwiki-devs] unable to compile XWiki Workspace 1.1 - milestone 1

by neel seer

I am building XWiki Workspace from the source. i made a change to XWiki core and built it fine. I see it being installed to the local repository as well. However, when i try to build the Workspace web module I always see the old xwiki-core-1.4.1.jar being picked up from elsewhere instead of pikcing the one from my local repository. Can someone tell me what I am doing wrong. Are there any dependency issues? Your help is greatly appreciated. /ns

17 years, 1 month

2
1
0 0

[xwiki-devs] [GSOC][WEBDAV] Status - Refactoring Completed.

by Asiri Rathnayake

Hi Ludovic and all, I have completed refactoring xwiki-webdav code base. *Benefits:* 1. Code is easy to read & understand (still missing javadoc though). 2. Increased modularity. 3. Very easy to extend (Add new views, types etc). *Features :* 1. True parent-child navigations is possible (wasn't possible before). 2. Add / Remove child pages into / from pages. 3. Edit Wiki content of pages. 4. Delete child pages / Attachments. 5. (Adding attachments is one step ahead - need 1.6 core) 6. Add / Remove pages into / from spaces. 7. Add / Remove spaces - partially done. Ludovic, please have a look at the new code and let me know what you think :) *Missing :* 1. Copy / Move operations. 2. Locking & Versionning. *Questions / Concerns :* 1. What should be the content-length of collection resources (currrently 0) 2. Is it meaning full to have GET / HEAD methods on collection resources (as this would mean downloading a directory hierarchy, which is not possible AFAIK) 3. LIBRARY_VIEW : I didn't implement this view (yet) because i don't understand how we can upload a directory hierarchy into a server as mentioned on the design<http://dev.xwiki.org/xwiki/bin/view/Design/WebDAVService>. Can someone please explain what exactly 'uploading a directory' means ? 4. Deleting collection resources seems to present few complications : i) Some clients (nautilus) uses a recursive delete procedure. Some clients (dav explorer) does not allow deleting collection resources. ii) If a page is deleted recursively, all child pages are deleted before the parent is removed :( 5. attachments / orphans views, should we allow pages to be added / deleted on this views ? *What's Next :* I will start to write test cases for xwiki-webdav using jakarta slide<http://jakarta.apache.org/slide/>for next week to come (but i don't have much of an idea what it would be like). It would be nice to have some comments on the current code base and possibly answers to above questions :) Thanks. - Asiri

17 years, 1 month

2
2
0 0

[xwiki-devs] Fwd: [GSOC][WEBDAV] Status (Integration Testing)

by Asiri Rathnayake

---------- Forwarded message ---------- From: Asiri Rathnayake <asiri.rathnayake(a)gmail.com> Date: Sat, Jul 26, 2008 at 11:48 AM Subject: Re: [GSOC][WEBDAV] Status (Integration Testing) To: Ludovic Dubost <ludovic(a)xwiki.org> Hi Ludovic, On Sat, Jul 26, 2008 at 4:10 AM, Ludovic Dubost <ludovic(a)xwiki.org> wrote: > > Asiri, > > The integration tests are really looking good. This is great to have tests > like that to see the webdav server working. > Yes I think you should replicate them on the different view. > > The more tricky part is going to replicate the behavior of clients that are > doing some complex things, like trying to save temporary files > (.wiki.txt.swp like vi does) > Yes, this is going to be challenging. But if the editor is aware of the fact that it is handling a dav file, it might resolve to some other technique to store swap files, but we cannot depend on that, true. > > Make sure you verify that your tests are really testing by introducing an > error in your webdav code. > Well, i encountered few bugs in the code while writing the tests and fixed them along .. :P > > Once you have decent testing, the most important will be to have the > Windows and Mac webdav client behave properly especially with standard > applications (Notepad, MS Word on Windows, TextEdit, OpenOffice on Mac) Yeah, as i mentioned in one of my previous mails, some editors (ex: notepad) doesn't even know what is DAV. I mean it complains that it is an invalid protocol or something, there is not a single request listed on the server. I doubt whether we can fix such issues. Anyway, i will look into it bit thoroughly. Thanks. - Asiri > > > Ludovic > > > Asiri Rathnayake wrote: > >> Hi Ludovic, >> >> I have setup the pom file to allow integration tests. Also, plain old >> junit tests can be added if required (**/*TTest.java : unit-tests, >> **/*ITest.java : integration-tests). Also, I have added integration tests >> for basic operations on spaces and pages. I was thinking if i should >> replicate these tests across different views ? WDYT ? >> >> To run the tests, simply execute `mvn clean integration-test` >> >> Thanks. >> >> - Asiri >> > > > -- > Ludovic Dubost > Blog: http://blog.ludovic.org/ > XWiki: http://www.xwiki.com > Skype: ldubost GTalk: ldubost > >

17 years, 1 month

1
0
0 0

[xwiki-devs] [GSOC][WEBDAV] Status (Integration Testing)

by Asiri Rathnayake

Hi Ludovic, I have setup the pom file to allow integration tests. Also, plain old junit tests can be added if required (**/*TTest.java : unit-tests, **/*ITest.java : integration-tests). Also, I have added integration tests for basic operations on spaces and pages. I was thinking if i should replicate these tests across different views ? WDYT ? To run the tests, simply execute `mvn clean integration-test` Thanks. - Asiri

17 years, 1 month

2
1
0 0

[xwiki-devs] [Proposal] new "/plain/" and "/feed/" actions mapped to plain.vm template

by Jerome Velociter

Hello devs, Yesterday I've applied Marius's XWIKI-2149 patch "Extend the FeedPlugin to allow the creation of RSS/Atom feeds from any source". New RSS urls with this revamped mechanism are of the type "/xwiki/bin/view/Space/DocRss?xpage=plain" (while the current way is /xwiki/bin/view/Space/DocRss?xpage=rdf"). I propose we add an action that return the "plain.vm" velocity template as entry point to render the document, and map a new "/feed/" action to it. This would allow us for example to have a blog feed URL like this : "/xwiki/bin/feed/Main/BlogRss" when the blog will actually use this new mechanism for its feed. I would also like to map an action with a more generic name to it, like "/plain/". "xpage=plain" is for example used when we create pseudo-REST web services (for example, all the AJAX/gridview features in XE do use URLs of that type). I believe it would be nice to have in the service request URL only parameters linked to the actual service. Thus I would propose we have something like "/xwiki/bin/plain/XWiki/MyService?myparam1=myvalue&..." I am +1 for doing this, WDYT ? Now, I have a working version of this on my computer, but I'm not very happy how it is done. basically, I followed the way the "attach" action works : I added a PlainAction in com.xpn.xwiki.web that just returns "plain" on render, and added the following action in struts-config action mappings : <action path="/feed/" type="com.xpn.xwiki.web.PlainAction" name="feed" scope="request"> <forward name="feed" path="/templates/plain.vm"/> </action> Is there a nicer way of doing this with struts ? (At first, I tried to use "global-forwards" like <forward name="feed" path="/templates/plain.vm"/>, but without success.) Thanks, Jerome.

17 years, 1 month

2
1
0 0

[xwiki-devs] build-break: invalid jar in repository

by rssh

Good day. Now exist problem with default build of sources from repository: we have invalid xwiki-core-1.5-SNAPSHOT.jar (which breaks default build, becouse skinx require such snapshot) (i, e. jar -tf /home/rssh/.m2/repository/com/xpn/xwiki/platform/xwiki-core/1.5-SNAPSHOT/xwiki-core-1.5-SNAPSHOT.jar show something like: com/xpn/xwiki/pref/api/XWikiPrefService.class com/xpn/xwiki/pref/impl/xwiki/XWikiPrefServiceImpl.class com/xpn/xwiki/XWikiCompatibilityAspect.class java.util.zip.ZipException: invalid stored block lengths at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:164) at java.util.zip.ZipInputStream.read(ZipInputStream.java:163) at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:109) at sun.tools.jar.Main.list(Main.java:885) at sun.tools.jar.Main.run(Main.java:230) at sun.tools.jar.Main.main(Main.java:1044) [rssh@localhost skinx]$ P.S. java is OpenJDK -- Ruslan Shevchenko GradSoft. http://www.gradsoft.ua

17 years, 1 month

1
0
0 0

Re: [xwiki-devs] [xwiki-users] overriding view.vm in own skin

by rssh

On Thu, 24 Jul 2008 19:13:12 +0300, rssh wrote > On Thu, 24 Jul 2008 19:02:20 +0300, rssh wrote > > Good day, community. > > Yet one update: looks like this is error in xwiki: (from XWiki.java: ) try { // Try to get it from context skin = (String) context.get("skin"); if (skin != null) { return skin; } // Try to get it from URL if (context.getRequest() != null) { skin = context.getRequest().getParameter("skin"); } if ((skin == null) || (skin.equals(""))) { skin = getUserPreference("skin", context); } if (skin.equals("")) { ******************** - must be skin!=null || skin.equals("") *** (so, I think that error is here). skin = Param("xwiki.defaultskin", getDefaultBaseSkin(context)); } } catch (Exception e) { ****************** (!) --- why we don't log anything (may be in debug mode) skin = getDefaultBaseSkin(context); } Can anybosy from core team quicly say: is such errors possible or I forgott something very basic ? If this error is possible, I will submit patch during next few days. Also I'm a bit frustrated by number of empty generic catch bloks in XWiki.java. Debugging such code can become a hard task. About cited part from xwiki.cfg: I guess that FileNotFoundException must be catched with logging only in debug mode, any other Exception must be logged in warnings. > > Small question about customizing xwiki: > > - I want to customize skin, by creating own skin (with name 'x'), > > After reading http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Skins > > I do next sequences of steps: > > > > a) creating directory <xwiki-base>/skins/x, > > b) copying all files from touckan to x > > c) changing default skin in xwiki.cfg grom touckan to x > > d) copying file templates/view.vm to x > > e) customizing view.vm (writing onethins inside) > > > > Last step does not work; i. e. if I change view.vm, nothing changed > > in xwiki. > > > > So, question: it is such problem with my installation, or I missed something > > during creation of skin ? > > > > self-moderation: whith ?skin=x additional parameter all works. > > So: is exists way, where xwiki.defaultskin parameter from xwiki.cfg > is incorrect ? > > > -- > > Ruslan Shevchenko > > GradSoft. http://www.gradsoft.ua > > > > _______________________________________________ > > users mailing list > > users(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/users > > -- > Ruslan Shevchenko > GradSoft. http://www.gradsoft.ua > > _______________________________________________ > users mailing list > users(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/users -- Ruslan Shevchenko GradSoft. http://www.gradsoft.ua

17 years, 1 month

2
2
0 0

[xwiki-devs] Smtp Authentication and pdf export with Chines Problem

by Wang Ning

Hi devs, I saw the release note of xe 1.6 http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise15, which says 1. Mail sender plugin now supports SMTP authentication But I can't config it in the xwiki administration. Any one can tell me how to config stmp username and password? 2. UTF-8 characters are now all correctly rendered in PDF exports I add some Chinese in a xwiki page, and export it as pdf. However, the Chinese characters still are ???. I see some fonts are added to xwiki. Can I use other fonts by config something? Thanks. Sincerely, Wang Ning

17 years, 1 month

1
0
0 0

[xwiki-devs] [GSOC]Daily report

by malaka ekanayake

Hi Fabio, Yesterday I mainly look at how the velocity scripting use in the xwiki pages. Velocity scripting can be used mix with the xwiki script.But then there has to be a way to separate the velocity scripts from other syntax.Such as to a separate partition.since every velocity script starts with # I'm thinking of using that to separate from the rest of the syntax. At the moment the current editor identify macros (#info,#warning) as separate partitions () .But since they are also velocity macros they should also move to the velocity partition as well. According to my findings Thus there will be no problem of separating all the velocity syntax from the rest of by looking at the # character at the start of the line WDUT of that. Is this correct. Then I can start by moving all the macros to a separate partition -- Malaka Ekanayake CSE UOM

17 years, 2 months

3
2
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