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

Why are we creating Tag objects automatically?

by Vincent Massol

Hi, Can someone tell me why we are creating empty Tag objects automatically for all documents. It seems to me this is wrong. Thanks -Vincent

18 years, 2 months

2
1
0 0

LDAP and user registration

by Jacob Bresciani

I¹m setting up an xwiki for my organization and I¹ve managed to tie it to our 2003 Domain controller for user authentication. My problem is that with xwiki 1.0 users could just log in with their domain accounts, registration of said user was automatic. With 1.1 milestone 2 the user must be registered first or they don¹t seem to have permissions to view anything, sometimes it just won¹t accept them at all. I¹m using the same configuration lines in xwiki.cfg for 1.1 as I did for 1.0. Am I missing something? Or is this working as intended? ------------------------------------------------------------------ Jacob Bresciani Systems Analyst, Information Systems Support Procurement and Supply Services Phone: (250) 356-7115 Fax: (250) 387-0388 E-mail: jacob.bresciani(a)gov.bc.ca Visit us online at: http://www.pss.gov.bc.ca/ Committed to our customers ... always working for you!

18 years, 2 months

2
2
0 0

Fwd: About XWiki XMLRPC

by Asiri Rathnayake

I'm re-sending this email because i just heard that mailing list was down for past two days. Please excuse me If you receive this mail twice. Thanks. - Asiri ---------- Forwarded message ---------- From: Asiri Rathnayake <asiri.rathnayake(a)gmail.com> Date: Jul 18, 2007 9:37 AM Subject: About XWiki XMLRPC To: xwiki-dev(a)objectweb.org Hi all, After going through xwiki sources, I finally managed to fix the issues with XMLRPC. But before opening up any JIRA issues or submitting patches, i thought it would be better to get some feedback. Following are my observations on XMLRPCs, 1. XWiki's XMLRPC implementation does not map one-to-one with the given documentation<http://confluence.atlassian.com/display/DOC/Remote+API+Specification> Ex. - in XWiki, there is no method as removePage(), instead we have deletePage() - in XWiki, there is no method as removeSpace() but it's achieved by deleting all the child pages. 2. Some XMLRPCs are not implemented. But these are not used used in Xeclipse (yet), so i didn't pay much attention to them. 3. One XMLRPC call threw an exception when it's return type was 'void'. I changed this one to 'boolean' and everything works fine. I don't know why this happens though. 4. storePage() RPC had a problem which makes it override other pages when trying to save a newly created page. I think this is a typo, anyway, it's fixed. 5. I also noted that there is a XWiki specific XMLRPC API too (which is very limited). So, if any of you have any concerns, thoughts, opinions, please throw them in. I'll create the JIRA issues little later. Thanks. - Asiri

18 years, 2 months

2
3
0 0

XWikiMessageTool refactoring

by Sergiu Dumitriu

Hi, I looked today over the XWikiMessageTool class, and I must say that I'm not quite satisfied with it. First, there was XWIKI-919, which I implemented. OK, I understand that files stored on disk should be charset independent, so only ASCII characters are supported by the ResourceBundle class (jvm) .But, when I can edit a wiki document for storing bundles, I expect it to accept all the characters the wiki supports (in my case, it was an UTF8 instance). I had some troubles fixing this, since the JavaDoc says that bundles accepts only ASCII characters, but it understands and parses unicode references ( \u0123 ). Maybe I did something wrong, but doing content.replaceAll("\u0139", "\\u0139") resulted in the string u0139 being displayed in the page. So I had to trick it into believing that the component bytes of the encoding are ASCII characters and manually restore the multibyte chars. Second, I don't like the fact that XWIKI-921 was not already implemented. Third, I don't like the cache refresh mechanism. It retrieves the XWikiProperties->documentBundles property for each request, and It retrieves the bundle documents for every request and checks if it must be refreshed or not. Why isn't the com.xpn.xwiki.notify package used? It allows registering callback handlers for specific document changes. How I see it: - at startup, register a handler for XWiki.XWikiPreferences (so that we know when the documentBundles property might change). - remember the list of document bundles, don't ask it for each request - also register handlers for the current bundle documents and load the strings from these documents - when XWikiPreferences is changed, if the documentBundle property is also changed, remove the unused bundles and build the new ones - when a undle document (or a translation for it) is changed, rebuild the bundle for that document This should speedup the code a bit, it makes use of a nice, but mostly unknown feature, it doesn't log an error for each request when a specified document is not found in the wiki, and it doesn't require so many variables (previousDates, docsToRefresh). Fourth, as I said above, if a document is specified in the documentBundles property, but it does not exist in the wiki, for each $msg.get call an error is logged. And there are a lot of calls for each request. Now, in my opinion this is a nice way to get in the core of XWiki for a newcomer, so does anybody want to write the changes I mentioned? Also, this is a good occasion to document the event notification mechanism, in JavaDoc and on www.xwiki.org Regards, Sergiu Dumitriu -- http://purl.org/net/sergiu

18 years, 2 months

2
1
0 0

Test failures in platform-core ? or ..... ?

by Asiri Rathnayake

Hi all, I'm pretty new to building xwiki from source and ran into a little problem. When I did 'mvn package' in xwiki-platform-core i get the following output, ===================================================================== [asiri@asiri-desktop xwiki-dev]$ cd xwiki-platform-core/ [asiri@asiri-desktop xwiki-platform-core]$ mvn package [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building XWiki Platform - Core [INFO] task-segment: [package] [INFO] ---------------------------------------------------------------------------- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://maven.xwiki.org/externals/groovy/groovy-all-1.0-jsr/06/groovy-all-1.… Downloading: http://maven.xwiki.org/releases/groovy/groovy-all-1.0-jsr/06/groovy-all-1.0… Downloading: http://repo1.maven.org/maven2/groovy/groovy-all-1.0-jsr/06/groovy-all-1.0-j… [WARNING] While downloading xml-apis:xml-apis:2.0.2 This artifact has been relocated to xml-apis:xml-apis:1.0.b2. [INFO] [compiler:compile] [INFO] Compiling 520 source files to /home/asiri/projects/xwiki-dev/xwiki-platform-core/target/classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Compiling 15 source files to /home/asiri/projects/xwiki-dev/xwiki-platform-core/target/test-classes [INFO] [surefire:test] [INFO] Surefire report directory: /home/asiri/projects/xwiki-dev/xwiki-platform-core/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running com.xpn.xwiki.content.parsers.LinkParserTest Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.137 sec Running com.xpn.xwiki.web.XWikiMessageToolTest Tests run: 9, Failures: 0, Errors: 9, Skipped: 0, Time elapsed: 0.176 sec <<< FAILURE! Running com.xpn.xwiki.user.impl.xwiki.XWikiAuthServiceImplTest Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.023 sec <<< FAILURE! Running com.xpn.xwiki.doc.XWikiDocumentTest Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.068 sec <<< FAILURE! Running com.xpn.xwiki.doc.XWikiDocumentArchiveTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.09 sec Running com.xpn.xwiki.store.XWikiHibernateStoreTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec Running com.xpn.xwiki.content.LinkTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running com.xpn.xwiki.render.XWikiRadeoxRendererTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.02 sec <<< FAILURE! Running com.xpn.xwiki.render.XWikiVelocityRendererTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.018 sec <<< FAILURE! Running com.xpn.xwiki.content.parsers.RenamePageReplaceLinkHandlerTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running com.xpn.xwiki.content.parsers.DocumentParserTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec Running com.xpn.xwiki.plugin.packaging.PackageTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.014 sec <<< FAILURE! Running com.xpn.xwiki.plugin.captcha.CaptchaPluginTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.013 sec <<< FAILURE! Running com.xpn.xwiki.atom.WSSEHeaderTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 sec Running com.xpn.xwiki.plugin.zipexplorer.ZipExplorerTest Tests run: 10, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.034 sec <<< FAILURE! Results : Tests in error: testGetWhenPreferenceDoesNotExist(com.xpn.xwiki.web.XWikiMessageToolTest) testGetWhenNoTranslationAvailable(com.xpn.xwiki.web.XWikiMessageToolTest) testGetWhenKeyIsNull(com.xpn.xwiki.web.XWikiMessageToolTest) testGetWhenInXWikiPreferences(com.xpn.xwiki.web.XWikiMessageToolTest) testGetWhenInXWikiConfigurationFile(com.xpn.xwiki.web.XWikiMessageToolTest ) testGetWithParameters(com.xpn.xwiki.web.XWikiMessageToolTest) testGetDocumentBundlesWhenDocumentDoesNotExist( com.xpn.xwiki.web.XWikiMessageToolTest) testGetReturnsFromCacheWhenCalledTwice( com.xpn.xwiki.web.XWikiMessageToolTest) testGetWhenDocumentModifiedAfterItIsInCache( com.xpn.xwiki.web.XWikiMessageToolTest) testAuthenticateWithSuperAdminWhenSuperAdminPasswordIsTurnedOff( com.xpn.xwiki.user.impl.xwiki.XWikiAuthServiceImplTest) testAuthenticateWithSuperAdminPrefixedWithXWikiWhenSuperAdminPasswordIsTurnedOff( com.xpn.xwiki.user.impl.xwiki.XWikiAuthServiceImplTest) testAuthenticateWithSuperAdminWithWhiteSpacesWhenSuperAdminPasswordIsTurnedOff( com.xpn.xwiki.user.impl.xwiki.XWikiAuthServiceImplTest) testGetDisplayTitleWhenNoTitleAndNoContent( com.xpn.xwiki.doc.XWikiDocumentTest) testGetDisplayWhenTitleExists(com.xpn.xwiki.doc.XWikiDocumentTest) testGetDisplayWhenNoTitleButSectionExists( com.xpn.xwiki.doc.XWikiDocumentTest) testRenderWithSimpleText(com.xpn.xwiki.render.XWikiRadeoxRendererTest) testRenderLinkToNewPage(com.xpn.xwiki.render.XWikiRadeoxRendererTest) testRenderWithSimpleText(com.xpn.xwiki.render.XWikiVelocityRendererTest) testRenderWithVelocityContent( com.xpn.xwiki.render.XWikiVelocityRendererTest) testImportWithHeterogeneousEncodingInFiles( com.xpn.xwiki.plugin.packaging.PackageTest) testVerifyCaptchaUsingTextWithValidAnswerAndAnonymousUser( com.xpn.xwiki.plugin.captcha.CaptchaPluginTest) testVerifyCaptchaUsingTextWhenInvalidAnswerAndAnonymousUser( com.xpn.xwiki.plugin.captcha.CaptchaPluginTest) testDownloadAttachmentWithInvalidZipURL( com.xpn.xwiki.plugin.zipexplorer.ZipExplorerTest) testDownloadAttachment(com.xpn.xwiki.plugin.zipexplorer.ZipExplorerTest) testDownloadAttachmentWhenURLIsNotZipFile( com.xpn.xwiki.plugin.zipexplorer.ZipExplorerTest) testDownloadAttachmentWhenURLIsZipButNotPointingInsideZip( com.xpn.xwiki.plugin.zipexplorer.ZipExplorerTest) testGetFileList(com.xpn.xwiki.plugin.zipexplorer.ZipExplorerTest) testGetFileTreeList(com.xpn.xwiki.plugin.zipexplorer.ZipExplorerTest) testGetFileLink(com.xpn.xwiki.plugin.zipexplorer.ZipExplorerTest) Tests run: 65, Failures: 0, Errors: 29, Skipped: 0 [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] There are test failures. [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 11 seconds [INFO] Finished at: Mon Jul 16 07:38:28 LKT 2007 [INFO] Final Memory: 8M/56M [INFO] ------------------------------------------------------------------------ ====================================================================================== Then one of my friends did the following and got it working,, 'mvn package -Dmaven.test.skip=true' But I believe i'm doing something wrong to cause those tests to fail, so please help me out. Also, i need to know how to get that stand-alone version (HSQLDB, Jetty and so on) of XWiki built out of XWiki sources. So far I couldn't figure it out. Any help would be highly appreciated. Thanks a lot. - Asiri

18 years, 2 months

3
4
0 0

Re:Problem with jetty

by evelyne24＠gmail.com

Hello Vincent, Actually, I must apologize because I didn't try Maven shapshot after installing Linux, I just kept my settings from Windows and on Windows the snapshot didn't work (I was using 2.0.7 without a problem). Thanks for your help. Evelina

18 years, 2 months

2
1
0 0

Create an enumerated DocumentAction class for document actions (edit, view, download, etc)

by Anca Luca

Hi, I have started (and finished, somehow) work on http://jira.xwiki.org/jira/browse/XWIKI-436 . I am interested of more opinions on the problems vmassol reported, or new problems that might raise. Best regards, Anca Luca

18 years, 2 months

1
0
0 0

Problem with jetty

by evelyne24＠gmail.com

Hi Artem, Done all that already. Yes, the profiles are Active Profiles for Project 'com.xpn.xwiki.platform:xwiki-web-standard:pom:1.1-SNAPSHOT': The following profiles are active: - jettyrun (source: pom) - xwiki (source: settings.xml) I have maven 2.0.7 installed because last time I tried to install the snapshot it didn't work so...it was the only version that worked on windows...now i'm using linux, but kept the version....i don't know if this is the problem since everything builds fine. The error from the browser: HTTP ERROR: 500 Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: null RequestURI=/xwiki/bin/view/Main/WebHome Caused by: com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: null at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:292) at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:384) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:94) 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:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1098) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:295) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:827) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:511) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) Wrapped Exception: java.lang.NullPointerException at java.util.Properties$LineReader.readLine(Properties.java:418) at java.util.Properties.load0(Properties.java:337) at java.util.Properties.load(Properties.java:325) at com.xpn.xwiki.XWikiConfig.loadConfig(XWikiConfig.java:56) at com.xpn.xwiki.XWikiConfig.(XWikiConfig.java:51) at com.xpn.xwiki.XWiki.(XWiki.java:568) at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:283) at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:384) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:94) 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:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1098) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:295) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:827) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:511) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) Powered by Jetty:// I am waiting for your answer. Thank you very much. Evelina

18 years, 2 months

2
2
0 0

terminology for spaces

by Erin Schnabel

So, on xwiki.org it's Spaces. In the code, it's Webs. And in the PanelWizard/PanelLayoutUpdate documents, it's Places. Which one do we want? And whichever that one is, we should stick with it. -- Waste of a good apple. --Samwise Gamgee

18 years, 2 months

2
1
0 0

Building XWiki

by Vincent Massol

Hi everyone, I felt that I needed to repeat these instructions about building XWiki from sources: 1) The XWiki build works fine. Yes it does ;) 2) Whenever you think there's an issue check our CI at http:// teamcity.xwiki.org and if it works don't send an email saying the build doesn't work. Instead refer to points 3 and 4. 3) If your build fails, it's likely that you haven't read the documentation closely enough. Go read the Building page again. 4) It's likely your error is one of these 2 (in that case read the building page again): A) You're not using the correct version of Maven B) You haven't defined the repos or the correct repos in your settings.xml file Thanks -Vincent

18 years, 2 months

1
0
0 0

build error

by Jackson Wang

Hi, I change mysql url setting in xwiki-2.pom from <xwiki.db.connection.url >"jdbc:mysql://localhost/xwiki?useServerPrepStmts=false"</xwiki.db.connection.url> to <xwiki.db.connection.url >"jdbc:mysql://localhost/xwiki?useUnicode=true&useServerPrepStmts=false"</xwiki.db.connection.url> then build 'xwiki-web-standard' by 'mvn install -Pxe,mysql ', get eror: [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: unknown:xwiki-web-standard POM Location: E:\dev\xwiki\svnroot\xwiki-users\xwiki-platform-web\standard\pom.xml Reason: Cannot read project model from interpolating filter of serialized version. I have build successfully before this modification. Does pom file can not use the expression '&' ?

18 years, 2 months

1
1
0 0

PageLayout application

by Erin Schnabel

I created a PageLayout application in the CodeZone: http://www.xwiki.org/xwiki/bin/view/Code/PageLayout As I described to someone on the IRC channel awhile ago (probably Vincent, as bothering him has become one of my favorite things to do.. :-P), PageLayout is just a class with some variables, the idea being: You a PageLayout object to a page, and then select, for that page only, whether or not you want the left or right sidebars to display, whether or not you want the collapsable comment/attachment boxes to display, and which (if any) editor is required. Some examples are in the description. Template mods are required to support this, as the code doing the actual rendering has to figure out what it should or shouldn't do. I included information about/examples of the changes I had to make to support per-page layout changes. Let me know what y'all think. Erin -- Waste of a good apple. --Samwise Gamgee

18 years, 2 months

1
0
0 0

Problem with jetty - solved

by evelyne24＠gmail.com

Yes, unfortunatelly is Maven 2.0.7 fault. It seems that the snapshot works fine on Linux and I am using it now. Thanks for trying to help me (especially Sergiu, like always).

18 years, 2 months

1
0
0 0

Problem with jetty

by evelyne24＠gmail.com

Hello all, I downloaded today xwiki sources and buided with maven as it is described on community->building, the run mvn install -Pjettyrun (the command was changed recently...as far as I remember it was another one...) anyway, the server starts, and in browser at localhost:8080 I see XWiki home page, but when I try to go to it, I have the following error: HTTP ERROR: 500 Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: null RequestURI=/xwiki/bin/view/Main/WebHome Caused by: com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: null at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:292) at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:384) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:94) 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:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1098) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:295) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:827) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:511) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) etc... As far as I know, 500 is not a client-side error, so it must be produced by the jetty server. Any ideea how to fix this? Thank you very much. Evelina

18 years, 2 months

3
2
0 0

Notification plugin

by Stéphane Laurière

Short note to let you know that I committed a notification plugin to the sandbox under the xwiki-sandbox/plugins/notification folder. The plugin uses the scheduler plugin (the version used is the one under xwiki-sandbox/plugins/tasks/ , currently being reviewed and completed by Vincent), and the mailsender plugin (see my previous email). I'm aware this will raise issues since we already have the notification plugin "net.jkraemer.xwiki.plugins.emailnotify", but I needed the following behaviour: - retrive the recent changes by querying the database (as opposed to emailnotify, which uses the in memory notifications caught by XWikiDocChangeNotificationInterface), - use mail templates as provided by the mailsender plugin for sending customized messages, - scheduling tasks that can be managed through the scheduler plugin. The plugin currently comes with a XWiki.NotificationRule class consisting of the following fields: - watched documents (comma separated) - watched spaces (comma separated) - watched documents query Users wishing to be notified have to attach one or several rule objects to their account page. The message used for sending the notifications is an instance of XWiki.Mail attached to the document XWiki.NotificationMessage (this should be configurable later on). Here's the current API of the plugin, comments are welcome: ========== int registerNotificationRuleForUser(String userFullName, String watchedSpaces, String watchedDocuments, String watchedDocumentsQuery) int addWatchedDocumentForUser(String userFullName, String watchedDocument) int addWatchedSpaceForUser(String userFullName, String watchedSpace) ========== Pending: draw a sound plan for a unified notification plugin and merge the API with the emailnotify one, add support for group notification, let users choose the notification frequency they wish, write tests and XWiki documents.. Here's the JIRA issue that relates to this plugin: http://jira.xwiki.org/jira/browse/XPEMAIL-2 Cheers Stéphane

18 years, 2 months

1
0
0 0

Mailsender plugin

by Stéphane Laurière

Hi everyone, I've refactored some code contributed by Fabrice and Jérome into a plugin that I committed to the xwiki-sandbox, under the plugins/mailsender folder (I'm using the sandbox since I find it handy for progressive refactoring and integration, but Vincent, please let me know if I should use JIRA attachments instead!). The plugin currently has the following API: =========== int sendTextMessage(String from, String to, String subject, String message) int sendTextMessage(String from, String to, String cc, String bcc, String subject,String message, List<Attachment> attachments) int sendHtmlMessage(String from, String to, String cc, String bcc, String subject, String body, String alternative, List<Attachment> attachments) int sendMessageFromTemplate(String from, String to, String cc, String bcc, String language, String documentFullName, VelocityContext vcontext) =========== The plugin creates its own "XWiki.Mail" class that has the following fields: - subject - language - text part - optional html part The class XWik.Mail is used by the method "sendMessageFromTemplate": this method evaluates the fields of the XWiki.Mail objects attached to the template document for building a custom message by using a VelocityRenderer. What do you think of the API? Any refactoring or enhancement remarks? Can we proceed with test and documentation writing, and submission for integration into 1.1M4? Related JIRA thread: http://jira.xwiki.org/jira/browse/XWIKI-1473 Cheers Stéphane

18 years, 2 months

1
0
0 0

[Architecture V2] Request Handling

by Vincent Massol

Hi, After discussing the Model I'd now like to discuss the architecture for request handling. I propose the following: General Architecture: * A Request Manager component to handle incoming requests. * Action classes called by the Request Manager Details: * In web.xml we define a ServletContextListener for initializing the Component Manager (CM) the first time XWiki is started. This puts the component manager as an attribute in ServletContext. For Plexus this means registering PlexusServletContextListener.java * In web.xml we define the main XWiki Servlet. It depends on the CM. For Plexus this means extending the PlexusServlet class. The main thing that Servlet does it use the CM to find the Request Manager component and to call it. The other thing it does is create a XWikiRequest component and a Session component so that the CM can inject them in components requiring them. * The request manager is configured using the Component Manager configuration mechanism. For Plexus this is through a component.xml file located in META-INF/plexus. The configuration defines the different components to use for the different actions. For example: <components> <component> <role>org.xwiki.request.Action</role> <implementation>org.xwiki.request.ViewAction</implementation> <configuration> <action>view</action> <order>100</order> </configuration> </component> ... </components> Note: The order is there so that it's possible for non-core components to contribute Actions. For example this is useful for the ZipExplorer component which will contribute a ZipExplorerDownloadAction which should be executed before the default DownloadAction. * Other details: We'll have a XWikiRequest and a XWikiResponse classes and a URL Handler component and a XWikiURL class. * Here's an example of how an Action will be coded: public class MyAction implements Action { private XWikiRequest request; private XWikiSession session; public XWikiResponse execute() { ... } } The request and session object in this example are being injected automatically by the CM. * There are 2 kinds of configuration: static configuration like the one shown above for registering action names and order for Actions and user configuration (the one we currently have in xwiki.cfg). For user configuration we can have a Configuration component or even better have the config properties automatically injected in the component so that the component writer would one write: private List plugins; (in that case the mapping between "plugins" and the xwiki.plugins property would be defined in components.xml) * For logging, we can have define our own LoggerManager component and tell the CM to use it by registering it in plexus.xml. This will allow not to depend on any specific CM for logging (otherwise we would get a org.plexus.logger.Logger object). To summarize, with this proposal there are only 2 classes that depend on the CM: - the servlet context initializer - the main servlet which is just using the CM to call the Request Manager. WDYT? For OSGi lovers, how would you implement this in OSGi? Thanks -Vincent

18 years, 2 months

1
0
0 0

removePage() XMLRPC not implemented ?

by tharindu jayasuriya

Hi All, I implemented the Boolean removeSpace(String token, String spaceKey)<http://confluence.atlassian.com/display/DOC/Remote+API+Specification> XML-RPC and executed that method. Then I got get an exception saying, "No such handler: confluence1.removePage". It seems like that removePage XMLRPC does not seem to be implemented on the server. Any help for this concern is highly appriciated. Here is the full stack-trace..................... org.apache.xmlrpc.XmlRpcException: No such handler: confluence1.removePage at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse( XmlRpcStreamTransport.java:184) at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest( XmlRpcStreamTransport.java:145) at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest( XmlRpcHttpTransport.java:94) at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest( XmlRpcSunHttpTransport.java:39) at org.apache.xmlrpc.client.XmlRpcClientWorker.execute( XmlRpcClientWorker.java:53) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java :166) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java :157) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java :146) at org.xwiki.plugins.eclipse.rpc.impl.XWikiRPCHandler.rpcCall( XWikiRPCHandler.java:79) at org.xwiki.plugins.eclipse.rpc.impl.XWikiRPCHandler.removePage( XWikiRPCHandler.java:146) at org.xwiki.plugins.eclipse.model.impl.XWikiSpace.removeChildPage( XWikiSpace.java:408) at org.xwiki.plugins.eclipse.model.wrappers.XWikiSpaceWrapper$3.run( XWikiSpaceWrapper.java:271) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run( ModalContext.java:113) Thanks -Tharindu

18 years, 2 months

3
7
0 0

Notice: 1.1M4 is the last release before the RCs

by Vincent Massol

Hi, Just wanted to remind everyone that 1.1M4 is the last release planned before the 1.1 RCs. Thus if you have some code you wish to see in 1.1 you'll need to get it before end of July (1.1M4 release date). Thanks -Vincent

18 years, 2 months

1
0
0 0

Fwd: XWiki-Eclipse Plug-in Source Code Review.

by tharindu jayasuriya

For some reason this mail didn't go through. Sorry if you receive it twice.. - Tharindu ---------- Forwarded message ---------- From: tharindu jayasuriya <djtharindu(a)gmail.com> Date: Jul 13, 2007 1:37 PM Subject: XWiki-Eclipse Plug-in Source Code Review. To: xwiki-dev(a)objectweb.org Hi Vincent, We have cleaned up our source code and we're ready for a review. I have attached the eclipse project at, http://jira.xwiki.org/jira/browse/XECLIPSE-11 Looking forward to hear from you. Any comments that would help us improve our code are really appreciated. We'll start to implement the rest of the features allocated for R!.0M1 from now on. Thank you all. - Tharindu & Asiri

18 years, 2 months

1
0
0 0

New XWiki Syntax Guide

by Vincent Massol

Hi everyone, Just wanted to let you know I have completely rewritten the XWiki Syntax Guide. It's available at: http://www.xwiki.org/xwiki/bin/view/UserGuide/XWikiSyntax Please let me know if you think anything is missing or not correct. That'll help improve it. Thanks -Vincent

18 years, 2 months

2
1
0 0

Curriki database build (was Re: [xwiki-commits] r3966 - in xwiki-products/curriki/trunk: . gwt/src/main/java/org/curriki/gwt/client gwt/src/main/java/org/curriki/gwt/client/widgets/addfile gwt/src/main/java/org/curriki/gwt/client/wizard gwt/src/main/java/org/curriki/gwt/server web/src/main/webapp/skins/curriki8)

by Vincent Massol

Hi David, On Jul 13, 2007, at 12:41 AM, David Ward wrote: > Author: dward > Date: 2007-07-13 00:41:40 +0200 (Fri, 13 Jul 2007) > New Revision: 3966 > > Added: > xwiki-products/curriki/trunk/gwt/src/main/java/org/curriki/gwt/ > client/widgets/addfile/URLEntry.java > xwiki-products/curriki/trunk/gwt/src/main/java/org/curriki/gwt/ > client/widgets/addfile/VidiTalkUpload.java > xwiki-products/curriki/trunk/gwt/src/main/java/org/curriki/gwt/ > client/widgets/addfile/VidiTalkUploadDialog.java > Modified: > xwiki-products/curriki/trunk/gwt/src/main/java/org/curriki/gwt/ > client/Constants.java > xwiki-products/curriki/trunk/gwt/src/main/java/org/curriki/gwt/ > client/CurrikiService.java > xwiki-products/curriki/trunk/gwt/src/main/java/org/curriki/gwt/ > client/CurrikiServiceAsync.java > xwiki-products/curriki/trunk/gwt/src/main/java/org/curriki/gwt/ > client/widgets/addfile/AddFileDialog.java > xwiki-products/curriki/trunk/gwt/src/main/java/org/curriki/gwt/ > client/wizard/AddFileWizard.java > xwiki-products/curriki/trunk/gwt/src/main/java/org/curriki/gwt/ > server/CurrikiServiceImpl.java > xwiki-products/curriki/trunk/pom.xml > xwiki-products/curriki/trunk/web/src/main/webapp/skins/curriki8/ > macros.vm > Log: > - Add VIDITalk video asset creation to GWT code > - Center the VIDITalk playback component > - Allow compiling without database pieces (still has issues with > mysql) [snip] What's the problem? Thanks -Vincent > Modified: xwiki-products/curriki/trunk/pom.xml > =================================================================== > --- xwiki-products/curriki/trunk/pom.xml 2007-07-12 20:36:23 UTC > (rev 3965) > +++ xwiki-products/curriki/trunk/pom.xml 2007-07-12 22:41:40 UTC > (rev 3966) > @@ -41,14 +41,30 @@ > <developerConnection>scm:svn:svn+ssh://svn.forge.objectweb.org/ > svnroot/xwiki/xwiki-applications/curriki/trunk</developerConnection> > <url>http://svn.forge.objectweb.org/cgi-bin/viewcvs.cgi/xwiki/ > xwiki-applications/curriki/trunk</url> > </scm> > - <modules> > - <module>plugins</module> > - <module>gwt</module> > - <module>web</module> > - <module>wiki</module> > - <module>database</module> > - <module>distribution</module> > - </modules> > + <profiles> > + <profile> > + <id>default</id> > + <activation> > + <activeByDefault>true</activeByDefault> > + </activation> > + <modules> > + <module>plugins</module> > + <module>gwt</module> > + <module>web</module> > + <module>wiki</module> > + <module>database</module> > + <module>distribution</module> > + </modules> > + </profile> > + <profile> > + <id>curriki-nodb</id> > + <modules> > + <module>plugins</module> > + <module>gwt</module> > + <module>web</module> > + </modules> > + </profile> > + </profiles> > <build> > <extensions> > <extension>

18 years, 2 months

1
0
0 0

Removing the Navigation panel

by Vincent Massol

Hi, Yesterday, we had a discussion on IRC about removing the Navigation panel from right menu in the default XE menu. We all (Sergiu, Marta, Catalin and me) agree to remove it and thus I've gone ahead with it and it's now removed. With this email I'd like to make sure this is ok with everyone. I have added a new Panel called Quick Links which presents links to the most important pages on the wiki. Now I'm having some second thoughts. The Quick Links is great to navigate in the default wiki. The issue I have is the following: - We have a Create Panel and thus users are going to use it to create pages. This means their pages are not going to be linked from an existing page and thus the only way to browse them will be either though the Search or through the Index page/Treeview page. I think this is not enough as it's too long to require users to click on Index and search for their pages to access them. Of course they should create a navigation (as we're doing on xwiki.org for example) but they might need some practices before realising this. I think I'd be ok to add again the Navigation panel but we should exclude by default all the pages that have a quick links. WDYT? Any better idea? <some time pass/> Ah I have another idea. We could have a Navigation Panel showing pages that have no link to them (we need that anyway and we need to add that to the AllDocs page too). In that way any page that is linked could be accessed through their navigation and pages that are not linked can still be accessed easily. This should try to encourage users to create navigations without penalizing them . WDYT? Thanks -Vincent PS: I've just had an idea and I think it would be a killer feature... :) What about adding a shortcut so that on any page you can type ctrl+P (or ctrl+D or whatever other shortcut) and it would present a text field in the middle of the page allowing you to enter the name of the page you want to navigate to. It would work exactly as it works on IntelliJ IDEA (Ctrl+N) so you can type some letters and it'll propose pages. Even better, if the user hits the right arrow key, it would provide some actions for that page: view, edit, rename, delete with view being the default action so ctrl+P + Enter opens the page in view mode and ctrl+P + right arrow + down arrow + Enter opens the page in edit mode, etc. I'm very excited by the idea... WDYT?

18 years, 2 months

3
4
0 0

XEM and Curriki duplicates

by Vincent Massol

Hi, I've noticed that the curriki and xem project duplicate a lot of content from the XE wiki. Just to give an example: - XWiki.Results - Admin.CopyDocument XE is being improved almost daily and as these are copy XEM and Curriki are not improved on their side. Also if they make improvements to these pages XE won't benefit from them either. I think we should not duplicate pages unless they are modified by XEM or Curriki. And even when there are modifications we should discuss how we could refactor the page to have common parts shared. This could be achieved by splitting the page in 2, or by creating templates or by creating new APIs for example. WDYT? Thanks -Vincent

18 years, 2 months

1
0
0 0

Are there issues with the Maven build, or is it just me?

by Radu Danciu

For the last week or so, the build hasn't been working for me. I keep getting errors around the GWT Curriki part of the build. I thought it was something I did (I ctrl+c-ed out of the mvn install once), so I deleted the whole trunks-users from my drive, and svn co again. Tried mvn install then, and a new error pops up at about the same place: [INFO] Building XWiki Products - Curriki - Database [INFO] task-segment: [install] [INFO] ---------------------------------------------------------------------------- [INFO] [remote-resources:process] [INFO] [xwiki-build-xar:unxar] [INFO] [xwiki-packager:import] --------------------------------------------------- constituent[0]: file:/maven2/lib/maven-embedder-2.1-SNAPSHOT-ueber.jar constituent[1]: file:/Users/rhadoo/.m2/repository/com/xpn/xwiki/platform/xwiki-build-xar-handlers/1.1-SNAPSHOT/xwiki- build-xar-handlers-1.1-SNAPSHOT.jar --------------------------------------------------- Exception in thread "main" java.lang.OutOfMemoryError: Java heap space and it just freezes there, i have to force quit out of the terminal. I've updated the settings.xml to the latest version, and at this point I'm completely out of ideas. Help? Please? Radu

18 years, 2 months

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