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

by jeremi joslin

For testing the package, I need to get the Output Stream from HttpServletResponse to put it in a byte[]. Does anyone now how to do this? Jérémi -- http://www.sport42.net - http://stage.xwiki.com Tel : 06.84.50.33.49 skype: jeremi23

20 years, 3 months

1
0
0 0

RFI: javascript ban problem

by Jim Stuttard

Hi, 1. I mentioned this problem to someone on the list the other week. Would like to know what you folks think. On the Sonera-Zed, British Gas and Philips projects javascript was unneeded (WAP-WML), minimised or banned for security reasons. This might be another barrier to acceptance. I've had to turn javascript on to access XWiki. A standard set of security problems is referenced at: http://www.panix.com/~aahz/javascript.html Do folks reckon the security problems have now been tied up then and these corps should change their policy? Cheers Jim 2. PS Ajax is not the only way of doing asynch before this project adopts yet another technology. FI: List members might enjoy Phil Wadler's 'The next 700 computer languages' http://homepages.inf.ed.ac.uk/wadler/topics/xml.html I regard it as pretty mandatory reading.

20 years, 3 months

2
4
0 0

xwiki build.49 Build Successful

by ludovic＠xwiki.org

View results here -> http://build.xpertnet.biz/cc/buildresults/xwiki?log=log20050607135638Lbuild…

20 years, 3 months

1
0
0 0

RE: [xwiki-commits] r596 - in xwiki/trunk/src: main/java/com/xpn/xwiki/plugin/packaging test/com/xpn/xwiki/test

by Vincent Massol

> -----Original Message----- > From: Jeremi Joslin [mailto:jeremi@users.forge.objectweb.org] > Sent: mardi 7 juin 2005 13:53 > To: xwiki-commits(a)objectweb.org > Subject: [xwiki-commits] r596 - in xwiki/trunk/src: > main/java/com/xpn/xwiki/plugin/packaging test/com/xpn/xwiki/test [snip] > +/** > + * =================================================================== > + * > + * Copyright (c) 2005 Jrmi Joslin, XpertNet, All rights reserved. Jeremi, you're going to find me a pain in the ... but there are 2 issues here: 1/ I think the copyright should go to Ludovic Dubost. At least that's the current policy AFAIK 2/ Your name is Jeremi, right? ;-) [snip] -Vincent

20 years, 3 months

2
1
0 0

RE: [xwiki-commits] r594 - xwiki/trunk/src/test/com/xpn/xwiki/test

by Vincent Massol

Hi Jeremi, > -----Original Message----- > From: Jeremi Joslin [mailto:jeremi@users.forge.objectweb.org] > Sent: mardi 7 juin 2005 13:08 > To: xwiki-commits(a)objectweb.org > Subject: [xwiki-commits] r594 - xwiki/trunk/src/test/com/xpn/xwiki/test [snip] > +/** > + * =================================================================== > + * <p/> > + * Copyright (c) 2005 Jrmi Joslin, All rights reserved. > + * <p/> This looks like a strange header. Why are there "<p/>" tags? > + * User: jeremi > + * Date: May 13, 2005 > + * Time: 2:30:12 PM > + */ I though we had agreed that we didn't want these anymore? :-) > +public class DocumentInfoTest extends HibernateTestCase{ Minor space issues > + public void testActionTo() > + { We really need the checkstyle stuff. I'll work on it. Thanks -Vincent

20 years, 3 months

2
1
0 0

xwiki build.48 Build Fixed

by ludovic＠xwiki.org

View results here -> http://build.xpertnet.biz/cc/buildresults/xwiki?log=log20050607132045Lbuild…

20 years, 3 months

1
0
0 0

xwiki Build Failed

by ludovic＠xwiki.org

View results here -> http://build.xpertnet.biz/cc/buildresults/xwiki?log=log20050607130953

20 years, 3 months

1
0
0 0

xwiki build.47 Build Fixed

by ludovic＠xwiki.org

View results here -> http://build.xpertnet.biz/cc/buildresults/xwiki?log=log20050606173151Lbuild…

20 years, 3 months

1
0
0 0

Google Summer Coding - P2P XWiki (offline editor)

by Jaroslav Pšenička

Hi all, my name is Slavek Psenicka, Jirka's colleague (mentioned in http://www.objectweb.org/wws/arc/xwiki-dev/2005-06/msg00043.html message). I'm currently working on a prototype of Eclipse-based (X)Wiki offline editor. The stuff is just reaching hardly-but-useful version with limited functionality (local and remote repository browsing, page editing and previewing, repository API -- also referred as M1). I'd like to commit the code to XWiki community and continue together. The fact is, that the code was (partially) developed as a part of my work activities and some kind of approval from my management is neccessary. We will meet with them and discuss these questions ASAP, hopefully at the end of this week will inform you about the result. Best Regards, Slavek

20 years, 3 months

2
1
0 0

XWiki on the Google Summer of Code program

by Ludovic Dubost

XWiki has made it's way on the Google Summer of Code program (very cool !!!) It's a very cool initiative by Google: Google Summer of Code <http://code.google.com/summerofcode.html>. Thanks to Jeremi who noticed it, we have been very reactive and we managed to get XWiki on the list of mentoring organizations. This has been very positive both because we have had lots of visits on the xwiki.org site to see the page of proposed projects <http://www.xwiki.org/xwiki/bin/view/Dev/SummerOfCode>. I've had about 7 students contacting me for projects on this page and some of them seem to know what they are talking about.. The guy proposing the XWiki P2P project for example seems to be quite interesting. We also have a proposal for the WYSIWYG Editor. If some people in the team would like to help mentor some of the students working on a specific project, don't hesitate to volunteer ! Let's hope we will be allowed to have many of these projects accepted. Google has a budget for 200 projects (that's 1M$) and there are 40 organizations right now which means an average of 5 projects, knowing that there are some big organizations in the list. Just Nmap has been notified of 31 proposals sent out for 19 different projects. They stated they can only handle 5 to 7 students. Ludovic -- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic

20 years, 3 months

1
1
0 0

Re: Google Summer Coding - P2P XWiki

by Ludovic Dubost

Hi, This is a very cool project.. very ambitious and it has a good chance being accepted. I see that you have a very decent experience with the GRID computing thing.. You could actually merge it with the "offline" wiki so that it is a 2 step process.. So the deliverables would be: 1/ Java program allowing to synchronize a local wiki with a remote (centrally localted) wiki and handle conflicts. XWiki uses CVS for versioning it's files so conflict management should be possible and provided through an interface Users would access the local wiki through their usual web interface. 2/ Implement a P2P protocol which would allow to have no central server containing the wiki data. Documents would be synched from user to user on a document by document basis. Conflicts management will be needed. A central server can be kept (or not) to manage the participant lists. A system for security is needed (a key ? PGP keys ? something else ?). Sync could be manual or automated (near-real-time).. 3/ Optional: Eclipse RCP client embedding Gekko and managing the remote/P2P aspects of XWiki, manage the sync conflicts and adding some cool XWiki interface navigation features (spaces, documents, active users, etc..). The XWiki content would be shown using the embedded Gekko component. Basically the deliverables would be to amaze us.. This is probably one of the only project with the WYSIWYG editor where there is significant obstacles to make this work. So we can understand the result isn't perfect.. If we have a working prototype even if not everything is solved we would consider this ok. Ludovic Bikash Agarwalla a écrit : >Hello, > I am a graduate student studying at Gatech, Atlanta. I am interested in >working on the p2p XWiki project listed on as part of google summer >coding on your website. > >I am interested in learning more about the existing implementation and >what is required as part of this project. I have exposure to P2P research >systems such as Chords, Pastry. I will be willing to investigate P2P search >technologies and propose an architecture for XWiki that allows >users to come "online", search for other users and synchronize their content. > >Since this is an ambitious project, I am curious about what deliverables are >expected. Please provide me any necessary details. My background and experience >can be found on my website. I believe my research and development >experience makes me a >strong candidate for this project. I will be excited to work on it >once I understand what are the >expectations out of this work within the timeframe. > >Regards, >-Bikash Agarwalla >Graduate Student, Gatech >Atlanta, GA >http://www.cc.gatech.edu/~bikash > > > -- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic

20 years, 3 months

3
2
0 0

Considering a licence change

by Ludovic Dubost

Hi Contributors, I'd like to open a discussion about a licence change. I've been thinking for a while to open up the licence more. Currently the code is GPL which allows end-users (including commercial companies using XWiki internally or for their web sites) to use XWiki without being required to contribute code back, but requires software distributors to contribute all modifications using the GPL. Until version 0.9.543 there was only code from myself in it which allowed me to double licence code, which has been done with one company in the US who has embedded XWiki in a proprietary product. Starting with release 0.9.793, XWiki has significant contributions from other users which if we want to be able to allow this company or others in the future to use XWiki in compliance with the open-source licence we need to: 1/ Either get the right from ALL contributors to allow XPertNet to double-licence the contributions for proprietary usage and charge for it as well as support. 2/ Open up the licence to a licence which would allow them to do it without a double licence. This licence could be LGPL or ASL. Customers could still take a support contract with XPertNet. I'd like to hear the opinions of everybody and of course especially of contributors who have commited code to XWiki. Which route should be go from your point of view and are you willing to relicence your code to any of the licence proposed (giving the right to double licence, changing licence to LGPL or changing licence to ASL). This question is also true for Jens who has contributed the Lucene plugin and the email notification plugin but to a lesser extent as these are plugins and could keep a separate licence. It would just restrict specific usage of these specific plugins. Whatever we decide, we will need to create some documents that contributors would sign to specifically accept the conditions under with the contributions are made to the code base. Ludovic -- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic

20 years, 3 months

5
6
0 0

Re: Summer of Code

by Ludovic Dubost

Hi Chris, The WYSIWYG editor is quite ambitious.. There are two ways.. 1/ Integrating an Editor like FCKEditor with back and forth Wiki Syntax conversion 2/ Making a pure DHTML AJAX Editor able to edit in place and have the data inserted in the Wiki Syntax document in memory and show up transformed as HTML on the Fly (by Javascript or by a call to the server).. Existing tools like BitFlux Editor or this project around WikiMedia could be good starting points: http://81.5.150.113/wysi/Main_Page I view the number 2/ like the most ambitious project. It's not easy at all but would be really powerfull since it would allow to have real WYSIWYG editing including for non HTML elements (XWiki macros for example which could be replaced by a preview block which could be edited using a WIZARD). If you want to have your project accepted you need to present a vision of what you would like to do and be pretty ambitious.. There are lot's of proposals so it needs to stand out.. Now if it is too difficult you might fail completing it.. Choose the right balance.. Ludovic Chris Walton a écrit : >Hello, > >I just found what I was looking for to do! I would like to work on >the WYSIWYG editor. I am assuming this refers to editing the actual >Wiki pages. Although I haven't done (much) AJAX work, I'm pretty quick >to learn. > >Please, let me know if you have an opening, and what you envision for >the editor. I can also be reached with AIM under arke87. Thanks :) > > > -- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic

20 years, 3 months

1
0
0 0

[Fwd: Re: Google Summer of Code]

by Ludovic Dubost

Proposal for the Summer of Code from Google :) -- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic

20 years, 3 months

1
0
0 0

Comments and log statements?

by Lilianne E. Blaze

Hello, Would patches containing only (or mostly) comments and log statements increasing source code's ease to read / debug be welcome? Greetings, Lilianne E. Blaze

20 years, 3 months

2
1
0 0

[Checkstyle] Coding rules

by Vincent Massol

Hi, I have just made my first code commits. However, I had no code rules to go by so I've tried to copy existing code. The problem is that the existing code is not consistent itself!... I would like us to define what are our coding rules. Questions such as: - max number of characters on a ligne. 100? 120? More? - indentation rules - spacing rules, like "(SomeClass)myobject" or "(SomeClass) myobject" - etc We could of course have a wiki topic for describing the rules but I don't think that's the right approach. I would prefer doing what I've done on my other projects: have a checkstyle.xml file describing those rules and apply them in the build. ATM as we have lots of inconstancies, the build would not fail on checkstyle error. However we should work towards eliminating checkstyle violations and move the checks, one by one, from warning to error (error fails the build). WDYT? Thanks -Vincent _____________________________________________________________________________ D�couvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vid�os ! Cr�ez votre Yahoo! Mail sur http://fr.mail.yahoo.com

20 years, 3 months

4
4
0 0

xwiki Build Failed

by ludovic＠xwiki.org

View results here -> http://build.xpertnet.biz/cc/buildresults/xwiki?log=log20050602141808

20 years, 3 months

1
0
0 0

[Process] Decision management

by Vincent Massol

Hi, I'd like to be sure I'm doing the right thing, hence this email. Are we following any rule for deciding whether or not a proposal should be applied or not? For example, I've just sent an email about modifying the XWiki constructor interface. Ludovic has answered but not other committers. Should I go ahead or do I need to wait for others to chime in? Are we following the ASF rules defined here: http://apache.org/foundation/how-it-works.html#management? However this is not enough. Here's an additional rule followed on most Apache projects: " The development process is intentionally lightweight; like other Apache projects, the committers decide which changes may be committed to the repository. Three +1 ('yes' votes) with no -1 ('no' votes or vetoes) are needed to approve a code change. For efficiency, some code changes from some contributors (e.g. feature additions, bug fixes) may be approved in advance, in which case they may be committed first and changed as needed, with conflicts resolved by majority vote of the committers. " Is this too heavyweight? Is it ok? What do you want? Should I wait before committing the xwiki constructor change I have proposed? The reason I'm asking this is because I am a new member of the community and I'm sure other newcomers may also have some doubt when they want to change existing code. Thanks -Vincent _____________________________________________________________________________ D�couvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vid�os ! Cr�ez votre Yahoo! Mail sur http://fr.mail.yahoo.com

20 years, 3 months

4
6
0 0

[API refactoring] Add default constructor to XWikiConfig

by Vincent Massol

Hi, I'd like to add a default constructor to XWikiConfig so that config can be added in java code: XWikiConfig config = new XWikiConfig(); config.put("xwiki.store.class", "com.xpn.xwiki.store.XWikiHibernateStore"); config.put("xwiki.store.hibernate.path", getClass().getResource(StoreHibernateTest.HIB_LOCATION).getFile()); WDYT? Thanks -Vincent _____________________________________________________________________________ D�couvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vid�os ! Cr�ez votre Yahoo! Mail sur http://fr.mail.yahoo.com

20 years, 3 months

2
1
0 0

Including Servlets/JSPs in templates?

by Lilianne E. Blaze

Hello, I need to be able to include a Servlet or JSP from inside of /templates/*.vm files (specifically header and footer). I tried things like: $request.getRequestDispatcher("/xxx.jsp").include( $request, $response ) But for some reason (buffering in Velocity I guess) it renders included page before anything else, no matter where it's actually placed. Is there some workaround? If not, I think I have an idea how to implement a kind of "#includeServlet" directive, could it be included in XWiki then? Greetings, Lilianne E. Blaze

20 years, 3 months

2
4
0 0

[Coding rules] Author/Creator information

by Vincent Massol

Hi everyone, Do you really want to keep the following which is part of most file headers: * Created by * User: Ludovic Dubost * Date: 26 nov. 2003 * Time: 13:52:39 This seems to me information that can be retrieved from the SCM. And if we want to store SCM information in the file then it is only fair that whoever modifies the file should also get credit there. In addition usually we would use the @author tag for storing this kind of information. Having it in an undefined format like above is a bit strange... ;-) So I think there are 2 options: Option 1: --------- - We do not store author information in the file - We have a credits Wiki page that lists all contributors and what they have done. Something like: - http://jakarta.apache.org/cactus/participating/contributors.html - http://cargo.codehaus.org/Credits - It's still a good idea to have a @version tag in the file, as in: * @version $Id: Container.java 348 2005-04-26 23:03:22Z vmassol $ The content of this tag is generated automatically by the SCM upon commit. Option 2: --------- - We save author information in the file using @author tags. For example @author <a href="mailto:...@...">Ludovic Dubost</a> @author <a href="mailto:...@...">Vincent Massol</a> [...] There have been *lots* of debates (which I'll spare you here but you can google it) between these 2 options and the one chosen @ Apache is option 1. I have done the same for Cargo. I don't mind the chosen solution but I think the current option is not good enough. Thanks -Vincent _____________________________________________________________________________ D�couvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vid�os ! Cr�ez votre Yahoo! Mail sur http://fr.mail.yahoo.com

20 years, 3 months

3
2
0 0

[API Refactoring] Modify XWiki constructor

by Vincent Massol

Hi, I'm trying to fix some unit tests and by doing so I'm working my way in the XWiki API. I have thousands of ideas to improve the design but honestly I don't know where to start from; it's a bit overwhelming ;-) We need to start somewhere, so we might as well start with the XWiki class constructor. ATM, the constructor is: public XWiki(String xwikicfgpath, XWikiContext context) public XWiki(String xwikicfgpath, XWikiContext context, XWikiEngineContext engine_context, boolean noupdate) public XWiki(InputStream is, XWikiContext context, XWikiEngineContext engine_context) The first parameter is used to pass a location of a config file. Actually this parameter is only used to create a XWikiConfig object. I believe we should delegate the creation of a XWikiConfig object to the XWikiConfig object itself so that our API can resist to change. Imagine that tomorrow I want to store a XWiki config in a database. Today the API would not cope with this because it's rigid and unflexible. It violates IOC. Here's my proposal for the XWiki class: - Deprecate the current constructors - add 2 new constructors: public XWiki(XWikiConfig config, XWikiContext context) public XWiki(XWikiConfig config, XWikiContext context, XWikiEngineContext engine_context, boolean noupdate) Thus the "user" must start by creating a XWikiConfig, then a XWikiContext, possibly an EngineContext and then only he can create a XWiki object. The idea is that the creation of a config should be left to the config object and NOT to the Wiki class (it's not its role). This leads to a better design. In addition to being more flexible this will allow for easier unit testing as we will not need a xwiki.cfg file anymore (it will still be used for functional testing though). Obviously the next step would be to transform XWikiConfig into an interface. What do you think? Thanks -Vincent _____________________________________________________________________________ D�couvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vid�os ! Cr�ez votre Yahoo! Mail sur http://fr.mail.yahoo.com

20 years, 3 months

2
1
0 0

Displaying pages in plain formatting

by aprotogerellis＠mailsnare.net

Hello, I am trying to use XWiki in conjunction with Selenium to enable any user to write application tests through xwiki and run them on selenium. I have been quite succesful but require a way of accessing an xwiki page in completelly plain formatting. I.e. without the side bars, google add bar etc. What would be a good way of doing this? I've attempted using skins but to limited effect. Thanks Alex

20 years, 3 months

2
1
0 0

Pb in unit tests with my refactoring...

by Vincent Massol

Hi, I'm still struggling to fix the tests that I have broken with my last refactoring (the generation of the hibernate config file tests.build.dir and its retrieval through the classpath). Sorry about that... I'm not sure what's the reason. Here's attached the test report of a test class that now fails. If you have any idea let me know. Also, I've noticed that the test/wiki.cfg file has: xwiki.store.hibernate.path=hibernate-test.cfg.xml Is that used anywhere? I thought that the config file was passed by the Java classes. Thanks -Vincent

20 years, 3 months

2
3
0 0

RE: [xwiki-dev] [Build] About to move tests

by Vincent Massol

> -----Original Message----- > From: Vincent Massol [mailto:vincent@massol.net] > Sent: mardi 31 mai 2005 09:58 > To: 'xwiki-dev(a)objectweb.org' > Subject: RE: [xwiki-dev] [Build] About to move tests > > Hi, > > It seems that the tests are generating some files during their execution. > They seem to generate: > > - test/velocity.log > - test/xwiki.log > - test/hibernate-test.cfg.xml > - test/rcs/Test/* > > Could someone tell me how I can update the test files so that these > generated files go into the build/ directory instead of going into a > source directory? This is pre-requisite before I can make any modification to the directory structure. Actually what should be done is remove the dependency on paths. ATM, I've noticed that several tests are using path to find test resources. I believe this is not right and should be improved by using the classpath to locate the test resources. In other words, instead of doing something like: public static final String hibpath = "hibernate-test.cfg.xml"; XWikiHibernateStore hibstore = new XWikiHibernateStore(hibpath); We should be doing: public static final String hibLocation = "/hibernate-test.cfg.xml"; URL hibURL = getClass().getResource(hibLocation); XWikiHibernateStore hibstore = new XWikiHibernateStore(hibURL); And we add src/test/resources to the JUnit execution CP. What's wrong with paths? - they are system dependent - they can be absolute or relative and the result will depend from where you execute the code. Thus they are brittle WDYT? I don't know the code well so I would need your help in fleshing out the places where paths are used. I've noticed one in AllTests.java (see attached "patch" - I've also added some other comments). Once we don't rely any more on paths then we'll be able to move /test in src/test/resources. Thanks for your help -Vincent > > Thanks > -Vincent > > > -----Original Message----- > > From: Vincent Massol [mailto:vincent@massol.net] > > Sent: mardi 31 mai 2005 09:47 > > To: xwiki-dev(a)objectweb.org > > Subject: [xwiki-dev] [Build] About to move tests > > > > Hi developers, > > > > This is a heads up as I'm about to move test sources and resources as > > planned in a previous email (see also XWIKI-12). > > > > The following changes will happen: > > > > - trunk/test will go in src/test/resources > > - trunk/src/test will go in src/test/java > > - trunk/src/test-cactus will go in src/test/cactus > > > > This means that you'll need to add the src/test/resources directory to > > your > > execution classapath in your IDE project files. You'll also need to > change > > src/test to src/test/java and src/test-cactus to src/test/cactus. > > > > Please shout if you have an issue with this. I'll be doing it in about 1 > > hour. > > > > Thanks > > -Vincent > > > > > > > > > > > > > > > __________________________________________________________________________ > > ___ > > Dicouvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos > > mails, photos et vidios ! > > Criez votre Yahoo! Mail sur http://fr.mail.yahoo.com

20 years, 3 months

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