xwiki-devs October 2008

xwiki-devs@xwiki.org

40 participants
133 discussions

[xwiki-devs] Porting xwiki-webdav to xwiki-core 1.7-SNAPSHOT

by Asiri Rathnayake

Hi, Currently xwiki-webdav is using xwiki-core 1.6-SNAPSHOT and it's working fine. But when it's changed to 1.7-SNAPSHOT (${pom.version}) I get the following exception : <dump> Caused by: com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: Failed to load component [org.xwiki.cache.CacheManager] for hint [default] at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:326) at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:387) at com.xpn.xwiki.plugin.webdav.utils.XWikiDavResourceFactory.initXWikiContext(XWikiDavResourceFactory.java:169) at com.xpn.xwiki.plugin.webdav.utils.XWikiDavResourceFactory.createResource(XWikiDavResourceFactory.java:113) </dump> The exception is thrown when the XWikiContext is being initialized. The code looks like bellow : <code> private void initXWikiContext(DavServletRequest drequest, DavServletResponse dresponse, ServletContext servletContext) throws XWikiException { XWikiEngineContext xwikiEngine = new XWikiServletContext(servletContext); XWikiRequest xwikiRequest = new XWikiServletRequest(drequest); XWikiResponse xwikiResponse = new XWikiXmlRpcResponse(dresponse); xwikiContext = Utils.prepareContext("", xwikiRequest, xwikiResponse, xwikiEngine); xwikiContext.setMode(XWikiContext.MODE_GWT); xwikiContext.setDatabase("xwiki"); ServletContainerInitializer containerInitializer = (ServletContainerInitializer) Utils.getComponent(ServletContainerInitializer.ROLE); try { containerInitializer.initializeRequest(xwikiContext.getRequest() .getHttpServletRequest(), xwikiContext); containerInitializer.initializeResponse(xwikiContext.getResponse() .getHttpServletResponse()); containerInitializer.initializeSession(xwikiContext.getRequest() .getHttpServletRequest()); containerInitializer.initializeApplicationContext(servletContext); } catch (ServletContainerException e) { throw new XWikiException(XWikiException.MODULE_XWIKI_PLUGINS, XWikiException.ERROR_XWIKI_INIT_FAILED, "Failed to initialize Request/Response or Session", e); } *XWiki xwiki = XWiki.getXWiki(xwikiContext);* // (This is where the exception get's thrown) </code> Can someone please help me with how to properly initialize the XWikiContext with 1.7-SNAPSHOT core ? Thanks. - Asiri

16 years, 2 months

[xwiki-devs] [Proposal] XE 1.7 Roadmap

by Vincent Massol

Hi there, Today is XE 1.6 release date so let's start planning for XE 1.7. Here are the dates (to reach a release for Javapolis 2008): - 1.7M1: 20th of October (that's more than 3 weeks after the 1.6 release) - 1.7M2: 10th of November (3 weeks after 1.7M1) - 1.7RC1: 17 Nov (one week after) - 1.7RC2 or final: 24 Nov (one week after) - 1.7 final (if needed): 1st of December Thus it's a short release (2 months). Proposed content: * Working and usable (i.e. users can use them for their day to day work instead of the old Syntax and old WYSIWYG editor) versions of new rendering and new WYSIWYG editor. (Vincent, Thomas, Marius) * Working JCR (can be used for day to day work instead of Hibernate). (Artem) * French XE (Jean-Vincent) * Blog revamping (Sergiu) * Webdav integration (Asiri) And bug fixes of course. Anything else planned? (I think we should be careful not to over commit). I'd like to have Office import too (Wang Ning) but I don't know how much time he'll get. Thanks -Vincent Note: I've updated http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap

16 years, 2 months

Re: [xwiki-devs] [xwiki-users] LDAP Authentiction -- Errors on LDAP Server for not doing a clean Bind and UnBind.

by sharanabasavaraj.x.mudgal＠jpmchase.com

Does anyone have any inputs on the issue below? Thanks. Sharan. sharanabasavaraj.x.mudgal(a)jpmchase.com Sent by: users-bounces(a)xwiki.org 10/16/2008 05:38 PM Please respond to XWiki Users <users(a)xwiki.org> To "XWiki Users" <users(a)xwiki.org> cc Subject [xwiki-users] LDAP Authentiction -- Errors on LDAP Server for not doing a clean Bind and UnBind. Hi! Thomas, There are errors we see on the ldap server on authenicating users with LDAP for XWiki. It is critical to fix this issue for us to be able to use xwiki. This is what seems to be happening. Normally when you do a 'DoBind' with a LDAP directory it establishes the connection after successful authentication. Once you establish the connection you may ask for information within the LDAP directory or simple logout with a 'DoUnbind'. Since you did not ask for any more information or issue a DoUnbind the LDAP directory tried to extend your session, which was eventually dropped. Also below is an example of a Bind with simple authentication and then an UnBind. we would like to see a 'DoUnbind' following a 'Dobind' when authenticating to the LDAP directory. Could you please advise. 10:48:27 B0EB7BB0 LDAP: New cleartext connection 0x8352b08 from x.x.x.x, monitor = 0x7ac4dbb0, index = 6 10:48:27 B32C0BB0 LDAP: (x.x.x.x)(0x0044:0x60) DoBind on connection 0x8352b08 10:48:27 B32C0BB0 LDAP: (x.x.x.x)(0x0044:0x60) Bind name:cn=abc,ou=xyz, version:3, authentication:simple 10:48:27 B32C0BB0 LDAP: (x.x.x.x)(0x0044:0x60) Sending operation result 0:"":"" to connection 0x8352b08 10:48:27 B32C0BB0 LDAP: (x.x.x.x)(0x0044:0x60) Operation 0x44:0x60 on connection 0x8352b08 completed in 0 seconds 10:48:27 7FBC5BB0 LDAP: (x.x.x.x)(0x0045:0x77) DoExtended on connection 0x8352b08 10:48:27 7FBC5BB0 LDAP: (x.x.x.x)(0x0045:0x77) DoExtended: Extension Request OID: 0.0.0.0 10:48:27 7FBC5BB0 LDAP: (x.x.x.x)(0x0045:0x77) Unable to find extension handler 0.0.0.0 in extension list 10:48:27 7FBC5BB0 LDAP: (x.x.x.x)(0x0045:0x77) Sending operation result 2:"":"Unrecognized extended operation" to connection 0x8352b08 10:48:27 7FBC5BB0 LDAP: (x.x.x.x)(0x0045:0x77) Operation 0x45:0x77 on connection 0x8352b08 completed in 0 seconds Trace Example 'Successful Bind and UnBind' 14:06:54 B0AB6BB0 LDAP: New TLS connection 0x838b948 from x.x.x.x, monitor = 0x969a4bb0, index = 6 14:06:54 969A4BB0 LDAP: Monitor 0x969a4bb0 initiating TLS handshake on connection 0x838b948 14:06:54 89F1EBB0 LDAP: (x.x.x.x)(0x0000:0x00) DoTLSHandshake on connection 0x838b948 14:06:54 89F1EBB0 LDAP: (x.x.x.x)(0x0000:0x00) Completed TLS handshake on connection 0x838b948 14:06:54 4C1FFBB0 LDAP: (x.x.x.x)(0xca72:0x60) DoBind on connection 0x838b948 14:06:54 4C1FFBB0 LDAP: (x.x.x.x)(0xca72:0x60) Bind name:cn=abc,ou=xyz,, version:3, authentication:simple 14:06:54 4C1FFBB0 LDAP: (x.x.x.x)(0xca72:0x60) Sending operation result 0:"":"" to connection 0x838b948 14:06:54 4C1FFBB0 LDAP: (x.x.x.x)(0xca72:0x60) Operation 0xca72:0x60 on connection 0x838b948 completed in 0 seconds 14:06:54 8CB10BB0 LDAP: (x.x.x.x)(0xca73:0x42) DoUnbind on connection 0x838b948 14:06:54 8CB10BB0 LDAP: Connection 0x838b948 closed Thanks. Sharan. ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.

16 years, 2 months

[xwiki-devs] Building XWiki from sources

by Firvin

I tried to build xwiki from sources. Since the build system is powered by maven it shouldn't be a problem ;-) I've added all xwiki repositories and the google web toolkit repositories as described in http://dev.xwiki.org/xwiki/bin/view/Community/Building. But I cannot get the maven-googlewebtoolkit2-plugin artifact. The build stops with the following error message: Reason: POM 'com.totsp.gwt:maven-googlewebtoolkit2-plugin' not found in repository: Unable to download the artifact from any repository com.totsp.gwt:maven-googlewebtoolkit2-plugin:pom:1.5.3 If you point your webbrowser to the google maven repository at http://gwt-maven.googlecode.com/svn/trunk/mavenrepo/ there is only the new 2.0 version inside the maven-2 repository structure. The old 1.5.3 version is only accessible in the maven-1 repository structure. Well, to cut a long story short the question is: How can I resolve this specific artifact? Thanks in advance Firvin -- View this message in context: http://n2.nabble.com/Building-XWiki-from-sources-tp1351482p1351482.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years, 2 months

[xwiki-devs] Where to host new version of FoXWiki ?

by Asiri Rathnayake

Hi Devs, As you might know, to complete the integration of xwiki-webdav component in the XWiki-UI (that is to allow users to edit attachments via webdav), we needed some support from FoXWiki (on FireFox). Now comes the problem of where to host FoXWiki. NOTE : We need a download link to FoXWiki that we can embed inside one of our js files that will trigger an automatic installation. So, we must host FoXWiki somewhere before providing webdav functionalities in xwiki UI. So, we have two options : 1. Host FoXWiki in addons.mozilla.org :- With this option, we don't need to worry about automatic updates (it is automatically handled) and there is a nice web interface that allows us to manage various versions. But the downside is, each version need to spend some time on the sandbox (of addons.mozilla.org) before it becomes public - some users need review and rate it. Ex : https://addons.mozilla.org/en-US/firefox/addon/2358 2. In xwiki.org :- With this option we have to handle everything manually and we need to provide an update url (which has to be an https url) which will contain information about updates. The good side of this is that there is no waiting with this approach. Any ideas about which approach to be taken ? Thanks. - Asiri

16 years, 2 months

[xwiki-devs] 2 XWiki guys coming to Silicon Valley next week

by Ludovic Dubost

Hi, We'll be two XWiki guys in the valley Monday <-> Wednesday. Anybody interested in a meetup on monday or tuesday evening ? Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

16 years, 2 months

[xwiki-devs] Problem with context initialization in the XMLRPC subsystem

by Fabio Mancinelli

Dear all, I am taking advantage of the weekend in order to work on XEclipse's release. However I've just found a problem on the server side. While doing some tests using all XWiki versions, when I try to connect to XWiki 1.6 I get this exception: http://pastebin.com/m49b769bd Other XWiki versions work fine. Tests seems to be fine on hudson so I don't know why I am getting this exception when testing against the packaged hsqldb.zip version. Any clue? -Fabio

16 years, 2 months

[xwiki-devs] [ANN] XWiki Workspaces 1.1.1 released

by Jerome Velociter

The XWiki development team is pleased to announce the release of XWiki Workspaces 1.1.1 Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This is a bug-fix release. It does correct the following bugs : * XWS-176 - Cannot access history of a wiki page when only "reader" * XWS-183 - When creating a space, sample wiki page and blog post last modification date is not updated * XWS-184 - Events from archived spaces do appear on dashboards and are clickables * XWS-188 - When we attach a new image in an existing gallery, in the activity stream the message is "created" when it should be "updated" * XWS-190 - On dashboards, the links to photo gallery images lead to an empty page For more information see the Release Notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesWorkspaces111 Regards -The XWiki dev team

16 years, 2 months

[xwiki-devs] [VOTE] Release XWiki Workspaces 1.1.1

by Jerome Velociter

Hello Devs, I would like to release XWiki Workspaces 1.1.1, which will bring fixes for the following issues : http://jira.xwiki.org/jira/secure/ReleaseNote.jspa?version=10863&styleName=… My +1 Regards, Jerome

16 years, 2 months

[xwiki-devs] JSX extension: proposition for passing custom parameters to JS code with velocity parsing

by Pascal Voitot

hello, I finally found the way of using JSX with Velocity variables :) I was defining the custom Velocity variables in the doc containing the JSX object and it doesn't work. These variables must be defined inside the JSX object code because the Velocity context is specific to this code interpretation. But in my case, I really need to use $xwiki.jsx.use() with some custom parameters since my javascript requires this customization to work. Basic velocity context with $xwiki, $doc etc... is too blank to help me. I think being able to pass some custom parameters to JSX could be really practical in many cases (as explained in the http://dev.xwiki.org/xwiki/bin/view/Design/SkinExtensions) Don't see very big security issues but you may find some :) I propose to manage this using simple HTTP parameters while calling jsx.use() in order to provision the $request velocity variable with custom parameters. For example: $xwiki.jsx.use("myJSXdoc?param1=value1&param2=value2&param3=value3") Then in myJSXdoc, you create a JSX object with code looking like: #set($param1 = $request.get("param1")) #set($param2 = $request.get("param2")) #set($param3 = $request.get("param3")) doit() { dosomething("${param1}"); dosomething2("${param2}"); dosomething3("${param3}"); } The code patch is really simple. Just a modification of: public String getLink(String documentName, XWikiContext context) in skinx.jsSkinExtensionPlugin in order to create a link such as: <script src=" /xwiki/bin/jsx/myspace/myJSXdoc?param1=value1&param2=value2&param3=value3" type="text/javascript"> regards Pascal

16 years, 2 months

← Newer
1
2
3
4
5
6
7
8
9
...
14
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 October 2008