Widgetset does not contain implementation for
org.vaadin.openesignforms.ckeditor.CKEditorTextField.
Check its @ClientWidget mapping, widgetsets GWT module
descrioption file and re-compile your widgetset. Unrendered UIDL:
org.vaadin.openesignforms.ckeditor.CKEditorTextField(NO CLIENT IMPLEMENTATION FOUND)
Can anyone say me why my CKEditor cannot be loaded?
It’s all during compile time: I’ve put link to this widget in web.xml file, too.
Unfortunately, I’m traveling now so I don’t have access to my Vaadin dev box.
Did you do a Vaadin compile after you put the JAR in? It does expect 6.3 and I think it was compiled with JDK 1.6, should any of that matter. I’m sure if you download the source and compile it with JDK 1.5 it will work though, if that’s an issue.
I know that any time you use a widget JAR like this, you do need to do a Vaadin compile to do the widgetsets. Hope that helps…
Even though you just need to drop the JAR in you WEB-INF/lib, you need to do the Vaadin compile which wraps the GWT compile (I believe) so that the client-side javascript is generated. This is true of all components that have a client-side element (GWT or Vaadin).
I don’t use Netbeans, so have no specific knowledge. With the Eclipse Vaadin plugin, you can just click a button.
I recompiled and released a 0.3 version that resolves a compile error introduced in the past month with changes to the Vaadin 6.3 nightly builds. The code now uses the EventId class for literals which must be the new standard. There was no real functional change, just this code change so it will compile using the latest 6.3 nightly JAR. Once 6.3 is officially released, we’ll be sure to keep it current only with the standard releases and not nightly builds.
Hello David
Im developing a vaadin portlet for liferay im using CKEditor wrapper for vaadin 0.7
I’m using eclipse with vaadin 6.4.6 and java 1.6
after i complied it and deploy the portlet its this message appeared
Widgetset does not contain implementation for org.vaadin.openesignforms.
ckeditor.CKEditorTextField.
Check its @ClientWidget mapping,
widgetsets GWT module descrioption file and re-compile your widgetset.
Unrendered UIDL:
I hope someone at Vaadin or someone familiar with the portlet and/or Liferay has some insights. I do not know what the issue would be. In my own regular Vaadin project, I just put the JAR in the WEB-INF/lib and recompile the widgetset, which shows my JAR in the list. Naturally, it works fine.
Is it possible that Liferay/portlet runtime is not using Java 6, since that is the one oddity compared to standard Vaadin components. (I did try Java 5, but the code did not compile because we were using some Java 6isms and we had no interest in spending time to restructure the code to make it work on old technology we’ll never use ourselves.)
I have noted in my Eclipse project, if I just put the new JAR in WEB-INF/lib (and remove the prior version), and the project is not configured to use the JAR (project Properties → Java Build Path → Libraries), my code won’t compile if it uses new API calls in the new release unless I close and re-open the project. So, we either close/reopen, or we configure it as Library in Eclipse. Maybe it’s somehow related? I hope someone else can help answer this…
On Liferay, a shared copy of a widgetset (typically PortalDefaultWidgetset) on the portal is used - that widgetset needs to be compiled with the version of Vaadin that is used on the portal (or by the portlet), or you need to tell the portal to use another (shared) widgetset by default.
I would recommend testing out the
Vaadin Control Panel for Liferay , which takes care of widgetset compilation etc. - you just need to drop the right add-ons and GWT JARs in the correct directory on the portal, and start widgetset compilation from the portlet.
Also, your project should probably refer to the Vaadin JAR in the portal in your liferay-plugin-package.properties and have it on the classpath instead of having a Vaadin JAR in your project.
