I finally committed my LuceneContainer project into
incubator svn
. The project contains also a demo application.

The LuceneContainer is simple Vaadin container integrated with
the lucene index
. For more information and live demo visit the homepage of
the LuceneContainer

Please reply to the thread if you have bug reports or feature requests.

edit: fixed demo url


I, just added the support for the server side lazy loading into the LuceneContainer. Now, also the sorting is optional, which saves the memory if no sorting is needed. Please, test it and report back if you find bugs etc :slight_smile:


I updated the LuceneContainer add-on and its demo application. It is now more tightly integrated with the There is two new classes: LuceneContainerItem and LuceneContainerProperty.

I’m trying to use your component but I have issues compiling it into my widgetset. The issue I have is that it is not seen during the process. For example:

INFO: Widgetsets found from classpath:
	com.vaadin.terminal.gwt.DefaultWidgetSet in jar:file:Z:/NetBeans/Xinco/3.00.xx/XincoLibs/vaadin-6.7.2.jar!/
	org.vaadin.easyuploads.EasyuploadsWidgetset in jar:file:Z:/NetBeans/Xinco/3.00.xx/XincoLibs/Vaadin Addons/easyuploads-0.4.9.jar!/
	org.vaadin.hene.expandingtextarea.widgetset.ExpandingtextareaWidgetset in jar:file:Z:/NetBeans/Xinco/3.00.xx/XincoLibs/Vaadin Addons/expandingtextarea-0.1.jar!/
	org.vaadin.risto.stepper.widgetset.StepperWidgetset in jar:file:Z:/NetBeans/Xinco/3.00.xx/XincoLibs/Vaadin Addons/stepper-1.1.0.jar!/

Your add-on is in the same folder as the others and part of the class path. Maybe a version issue? I’m on Vaadin 6.7.2.

Never mind, it does work even not showing there.

It is a fully server-side add-on so there is nothing to include in the widgetset for it.

Hello Johannes Tuikkala,

I am trying to use LuceneContainer, but JBoss7 was giving me the following error:

Caused by: javax.persistence.PersistenceException: PersistenceProvider ’ org.eclipse.persistence.jpa.PersistenceProvider ’ not found

This problem is related to jpa and persistence.xml, none of which I am using in my project. And so it left me puzzling for a whole day as to the sources of the problem. By a tedious process of elimination, I identified LuceneContainer as the culprit – precisely, in the /lucene/META-INF/persistence.xml file.

Why force the user to use eclipselink.jar? In JBoss7 (which is what I am using), eclipselink as a ‘persistence provider’ is not yet supported. There is not even a LuceneContainer README to inform users of the eclipselink requirement. See the LuceneContainer persistence.xml below:

<?xml version="1.0" encoding="UTF-8"?>




Good job with the LuceneContainer; I have no choice but to ‘dis-use’ it in my project.