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

[xwiki-devs] [Proposal] Add a WikiReadyEvent?

by Vincent Massol

Hi devs, We already have ApplicationStartedEvent and ApplicationReadyEvent (when DB is ready). We also need an event when the wiki is ready since in s a multiwiki environment when you create a new wiki for example, you might need to init some stuff (like initialize mandatory classes). It's also needed the first time a request comes in for a given wiki. Thus I propose to add a WikiReadyEvent next to ApplicationStartedEvent and to send it in XWiki.updateDatabase(): ... synchronized (wikiName) { if (!wikiList.contains(wikiName)) { wikiList.add(wikiName); // Make sure these classes exists if (initClasses) { initializeMandatoryClasses(context); getPluginManager().virtualInit(context); getRenderingEngine().virtualInit(context); } --> send WikiReadyEvent here } } WDYT? Note that I was tempted to have a WikiCreatedEvent event sent when creating a wiki but that wouldn't fill the use case of initializing the wiki on the first request to it. Thanks -Vincent

13 years, 4 months

5
11
0 0

Re: [xwiki-devs] [Proposal] Add a WikiReadyEvent?

by Richard Hierlmeier

Am 13.04.2012 17:43 schrieb "Vincent Massol" <vincent(a)massol.net>: > > Hi devs, > > We already have ApplicationStartedEvent and ApplicationReadyEvent (when DB is ready). We also need an event when the wiki is ready since in s a multiwiki environment when you create a new wiki for example, you might need to init some stuff (like initialize mandatory classes). It's also needed the first time a request comes in for a given wiki. > > Thus I propose to add a WikiReadyEvent next to ApplicationStartedEvent and to send it in XWiki.updateDatabase(): > > ... > synchronized (wikiName) { > if (!wikiList.contains(wikiName)) { > wikiList.add(wikiName); > > // Make sure these classes exists > if (initClasses) { > initializeMandatoryClasses(context); > getPluginManager().virtualInit(context); > getRenderingEngine().virtualInit(context); > } > > --> send WikiReadyEvent here > > } > } > Is it a good practise to call event listeners in the synchronized block? (see Brian Götz, Java Concurrence in Practise, never call alien code from a synchronized block) My 2cents Richard > WDYT? > > Note that I was tempted to have a WikiCreatedEvent event sent when creating a wiki but that wouldn't fill the use case of initializing the wiki on the first request to it. > > Thanks > -Vincent > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs

13 years, 4 months

2
1
0 0

[xwiki-devs] [Proposal] Rule: one platform core module == one space

by Vincent Massol

Hi devs, Now that we have support for Hidden documents, I'd like to propose a general rule where to put XAR pages in platform modules. The rule I'm proposing is: * Each top level module in xwiki-platform-core/ that has a UI submodule should put its pages in a single space, generally named after the module but with a pretty name Examples: * xwiki-platform-appwithinminutes --> AppWithinMinutes (could also have been "App Within Minutes") (currently using: "AppWithinMinutes") * xwiki-platform-index --> Index (currently using: "Main" and "XWiki") * xwiki-platform-ircbot --> IRC (or "IRC Bot" or "IRCBot") (currently using: "IRC") * xwiki-platform-livetable --> Livetable (currently using: "XWiki") * xwiki-platform-user --> User (currently using: "XWiki") etc What's important is the rule: one module == one dedicated space WDYT? Note 1: This means that we the "Main" space will not be really needed anymore but I think we should keep it as the space name for the XE application for now (or we could introduce an application for it in xwiki-platform-core). It could simply contain the current Main.WebHome. Note 2: When we add support for nested spaces, the rule would mean but we would be be able to better organize content in nested spaces. Thanks -Vincent

13 years, 4 months

2
3
0 0

[xwiki-devs] tomcat OutOfMemoryError permgen space

by jinlong liu

I deployed XWiki 3.5 on tomcat 7.0 , then it always occurs a OutOfMemory Error:permgen space.Is there any good solution to it?I have changed the configuration of tomcat to sovle the problem tentatively . But I want to know if there any good solution or suggestion to it ? Thanks a lot.

13 years, 5 months

2
1
0 0

[xwiki-devs] Activity Stream no more properly subclassable in 3.5?

by Paul Libbrecht

hello devs, having moved Curriki to the 3.5 core, we noticed our activity stream was having empty getDisplayBody... looking more closely revealed that the objects were all of type ActivityEvent while a family of sub-classes was available in the CurrikiActivityStream: the method ActivityStreamPluginApi.wrapEvents was made private hence its subclass was ignored! This appears to have been made at https://github.com/xwiki/xwiki-platform/commit/1837196f0f6434603c4c24a13b7c… as part of a "code cleanup". Jean-Vincent, or someone else, could you explain the rationale behind it? I am sure this was checked for "others usages" but Curriki was not considered as part of that. Having somewhat fixed this on my side by bringing more methods to the subclass (for the display of older events), I come to realize that newer events are also not of the right type so I'll have to hunt more for "compromised subclassing"... This is rather an API breakage to my taste. Has there been a policy about this? Could we set-up one? I wonder if such a search engine exists that would have indicated that such a breakage would have been avoided. paul

13 years, 5 months

3
6
0 0

[xwiki-devs] [VOTE] Creation of xwiki-platform-uiextension module

by Vincent Massol

Hi devs, I'm implementing the LinkChecker UI and I want to be able to add a Tab in AllDocs. Right now I've coded it with a hardcoded #if but I really hate this. So here's my proposal: * Create the following modules: xwiki-platform-uiextension/ |_ xwiki-platform-uiextension-ui/ |_ xwiki-platform-uiextension-api/ where: * xwiki-platform-uiextension-ui/: contains XWiki.UIExtensionClass page * xwiki-platform-uiextension-api/: contains a ScriptService to get UIExtension data + contains an EventListener that refreshes the UI Extension Cache when an UIExtensionClass object is modified (this is for performance reasons) To start with I'm proposing to have the following fields for UIExtensionClass: * type: String, represents the type of the extension (for example for the AllDocs needs, I'll use a "IndexTab" type (or "AllDocsTab" type) * id: String, the technical name of the extension, which can be used for example as suffix for HTML class or ids. * name: String, the name of the extension, which can be used for displaying. For example for the AllDocs needs, it would be used as the name of the Tab * content: Textarea: the content of the extension. For example for the AllDocs needs, it would be used as the content to display when clicking on a tab I'd like to implement this ASAP and thus stop hardcoding UI Extensions from now on. Here's my +1 Thanks -Vincent PS: If you find a better than "uiextension" I'm all ears. A name without "extension" would be great to not confuse it with our Extensions (and with xwiki-platform-extension).

13 years, 5 months

6
10
0 0

[xwiki-devs] Fwd: [ANNOUNCE] Apache Solr 3.6 released

by Vincent Massol

fyi… -Vincent Begin forwarded message: > From: Robert Muir <rmuir(a)apache.org> > Subject: [ANNOUNCE] Apache Solr 3.6 released > Date: April 12, 2012 10:33:00 PM GMT+02:00 > To: dev(a)lucene.apache.org, solr-user(a)lucene.apache.org, Lucene mailing list <general(a)lucene.apache.org>, announce <announce(a)apache.org> > > 12 April 2012, Apache Solr™ 3.6.0 available > The Lucene PMC is pleased to announce the release of Apache Solr 3.6.0. > > Solr is the popular, blazing fast open source enterprise search platform from > the Apache Lucene project. Its major features include powerful full-text > search, hit highlighting, faceted search, dynamic clustering, database > integration, rich document (e.g., Word, PDF) handling, and geospatial search. > Solr is highly scalable, providing distributed search and index replication, > and it powers the search and navigation features of many of the world's > largest internet sites. > > This release contains numerous bug fixes, optimizations, and > improvements, some of which are highlighted below. The release > is available for immediate download at: > http://lucene.apache.org/solr/mirrors-solr-latest-redir.html (see > note below). > > See the CHANGES.txt file included with the release for a full list of > details. > > Solr 3.6.0 Release Highlights: > > * New SolrJ client connector using Apache Http Components http client > (SOLR-2020) > > * Many analyzer factories are now "multi term query aware" allowing for things > like field type aware lowercasing when building prefix & wildcard queries. > (SOLR-2438) > > * New Kuromoji morphological analyzer tokenizes Japanese text, producing > both compound words and their segmentation. (SOLR-3056) > > * Range Faceting (Dates & Numbers) is now supported in distributed search > (SOLR-1709) > > * HTMLStripCharFilter has been completely re-implemented, fixing many bugs > and greatly improving the performance (LUCENE-3690) > > * StreamingUpdateSolrServer now supports the javabin format (SOLR-1565) > > * New LFU Cache option for use in Solr's internal caches. (SOLR-2906) > > * Memory performance improvements to all FST based suggesters (SOLR-2888) > > * New WFSTLookupFactory suggester supports finer-grained ranking for > suggestions. (LUCENE-3714) > > * New options for configuring the amount of concurrency used in distributed > searches (SOLR-3221) > > * Many bug fixes > > Note: The Apache Software Foundation uses an extensive mirroring network for > distributing releases. It is possible that the mirror you are using may not > have replicated the release yet. If that is the case, please try another > mirror. This also goes for Maven access. > > Happy searching, > > Lucene/Solr developers

13 years, 5 months

1
0
0 0

[xwiki-devs] [UX][Proposal] User Roles

by Ecaterina Moraru (Valica)

Hi, When talking with JV about the first 5 minutes experience, we thought about adding some user roles inside XE. >From the start the user could select his appropriate role inside the wiki and we could customize his environment according to that role. We talked about: - display a "Get started" wizard the first time a user logs in: Already proposed at: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/XWiki5MinutesPropo… - when the user starts/finishes the wizard, he's asked to choose a role/flavor: (normal, advanced), (user, developer, administrator), etc. - choosing a role configures the wiki with some predefined values for the profile preferences; - a user can later fine tune his preferences. You can see the proposal at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/UserRoles Waiting for your feedback. Thanks, Caty

13 years, 5 months

3
5
0 0

[xwiki-devs] [Proposal] Deprecation Day on 26th of April 2012

by Vincent Massol

Hi devs, I'd like to propose a Deprecation Day on the 26th of April 2012. The idea is that during this day all committers who would like to participate focus on moving deprecated APIs to legacy modules. At the end of the day we'll count how many deprecated API we've moved (each committer should keep tab of how many APIs he moves to make that count easy). Then we'll blog about it on xwiki.org WDYT? Thanks -Vincent

13 years, 5 months

3
3
0 0

[xwiki-devs] Temp files for images with width param grow until JVM exit

by Jamie Maher

Hi there, I was testing out the XWiki Enterprise 3.5 release and I noticed that the temporary files folder under my Tomcat 7 kept growing while I was testing out XWiki. I had added a number of jpg attachments to a page that was using the {{photoalbum}} macro to display them. However, I found that this causes a number of download requests with the width parameter set, which seems to cause a new temporary file to be created for each request. It seems that even though the original image is cached it re-creates a new XWikiAttachmentContent thumbnail from those original bytes each time, causing multiple DiskFileItems to be created. Looking through the code for XWikiAttachmentContent it does set the deleteOnExit() for the DiskFileItem's store location file, but this file then will only be deleted when the JVM is shutdown. If multiple pages have many images each and they are being displayed in the photoalbum macro, then this creates a problem with diskspace being used up until the server is restarted. (And in my case for some reason stopping Tomcat via the service icon terminates the JVM in a way that doesn't cause the deleteOnExit() to be called as all of the temporary files are left behind after Tomcat is stopped) How can we stop all these temporary files from becoming a problem with a long running web application? There may be a better way, but I tried hacking around with the 3.5 platform on my github account and created a component to fix the problem by deleting files that had their DiskFileItem no longer being referenced: Modified 3.5 platform (mainly XWikiAttachmentContent) https://github.com/jamiemaher/xwiki-platform/tree/feature-tempfiles-3.5 Temporary Files provider component referenced by the XWikiAttachmentContent: https://github.com/jamiemaher/xwiki-tempfiles-component It seems to work pretty well, although there seem to be some files that don't seem to be reclaimed, although I haven't tracked down if it's because they are also in the regular xwiki cache as well. Thanks, Jamie

13 years, 5 months

1
0
0 0

[xwiki-devs] [VOTE] Change our Maven POM Names and Description for Extension Manager

by Vincent Massol

Hi devs, Now that we're starting to use the Extension Manager (EM) we need to be careful about the Description and Names we use in our pom.xml since they're used by the EM to display information to the user. They're also used by the XR application to import extensions located in maven repository into extensions.xwiki.org (EXO). Right now our names are of the type shown here: https://gist.github.com/2311321 For example: [INFO] XWiki Commons - Extension - Parent POM ............ SUCCESS [0.004s] [INFO] XWiki Commons - Extension - API ................... SUCCESS [2.066s] [INFO] XWiki Commons - Extension - Handler - Parent POM .. SUCCESS [0.017s] [INFO] XWiki Commons - Extension - Handler - JAR ......... SUCCESS [0.133s] [INFO] XWiki Commons - Extension - Repository - Parent POM SUCCESS [0.004s] [INFO] XWiki Commons - Extension - Repository - Aether ... SUCCESS [0.132s] [INFO] XWiki Commons - Extension - Repository - XWiki .... SUCCESS [0.006s] [INFO] XWiki Commons - Extension - Repository - XWiki model SUCCESS [0.188s] [INFO] XWiki Commons - Extension - Repository - XWiki api SUCCESS [0.010s] [INFO] XWiki Commons - Extension - Repository - XWiki handler SUCCESS [0.024s] These names are not nice names for users. Actually they're more IDs than names. And having the users see those in our livetable on EXO isn't nice for example. Nor is it nice if they see them in the EM UI. I thus propose that we change the way we use names in our pom.xml to use English-readable names, without any "XWiki" prefix. For example, for the example show above we could have: Extensions Extension API Extension Handlers JAR Extension Handler Extension Repositories Aether Extension Repository XWiki Extension Repository XWiki Extension Repository Model XWiki Extension Repository API XWiki Extension Repository Handler The alternative is to introduce a custom property in our pom.xm that would be used by the EM and XR but that's not a good solution because it means even more maintenance work. While not using technical id as names in our pom.xml is not as nice when displayed in the Maven Reactor I feel it's still the best solution we have. Here's my +1 Thanks -Vincent

13 years, 5 months

5
13
0 0

[xwiki-devs] [UX][Proposal] Improving Homepage Content

by Ecaterina Moraru (Valica)

Hi devs, I've made a proposal with some suggestions on what we can change on the Homepage. http://incubator.myxwiki.org/xwiki/bin/view/Improvements/HomepageContent The proposal is divided in Homepage Content improvements and Dashboard improvements (that still need some work). The Homepage improvements contains things like: - Improved Welcome message (a link to the Getting Started guide has already been added) http://incubator.myxwiki.org/xwiki/bin/download/Improvements/HomepageConten… You can see this in action on http://incubator.myxwiki.org/xwiki/bin/view/Main/WebHome This proposal would imply adding other 3 external links to: http://platform.xwiki.org/xwiki/bin/view/Features/DocumentLifecycle http://platform.xwiki.org/xwiki/bin/view/Features/PageEditing http://extensions.xwiki.org/xwiki/bin/view/Extension/Index+Application IMO these documentation pages contain valuable information and would also educate the user on how to make use of xwiki.org. - Implement mechanism to hide technical content (in progress by JV) - Simplify the 'Tags' section initial text http://jira.xwiki.org/browse/XWIKI-7678 - Separate Message Stream input from Activity Stream http://jira.xwiki.org/browse/XWIKI-7679 The Dashboard improvements contains: - Improve gadget's container styling in INLINE mode to better suggest dragging and delimitation http://jira.xwiki.org/browse/XWIKI-7681 Please share your thoughts about these ideas. Thanks, Caty

13 years, 5 months

3
3
0 0

[xwiki-devs] CLIRR reports and moved modules

by Sergiu Dumitriu

Hi devs, I noticed that no CLIRR errors are generated for modules that have been moved from platform to commons. This isn't good, since we're not reporting all the API breakages. I propose that whenever a module is moved, we add a special configuration for the maven clirr plugin in that module's pom.xml file, so that it compares with the previous version with the platform groupId. See http://mojo.codehaus.org/clirr-maven-plugin/examples/specific-artifacts.html for more details about the required configuration. -- Sergiu Dumitriu http://purl.org/net/sergiu/

13 years, 5 months

2
1
0 0

[xwiki-devs] Candidate Xwiki for http://www.socialsoftwarematrix.org

by Gianluca Sabena

Hi, I suggest to candidate Xwiki for http://www.socialsoftwarematrix.org. There is a specific page for new platform proposal at http://www.socialsoftwarematrix.org/rising_vendors/index.php Gianluca

13 years, 5 months

4
5
0 0

[xwiki-devs] [Announcement] XWiki Enterprise 4.0 Release Candidate 1 Released

by Sergiu Dumitriu

The XWiki development team is proud to announce the availability of XWiki Commons, XWiki Rendering, XWiki Platform, XWiki Enterprise and XWiki Enterprise Manager 4.0 Release Candidate 1. This is the first and hopefully last release candidate for XWiki Enterprise 4.0 version. This is mostly a polishing release before the final one. See the full release notes at http://www.xwiki.org/xwiki/bin/ReleaseNotes/ReleaseNotesXWikiEnterprise40RC1 for more details. -- Sergiu Dumitriu http://purl.org/net/sergiu/

13 years, 5 months

1
0
0 0

[xwiki-devs] Including jquery javascript library issues

by du du

Hi, all, I got a strange problem, whenever I include the jquery script in my vm file like this: <script type="text/javascript" src="/xwikim/bin/skin/resources/JScripts/jQuery/slickgrid/lib/jquery-1.7.min.js"></script> I got the following exception; I thought it caused by jquery and prototype conflict, but I included <script type="text/javascript"> jQuery.noConflict(); var $j = jQuery; </script> replaced $ for jquery with $j, but the same error, I also tried to use $xwiki.jsfx.use(), still same, any solution for this? Thanks Dave missing ; before statement ...h id [xwiki:resources.JScripts]</a><div id="xwikierror1" style="display: none;">... jquery....min.js (line 2, col 89) <a href="" onclick="document.getElementById('xwikierror1').style.display='block'; return false;">Error number 4001 in 4: Error while parsing velocity page xwiki:resources.JScripts Wrapped Exception: Failed to evaluate content with id [xwiki:resources.JScripts]</a><div id="xwikierror1" style="display: none;"><pre class="xwikierror"> Error number 4001 in 4: Error while parsing velocity page xwiki:resources.JScripts Wrapped Exception: Failed to evaluate content with id [xwiki:resources.JScripts] com.xpn.xwiki.XWikiException: Error number 4001 in 4: Error while parsing velocity page xwiki:resources.JScripts Wrapped Exception: Failed to evaluate content with id [xwiki:resources.JScripts] at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:122) at com.xpn.xwiki.render.XWikiVelocityRenderer.render(XWikiVelocityRenderer.java:94) at com.xpn.xwiki.render.XWikiVelocityRenderer.interpret(XWikiVelocityRenderer.java:55) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:288) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.interpretText(DefaultXWikiRenderingEngine.java:194) at com.xpn.xwiki.XWiki.parseContent(XWiki.java:1711) at com.xpn.xwiki.web.SkinAction.renderFileFromFilesystem(SkinAction.java:252) at com.xpn.xwiki.web.SkinAction.render(SkinAction.java:137) at com.xpn.xwiki.web.SkinAction.render(SkinAction.java:80) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:231) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:116) 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:621) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:128) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:144) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:217) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:109) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:1805) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: org.xwiki.velocity.XWikiVelocityException: Failed to evaluate content with id [xwiki:resources.JScripts] at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:247) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:184) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:117) ... 47 more Caused by: org.apache.velocity.runtime.parser.ParseException: Lexical error: org.apache.velocity.runtime.parser.TokenMgrError: Lexical error at line 210, column 200. Encountered: "?" (63), after : "" at org.apache.velocity.runtime.parser.Parser.parse(Parser.java:136) at org.apache.velocity.runtime.RuntimeInstance.parse(RuntimeInstance.java:1226) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:211) ... 49 more Wrapped Exception: org.apache.velocity.runtime.parser.ParseException: Lexical error: org.apache.velocity.runtime.parser.TokenMgrError: Lexical error at line 210, column 200. Encountered: "?" (63), after : "" at org.apache.velocity.runtime.parser.Parser.parse(Parser.java:136) at org.apache.velocity.runtime.RuntimeInstance.parse(RuntimeInstance.java:1226) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:211) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:184) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:117) at com.xpn.xwiki.render.XWikiVelocityRenderer.render(XWikiVelocityRenderer.java:94) at com.xpn.xwiki.render.XWikiVelocityRenderer.interpret(XWikiVelocityRenderer.java:55) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:288) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.interpretText(DefaultXWikiRenderingEngine.java:194) at com.xpn.xwiki.XWiki.parseContent(XWiki.java:1711) at com.xpn.xwiki.web.SkinAction.renderFileFromFilesystem(SkinAction.java:252) at com.xpn.xwiki.web.SkinAction.render(SkinAction.java:137) at com.xpn.xwiki.web.SkinAction.render(SkinAction.java:80) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:231) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:116) 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:621) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:128) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:144) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:217) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:109) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:1805) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) </pre></div>

13 years, 5 months

2
2
0 0

[xwiki-devs] Logging problem

by du du

Hi, all, I have the following logback.xml file, I developed a servlet, and used common logging library, import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; Log logger = LogFactory.getLog(FileTestServlet.class); I also added this to the logback.xml: <logger name="next.filetest" level="debug"/> In the code, I have the following code: logger.debug("FileTestServlet doGet..."); But in the xwiki.log file, the message is not logged to the log file, anything wrong? I tried to configure log4j.properties in the classes folder, used log4j logger for logging, there is no message logged either. Thanks for your help. Dave <configuration> <appender name="xwiki" class="ch.qos.logback.core.rolling.RollingFileAppender">  <file>C:\apache-tomcat-7.0.25\logs\xwiki.log</file> <append>false</append> <encoder> <pattern>%d [%t] %-5p %c - %m%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <maxIndex>10</maxIndex> <FileNamePattern>C:\apache-tomcat-7.0.25\logs\xwiki.log.%i</FileNamePattern> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>5MB</MaxFileSize> </triggeringPolicy> </appender> <logger name="com.xpn.xwiki.render.XWikiRadeoxRenderEngine" level="warn"/> <logger name="org.apache.fop.layoutmgr.inline.ContentLayoutManager" level="error"/> <logger name="org.apache.struts.util.RequestUtils" level="error"/> <logger name="org.hibernate.type" level="warn"/> <logger name="com.xpn.xwiki.store.migration" level="info"/> <logger name="org.hibernate.SQL" level="debug"/> <logger name="org.jgroups" level="error"/> <logger name="org.hibernate" level="warn"/> <logger name="info.informatica.doc.style.css.dom" level="error"/> <logger name="org.hibernate.ps.PreparedStatementCache" level="warn"/> <logger name="org.xwiki" level="info"/> <logger name="com.xpn.xwiki" level="warn"/> <logger name="next.filetest" level="debug"/> <root level="DEBUG"> <appender-ref ref="xwiki"/> </root> </configuration>

13 years, 5 months

1
0
0 0

[xwiki-devs] [Proposal] XWiki 4.x Cycle Themes

by Vincent Massol

Hi devs, Now that our Survey is over (see ) I'd like to propose that we settle on the following 2 themes for XWiki 4.x: * Theme 1: Ease of use * Theme 2: Quality This means that when we define roadmaps and more generally when each of us do development tasks, we should try to focus on doing things that are about "ease of use" first and barring that about "quality". These themes are quite general but they should be understood as improving what we already have vs developing brand new features. Of course it doesn't mean we shouldn't accept any brand new feature but more that, whenever we can, we should go in the direction of the themes. WDYT? If we agree I''ll add those themes to our Roadmap page at http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap Thanks -Vincent

13 years, 5 months

6
6
0 0

Re: [xwiki-devs] [GSOC] A basic search implementation with SOLR

by savitha sundaramurthy

Hi Paul, Here is the link to the document https://docs.google.com/document/pub?id=1-2GqvjtzS_a8TRKDNsom9egDZHTT5xIzUf… Thanks a lot, Savitha > On Wed, Apr 4, 2012 at 12:03 PM, Paul Libbrecht <paul(a)hoplahup.net> wrote: > >> Hi Savitha, >> >> things are moving. This is good. >> >> Do you have a (temporary) server address where this could be tested? >> (maybe best over IRC?). >> Or, how could I build your code and inject it on a fresh XWiki? >> >> Le 4 avr. 2012 à 18:46, savitha sundaramurthy a écrit : >> > I went through Fabio Mancinelli's code and with the help of few >> > inputs from there , I have implemented a basic search functionality >> using >> > solr. It also fixes the issue http://jira.xwiki.org/browse/XWIKI-6226. I >> > have indexed the page in English, french and Spanish. I have implemented >> > these main functionality: >> > >> > 1) Simple text search using solr. >> > 2) Used *Extended Dismax Parser *to customize search relevancy using >> boost >> > index. >> >> which fixes well the apostrophe case for sure (and a zillion other >> ambiguities, and another zillion power user tricks). >> >> > 3) Hit highlighting for English. >> >> This is a good usage of solr. >> >> > Below is the link to the source code >> > https://github.com/savis/xwiki-platform-search >> > XWiki front end , HTML and Velocity code >> > >> > https://gist.github.com/2295648 >> > >> > I wanted to send a pull request but I was playing around when renaming >> my >> > username and deleted the forked repository and I'm having difficulty >> > forking it again. So I have created a new repository and shared the code >> > above. >> >> I think forking is really useful. If not today, it will be needed any day >> soon. >> We need to see the diffs. >> Best would be to create the fork again, then copy your files and let git >> give us the diff. >> >> > I have taken few screen shots and have attached the document. >> >> where? >> >> > I'm working on my application and it should be done today. >> >> What is the planned schedule? >> >> paul >> _______________________________________________ >> devs mailing list >> devs(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/devs >> > > > > -- > best regards, > Savitha.s > -- best regards, Savitha.s

13 years, 5 months

7
14
0 0

[xwiki-devs] XWiki on cloud environments

by Fabio Mancinelli

Hi everybody, at XWiki we are participating in different research activities, many of them focused on cloud computing. As a part of this research efforts we've build this project that allows you to deploy XWiki in different cloud environments. In the current state, it allows to build an XWiki distribution that can be deployed on Amazon Beanstalk (http://aws.amazon.com/elasticbeanstalk/) and can also take advantage of the Amazon S3 Blobstore (http://aws.amazon.com/s3/) for storing attachments. The project is extensible, so other environments could be supported (e.g., Openstack SWIFT blobstore, http://swift.openstack.org/) and also deployment that are dynamically configured when started in virtual machines that are started up in other platforms. If you want to have a look you can find it here: https://github.com/fmancinelli/xwiki-platform-cloud For the moment I've put it on my personal GitHub account but I'll move it to XWiki contrib as soon as possible. Thanks, Fabio P.S.: If you want to experiment with it, Amazon provides a free usage tier (http://aws.amazon.com/free/)

13 years, 5 months

2
3
0 0

[xwiki-devs] Blog.CreatePost forwarded to wrong url

by du du

Hi, all, I got a weired problem with url handling, when I am on this page: http://mydomain.com/xwikim/bin/view/Blog/CreatePost, which gives me a create post button to create post, I check the form action url is: "/xwikim/bin/view/Blog/CreatePost?xpage=plain", when I click on the create button, it comes to this url: http://localhost/xwikim/bin/edit/Blog/Post+title?template=Blog.BlogPostTemp…, from which I got "Unable to connect" error, I am not sure why it switched from mydomain.com to localhost, all other links and buttons are working fine without this kind of problem. My setup is like that I have an apache web server installed with port 80 opened to the public internet, which forwards request to tomcat with port 8082 on localhost. all other links work fine, only the createpost has this problem. Any clue from any of you? Thanks very much in advance Dave

13 years, 5 months

1
0
0 0

[xwiki-devs] XWikiPreferences Source Code

by du du

Hi, all, One question, I am trying to look at the source code of XWikiPreferences class, AdminSheet class, but after I searched Data Type, I got a lot of classes back, I clicked on these two classes, it always shows the rendering result, I have no way to look at the velocity code behind the classes, but other classes like BlogClass, I can go inside the BlogSheet and use Edit button - Wiki to see the velocty code, why for these two classes I cannot see the code, any ideas? Thanks Dave

13 years, 5 months

1
0
0 0

[xwiki-devs] File Upload Page

by du du

Hi, all, I am trying to add a file upload page to xwiki, since the FileUploadPlugin java class is deprecated, is there any other fileupload component available for reuse? if no, I need to create the component on my own, my concern is I need to insert the file uploaded into database and keep it separate from all the other wiki tables, I like to create a separate table specifically for files uploaded, that means I need to use Hibernate in java code to handle that, any examples about how to do that? BTW, I am coming from IBatis background. Thanks in advance Dave

13 years, 5 months

1
0
0 0

[xwiki-devs] [VOTE] Use ComponentManager.getInstance*() instead of lookupComponent/LookupList/LookupMap

by Vincent Massol

Hi devs, In another thread we had a discussion about the new name of the method for looking up components. We had to provide a new one since we introduced support for Types in http://jira.xwiki.org/jira/browse/XCOMMONS-121 Thomas has introduced a new lookupComponent() method and has asked in a mail to speak up if we wanted a different name. I have replied to this thread and explained why I preferred a new one (see http://markmail.org/message/lvah3d6f37ak66p3). I'm copying my rationale here: " All looks good except CM.lookupComponent() which Ï don't like a lot for the following reasons: * It's a bit long. It's longer than before and it would be nicer if it were as short as before or even shorter ;) * It's not symmetrical with other lookups like lookupList and lookupMap, which should theoretically be lookupComponentList() and lookupComponentMap() which are even longer " I've proposed several possibilities and some committers have expressed their preferences for getInstance*() so I'm officially proposing it here as a VOTE since it's an important API that we're going to keep for a long time ;) So this vote is about using: * CM.getInstance(…) * CM.getInstanceList(…) * CM.getInstanceMap(…) Rationale: * Shorter than lookupComponent, LookupComponentList, LookupComponentMap * This is what is used in Guice and Picocontainer and seems to be a well-known name Here's my +1 IMPORTANT: Please vote quickly since we need to agree before the release of 4.0 final and 4.0RC1 is planned for this coming Monday so it would be ideal to speed up this vote and do the change today if we agree about it. Thanks -Vincent

13 years, 5 months

5
5
0 0

[xwiki-devs] [VOTE] Postpone 4.0RC1 release to Tuesday 10th

by Thomas Mortagne

Hi devs, I won't be available to release 4.0RC1 next Monday which is the planned release date so unless someone else want to do it we need to move it. I see two possibilities: 1) today 2) next Tuesday Here is my +1 for 2) for the following reasons: * we slipped a bit with 4.0M2 which mean that it has just been released this week which makes it too short to release the RC1 today IMO * we need to finish with new ComponentManager API (please answer to Vincent's vote mail) before the release candidate or then it's not a release candidate * I would like to finish with relative vs absolute URL in sendRedirect so that this change is introduced in a new major version (but it's more nice than critical) * anything else left to do for 4.0 ? -- Thomas Mortagne

13 years, 5 months

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