xwiki-devs March 2008

xwiki-devs@xwiki.org

52 participants
193 discussions

Re: [xwiki-devs] compilation errors in com.xpn.xwiki.objects.classes.*

by Kamna Jain

Hello Pascal, I had the ecs-1.4.2.jar file in ecs/ecs/1.4.2 and also these 2 files - ecs-1.4.2.pom, ecs-1.4.2.pom.sha1. But I deleted that entire folder and ran maven again. It worked. :-) Thanks.... Can you tell me what does "xwiki-core-1.2-rc-1.jar" contain and how is it different from "xwiki-core-1.3-SNAPSHOT.jar" Both these jars are present in the "\XWiki Enterprise\webapps\xwiki\WEB-INF\lib" If I replace both of these with the "xwiki-core-1.4-SNAPSHOT.jar" that was created as a result of the build, I get ClassDef not found error for the org.observation.event class But, it works if I just replace the 1.3 snapshot with 1.4 snapshot. Is that how it is supposed to behave. what is "xwiki-core-1.2-rc-1.jar" for? Thanks

16 years, 5 months

[xwiki-devs] compilation errors in com.xpn.xwiki.objects.classes.*

by Kamna Jain

Hello, Thanks for the input on setting the proxy in my settings.xml. That WAS the problem. Now I am building xwiki-core and trying to resolve errors as I get them. Finally, I have reached the stage where the "target" folder gets created but, I am running into these errors and others like this: \xwiki-platform-core\xwiki-core\src\main\java\com\xpn\xwiki\objects\classes\NumberCla ss.java:138:0::0 input cannot be resolved to a type error at input input2 = new input(); \xwiki-platform-core\xwiki-core\src\main\java\com\xpn\xwiki\objects\classes\NumberCla ss.java:149:0::0 input cannot be resolved to a type error at input input2 = new input(); \xwiki-platform-core\xwiki-core\src\main\java\com\xpn\xwiki\objects\classes\GroupsCla ss.java:107:0::0 select cannot be resolved to a type error at option option = new option(display, value); \xwiki-platform-core\xwiki-core\src\main\java\com\xpn\xwiki\objects\classes\GroupsCla ss.java:143:0::0 option cannot be resolved to a type error at option option = new option(display, value); and more like these...Can anybody point out whats going wrong here. Thanks

16 years, 5 months

[xwiki-devs] Away till Tuesday

by Vincent Massol

Hi, Just wanted to let you know that I'll be away till Tuesday night. This wasn't planned and came up unexpectedly so I'm sorry for the short notice. I'll try to be connected in the evenings though. I'm also trying to fix the Velocity issue right now (although I'm having a hard time to understand the pb so far). Thanks -Vincent

16 years, 5 months

[xwiki-devs] [VOTE] Integrate activitystream plugin in platform-plugins/

by Jerome Velociter

Hello devs, I propose we integrate the activitystream plugin developed for the curriki product the into platform plugins. The plugin provides a notification rule that records doc changes events into dedicated tables in the db, methods to retrieve such events (on a per space basis, or per user basis) + methods to get RSS feeds from those streams. The plugin is not curriki-specific, and provides a "framework" to implement product-specific streams. (see currikiactivitystream plugin as a example). Steps I'm planning to take to integrate the plugin : - Rename its packages (to match XWiki naming strategy) - Write javadoc for it/apply checkstyle - Document its use on code.xwiki.org Here is my +1 to do this. (Note: a goal behind this move is also being able to use the plugin in XWiki Workspaces). Jerome.

16 years, 5 months

[xwiki-devs] collaborating with a project

by Harsha Halgaswatta

Dear all I am a level 3 Computer Science and Engineering undergraduate at University of Moratuwa,Sri Lanka.Currently i have almost finished implementing a member section at E-channelling (pvt) Ltd which is the market leader of health care system upon online channel booking system and first listed company in Colombo stock exchange.I developed this project from the scratch using STRUTS2 web framework.I am now fairly familiar those areas passionating specially on JAVA. I am really interesting in doing a project upon XWiki.Indeed a review application. Here i have understood that it would better to devide this review application into two portions.first one is indeed the user interactivity portion .In this case i hope to develop the review mode of client portion (adding reviews,with anchoring facility) just by clicking on a spot on the document. Then the second portion is author portion,It is the case whenever the author of a particular document wants to see reviews for his stuff he should be in a position to list up all the reviews in a regular way and takes suitable action accordingly while accessing each and every reviews without a mesh. Is their any different idea apart from what i have intended above,if so pl let me know. I am still trying to familiarize with XWiki platform cheers harsha(hala)

16 years, 5 months

[xwiki-devs] Problems with setting Maven (Can't get artifact..)

by Kamna Jain

Hello Pascal, This is what happens when I try to build. I am running into the same error (even if I use -nsu clean install) [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-remote-resources-plugin Version: 1.0-beta-2 Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-remote-resources-plugin:pom:1.0-beta-2 from the specified remote repositories: xwiki-releases (http://maven.xwiki.org/releases), central (http://repo1.maven.org/maven2), xwiki-plugins-snapshots (http://maven.xwiki.org/snapshots), xwiki-snapshots (http://maven.xwiki.org/snapshots), xwiki-externals (http://maven.xwiki.org/externals), xwiki-plugins-releases (http://maven.xwiki.org/releases), xwiki-plugins-externals (http://maven.xwiki.org/externals) [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2 minutes 6 seconds [INFO] Finished at: Thu Mar 27 11:38:44 CDT 2008 [INFO] Final Memory: 1M/3M [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2 minutes 6 seconds [INFO] Finished at: Thu Mar 27 11:38:44 CDT 2008 [INFO] Final Memory: 1M/3M [INFO] ------------------------------------------------------------------------

16 years, 5 months

[xwiki-devs] Unable to login Xwiki with IE explorer

by ashok.code

Hi All, I am new to Xwiki, I am having this strange problem with Xwiki i am unable to login using IE 6 but by Mozilla it is working fine, i am using wiki(1.3.8295) with MYSQL 5 with Tomcat 5.5.26 in Linux platform, but when deploying it on Window XP and with same database and web server it is working fine. For both mozilla and IE 6. Please any information on this very much beneficial. Thanking You Ashok Gupta -- View this message in context: http://www.nabble.com/Unable-to-login-Xwiki-with-IE-explorer-tp16300805p163… Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years, 5 months

[xwiki-devs] Session Error?

by Squirrel

Hi, This morning I saw instead of my XWiki an error page: [Wed Mar 26 15:03:22 2008] [error] [client xx.xx.xxx.xxx] proxy: Error > reading from remote server returned by /xwiki/bin/view/Main/WebHome > [Wed Mar 26 15:04:29 2008] [error] [client xx.xx.xxx.xxx] proxy: error > reading status line from remote server xx.xxx.xxx.xxx In my Tomcat log-file: 2008-03-26 04:18:14,396 [ > http://xx.xxx.xxx.xxx/xwiki//bin/skin/skins/toucan/images/panel-v.png] > [http-8082-Processor25] WARN xwiki.XWiki - Request > URI [/xwiki//bin/skin/skins/toucan/images/panel-v.png] should have matched > context path [/xwiki] and servlet path [/bin] > 2008-03-26 13:49:52,219 [http://xx.xxx.xxx.xxx/xwiki//bin/view/Main/] > [http-8082-Processor22] WARN xwiki.XWiki - Request > URI [/xwiki//bin/view/Main/] should have matched context path [/xwiki] and > servlet path [/bin] > 2008-03-26 13:49:52,220 [http://xx.xxx.xxx.xxx/xwiki//bin/view/Main/] > [http-8082-Processor22] WARN xwiki.MyPersistentLoginManager - Login > cookie validation hash mismatch! Cookies have been tampered with > 2008-03-26 13:49:52,220 [http://xx.xxx.xxx.xxx/xwiki//bin/view/Main/] > [http-8082-Processor22] WARN xwiki.MyPersistentLoginManager - Login > cookie validation hash mismatch! Cookies have been tampered with > 2008-03-26 13:49:52,284 [http://xx.xxx.xxx.xxx/xwiki//bin/view/Main/] > [http-8082-Processor22] WARN xwiki.MyPersistentLoginManager - Login > cookie validation hash mismatch! Cookies have been tampered with > 2008-03-26 13:49:52,284 [http://xx.xxx.xxx.xxx/xwiki//bin/view/Main/] > [http-8082-Processor22] WARN xwiki.MyPersistentLoginManager - Login > cookie validation hash mismatch! Cookies have been tampered with > 2008-03-26 13:49:52,352 [http://xx.xxx.xxx.xxx/xwiki//bin/view/Main/] > [http-8082-Processor22] WARN web.XWikiAction - Uncaught > exception: Error number 0 in 11: Uncaught exception > Wrapped Exception: 8192 > com.xpn.xwiki.XWikiException: Error number 0 in 11: Uncaught exception > Wrapped Exception: 8192 > at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:214) > 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:869) > at > org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection > (Http11BaseProtocol.java:664) > 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) > > > Wrapped Exception: > > > java.lang.ArrayIndexOutOfBoundsException: 8192 > at org.apache.coyote.http11.InternalOutputBuffer.write( > InternalOutputBuffer.java:720) > at org.apache.coyote.http11.InternalOutputBuffer.write( > InternalOutputBuffer.java:627) > at org.apache.coyote.http11.InternalOutputBuffer.sendHeader( > InternalOutputBuffer.java:497) > at org.apache.coyote.http11.Http11Processor.prepareResponse( > Http11Processor.java:1615) > at org.apache.coyote.http11.Http11Processor.action( > Http11Processor.java:962) > at org.apache.coyote.Response.action(Response.java:180) > at org.apache.coyote.http11.InternalOutputBuffer.doWrite( > InternalOutputBuffer.java:572) > at org.apache.coyote.Response.doWrite(Response.java:559) > at org.apache.catalina.connector.OutputBuffer.realWriteBytes( > OutputBuffer.java:361) > at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java > :433) > at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:348) > at org.apache.catalina.connector.OutputBuffer.writeBytes( > OutputBuffer.java:392) > at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java > :381) > at org.apache.catalina.connector.CoyoteOutputStream.write( > CoyoteOutputStream.java:88) > at org.apache.catalina.connector.CoyoteOutputStream.write( > CoyoteOutputStream.java:82) > at com.xpn.xwiki.web.Utils.parseTemplate(Utils.java:132) > at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:199) > 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:869) > at > org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection > (Http11BaseProtocol.java:664) > 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) I didn't change anything, I was asleep (-6 hours/timezone). Is that a session-error? After I deleted my cache, everything went back to normal...

16 years, 5 months

[xwiki-devs] [proposal] Authentication cookie handling

by Sergiu Dumitriu

Hi devs, There seems to be a problem with the way the login cookies are handled in the latest code. The problem was introduced in order to fix XWIKI-1655, XE-91 and similar issues. The failing scenario was: - wiki A sending cookies for .company.com - wiki B sending cookies for my.company.com - Login in wiki A with a user that doesn't exist in wiki B - Access wiki B and try to login The user will not be able to login on wiki B, unless he logouts from wiki A, changes the browser, or manually removes the cookies. This is caused by the fact that both cookies will be sent by the client, and XWiki uses only the first value found. My initial fix was to remove cookies from all possible domain names matching the current URL, so when accessing www.my.wiki.net, on login invalidation the server would send cookie removal requests from the following domains: <empty>, "www.my.wiki.net", "my.wiki.net", "wiki.net". However, this causes problems because container implementations are wrong. The cookie spec says that a server can request at least as much as 20 cookies for each domain, and each cookie should support at least 4096 bytes. While we do stay in these limits, containers allow only 4096 bytes for ALL cookies sent in one request, instead of 4096 for each cookie (tomcat allows 8192). And when using a domain name with many dots inside, there's an exception that prevents the page from being displayed. Because we can't change the containers, we have to find another solution. I have improved the current code a bit, by: - removing duplicate calls to forgetLogin (yep, containers are stupid enough not to check if the same cookie was set more than once) - if there were no cookies, don't request to remove them (yep, XWiki did that) - using not the first value found for a cookie, but the last one, as most popular browsers send cookie in the order they were set, so in the example above the cookies set by wiki B will be picked instead of those set by wiki A (this flips which browsers fail the above scenario, for example now it works on FF and Safari, but fails on Links and Opera) I could still improve: - override ServletResponse to detect duplicate cookies - remove only some of the cookies (username and password), as the other cookies alone cannot be used Still, this is not enough to ensure that the 4096 limit will never be reached. If there's a really long domain name, say with 10 dots, then there will be too many cookies. Thus, I propose to revert this exhaustive cookie removal. While this will imply that the scenario above will continue to fail on some browsers, I think that this scenario shows an administration error, and not an XWiki error. Either wiki B should be a virtual wiki, or wiki A should not set cookies for all the subdomains. Ludovic suggested another fix, which is to prefix cookie names with the domain name. I don't like this option very much for the default behavior. I agree that it should be an optional feature. So, my proposal is to: - revert the exhaustive cookie removal, and stick to the old behavior (remove cookies for the <empty> domain and the configured cookieDomain, if any) - add a cookiePrefix parameter WDYT? -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 5 months

Re: [xwiki-devs] [xwiki-notifications] r8703 - xwiki-platform/core/trunk/xwiki-core/src/main/resources

by Artem Melentyev

Hi, Sergiu. 1. lazy="true" should be in <property>. (eclipse validation fails) 2. lazy feature is working while session is open. So only in storage level. If we'll call DeletedAttachment#getXml() or #restoreAttachment outside store, we'll get a exception. This is very bad. That is why I've separated XWikiRCSNode into RCSInfo and RCSContent. Maybe there is another way to accomplish this? I think we need not lazy for DeletedAttachment now. sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2008-03-27 02:51:12 +0100 (Thu, 27 Mar 2008) > New Revision: 8703 > > Modified: > xwiki-platform/core/trunk/xwiki-core/src/main/resources/xwiki.derby.hbm.xml > xwiki-platform/core/trunk/xwiki-core/src/main/resources/xwiki.hbm.xml > xwiki-platform/core/trunk/xwiki-core/src/main/resources/xwiki.oracle.hbm.xml > Log: > XWIKI-2254: Attachment recycle bin > XWIKI-37: Deleted attachments not accessible via document history > Added hibernate mapping > <snip> > +  > +  > + <property name="xml" type="text"> > + <column name="XDA_XML" sql-type="clob" not-null="true" length="1000000000" lazy="true" /> > + </property> -- Artem Melentyev

16 years, 5 months

← Newer
1
2
3
4
5
6
7
8
...
20
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs March 2008