Hi everyone,
We're about to release XE 2.2 final tomorrow.
If you know of any critical/blocking issue that remains please let us know quickly so that we can fix it before the release.
Thanks a lot
-Vincent
Hi devs,
I would like to add a Lucene related section in Admin page. I will
mainly contains a UI to control new possibilities coming with
http://jira.xwiki.org/jira/browse/XPLUCENE-29
I'm trying to find where to put it:
1/ A new Lucene application
Lucene is a plugin you can install anywhere you want, should be the
same for the related UI. In that case the Lucene search page should
also move into the Lucene application.
2/ Admin application
The Lucene admin page has to be targeted from Admin UI anyway since
the UI is static for now.
3/ XE application
It already contains Lucene search page.
I'm +1 for 1/ and -0 for 2/ and 3/
--
Thomas Mortagne
Hi,
I've started adding:
/**
* Return default values for specified Entity Reference types. Useful when an Entity Reference value has not been
* specified and we need to find a default value for it (the default value returned will depend on the implementations,
* some will return default values defined in the XWiki configuration, others will return values taken from the
* current document reference, etc).
*
* @version $Id$
* @since 2.3M1
*/
@ComponentRole
public interface EntityReferenceValueProvider
{
/**
* @param type the entity reference type for which to get the default value
* @return the default value for the passed type
*/
String getDefaultValue(EntityType type);
}
The idea is to use it in our resolvers but also to allow using it by any code that needs to get default values.
My initial itch was to remove all the code duplication we currently have in the resolver implementations.
Just yell if you don't agree. I'm about to commit it in about 1 hour.
Thanks
-Vincent
Hello XWiki Rendering Experts,
This is something used to work sometime ago but it seems things have
changed.
I have the following rendering test case:
<code>
.#----------------------------
-------------------------
.input|xwiki/2.0
.#-----------------------------------------------------
{{velocity}}
#set($url=$xwiki.zipexplorer.getFileLink($doc, 'presentation.zip',
'output.html'))
{{html}}
<iframe src="$url" frameborder=0 width=800px height=600px></iframe>
{{/html}}
{{/velocity}}
.#-----------------------------------------------------
.expect|xhtml/1.0
.#-----------------------------------------------------
</code>
The problem is, this test case passes. Which means the velocity / html
macros are rendered into nothing... I'm pretty certain this used to work
sometime ago (I didn't change anything) but it seems to be broken now.
Can you help me fix this? Wysiwyg ppt imports are broken because of this.
Thanks.
- Asiri
Hi Asiri,
On Feb 13, 2010, at 5:03 PM, asiri (SVN) wrote:
> Author: asiri
> Date: 2010-02-13 17:03:01 +0100 (Sat, 13 Feb 2010)
> New Revision: 27005
>
> Modified:
> platform/web/trunk/xwiki-gwt-wysiwyg-server/src/main/java/com/xpn/xwiki/wysiwyg/server/plugin/importer/XWikiImportService.java
> Log:
> * Added missing @Requirement annotation which was causing total failure of wysiwyg office imports.
> * This typo does not seem to be present in any other branches.
>
> Modified: platform/web/trunk/xwiki-gwt-wysiwyg-server/src/main/java/com/xpn/xwiki/wysiwyg/server/plugin/importer/XWikiImportService.java
> ===================================================================
> --- platform/web/trunk/xwiki-gwt-wysiwyg-server/src/main/java/com/xpn/xwiki/wysiwyg/server/plugin/importer/XWikiImportService.java 2010-02-13 15:40:57 UTC (rev 27004)
> +++ platform/web/trunk/xwiki-gwt-wysiwyg-server/src/main/java/com/xpn/xwiki/wysiwyg/server/plugin/importer/XWikiImportService.java 2010-02-13 16:03:01 UTC (rev 27005)
> @@ -67,6 +67,7 @@
> /**
> * The component used to parse attachment references.
> */
> + @Requirement
> private AttachmentReferenceResolver<String> attachmentReferenceResolver;
Are you sure about this?
In the 2.2 branch we have:
/**
* The component used to parse attachment references.
*/
@Requirement("current")
private AttachmentReferenceResolver attachmentReferenceResolver;
Thanks
-Vincent
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.
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
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/