xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

by Richard Hierlmeier

most of our customers use MSSQL as database system. From time to time we have the opportunity to establish XWiki in customer projects. However it is difficulty and risky to recomment XWiki on a database system that is not supported by XWiki.org. What are the reasons for not supporting MSSQL? Is it simply a license or resource problem? Can we contribute here something? Richard

11 years, 1 month

[xwiki-devs] Preliminary memory analysis of xwiki.org dump of 2013-12-01

by vincent＠massol.net

Hi devs, Yesterday xwiki.org crashed and I had configured it to take a heap dump. I’ve done a quick analysis that I’m sharing here (I’ll continue to analyse): Memory retained: 1GB Main contenders: 1) Document cache: 178MB 2) Lucene WeightedSpanTermExtractor: 166MB 3) IRCBot Threads: 165MB 4) Velocity RuntimeInstance: 38MB 5) SOLR LRUCache (Lucene Document): 38MB 6) EM DefaultCoreExtensionRepository: 38MB 7) NamespaceURLClassLoader: 23MB I’ve started analyzing some below. 1 - Document Cache Analysis ======================= * There are 3552 XWikiDocument in memory for 195MB * The document cache size is 2000 on xwiki.org * Large documents (such as Test Reports) take 6MB each (XDOM caching) * So if we had only large documents in the wiki the cache would need 2000*6MB = 12TO * I don’t think this cache is memory aware, meaning it doesn’t free its entries when memory is low * 178MB for 2000 docs means average of 89K per document. Huge variation between docs with big content and docs with no or small content This means that when memory is low on xwiki.org it should be enough to call a few pages with some large content to get an OOM. 4 ideas to explore: Idea 1: Use a cache that evicts entries when some max threshold is reached ** Infinispan doesn’t support this yet: https://issues.jboss.org/browse/ISPN-863 and https://community.jboss.org/thread/165951?start=0&tstart=0 ** Guava seems to support size-based eviction with the ability to pass a weight function: http://code.google.com/p/guava-libraries/wiki/CachesExplained#Size-based_Ev… Idea 2: Another idea is a usage of a distributed cache such as memcached or elasticsearch. I wonder if the overhead of the network communication is too high to make it interesting vs not caching the XDOM and rendering it every time it’s needed. Idea 3: Try to reduce even more how the XDOM is stored in memory Idea 4: Don’t cache the XDOM and render every time and use a title cache for titles. Also do that for getting sections. I think they are the 2 main uses cases for getting the XDOM. As a short term action, I’d recommend to immediately reduce the document cache size from 2000 to 1000 on wiki.org or double the heap memory. 2 - Lucene WeightedSpanTermExtractor Analysis ===================================== I’m not sure what this is about yet but it looks strange. * There is 166MB stored in the Map<String,AtomicReaderContext> of WeightedSpanTermExtractor. * That map contains 192 instances * Example of map items: “doccontent_pt” (2.4MB), “title_ru” (1.8MB), “title_ro” (1.8MB), etc Any idea Marius? 3 - IRCBot Analysis =============== * We use 3 IRCBot threads. They take 55MB each! * The 55MB is taken by the ExecutionContext * More precisely the 55MB are held in 77371 org.apache.velocity.runtime.parser.node.Node[] objects I need to understand more why it’s so large since it doesn’t look normal. I also wonder if it keeps increasing or not. 5 - SOLR LRUCache Analysis ======================= * It’s map of 512 entries (Lucene Document objects). 512 is the cache size. * Entries are instances of DocSlice Looks ok and normal. 6 - EM DefaultCoreExtensionRepository Analysis ====================================== * 38MB in "Map<String, DefaultCoreExtension> extensions” * 33MB in org.codehaus.plexus.util.xml.Xpp3Dom instances (44844 instances) which I guess corresponds to the pom.xml of all our core extensions mostly. Looks normal even though 33MB is quite a lot. 7 - NamespaceURLClassLoader Analysis ================================ * 23MB in org.eclipse.jgit.storage.file.WindowCache * So this seems related to the XWiki Git Module used by the GitHubStats application installed on dev.xwiki.org This looks ok and normal according to http://download.eclipse.org/jgit/docs/jgit-2.0.0.201206130900-r/apidocs/org… Thanks -Vincent

11 years, 1 month

[xwiki-devs] About how to import the source code into eclipse.

by zhefangwu

I just want import the project to eclipse. But there are some errors during maven compile. Where can I find some help to do so? 发自我的 iPhone

11 years, 1 month

[xwiki-devs] HTML Cleaner and inline SVG

by Sergiu Dumitriu

Hi devs, Trying to fix http://jira.xwiki.org/browse/XWIKI-9753 I found 4 plausible solutions (other than switching to something better than HTMLCleaner): 1. Provide a PdfHTMLCleaner implementation which inherits DefaultHTMLCleaner but doesn't omit unknown tags 2. Change the DefaultHTMLCleaner so that it doesn't omit unknown tags 3. Instead of relying on org.htmlcleaner.DefaultTagProvider, use org.htmlcleaner.ConfigFileTagProvider with a custom tag configuration that allows all HTML5+SVG+MathML, which is a good idea if we want to switch to HTML5 in the future 4. Add another custom key for HTMLCleanerConfiguration for switching this unknown tags setting on or off Which do you prefer? 1 is quick to implement, but might introduce some other regressions in the PDF export if we're allowing all unknown tags 2 might be a dangerous change, which will break other things 3 is a clean fix, but involves some work 4 is also quick to implement, but it means adding another custom setting that limits the possible choices for the HTMLCleaner backend I vote for 4 as a quick fix, with 3 as a long term goal. WDYT? -- Sergiu Dumitriu http://purl.org/net/sergiu/

11 years, 1 month

[xwiki-devs] [Reminder] BFD#46

by vincent＠massol.net

Hi devs, Today is Bug Fixing Day 46. We're currently at -127 bugs (we were at -127 bugs last week!) for the 1600 days period: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 Bugs still seem to be winning ATM. Let's reduce this gap a bit... IMPORTANT: Since we're getting close to the end of the 5.x cycle and since this is RC time please be very careful about your commits and don't commit anything dangerous. Be on the safe side. It's better to do less bugs rather than commit regressions. We've been having issues of stability recently and they might have been added during BFD so we need to be careful. NOTE: Since we're again very late for 5.3 I think it's acceptable that some committers continue their work for 5.3 RC1 and final today instead of participating to this BFD. Here's the BFD#46 dashboard to follow the progress during the day: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=11798 Thanks -Vincent

11 years, 1 month

[xwiki-devs] [Solr] What do we search for?

by Marius Dumitru Florea

Hi devs, This is a very important question so think carefully. Let me explain: In XWiki (model) we have a few entity types. There are *wikis* which have *spaces* which have *documents*. A document can have *objects* and *attachments*. A document can also define a *class*. At the same time we like to say that in XWiki "everything is a document" because everything revolves around documents. The document is the central notion. We can query the database (using HQL or XWQL) for any of the previously mentioned entities but what should a Solr query return (semantically)? In other words: * are you searching for an object without caring about the document that holds the object? Same for an object property. * how often are you searching for an attachment without caring about the document that holds the attachment? * are you searching for a class or for the document that defines that class? * are you searching for a wiki without caring about the documents it contains? Same for a space. IMO the result of a Solr query should be, semantically, a list of documents. But maybe I'm wrong. ----------------------- Technical Details ----------------------- Unlike a relational database, Solr/Lucene index has a single 'table'. So normally you index a single entity type. Each row in the index represents an entity of that type. As a consequence the result of a Solr query is semantically a list of entities of that type. In our case the entity type is (naturally) *document*. If you want to index more entity types (e.g. index attachments and objects _separately_, not as part of a document) then, since there is only one 'table' in the index, you need to add a 'type' column that specifies the type of entity you have on each row (e.g. type=document, type=attachment, type=object etc.). The result of a Solr query is now, semantically, a list of different entity types, unless you filter by a specific type. It smells like a hack to me. Let's imagine what happens if we want to search for blog posts that has a specific tag. With the first approach this is easy because all the (indexed) information is on a single row. With the second approach this is considerably more complex because the information is spread on multiple rows: * one row with type=document for the blog post document * one row with type=object for the blog post object * one row with type=object for the tab object In a relational database when you have the information spread in multiple places (tables) you do joins. Fortunately (you would says) Solr supports joins. In this particular case we would have to perform 2 joins which means: index X index X index where X represents the cartesian product. The document name would be the join key. Pretty complex even before trying to write this in Solr query syntax.. So basically the question becomes: is it worth indexing more entities _separately_ instead of indexing just documents (with info about their objects and attachments) considering the complexity that it brings in writing Solr queries? Do we search for objects and attachments alone as separate entities often enough to justify this complexity? My answer is no. Thanks, Marius

11 years, 1 month

[xwiki-devs] help

by 云水谣

hi，all： when I got help from xwiki.org,I can not find useful message about how to develop in xwiki pages. I describe what I want to do：I just has some information to write on xwiki on one page，because these information may change everyday,so I want to get these information from a http api,and then put it down in wiki,I can not find one complete example in xwiki.org website:how to use this scripts in xwiki and where should i put these scripts file in? how these script files cooperates？ thanks

11 years, 1 month

[xwiki-devs] Retrieve the list of users based on the selected group

by le bihan matthieu

Hello, I researched the forum to see if a subject could meet my need, but I have not found a solution. My need: I want to make a day depending on the user group selection list select from a list. For lists, I use the wiki groups and users of xwiki. I want to retrieve the list of xwiki users in the selected group. To create the list of groups I used the velocity, by cons I think to create the user must use javascript because every time we change the group must make days the list of users. This is the part I select the group name but how do I find the list of users in this group? Thank you in advance, I am at your disposal for any further information! Regards, Matthieu Le Bihan -- View this message in context: http://xwiki.475771.n2.nabble.com/Retrieve-the-list-of-users-based-on-the-s… Sent from the XWiki- Dev mailing list archive at Nabble.com.

11 years, 1 month

[xwiki-devs] XWiki Rendering: WELD-001414 Bean name is ambiguous

by Gerry

Hi all, I'm new to XWiki development and trying to include XWiki rendering into my project. Unfortunately I'm getting the attached error message. Can anyone help me please? I'm using Maven 3, Glassfish 4.0, CDI1.1, JSF 2.2, and XWiki 5.2.1. Please let me know if you need any further information. Thanks for your help. Best regards, Gerry Error message: 2013-11-23T18:26:10.507+0100|SEVERE: Exception during lifecycle processing org.glassfish.deployment.common.DeploymentException: CDI deployment failure:WELD-001414 Bean name is ambiguous. Name xwiki/2.1 resolves to beans [Managed Bean [class org.xwiki.rendering.internal.parser.xwiki21.XWiki21Parser] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.XWikiSyntaxRendererFactory] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.XWikiSyntaxBlockRenderer] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.reference.XWiki21ResourceReferenceTypeSerializer] with qualifiers [@Default @Named @Any]] at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:225) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:328) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:493) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:219) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:491) at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:527) at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:523) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:356) at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:522) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:546) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1423) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1500(CommandRunnerImpl.java:108) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1762) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1674) at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:534) at com.sun.enterprise.v3.admin.AdminAdapter.onMissingResource(AdminAdapter.java:224) at org.glassfish.grizzly.http.server.StaticHttpHandler.service(StaticHttpHandler.java:297) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:246) at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) at java.lang.Thread.run(Thread.java:724) Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name xwiki/2.1 resolves to beans [Managed Bean [class org.xwiki.rendering.internal.parser.xwiki21.XWiki21Parser] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.XWikiSyntaxRendererFactory] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.XWikiSyntaxBlockRenderer] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.reference.XWiki21ResourceReferenceTypeSerializer] with qualifiers [@Default @Named @Any]] at org.jboss.weld.bootstrap.Validator.validateBeanNames(Validator.java:639) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:488) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:536) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:216) ... 36 more 2013-11-23T18:26:10.509+0100|SEVERE: Exception while loading the app 2013-11-23T18:26:10.509+0100|SEVERE: Undeployment failed for context /jasp-webapp 2013-11-23T18:26:10.556+0100|SEVERE: Exception while loading the app : CDI deployment failure:WELD-001414 Bean name is ambiguous. Name xwiki/2.1 resolves to beans [Managed Bean [class org.xwiki.rendering.internal.parser.xwiki21.XWiki21Parser] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.XWikiSyntaxRendererFactory] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.XWikiSyntaxBlockRenderer] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.reference.XWiki21ResourceReferenceTypeSerializer] with qualifiers [@Default @Named @Any]] org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name xwiki/2.1 resolves to beans [Managed Bean [class org.xwiki.rendering.internal.parser.xwiki21.XWiki21Parser] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.XWikiSyntaxRendererFactory] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.XWikiSyntaxBlockRenderer] with qualifiers [@Default @Named @Any], Managed Bean [class org.xwiki.rendering.internal.renderer.xwiki21.reference.XWiki21ResourceReferenceTypeSerializer] with qualifiers [@Default @Named @Any]] at org.jboss.weld.bootstrap.Validator.validateBeanNames(Validator.java:639) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:488) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:536) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:216) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:328) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:493) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:219) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:491) at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:527) at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:523) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:356) at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:522) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:546) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1423) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1500(CommandRunnerImpl.java:108) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1762) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1674) at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:534) at com.sun.enterprise.v3.admin.AdminAdapter.onMissingResource(AdminAdapter.java:224) at org.glassfish.grizzly.http.server.StaticHttpHandler.service(StaticHttpHandler.java:297) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:246) at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191) at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168) at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189) at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288) at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206) at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136) at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114) at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838) at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113) at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115) at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55) at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135) at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564) at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544) at java.lang.Thread.run(Thread.java:724) Relevant dependencies from pom.xml: <dependency> <groupId>org.xwiki.rendering</groupId> <artifactId>xwiki-rendering-syntax-xwiki21</artifactId> <version>5.2.1</version> </dependency> <dependency> <groupId>org.xwiki.commons</groupId> <artifactId>xwiki-commons-component-default</artifactId> <version>5.2.1</version> </dependency> <dependency> <groupId>org.xwiki.rendering</groupId> <artifactId>xwiki-rendering-macro-toc</artifactId> <version>5.2.1</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>1.0.13</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl-over-slf4j</artifactId> <version>1.7.5</version> </dependency> -- View this message in context: http://xwiki.475771.n2.nabble.com/XWiki-Rendering-WELD-001414-Bean-name-is-… Sent from the XWiki- Dev mailing list archive at Nabble.com.

11 years, 1 month

[xwiki-devs] [ANN] WebViewers, a way to view and edit attachments in XWiki (and other webapps!)

by Caleb James DeLisle

Hi guys, I am proud to announce WebViewers are now available for XWiki. As part of the Resilience research project, I and others have been working on a compatible solution for interfacing the variety of Javascript file viewers and editors with the many available web application frameworks. The first few WebViewers are available now on http://webviewers.org/ and as self-contained archive files, are installable on any system supporting the API. More interestingly, the first few WebViewers to be ported are now available as XWiki Extensions on http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ExtensionSearch?sp… and while they are largely prototypes, one which is useful right now is the PDF WebViewer based on Mozilla's pdf.js. http://extensions.xwiki.org/xwiki/bin/view/Extension/pdf+webviewer This is of course installable with the Extension Manager and supports XWiki versions 5.1 or newer. With this you will be able to both view in a preview window and embed in a wiki page, the content of a PDF attachment. Viewing of the attachment is done by clicking on the magnifying glass shown next to the PDF attachment and embedding a PDF attachment in the page is done using the {{embed}} macro (part of the XWiki WebViewers extension). You can see the embedded viewers and example uses of the {{embed}} macro here: http://webviewers.org/xwiki/bin/view/Viewers/Demo And you can see the magnifying glass icons next to the attachments here: http://webviewers.org/xwiki/bin/view/Viewers/Demo#Attachments If anyone has any questions or comments about WebViewers or the XWiki Extensions, I'd love to hear them. Thanks, Caleb

11 years, 1 month

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