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

Re: [xwiki-devs] [xwiki-notifications] r27004 - platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/store/hibernate

by Sergiu Dumitriu

On 02/13/2010 04:40 PM, vmassol (SVN) wrote: > Author: vmassol > Date: 2010-02-13 16:40:57 +0100 (Sat, 13 Feb 2010) > New Revision: 27004 > > Modified: > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/store/hibernate/DefaultHibernateSessionFactory.java > Log: > XWIKI-4893: Make XWiki support recovering from a connection problem with the database > > Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/store/hibernate/DefaultHibernateSessionFactory.java > =================================================================== > --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/store/hibernate/DefaultHibernateSessionFactory.java 2010-02-13 12:09:34 UTC (rev 27003) > +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/store/hibernate/DefaultHibernateSessionFactory.java 2010-02-13 15:40:57 UTC (rev 27004) > @@ -19,7 +19,9 @@ > */ > package com.xpn.xwiki.store.hibernate; > > +import java.io.File; > import java.io.InputStream; > +import java.net.URL; > > import org.hibernate.HibernateException; > import org.hibernate.SessionFactory; > @@ -33,8 +35,8 @@ > * > * @version $Id$ > * @since 2.0M1 > - * @todo this was coded by Artem. Find out why we need this as a component. > */ > +// TODO: This was coded by Artem. Find out why we need this as a component. > @Component > public class DefaultHibernateSessionFactory implements HibernateSessionFactory > { > @@ -45,6 +47,78 @@ > { > private static final long serialVersionUID = 1L; > > + /** > + * Whether the Hibernate Configuration has alreayd been initialized or not. We do this so that the > + * Hibernate {@link org.hibernate.cfg.Configuration#configure()} methods can be called several times in a > + * row without causing some Duplicate Mapping errors, see our overridden > + * {@link #getConfigurationInputStream(String)} below. > + */ > + private boolean isConfigurationInitialized; > + > + /** > + * {@inheritDoc} > + * @see org.hibernate.cfg.Configuration#configure() > + */ Are you sure there's no need for synchronized? Same for all the others. > + @Override public Configuration configure() throws HibernateException > + { > + Configuration configuration; > + if (this.isConfigurationInitialized) { > + configuration = this; > + } else { > + configuration = super.configure(); > + this.isConfigurationInitialized = true; > + } > + return configuration; > + } > + > + /** > + * {@inheritDoc} > + * @see org.hibernate.cfg.Configuration#configure(String) > + */ > + @Override public Configuration configure(String resource) throws HibernateException > + { > + Configuration configuration; > + if (this.isConfigurationInitialized) { > + configuration = this; > + } else { > + configuration = super.configure(resource); > + this.isConfigurationInitialized = true; > + } > + return configuration; > + } > + > + /** > + * {@inheritDoc} > + * @see org.hibernate.cfg.Configuration#configure(java.net.URL) > + */ > + @Override public Configuration configure(URL url) throws HibernateException > + { > + Configuration configuration; > + if (this.isConfigurationInitialized) { > + configuration = this; > + } else { > + configuration = super.configure(url); > + this.isConfigurationInitialized = true; > + } > + return configuration; > + } > + > + /** > + * {@inheritDoc} > + * @see org.hibernate.cfg.Configuration#configure(java.io.File) > + */ > + @Override public Configuration configure(File configFile) throws HibernateException > + { > + Configuration configuration; > + if (this.isConfigurationInitialized) { > + configuration = this; > + } else { > + configuration = super.configure(configFile); > + this.isConfigurationInitialized = true; > + } > + return configuration; > + } > + > // there is no #configure(InputStream) so we use #configure(String) and override #getConfigurationInputStream > @Override > protected InputStream getConfigurationInputStream(String resource) throws HibernateException -- Sergiu Dumitriu http://purl.org/net/sergiu/

15 years, 7 months

2
1
0 0

[xwiki-devs] XWiki 2.2 Lucene Plugin rebuild index fails

by Jared.Scott

Hey; I am just getting up and running with XWiki but am having some issues with getting the Lucene Plugin to work. I have uncommented the following lines in WEB-INF/xwiki.cfg: #-# Lucene search engine xwiki.plugins.lucene.indexdir=/tmp/xwiki/lucene xwiki.plugins.lucene.analyzer=org.apache.lucene.analysis.standard.StandardAnalyzer xwiki.plugins.lucene.indexinterval=20 And to do diagnostics I created a new page with just these lines of code: {{velocity}} #set($results = $xwiki.lucene.rebuildIndex()) {{/velocity}} when I view the page, the macro fails. when I look at the output, i see this (reduced): org.xwiki.rendering.macro.MacroExecutionException: Failed to evaluate Velocity Macro for content [#set($results = $xwiki.lucene.rebuildIndex())] at org.xwiki.rendering.internal.macro.velocity.VelocityMacro.evaluate(VelocityMacro.java:118) at org.xwiki.rendering.internal.macro.velocity.VelocityMacro.evaluate(VelocityMacro.java:44) ... (hundreds more) Caused by: org.apache.velocity.exception.MethodInvocationException: Invocation of method 'rebuildIndex' in class com.xpn.xwiki.plugin.lucene.LucenePluginApi threw exception java.lang.NullPointerException at velocity macro[line 1, column 31] at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:284) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:252) ...... 92 more Caused by: java.lang.NullPointerException at com.xpn.xwiki.plugin.lucene.LucenePlugin.rebuildIndex(LucenePlugin.java:146) at com.xpn.xwiki.plugin.lucene.LucenePluginApi.rebuildIndex(LucenePluginApi.java:68)... ... 98 more It seems that it is throwing a NullPointerException. This is exactly what it does when I try to rebuild the index on the XWiki provided Lucene Search page as well. Any ideas as to what I can do to solve this? Could it be a configuration error? -- View this message in context: http://n2.nabble.com/XWiki-2-2-Lucene-Plugin-rebuild-index-fails-tp4561718p… Sent from the XWiki- Dev mailing list archive at Nabble.com.

15 years, 7 months

2
2
0 0

[xwiki-devs] [ANN] Created branch xwiki-skin-colibri-1.12-web-2.2

by Thomas Mortagne

Hi devs, Since we want to introduce things not compatible with XE 2.2 branch, I created a colibri skin branch to be able to keep fixing bug in colibri for XE 2.2. This mail is mainly here to warn everyone to make sure to merge any colibri skin bugfix in its xwiki-skin-colibri-1.12-web-2.2 branch. Here is the URL for the branch https://svn.xwiki.org/svnroot/xwiki/platform/skins/branches/xwiki-skin-coli… Thanks, -- Thomas Mortagne

15 years, 7 months

1
0
0 0

[xwiki-devs] [myxwiki] XWiki Enterprise 2.2 Release Candidate 2 Upgrade

by Thomas Mortagne

Hello, myxwiki.org has been upgraded to XE 2.2 Release Candidate 2, if you own a wiki hosted there you should have a look at : http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise22RC2 We also strongly recommend an upgrade to the latest wiki version. To upgrade you must download XE 2.2 Release Candidate 2 XWiki XAR from : http://www.xwiki.org/xwiki/bin/view/Main/Download And follow the upgrade guide available at : http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HUpgrading… To be notified of the myxwiki.org server upgrade you can follow myxwiki on twitter: http://twitter.com/myxwiki Note: if the admin UI looks weird after an import of the xar, that's normal, you should fix it by cleaning your browser cache (ctrl+shift+r). Thanks, -- Thomas Mortagne

15 years, 7 months

1
0
0 0

[xwiki-devs] cert creation component

by Story Henry

Hi, Having got Xwiki to produce RDFa (very easy), and having switched of Twitter to allow me to concentrate,I am now working on allowing a user to click a button in his profile, and have it create a foaf+ssl certificate (which is just a normal certificate, but with a URL in the subject alternative name). The code for this is very simple: http://github.com/harbulot/keygenapp/blob/master/samplewebapp/src/main/java… (with a few lines of tweaks required to add the certificate information to the profile page). What happens is that a <keygen> XML element is added to a <form> element in the user's profile page. This forces the browser (Safari, Firefox, Opera) to create a <public, private> key pair and send the public part to the servlet referred to above (MiniCaServlet). That servlet creates a certificate and sends it back to an invisible iframe. The browser then adds that cert to the keystore (this is done automatically, it's part of browser behavior). So to move this code to XWiki, I understand I should create a component. I read about it here: http://platform.xwiki.org/xwiki/bin/view/DevGuide/WritingComponents and it makes sense. From a component I can get the user, and from that I can get his profile page, and then I can add the public key information to his profile (I wrote a RSAKeyClass in Xwiki to do this). The component should finally send the newly generated certificate back to the client, which it can do because it has access the the HTTPServletResponse. But where would I put such a component? In a specific wiki page? Does all that make sense? If not let me know before I go and code it up. Henry PS. It would be fun later to have the User's Profile page be a bit Ajaxy, so that if it notices a change to the invisible iframe the browser can make a reques to XWiki to refresh the table of public keys displayed to the user. Social Web Architect http://bblfish.net/

15 years, 7 months

3
4
0 0

Re: [xwiki-devs] [xwiki-notifications] r26953 - platform/web/trunk/standard/src/main/webapp/templates

by Sergiu Dumitriu

On 02/11/2010 05:49 PM, vmassol (SVN) wrote: > Author: vmassol > Date: 2010-02-11 17:49:55 +0100 (Thu, 11 Feb 2010) > New Revision: 26953 > > Modified: > platform/web/trunk/standard/src/main/webapp/templates/xwikivars.vm > Log: > Improved doc > > Modified: platform/web/trunk/standard/src/main/webapp/templates/xwikivars.vm > =================================================================== > --- platform/web/trunk/standard/src/main/webapp/templates/xwikivars.vm 2010-02-11 16:07:23 UTC (rev 26952) > +++ platform/web/trunk/standard/src/main/webapp/templates/xwikivars.vm 2010-02-11 16:49:55 UTC (rev 26953) > @@ -3,7 +3,9 @@ > #set($isSuperAdmin = ($context.user == 'XWiki.superadmin')) > #set($hasEdit = $xwiki.hasAccessLevel("edit")) > #set($hasAdmin = $xwiki.hasAccessLevel("admin")) This is so bad for the performance... Fills the cache with unneeded entries, makes two unneeded queries to the database (the random document plus the WebPreferences), and goes through the complex full rights check each time. > +## Note: In order to know if the user has the right to create a space we compute a space name that doesn't exist and check edit rights on that space > #set($hasCreateSpace = $xwiki.hasAccessLevel("edit", "${doc.space}${mathtool.random(0, 999)}.DocumentReservedForInternalXWikiUsage")) > +## Note: In order to know if the user has the right to create a page we compute a page name that doesn't exist and check edit rights on that page > #set($hasCreatePage = $xwiki.hasAccessLevel("edit", "${doc.space}.DocumentReservedForInternalXWikiUsage${mathtool.random(0, 999)}")) > #set($hasGlobalAdmin = $xwiki.hasAccessLevel("admin", $context.user, "XWiki.XWikiPreferences")) > #set($hasSpaceAdmin = $xwiki.hasAccessLevel("admin", $context.user, "${doc.space}.WebPreferences")) -- Sergiu Dumitriu http://purl.org/net/sergiu/

15 years, 7 months

2
2
0 0

[xwiki-devs] [Proposal] Add getID and getCategory methods to MacroDescriptor

by Anamaria Stoica

Hi devs, I'm proposing we add to org.xwiki.rendering.macro.descriptor.MacroDescriptor [0] the following methods: 1/ MacroId getId(); 2/ String getCategory(); // Note: Actually it should allow multiple categories for one macro, not just one, because usually this is the case There is a method called getDefaultCategory() in MacroDescriptor: String getDefaultCategory(); , but it is not the final category, as it can overridden by the wiki Admin. (see method comment in api) So, right now, if you have a list of MacroDescriptors, there is no way of telling which is the ID or the real category of each macro. Also, there is no "getRealMacroCategory by macroId"-like method neither in MacroCategorymManager [1], nor in MacroManager [2]. We should either have a getCategory() or getCategories() method in MacroDescriptor, or a getMacroCategory(MacroId macroId)/getMacroCategories(MacroId macroId) in MacroManager/MacroCategoryManager. Right now, whenever someone needs to add id or category to the macro descriptor, ends up creating their own MacroDescriptor class, which is the case of org.xwiki.gwt.wysiwyg.client.plugin.macro.MacroDescriptor [3] or in my case. More about why I need the macroId in the MacroDescriptor: - I need a component that returns the list of all macros (both XWiki Java Macros and XWiki Wiki Macros) in Velocity. The list needs to be sorted by the Macro Name, and not by the Macro ID. - Once I get the list, I need to display the info for each of them, plus a link to their wiki page (nonexistent at this point). Wiki Macros do have wiki pages (the ones with a XWiki.WikiMacroClass object attached), but the Java Macros don't. For the Java Macros, we could use the MacroId in the URL to identify the macro. Note: I cannot use org.xwiki.gwt.wysiwyg.client.plugin.macro.MacroDescriptor, because my component would depend on the gwt.wysiwyg module, and has nothing to do with it. Related Questions: 1/ How can I tell of which type is a macro (Wiki or Java), if I have its macro descriptor/id? 2/ How can I get the wiki page with the XWiki.WikiMacroClass for a given Wiki Macro, if I have its descriptor/id? So far, I couldn't think of anything better than doing a HQL for the document with a XWiki.WikiMacroClass object with the property macroId set to the one I'm looking for. Code snippet follows: #set($macros = $gadgets.getMacroDefinitions()) #foreach($m in $macros) #set($hql = "select doc.fullName from XWikiDocument doc, BaseObject obj, StringProperty prop where doc.fullName=obj.name and obj.className='XWiki.WikiMacroClass' and prop.id.id=obj.id and prop.name='id' and prop.value='${m.getMacroId().id}'") #set($results = $xwiki.search($hql)) #if($results.size() > 0) #set($macroDoc = $results.get(0)) ... Thanks, Anamaria [0] http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rendering/xwik… [1] http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rendering/xwik… [2] http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rendering/xwik… [3] http://svn.xwiki.org/svnroot/xwiki/platform/web/trunk/xwiki-gwt-wysiwyg-cli…

15 years, 7 months

4
3
0 0

[xwiki-devs] getting the type of a macro (Wiki or Java) / getting the wiki page for a macro

by Anamaria Stoica

Hi, I have 2 questions related to Macros: 1/ How can I tell of which type is a macro (Wiki or Java), if I have its macro descriptor/id? 2/ How can I get the wiki page with the XWiki.WikiMacroClass for a given Wiki Macro, if I have its descriptor/id? So far, I couldn't think of anything better than doing a HQL for the document with a XWiki.WikiMacroClass object with the property macroId set to the one I'm looking for. Code snippet follows: #set($macros = $gadgets.getMacroDefinitions()) #foreach($m in $macros) #set($hql = "select doc.fullName from XWikiDocument doc, BaseObject obj, StringProperty prop where doc.fullName=obj.name and obj.className='XWiki.WikiMacroClass' and prop.id.id=obj.id and prop.name='id' and prop.value='${m.getMacroId().id}'") #set($results = $xwiki.search($hql)) #if($results.size() > 0) #set($macroDoc = $results.get(0)) ... , $gadgets.getMacroDefinitions() - is a custom component which returns a list of org.xwiki.rendering.macro.descriptor.MacroDescriptor's with all the macros in the wiki Thanks, Anamaria

15 years, 7 months

2
1
0 0

[xwiki-devs] [Proposal] Add fields to administration app whose names are links to explanations of those fields on xwiki.org

by Caleb James DeLisle

The problem: When a new wiki administrator uses the registration application, they are faced with a set of fields with names which are too short to explain what each field is for. eg: Boolean field named: "Check Active fields for user authentication" To a new administrator, this is confusing and it's not apparent where to look for an explanation. Proposal: I would like to add fields with names which are links to descriptions of what those fields are for. I can implement this in the "configurable" class which I am working on. This means XE would have links to xwiki.org but it already does on the dashboard explanation of tags. WDYT? Caleb

15 years, 7 months

5
8
0 0

[xwiki-devs] Using Glassfish managed datasource

by GUILLEMP＠telefonica.net

Hi, I need some help configuring Glassfish-managed DataSource for XWiki Enterprise (stable 2.1.1). In short, does anyone know how to tweak WEB-INF/hibernate.cfg.xml so that Hibernate uses a JNDI resource that has been configured in Glassfish? (for instance, i've defined jdbc/xwiki in Glassfish and would like Hibernate to use it instead of the settings provided inside WEB-INF/hibernate.cfg.xml). The long version: I'm trying to do a manual installation (as in: http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HInstallin… ) on a Glassfish v3 app server, and would like to use a Glassfish managed datasource (let's say using JNDI jdbc/xwiki as javax.sql.DataSource). I haven't found explicit details on how to do this, so i started by commenting out line xwiki.store.hibernate.path=/WEB-INF/hibernate.cfg.xml inside file WEB-INF/xwiki.cfg and uncommenting the following inside WEB-INF/web.xml so that it's used instead: <resource-ref> <description>DB Connection</description> <res-ref-name>jdbc/xwiki</res-ref-name> <res-type>javax.sql.DataSource</res-type> <res-auth>Container</res-auth> </resource-ref> But this gave me the following error when, after deploying to Glassfish, i tried to go to http://localhost:8080/xwiki/bin/view/Main/ >HTTP Status 500 - >type Exception report > >message > >descriptionThe server encountered an internal error () that prevented >it from fulfilling this request. > >exception > >javax.servlet.ServletException: com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context >Wrapped Exception: Error number 3001 in 3: Cannot load class com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from param xwiki.store.migration.manager.class >Wrapped Exception: Error number 0 in 3: Exception while hibernate execute >Wrapped Exception: Hibernate Dialect must be explicitly set > >root cause > >com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context >Wrapped Exception: Error number 3001 in 3: Cannot load class com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from param xwiki.store.migration.manager.class >Wrapped Exception: Error number 0 in 3: Exception while hibernate execute >Wrapped Exception: Hibernate Dialect must be explicitly set Glassfish logs contain the following two logs of this error: >53:44,236 [http://localhost:8080/xwiki/bin/view/Main/] WARN >UserSuppliedConnectionProvider - No connection properties specified - >the user must supply JDBC connections and also >53:44,269 [http://localhost:8080/xwiki/bin/view/Main/] WARN >action.RequestProcessor - Unhandled Exception thrown: class >com.xpn.xwiki.XWikiException They seem to show that i need to use WEB-INF/hibernate.xml.cfg to set up the proper vendor Dialect So i modified WEB-INF/xwiki.cfg so to use the line: xwiki.store.hibernate.path=/WEB-INF/hibernate.cfg.xml Then, inside WEB-INF/hibernate.cfg.xml i ONLY uncommented the line <property name="dialect">org.hibernate.dialect.MySQLDialect</property> keeping all others (connection.username, connection.password ...) commented so to check that the ones provided by Glassfish are being used instead. After undeploying previous and deploying this modified version i get a different error when trying to visit http://localhost:8080/xwiki/bin/view/Main >HTTP Status 500 - >type Exception report >message > >descriptionThe server encountered an internal error () that prevented >it from fulfilling this request. > >exception > >javax.servlet.ServletException: com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context >Wrapped Exception: Error number 3001 in 3: Cannot load class com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from param xwiki.store.migration.manager.class >Wrapped Exception: Error number 0 in 3: Exception while hibernate execute >Wrapped Exception: Errors in named queries: listGroupsForUser, getSpaceDocsName, getAllUsers, getAllDocuments, getSpaces, getAllPublicDocuments, getAllSpaceDocuments > >root cause > >com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context >Wrapped Exception: Error number 3001 in 3: Cannot load class com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from param xwiki.store.migration.manager.class >Wrapped Exception: Error number 0 in 3: Exception while hibernate execute >Wrapped Exception: Errors in named queries: listGroupsForUser, getSpaceDocsName, getAllUsers, getAllDocuments, getSpaces, getAllPublicDocuments, getAllSpaceDocuments > And in Glassfish logs: >19:04,638 [http://localhost:8080/xwiki/bin/view/Main/] WARN >UserSuppliedConnectionProvider - No connection properties specified - >the user must supply JDBC connections and seven more like this one (i truncated the whole stack) that match the errors in named queries reported above (listGroupsForUser, getSpaceDocsName,getAllUsers,getAllDocuments,getSpaces,getAllPublicDocuments and getAllSpaceDocuments) : >19:05,013 [http://localhost:8080/xwiki/bin/view/Main/] ERROR >impl.SessionFactoryImpl - Error in named query: listGroupsForUser >org.hibernate.hql.ast.QuerySyntaxException: XWikiDocument is not mapped >[ select distinct doc.fullName from XWikiDocument as doc, BaseObject as >obj, StringProperty as prop where obj.name = doc.fullName and >obj.className='XWiki.XWikiGroups' and obj.id = prop.id.id and >prop.id.name='member' and (prop.value=:username or >prop.value=:shortname or prop.value=:veryshortname) ] This time the errors seem related to the searches themselves... I think that what might be happening is that Hibernate is not really configured to be using Glassfish datasource, but instead it expects to use the connection.username, connection.password, connection.driver_class, connection.pool_size ... properties defined in WEB-INF/hibernate.cfg.xml that i've commented out because i'd like to use Glassfish-configured datasource. I need help, so as to keep the properties that Hibernate reads from WEB-INF/hibernate.cfg.xml to a minimum and pointing it to Glassfish-defined JNDI resource instead. Thank you very much ! Guillem Plasencia

15 years, 7 months

1
1
0 0

[xwiki-devs] [Proposal] "Plug-in" application configuration using objects.

by Caleb James DeLisle

The problem: Each time an xar application is added, if it is to be configured it must alter XWikiPreferences and the administration application making the separation of different applications meaningless. The goal: Ability to install an application from an xar file and have configuration appear on the appropriate administration sheet, also the ability to remove an application easily without leaving anything behind. My proposal: Add a class called XWiki.Configurable, any document which contains an object of this class is pulled into the appropriate administration sheet via an includeForm call. Concerns: Upgradeability - We must be able to save the old configuration when the user does an update. I think this should be up to the individual application to detect that it has been updated, get it's configuration back from the document history and reinstall the old configuration. Security - We can't allow just anyone to create a page which will be pulled into the administration sheet. It must be limited to those with admin or programming rights. The Configurable class: I think it should contain two fields, one telling which administration sheet it should be displayed on and the other holding a version number which is incremented every time an application's configuration changes such that it cannot simply copy the old configuration into the updated application, much like the database is numbered according to the revision number of the last schema change. WDYT? Caleb

15 years, 7 months

3
6
0 0

[xwiki-devs] [ANN] XWiki Enterprise 2.2 Release Candidate 2 Released

by Thomas Mortagne

The XWiki development team is pleased to announce the release of XWiki Enterprise 2.2 RC 2. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This release is mostly a bugfix and stabilization release. Main changes from XWiki Enterprise 2.2 Release Candidate 1: * Several bugfixes on WYSIWYG and rendering * Several bugfixes on references refactoring * Use current database instead of current document database in Current*ReferenceResolver * New user profile pages are created in XWiki Syntax 2.0 * New zh_TW translation For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise22RC2 Thanks -The XWiki dev team

15 years, 7 months

1
0
0 0

[xwiki-devs] [ANN] XWiki Enterprise and XWiki Enterprise Manager 2.1.2 Released

by Jean-Vincent Drean

The XWiki development team is pleased to announce the release of XWiki Enterprise and XWiki Enterprise Manager 2.1.2 Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download Important bug fixes since 2.1.1: * XWIKI-4712 : Account Validation always fails * XWIKI-4615 : HTML export does not support Colibri skin * XWIKI-4695 : [regression] Private RSS feeds with Basic authentication does not work in some RSS clients * XWIKI-4708 : Double URL decoding of the document name * XWIKI-4709 : After editing a blog post and clicking "Preview" and "Back to edit" you are taken to page editing instead of blog post editing * XWIKI-4717 : Empty table cells not parsed correctly * XWIKI-4670 : WYSIWIG editor in Xwiki is slow under IE7 * XWIKI-4782 : Including a sheet in 2.0 syntax from a page in 1.0 syntax fails to display properly * XWIKI-4866 : Wrong skins/resources URLs generated on path based subwiki * XWIKI-4822 : Using XML symbols (<, >, &) inside the user's name breaks various parts of the UI and causes the PDF export to throw exceptions * XWIKI-4665 : Pressing Meta+G (Jump to page) in the WYSIWYG editor displays the popup inside the rich text area * XWIKI-4871 : Message macro does not support non inline content WYSIWYG: * XWIKI-4733 : Link is duplicated after being edited * XWIKI-4734 : Link changes style after being edited * XWIKI-4777 : Page titles are not interpreted when displayed in the Link dialog * XWIKI-4197 : No default font name and font size in IE 6&7 For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise212 http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM212 Thanks -The XWiki dev team

15 years, 7 months

1
0
0 0

Re: [xwiki-devs] [scala-user] Re: JSR 223?

by Story Henry

I asked the Scala group about the availability of a JSR-223 implementation, so that XWiki could make use of it. Below is one response, and here is the URL of the thread, in case other responses are added there in the meantime: http://old.nabble.com/JSR-223--td27529387.html Those who are familiar with JSR-223 might find it useful. Henry On 10 Feb 2010, at 13:33, michid wrote: > Story Henry <henry.story@...> writes: > >> I was just wondering if there is a good JSR-223 (plugin? Jar?) implementation >> for Scala. This would allow tools such as XWiki to easily make it available >> for scripting. Apparently if a language implements this, >> they can provide it just by placing a jar in a special directory. These are >> the jsr223 languages they support: Velocity, Groovy, Python, Ruby, PHP. > > Henry, > > I created a JSR-223 scripting engine for Apache Sling [1]. While it is used by > Sling and is interoperable with OSGi, it can also be used independently from > Sling and OSGi. The source is available from SVN [2] and there are some > instructions [3] on how to use it though these are mainly targeted to Sling. > > Note however, that the scripting engine is different from REPL scripting. It > only accepts 'real' Scala source entities as input. I chose this approach in > order to be able to use existing tools for developing scripts (i.e. editor, IDE, > debugging, unit testing). > > Michael > > [1] http://sling.apache.org/site/index.html > [2] http://svn.apache.org/repos/asf/sling/trunk/contrib/scripting/scala/script/ > [3] http://cwiki.apache.org/confluence/display/SLING/Using+Scala+with+Sling > > >

15 years, 7 months

2
1
0 0

[xwiki-devs] Problems installing 2.1 on Oracle OC4J

by Ian Neill

When I deploy xWiki to an Oracle Application server 10.3 and try to access the Wiki I get a 500 internal server error. The log file shows com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: java.lang.reflect.InvocationTargetException at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:341) ... Wrapped Exception: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ... Caused by: java.lang.SecurityException: Unauthorized access from application: xwiki to MBean: java.lang:type=ClassLoading at oracle.oc4j.admin.jmx.shared.UserMBeanServer.checkRegisterAccess(UserMBeanServer.java:873) >From what I can find out it is related to the security around Oracles JMX and the MBeans in xWiki, but I cann't seem to find a way to fix it. -- View this message in context: http://n2.nabble.com/Problems-installing-2-1-on-Oracle-OC4J-tp4548729p45487… Sent from the XWiki- Dev mailing list archive at Nabble.com.

15 years, 7 months

2
1
0 0

[xwiki-devs] [Proposal] Wiki logo as a property of the ColorTheme object

by Sergiu Dumitriu

Hi devs, Caty suggested a while ago to allow the users to set custom logos in the color theme. At first I thought this was not OK, since normally the logo should be the same regardless of the site colors, but now I realize it's a pretty good idea, because it ensures more flexibility, and, more importantly, it allows to workaround transparency issues that appear in some browsers (yes, I'm talking about IE6) by setting logos with the same background color as the header. The necessary changes would be: - in "ColorThemes.ColorThemeClass" add a property called 'logo' whose values are names of files attaches to the ColorTheme document - in "global.vm", when searching for the wiki logo, start by looking in the current ColorTheme, and, if not found, continue as before. WDYT? -- Sergiu Dumitriu http://purl.org/net/sergiu/

15 years, 7 months

3
2
0 0

[xwiki-devs] [VOTE] Release a XE 2.2 RC 2 before the 2.2 final

by Thomas Mortagne

Hi devs, We are not ready to release the 2.2 final version so I'm proposing to release a 2.2 RC 2 today and the final version on next Monday. Here is my +1. WDYT ? -- Thomas Mortagne

15 years, 7 months

5
8
0 0

[xwiki-devs] [VOTE] Releasing XE 2.1.2

by Vincent Massol

Hi, I think it's time to release XE 2.1.2, since there are quite a lot of fixes in it: http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10010&… Thomas, you have this one planned for 2.1.2, what's the status: http://jira.xwiki.org/jira/browse/XWIKI-4723 Thanks -Vincent

15 years, 7 months

3
3
0 0

[xwiki-devs] [VOTE] Use current database instead of current document database in Current*ReferenceResolver

by Thomas Mortagne

Hi devs, Currently when the reference does not contains any wiki name it's resolved using the wiki of the current document. Problem is that we generally use context wiki as the current wiki and references used to be resolved that way before the refactoring using official Resolver component. In many places we set the wiki we want to work on before doing a bunch of tasks: loading documents, executing queries etc... the problem is that when Current*ReferenceResolver is used you have to create some empty document and put it in the context just to set the wiki you want to work on. So i propose to change the behavior of all the Current*ReferenceResolver to get context wiki as default wiki name. Here is my +1 -- Thomas Mortagne

15 years, 7 months

5
8
0 0

[xwiki-devs] Disable some macros in wysiwyg

by farouk korteby

Hi, I want to disable some developpement macros in GWT based wysiwyg, how can i do it ? Thanks. -- Farouk Korteby

15 years, 7 months

4
7
0 0

[xwiki-devs] Removing viewheader.vm?

by Vincent Massol

Hi, I think viewheader.vm is not used anymore. I couldn't find any reference of it in other vm nor in skins. However it's still referenced from XWiki.java, in getSkinClass() (and from ApplicationResources*.properties files): needsUpdate |= bclass.addTemplateField("viewheader.vm", "View Header"); But I think this field is now not only useless but even misleading since filling it will have no effect AFAIK. Could someone confirm this? Does it mean people with custom skin will find their skin not working anymore? Anyone knows when viewheader.vm was stopped to be used because AFAICS this will break all existing custom skins? What new properties should we add t o the XWikiSkins class? Thanks -Vincent

15 years, 7 months

3
3
0 0

Re: [xwiki-devs] [xwiki-notifications] r26828 - platform/xwiki-applications/trunk/administration/src/main/resources/XWiki

by Vincent Massol

Hi Caleb, This commit has broken a functional test, please see: http://bit.ly/aNzmAF Thanks -Vincent On Tue, Feb 9, 2010 at 6:49 AM, cjdelisle <platform-notifications(a)xwiki.org> wrote: > Author: cjdelisle > Date: 2010-02-09 06:49:32 +0100 (Tue, 09 Feb 2010) > New Revision: 26828 > > Modified: > platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/Registration.xml > Log: > XAADMINISTRATION-103: Make registration page support lightbox so administrator can use it to add users in admin users sheet. - Modified registration page to be compatable with lightbox, also moved form tags and submit button outside of generateHtml macro. > > Modified: platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/Registration.xml > =================================================================== > --- platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/Registration.xml 2010-02-09 05:46:48 UTC (rev 26827) > +++ platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/Registration.xml 2010-02-09 05:49:32 UTC (rev 26828) > @@ -74,6 +74,11 @@ > #set($loginPage = 'XWiki.XWikiLogin') > #set($loginAction = 'loginsubmit') > ## > +## If this is true, then assume the registration page is being viewed inside of a lightbox > +#if($request.get('xpage')) > + #set($assumeLightbox = true) > +#end > +## > ## Use javascript based live validation see: http://www.livevalidation.com > ## Set false to stop using LiveValidation > #set($useLiveValidation = true) > @@ -457,16 +462,68 @@ > ## Then we display the registration form. > #if(!$registrationDone) > $welcomeMessage > - {{html clean=false}} > - ## I do not want to put this inside of a paragraph block so I end the block here and > - ## start it at the end. > - </p> > + {{html clean=false wiki=false}} > + <div> > + <form id="register" action="" method="post"> > + <div> > #generateHtml($fields, $fieldMandatoryStar, $failureMessageParams) > + <span class="buttonwrapper"> > + #if($assumeLightbox) > + ## LightBox detected... > + <script type="text/javascript"> > + ## Make the X button not reload the page. (overriding LbClose) > + window.lb.lbClose = function() { > + this.lbHide(); > + this.lbClearData(); > + ##return false; > + } > + ## Post the form entry to the page and load the result. (we override lbSaveForm) > + window.lb.lbSaveForm = function() { > + var formParams = Form.serialize(this.form); > + Form.disable(this.form); > + var ajaxRequest = new Ajax.Request(this.saveUrl, { > + parameters: formParams, > + asynchronous: false > + }); > + window.lb.lbFormDataLoaded(ajaxRequest.transport); > + } > + </script> > + ## It doesn't really matter where these are, the scripts will be relocated to the head. > +  > +  > + ## > + <input class="button" type="submit" value="$msg.get('save')" onclick="window.lb.lbSaveForm();"/> > + </span>#* End ButtonWrapper then start another...*#<span class="buttonwrapper"> > + <input class="button" type="submit" value="$msg.get("cancel")" onclick="Form.disable(window.lb.form); window.lb.lbClose();"/> > + #else > + ## Not using the LightBox > + <input type="submit" value="$msg.get('core.register.submit')" class="button"/> > + #end > + </span>## ButtonWrapper > + </div> > + </form> > #if($useLiveValidation) > #generateJavascript($fields) > #end > - <p> > + </div> > {{/html}} > +## If the registration is done (successful) and we detect the Lightbox simply send the user back to the original page. > +#elseif($assumeLightbox) > + {{html clean=false wiki=false}} > + <script type="text/javascript"> > + var url = window.lb.redirectUrl; > + window.lb.lbClose; > + if (url != undefined) { > + if(window.location.pathname + window.location.search == url) { > + ## Under certain circumstances (bug) Opera will not load a page if the location is the same as the current page. > + ## In these cases, location.reload() doesn't work either, the only solution (I could find) was to change the URL. > + window.location.href = url + "&"; > + } else { > + window.location.href = url; > + } > + } > + </script> > + {{/html}} > #end > ## > ####### The Macros (nothing below this point is run directly) ######### > @@ -608,7 +665,8 @@ > </span> > </div> > </form> > - #if($autoLogin) > + ## We don't want autoLogin if we are administrators adding users... > + #if($autoLogin && !$assumeLightbox) > <script type='text/javascript'> > document.observe('dom:loaded', function() { > document.forms['loginForm'].submit(); > @@ -632,59 +690,54 @@ > ## Put the same values back into the fields. > #getParams($fields) > ## > - <form id="register" action="" method="post"> > - <div><dl> > - ## > - #foreach($field in $fields) > - #if($field.get('name')) > - #set($fieldName = $field.get('name')) > - #if($field.get('label')) > - #set($label = $field.get('label')) > - <dt><label for="$fieldName">$label</label> > - #if($field.get('validate').get('mandatory')) > - <span > - #foreach($entry in $fieldMandatoryStar.entrySet()) > - $entry.getKey()="$entry.getValue()" > - #end > - >*</span> > + <dl> > + #foreach($field in $fields) > + #if($field.get('name')) > + #set($fieldName = $field.get('name')) > + #if($field.get('label')) > + #set($label = $field.get('label')) > + <dt><label for="$fieldName">$label</label> > + #if($field.get('validate').get('mandatory')) > + <span > + #foreach($entry in $fieldMandatoryStar.entrySet()) > + $entry.getKey()="$entry.getValue()" > #end > - </dt> > + >*</span> > #end > - ## If no tag then default tag is <input> > - #if($field.get('tag')) > - #set($tag = $field.get('tag')) > - #else > - #set($tag = 'input') > + </dt> > + #end > + ## If no tag then default tag is <input> > + #if($field.get('tag')) > + #set($tag = $field.get('tag')) > + #else > + #set($tag = 'input') > + #end > + <dd><$tag id="$fieldName" > + #set($params = $field.get('params')) > + ## If no name parameter is spacified, then we use the field name > + #if(!$params.get('name')) > + #set($discard = $params.put('name', $fieldName)) > + #end > + #foreach($entry in $params.entrySet()) > + ## If a parameter is specified as '' then we don't include it. > + #if($entry.getValue() != '') > + $entry.getKey()="$escapetool.html($entry.getValue())" > #end > - <dd><$tag id="$fieldName" > - #set($params = $field.get('params')) > - ## If no name parameter is spacified, then we use the field name > - #if(!$params.get('name')) > - #set($discard = $params.put('name', $fieldName)) > + #end > + ></$tag> > + #if($field.get('error')) > + <span > + #foreach($entry in $failureMessageParams.entrySet()) > + $entry.getKey()="$entry.getValue()" > #end > - #foreach($entry in $params.entrySet()) > - ## If a parameter is specified as '' then we don't include it. > - #if($entry.getValue() != '') > - $entry.getKey()="$escapetool.html($entry.getValue())" > - #end > - #end > - ></$tag> > - #if($field.get('error')) > - <span > - #foreach($entry in $failureMessageParams.entrySet()) > - $entry.getKey()="$entry.getValue()" > - #end > - >$field.get('error')</span> > - #end > - </dd> > - #else > - ERROR: Field with no name. > - #end##if fieldName exists > - #end > - </dl> > - <span class="buttonwrapper"><input type="submit" value="$msg.get('core.register.submit')" class="button"/></span> > - </div> > - </form> > + >$field.get('error')</span> > + #end > + </dd> > + #else > + ERROR: Field with no name. > + #end##if fieldName exists > + #end > + </dl> > #end > ## > ## Remove newlines inside of tags because tags are generated by loops.

15 years, 7 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r26812 - platform/xwiki-applications/trunk/watchlist/src/main/resources/XWiki

by Sergiu Dumitriu

On 02/08/2010 05:40 PM, jvdrean (SVN) wrote: > Author: jvdrean > Date: 2010-02-08 17:40:01 +0100 (Mon, 08 Feb 2010) > New Revision: 26812 > > Modified: > platform/xwiki-applications/trunk/watchlist/src/main/resources/XWiki/WatchListManager.xml > Log: > XPWATCHLIST-101 : Various accessibility issues in XWiki.WatchListManager > > Modified: platform/xwiki-applications/trunk/watchlist/src/main/resources/XWiki/WatchListManager.xml > =================================================================== > --- platform/xwiki-applications/trunk/watchlist/src/main/resources/XWiki/WatchListManager.xml 2010-02-08 16:37:47 UTC (rev 26811) > +++ platform/xwiki-applications/trunk/watchlist/src/main/resources/XWiki/WatchListManager.xml 2010-02-08 16:40:01 UTC (rev 26812) > @@ -117,7 +227,7 @@ > <tr> > #set ($idoc = $xwiki.getDocument($item)) > #if (!$idoc.isNew()) This was just removed, bad merge. > -<td><a href="$idoc.getURL()">$idoc.getDisplayTitle()</a></td> > +<td><a href="$idoc.getURL()">$idoc.getDisplayTitle().replaceAll("[^\\.,:]+:", "")</a></td> > <td>$idoc.space</td> > <td><a href="$doc.getURL("view", "removedocument=${item}")" title="$msg.get("watchlist.delete.tooltip")">$msg.get("watchlist.delete")</a></td> > #else -- Sergiu Dumitriu http://purl.org/net/sergiu/

15 years, 7 months

2
1
0 0

[xwiki-devs] [VOTE] Remove Main.RecentMembers from XE wiki

by Jean-Vincent Drean

Hi devs, While fixing WCAG issues I've discovered the Main.RecentMembers page. It looks deprecated and AFAIK it's not linked from anywhere. In order to keep the distrbution clean I'd like to remove it before 2.2 final. Here's my +1. Thanks, JV.

15 years, 7 months

6
5
0 0

[xwiki-devs] Problem in XEM with entity references refactoring

by Vincent Massol

Hi, Just to let you know I've found an important problem in XEM, caused by the changes brought by the entity references. The pb is in XWikiDocument's code for object manipulation. I've replaced the Map of String that was used to store objects with a Map of DocumentReference. So when you have code like: XWikiDocument doc = context.getWiki().getDocument("wiki:space.page", context); BaseObject obj = doc.getObject("XWiki.SomeClass); And if context.getDatabse() = "currentWiki" (with "currentWiki" != "wiki") Then doc.getObject will check if there's an object of ref "currentWiki:XWiki.SomeClass" in doc, which won't be found since there might indeed be an object but of ref "wiki:XWiki.SomeClass"... Basically we now allow objects and classes in a document to reference classes located in another wiki. To fix this all calling code should be modified to use full references. However since this isn't going to happen fast enough for 2.2 final and since in any case it could break user's code I think we need to modify XWikiDocument so that all class/object methods ignore the wiki part of the references, thus assuming all classes/objects refer to classes/objects in the current wiki, as it was assumed before... Let me know if you agree. I'll start looking at the code to see how much there is to do that in the meantime. Thanks -Vincent

15 years, 7 months

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