xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] [REQUEST] Help us make FoXWiki public.

by Asiri Rathnayake

Hi All, We need your support to make FoXWiki a public extension at addons.mozilla.org. The new version of FoXWiki includes all the features of previous version plus support for webdav. All you need to do is to try out new FoXWiki and rate / review the extension. Steps : 1. You need to have an account at addons.mozilla.org (this is the ugly part) 2. login to addons.mozilla.org and install https://addons.mozilla.org/en-US/firefox/addon/2358 3. Test FoXWiki using our test server located @ http://91.121.237.216/xwiki/bin/view/Main/ (Refer to screenshots provided at the plugin's location) 4. Rate / Review the extension :) Please keep in mind that webdav support is not yet included in official XE releases. Let us know if you have any trouble. Thanks. - Asiri ps : Introduction to FoXWiki (old) : http://soal.xwiki.com/xwiki/bin/view/Code/FoXWiki

16 years, 3 months

[xwiki-devs] Milton (webdav)

by Vincent Massol

This should interest Asiri: http://www.theserverside.com/news/thread.tss?thread_id=50906 " Milton is an open source java library for implementing desktop integration in your web apps with WEBDAV. For those not familiar with WEBDAV, its like FTP but implemented in HTTP. Its a mature standard and supported natively in all operating systems. Once integrated, your users can view and/or manipulate remote data in your application using drag and drop of files and folders in their native OS file browser - eg Windows Explorer, Nautilus, etc, over HTTP. Milton is agnostic of the nature of your data and can be used with any type of persistence mechanism, including hibernate, JPA, etc. Milton can be integrated easily into most web apps by implementing a Resource interface and a ResourceFactory, and adding the Milton servlet to web.xml. Milton allows you to specify which http methods to support (eg DELETE, PUT, MKCOL, etc). HTTP authentication and authorisation are delegated to your application logic. Milton is not bound to the Servlet API, so it can easily be integrated into alternative web servers. " Note: I'm not saying we should move to that. Just that we need to keep it in our radar and decide at some point if it's better or not better than the jackrabbit api we're using. Thanks -Vincent

16 years, 3 months

Re: [xwiki-devs] [xwiki-notifications] r13788 - in sandbox/microsoft-office-add-ins: . XWikiLib XWikiLib/Clients XWikiLib/Properties XWriter XWriter/Properties

by Vincent Massol

Hi Florin, Could you please always enter a commit log and also a JIRA issue reference? Thanks -Vincent On Oct 22, 2008, at 6:07 PM, fciubotaru (SVN) wrote: > Author: fciubotaru > Date: 2008-10-22 18:07:19 +0200 (Wed, 22 Oct 2008) > New Revision: 13788 > > Added: > sandbox/microsoft-office-add-ins/XWikiLib/ > sandbox/microsoft-office-add-ins/XWikiLib/Clients/ > sandbox/microsoft-office-add-ins/XWikiLib/Clients/IXWikiClient.cs > sandbox/microsoft-office-add-ins/XWikiLib/Clients/XWikiHTTPClient.cs > sandbox/microsoft-office-add-ins/XWikiLib/Clients/XWikiSOAPClient.cs > sandbox/microsoft-office-add-ins/XWikiLib/Clients/ > XWikiXMLRPCClient.cs > sandbox/microsoft-office-add-ins/XWikiLib/Properties/ > sandbox/microsoft-office-add-ins/XWikiLib/Properties/AssemblyInfo.cs > sandbox/microsoft-office-add-ins/XWikiLib/Properties/ > Settings.Designer.cs > sandbox/microsoft-office-add-ins/XWikiLib/Properties/ > Settings.settings > sandbox/microsoft-office-add-ins/XWikiLib/XWikiLib.csproj > sandbox/microsoft-office-add-ins/XWikiLib/app.config > sandbox/microsoft-office-add-ins/XWriter/XWikiTaskPane.cs > sandbox/microsoft-office-add-ins/XWriter/XWikiTaskPane.designer.cs > sandbox/microsoft-office-add-ins/XWriter/XWikiTaskPane.resx > Removed: > sandbox/microsoft-office-add-ins/XWriter/XWiki/ > Modified: > sandbox/microsoft-office-add-ins/MS Office Add-ins.sln > sandbox/microsoft-office-add-ins/XWriter/ > sandbox/microsoft-office-add-ins/XWriter/Properties/AssemblyInfo.cs > sandbox/microsoft-office-add-ins/XWriter/XWikiAddIn.cs > sandbox/microsoft-office-add-ins/XWriter/XWriter.csproj > Log: > > > Modified: sandbox/microsoft-office-add-ins/MS Office Add-ins.sln [snip]

16 years, 3 months

[xwiki-devs] Hiding underlying documents behind management interfaces (was: Administration of Groups not valid since 1.6)

by Sergiu Dumitriu

Jean-Vincent Drean wrote: > Side developer note : I'd be in favor of removing the link on the > group name (see ** above), I think the RMUI should be self-sufficient, > the AJAX UI in the inline view of group pages is disturbing imho. WDYT > ? The question is how much do we target advanced developers versus normal users/administrators. The link is there so that somebody that knows XWiki well can go to the document and edit the objects, or manipulate in other ways the document holding the group. I guess that if there's an interface powerful and stable enough to render raw object editing useless, we could completely hide this kind of documents, not just from the RMUI, but from all other applications. After all, an advanced dev can always manually enter the right URL manually and go on from there. WDYT? -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 3 months

[xwiki-devs] [ANN] XWiki Enterprise Manager 1.4 released

by Thomas Mortagne

The XWiki development team is pleased to announce the release of XWiki Enterprise Manager 1.4. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This release is based on XWiki Enterprise 1.6.1. Changes from 1.3: * As usual the main news is on XE side (from 1.5.1 to 1.6.1) * Some UI improvements on information panels For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM14 Thanks -The XWiki dev team

16 years, 3 months

[xwiki-devs] [ANN] XWiki Enterprise 1.7 Milestone 1 Released

by Jean-Vincent Drean

The XWiki development team is pleased to announce the release of XWiki Enterprise 1.7 Milestone 1. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download First milestone of the XWiki Enterprise 1.7 version. Main changes: * Work in progress on the new XWiki Syntax v2.0 * XWiki Syntax 2.0 allow wiki syntax inside links * Work in progress on the new experimental WYSIWYG editor. Important bug fixes: * Saving a blank wiki page throws exception in Oracle * Registration is still possible when right to register for Unregistered user is explicit set to deny * Documents with name with spaces or other special chars can't properly save added image in WYSIWYG editor * Support of dots in ldap login has introduce a security hole Note that general goals for XWiki Enterprise 1.7 are: * 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. * Working JCR (can be used for day to day work instead of Hibernate). * French XE * Blog revamping * Webdav integration For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise17M1 Thanks, The XWiki dev team

16 years, 3 months

[xwiki-devs] [Proposal] GWT WYSIWYG - Macro handling behavior

by Vincent Massol

Hi Marius and everyone, Here's an idea of a specification for macro handling in the new wysiwyg editor: * Macros are rendered when displayed in the editor * There's an outline so that the user can see what content corresponds to a macro * When the cursor is inside a macro the background color is changed * Clicking on Edit Macro to edit the selected macro * There's a background thread running that re-renders the page (and thus the macro) every N seconds. We need this since the macro content depends on other content (for example the TOC macro will depend on sections, the velocity macro will depend on values set in other velocity macros, etc). We should also have a way to let the user refresh the rendering manually. ** Note that since there are both inline and block macros we also need to refresh the rendering for that reason. For ex, if you put a velocity macro inside a list item and then you remove the list item the renderer result of the macro will be different (in the second case an extra paragraph will be added). * We should also have a button to switch between rendering macros and not rendering macros. For example when a page is including another page with some large content the user might want to disable macro rendering to focus only on the content of the current page. The default should be to render macros. WDYT? Thanks -Vincent

16 years, 3 months

[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, 3 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, 3 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, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs