Vaadin

Join Vaadin Log In
Combination View Flat View Tree View
Threads [ Previous | Next ]
Refresher
toggle
Refresher Henrik Paul 5/19/10 6:22 AM
RE: Refresher Henrik Paul 10/22/09 6:30 AM
RE: Refresher Henrik Paul 10/22/09 6:14 PM
HOWTO for beginners Jean-François Lamy 10/23/09 3:00 AM
RE: HOWTO for beginners Henrik Paul 10/23/09 5:31 AM
RE: HOWTO for beginners Jouni Koivuviita 10/23/09 11:50 AM
RE: HOWTO for beginners Jean-François Lamy 10/23/09 6:53 PM
RE: HOWTO for beginners Jouni Koivuviita 10/23/09 7:59 PM
RE: HOWTO for beginners Henrik Paul 10/23/09 8:13 PM
RE: HOWTO for beginners Jean-François Lamy 10/23/09 9:22 PM
RE: HOWTO for beginners Jean-François Lamy 10/23/09 8:16 PM
RE: Refresher Henri Muurimaa 12/20/09 9:54 PM
RE: Refresher Brain Max Lt 4/21/10 11:47 AM
RE: Refresher Henrik Paul 4/21/10 11:53 AM
RE: Refresher Nagaraju Magati 4/29/10 7:24 PM
RE: Refresher Henrik Paul 4/30/10 5:16 AM
RE: Refresher Arthur S 5/18/10 5:37 PM
RE: Refresher Arthur S 5/18/10 6:21 PM
RE: Refresher Arthur S 5/18/10 6:29 PM
RE: Refresher Joonas Lehtinen 5/18/10 6:30 PM
RE: Refresher Arthur S 5/18/10 7:40 PM
RE: Refresher Arthur S 5/18/10 8:36 PM
RE: Refresher Henrik Paul 5/19/10 6:24 AM
RE: Refresher Arthur S 5/19/10 12:00 PM
RE: Refresher Julio C Vergara 6/22/10 5:10 PM
RE: Refresher Henrik Paul 6/23/10 6:16 AM
RE: Refresher Joseph george 8/5/10 9:57 AM
RE: Refresher Teemu Pöntelin 6/23/10 6:10 AM
RE: Refresher Julio C Vergara 6/24/10 12:06 PM
RE: Refresher Julio C Vergara 6/24/10 1:26 PM
RE: Refresher Henrik Paul 6/28/10 5:39 AM
RE: Refresher Joseph george 8/5/10 9:51 AM
RE: Refresher Henri Sara 8/5/10 10:27 AM
RE: Refresher Henrik Paul 8/5/10 10:29 AM
RE: Refresher J Loke 7/15/10 6:04 AM
RE: Refresher Henrik Paul 7/26/10 5:34 AM
RE: Refresher Henri Muurimaa 7/28/10 1:11 PM
Refresher
5/19/10 6:22 AM
While I have this component in another package (called HComponents), I've re-packaged them as single components. They are also compatible with a current Vaadin 6.2-nighty. HComponents will be deprecated.

The Refresher is a component that tries to help with the lack of a push-functionality in Vaadin. It's a component that polls asynchronous UI changes from the server. While UI changes are normally made only during a user-initiated roundtrip from the client to the server and back, with the Refresher, you can have a background process that updates the UI with the user being inactive.

While a picture tells more than a thousand words, this video tells more than a few handful of pictures.

Sources are available at the incubator at http://dev.vaadin.com/svn/incubator/Refresher/ Sources moved to http://dev.vaadin.com/svn/contrib/Refresher/, but check the Directory for the official addon entry.

You are welcome to try the component out for yourself at http://henrik.virtuallypreinstalled.com/Refresher/
Flag Flag
RE: Refresher
10/22/09 6:30 AM as a reply to Henrik Paul.
Note for interested users: These are only the sources for the component. I will later today provide a JAR file that you can just drop in, instead of needing clutter your project with sources from various package structures.
Flag Flag
RE: Refresher
10/22/09 6:14 PM as a reply to Henrik Paul.
Jar is now in SVN! (http://dev.vaadin.com/browser/incubator/Refresher/refresher-0.0.1.jar). If you're using one of the latest Vaadin 6.2 nightlies and the experimental Eclipse plugin, you should be able to just drop the jar in your classpath, agree to re-compiling your widgetset, and you should be set.

Make sure that you have the string "<inherits name="com.vaadin.incubator.refresher.RefresherApplicationWidgetset" />" in your application's widgetset.gwt.xml-file.
Flag Flag
HOWTO for beginners
10/23/09 3:00 AM as a reply to Henrik Paul.
Thanks much for the pointers, but I had to do a bit more guesswork to get things working, because my application had no widgetset to begin with (as many people I suspect, I started with AddressBook and mutated it)

A ) The first thing to do is to edit web.xml to add a widget set named after your application
 1
 2    <servlet>
 3        <servlet-name>CompetitionApplication</servlet-name>
 4        <servlet-class>com.vaadin.terminal.gwt.server.ApplicationServlet</servlet-class>
 5        <init-param>
 6            <param-name>application</param-name>
 7            <param-value>org.concordiainternational.competition.ui.CompetitionApplication</param-value>
 8        </init-param>
 9        <init-param>
10            <description>Application widgetset</description>
11            <param-name>widgetset</param-name>
12            <param-value>org.concordiainternational.competition.ui.CompetitionApplicationWidgetset</param-value>
13        </init-param>
14    </servlet>


B ) You need to create a .xml file next to the application's .java (in this case, CompetitionApplicationWidgetset.gwt.xml ). with the following content (adjust for the various widget sets you are including)
1<module>
2    <!-- Inherit super widgetset -->
3    <inherits name="com.vaadin.terminal.gwt.DefaultWidgetSet" />
4    <inherits name="com.vaadin.incubator.superimmediatetextfield.SuperimmediatetextfieldApplicationWidgetset" />
5    <inherits name="com.vaadin.incubator.refresher.RefresherApplicationWidgetset" />
6</module>


C ) Drop the various jars for the widgetsets in your WEB-INF/lib (I took the Refresher and SuperImmediateTextField jars)

D ) If you want to recompile your widget set, there is a vaadin logo in the toolbar after you install the plugin. In theory you should be able to click on your project and trigger a recompile, but for some reason, this has stopped working for me. What seems to work reliably is to click on the .gwt.xml file that defines the widgetset, and then click on the icon.
Flag Flag
RE: HOWTO for beginners
10/23/09 5:31 AM as a reply to Jean-François Lamy.
Jean-François Lamy:
Thanks much for the pointers, but I had to do a bit more guesswork to get things working...


Thanks for the comprehensive how-to steps! I sure hope R&D will be supplying us with an official step-by-step howto/checklist for these new Vaadin Addons. But, to be fair, this is a very new feature, and it's only in the nightlies for now.

The R&D team has said that they have wishes and plans that the Plugin will handle all this even more intelligently, so I, for one, will be eagerly waiting for these updates.

In any case, these pointers might serve better outside this thread – I doubt people finding these nuggets of information from this thread, if they have the same problems.

Jean-François Lamy:
D ) If you want to recompile your widget set, there is a vaadin logo in the toolbar after you install the plugin. In theory you should be able to click on your project and trigger a recompile, but for some reason, this has stopped working for me. What seems to work reliably is to click on the .gwt.xml file that defines the widgetset, and then click on the icon.


I had troubles getting the vaadin-logo-compiler to work, too. The trick I did to get it working is to use the Project Explorer (I normally use the Package Explorer, which didn't work for me), and you have to make sure that the Project Explorer is active (and not, say, your source code window) before you click on the icon – otherwise the plugin doesn't understand which project you are trying to compile. The R&D has, again, expressed their regrets about this, they have are planning on getting this more robustly done.
Flag Flag
RE: HOWTO for beginners
10/23/09 11:50 AM as a reply to Jean-François Lamy.
Just to make things a bit easier:
Jean-François Lamy:
Thanks much for the pointers, but I had to do a bit more guesswork to get things working, because my application had no widgetset to begin with (as many people I suspect, I started with AddressBook and mutated it)

A ) The first thing to do is to edit web.xml to add a widget set named after your application

No longer needed with the latest plugin, you can ignore your web.xml on this part, as long as you don't have your own widgetset in that project.

Jean-François Lamy:
B ) You need to create a .xml file next to the application's .java (in this case, CompetitionApplicationWidgetset.gwt.xml ). with the following content (adjust for the various widget sets you are including)

Again, not needed. The Vaadin Widgetset Compiler will generate this for you automatically.

Happy compiling!

ps. remember, currently only with the latest and greatest plugin & nightlies
Flag Flag
RE: HOWTO for beginners
10/23/09 6:53 PM as a reply to Jouni Koivuviita.
Well, not quite.

If I drop two jars, and omit the .gwt.xml that does the inherits for both, the plugin gets confused and seems to generate a widget set named after the first jar, and gives a warning of the form
1[WARN] Widget implementation for com.vaadin.incubator.refresher.Refresher not available for GWT compiler (but mapped for component found in classpath). If this is not intentional, check your gwt module definition file.


Your comment could be interpreted in two ways:
a) the file is no longer necessary OR
b) the plugin now deals with the file and you no longer have to.

So it seems that at least the gwt file is required.
Flag Flag
RE: HOWTO for beginners
10/23/09 7:59 PM as a reply to Jean-François Lamy.
Jean-François Lamy:
If I drop two jars, and omit the .gwt.xml that does the inherits for both, the plugin gets confused and seems to generate a widget set named after the first jar, and gives a warning of the form
1[WARN] Widget implementation for com.vaadin.incubator.refresher.Refresher not available for GWT compiler (but mapped for component found in classpath). If this is not intentional, check your gwt module definition file.

You get the warning because Henrik has made a small mistake in packaging the JAR: the source files are not included, only the compiled .class-files. The GWT Compiler needs the actual .java-files. So this is Henrik's problem, ask for a new JAR.

The Widgetset Compiler should name the generated widgetset after the project, not one single JAR, as far as I know.

Jean-François Lamy:
Your comment could be interpreted in two ways:
a) the file is no longer necessary OR
b) the plugin now deals with the file and you no longer have to.

So it seems that at least the gwt file is required.

Do you mean web.xml or the .gwt.xml?

You can ignore the thing I said about web.xml, I guess you still need to specify the used widgetset there. My mistake.

About .gwt.xml, I can't say 100% sure how this is, since I'm not involved in the code level development of the plugin. But as I interpret it, the plugin generates the .gwt.xml file for you, and uses that in the compilation.

I hope Matti will provide us with more clear instructions soon enough, since I'm probably just confusing people more emoticon
Flag Flag
RE: HOWTO for beginners
10/23/09 8:13 PM as a reply to Jouni Koivuviita.
Jouni Koivuviita:
You get the warning because Henrik has made a small mistake in packaging the JAR: the source files are not included, only the compiled .class-files.


Although this starts to get off-topic (as the refresher has its own thread), I just checked that the jar in SVN contains both .java and .class files for both the server and client side components. The same applies to the SITF jar. There must be some kind of confusion here.
Flag Flag
RE: HOWTO for beginners
10/23/09 8:16 PM as a reply to Jouni Koivuviita.
As of 2009-10-13, both the entry in web.xml and the presence of a Application.gwt.xml file are required,

In my test configuration, the plugin does not generate a .gwt.xml. Furthermore, it does not correctly generate a widgetset when two jars are present.

The workaround is to add a .gwt.xml with inheritance for the two widgetsets.
Flag Flag
RE: HOWTO for beginners
10/23/09 9:22 PM as a reply to Henrik Paul.
Is there a way to move the "widgetset" HOWTO to its own thread somewhere else ?
Flag Flag
RE: Refresher
12/20/09 9:54 PM as a reply to Henrik Paul.
Henrik Paul:
you should be able to just drop the jar in your classpath, agree to re-compiling your widgetset, and you should be set.

Just to report that I just did that on 6.2.0 and everything is peachy, no other actions required. I love the new packaging system! emoticon

The refresher is very nice too, it's completely usable despite the too-modest version number.
Flag Flag
RE: Refresher
4/21/10 11:47 AM as a reply to Henri Muurimaa.
hi..
i want to implement refresher in my vaadin web, i'm using jetty and equinox for moduling as plugin my web application.
i want to asking about how i can implement the refresher component, in last tutorial explainded that configure it to web.xml, i'm really not using this file for configure the servlet becouse i'm using HttpService from osgi to register any servlet..
how can i introduce the refrehser component to my servlet that register with httpservice from osgi?
Flag Flag
RE: Refresher
4/21/10 11:53 AM as a reply to Brain Max Lt.
I'm not really sure about the problems you have with this, but OSGi, Jetty or Equinox shouldn't have anything to do with Vaadin add-ons. Please read http://vaadin.com/directory/help/using-vaadin-add-ons about how to use Vaadin add-ons.

To be clear, Refresher is a Vaadin add-on.
Flag Flag
RE: Refresher
4/29/10 7:24 PM as a reply to Henrik Paul.
Henrik,

Once you add Refresher to your layout, if user never closes the connection or goes idle does session expires automatically ? In otherwords, how do I still make session to expire when user is idle for long time?

Thanks

Raj.
Flag Flag
RE: Refresher
4/30/10 5:16 AM as a reply to Nagaraju Magati.
Nagaraju Magati:
Once you add Refresher to your layout, if user never closes the connection or goes idle does session expires automatically ?


No, as long as the Refresher is active (i.e. the component is refreshing, and the browser tab is still open), there is constant traffic between the browser and the server, therefore the session doesn't have a chance to expire...

You could try to have some kind of timer thread in your server that is reset every time the user does something of importance to your application, and once the timer runs out, you disable the refresher. After that, there is no traffic, and the session is allowed to start to expire.
Flag Flag
RE: Refresher
5/18/10 5:37 PM as a reply to Henrik Paul.
http://dev.vaadin.com/svn/incubator/Refresher/

Not Found
The requested URL /svn/incubator/Refresher/ was not found on this server.


Where can I find latest Refresher?

Thanks,
Arthur.
Flag Flag
RE: Refresher
5/18/10 6:21 PM as a reply to Henrik Paul.
I spend a lot of time analyzing sources and I found last Refresher here http://dev.vaadin.com/browser/incubator/Refresher?rev=10926 .

Where is it now? Was it replaced by new component/strategy?

I am using lates Vaadin 6.3.2.

Thanks,
Arthur.
Flag Flag
RE: Refresher
5/18/10 6:29 PM as a reply to Arthur S.
OK, now I found refresher here http://dev.vaadin.com/browser/contrib/Refresher thanks to google.

It's sad that searcher on dev.vaadin.com can't simply show location.

Thanks,
Arthur.
Flag Flag
RE: Refresher
5/18/10 6:30 PM as a reply to Arthur S.
Flag Flag
RE: Refresher
5/18/10 7:40 PM as a reply to Joonas Lehtinen.
Thanks, that is better searcher.

Now I have next problem.

In broswer I am getting

Widgetset does not contain implementation for org.vaadin.henrik.refresher.Refresher. Check its @ClientWidget mapping, widgetsets GWT module descrioption file and re-compile your widgetset. Unrendered UIDL:

org.vaadin.henrik.refresher.Refresher(NO CLIENT IMPLEMENTATION FOUND) id=PID3 pollinginterval=1000


or

HTTP Status 500 -

type Exception report

message

descriptionThe server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: java.lang.NoClassDefFoundError: org/vaadin/henrik/refresher/Refresher

root cause

java.lang.NoClassDefFoundError: org/vaadin/henrik/refresher/Refresher


I am using Eclipse. I added

<init-param>
<param-name>widgetset</param-name>
<param-value>org.vaadin.henrik.refresher.RefresherApplicationWidgetset</param-value>
</init-param>

to my web.xml

and

<inherits name="org.vaadin.henrik.refresher.RefresherApplicationWidgetset" />

to my *Widgetset.gwt.xm but it is always replaced with standard <inherits name="com.vaadin.terminal.gwt.DefaultWidgetSet" /> .

I also added refresher-1.0.0.jar to my libraries and checked to include it in Properties -> Java EE Module Dependences .

My program is as simple as Refresher example from here http://dev.vaadin.com/browser/contrib/Refresher .

Any suggestions what to do?

Thanks,
Arthur.
Flag Flag
RE: Refresher
5/18/10 8:36 PM as a reply to Arthur S.
OK, problem solved.

1) NO refresher-1.0.0.jar in libraries
2) NO refresher-1.0.0.jar checked in Properties -> Java EE Module Dependences
3) NO <inherits name="org.vaadin.henrik.refresher.RefresherApplicationWidgetset" /> in web.xml

4) YES <inherits name="org.vaadin.henrik.refresher.RefresherApplicationWidgetset" /> in *Widgets.gwt.xml
5) YES refresher-1.0.0.jar in WebContent/WEB-INF/lib/

If program is written in Scala then uncheck "java builder" in properties -> builders ('scala builder' is checked).

Thanksemoticon
Flag Flag
RE: Refresher
5/19/10 6:24 AM as a reply to Arthur S.
Arthur S:
OK, problem solved.


Sorry about being too lazy to update this thread about its current whereabouts. I guess I just assumed everyone had already found the Directory. Well, you know what they say about making assumptions...

Great that you got that fixed, and even more awesome that you're using Scala with this!
Flag Flag
RE: Refresher
5/19/10 12:00 PM as a reply to Henrik Paul.
Yes, I love Scala, I am using it for 2.5 year and it is future for many java developers.

I choosed to take a look at Vaadin because of possibility to use Scala - I don't want to go back to Java.

I hope Vaadin team also should consider to start using Scala, many things will be much easier emoticon.

Arthur.
Flag Flag
RE: Refresher
6/22/10 5:10 PM as a reply to Arthur S.
I'm trying to deploy the sample application (RefresherApplication) to Liferay as portlet 2.0, but I keep getting the following error:
Widgetset does not contain implementation for org.vaadin.henrik.refresher.Refresher. Check its @ClientWidget mapping, widgetsets GWT module descrioption file and re-compile your widgetset. Unrendered UIDL:

org.vaadin.henrik.refresher.Refresher(NO CLIENT IMPLEMENTATION FOUND) id=PID3 pollinginterval=1000


I'm using the Vaadin plug-in for Eclipse 3.5 as outline in the Plug-in different sections, re-gwt-compiling does not work either.

I added the refresher-1.0.0.jar into the WebContent/WEB-INF/lib folder

My *Widgetset.gwt.xml looks like:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 1.7.0//EN" "http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd">
<module>
<inherits name="com.vaadin.terminal.gwt.DefaultWidgetSet" />

<!--
Uncomment the following to compile the widgetset for one browser only.
This can reduce the GWT compilation time significantly when debugging.
The line should be commented out before deployment to production
environments.

Multiple browsers can be specified for GWT 1.7 as a comma separated
list. The supported user agents at the moment of writing were:
ie6,ie8,gecko,gecko1_8,safari,opera

The value gecko is used for Firefox 3 and later, gecko1_8 is for
Firefox 2 and safari is used for webkit based browsers including
Google Chrome.
-->
<!-- <set-property name="user.agent" value="gecko"/> -->


<inherits name="org.vaadin.henrik.refresher.RefresherApplicationWidgetset" />
</module>


Any suggestions?

Thanks,
Julio V.
Flag Flag
RE: Refresher
6/23/10 6:16 AM as a reply to Julio C Vergara.
Sorry, I can't find any problems with the info you posted - afaik, it should work as long as you compile the project's widgetset (which, apparently, you already has done).

I've never tried using the Refresher in a portlet (someone with portlet experience could chime in...), so you never know whether there's something interfering there. You could try Artur's ICEPush, if you have better luck with that.

Hope you get your app working.
Flag Flag
RE: Refresher
6/23/10 6:10 AM as a reply to Julio C Vergara.
Hi Julio,

make sure you have done the following two things.

1) In a portal environment you must copy the compiled widgetset into the /html/VAADIN/widgetsets/ directory under the Liferay installation. See also this section of the Book of Vaadin about installing Vaadin to Liferay.

2) Make sure you have defined the widgetset to be used by your portlet application in the portlet.xml file or in the portal-ext.properties file.
Flag Flag
RE: Refresher
6/24/10 12:06 PM as a reply to Teemu Pöntelin.
Teemu,

The instructions were right on target.
Thanks a lot.
Julio V.
Flag Flag
RE: Refresher
6/24/10 1:26 PM as a reply to Julio C Vergara.
Is there a Maven repository where I can fetch the plug-in from ? Or do I have to upload the plug-in by hand in my own maven repository?

Thanks,
Julio V.
Flag Flag
RE: Refresher
6/28/10 5:39 AM as a reply to Julio C Vergara.
Julio C Vergara:
Is there a Maven repository where I can fetch the plug-in from?


Sorry, no Maven repo for Refresher (afaik). I've put it only in the Directory.
Flag Flag
RE: Refresher
google gae deployment refresher suggestion
7/15/10 6:04 AM as a reply to Henrik Paul.
Refresher works fine on Tomcat server. But, it seems not working on Google App Engine.


web.xml (Tomcat server configuration)
...
<servlet-class>com.vaadin.terminal.gwt.server.ApplicationServlet</servlet-class>
...


web.xml (Google App Engine (GAE) configuration)
...
<servlet-class>com.vaadin.terminal.gwt.server.GAEApplicationServlet</servlet-class>
...


Any idea or suggestion would be appreciated!.
Flag Flag
RE: Refresher
7/26/10 5:34 AM as a reply to J Loke.
Unfortunately, I don't use GAE, so I can't support it either :/
Flag Flag
RE: Refresher
7/28/10 1:11 PM as a reply to J Loke.
I've used Refresher without problems in a GAE project. I didn't do anything special, just add it like any other addon, compile the widgetset, and use it.

Does it work for you in the Jetty based GAE dev server?
Flag Flag
RE: Refresher
8/5/10 9:51 AM as a reply to Teemu Pöntelin.
hi

thanks for the liferay pointers.. Had tried both these options with liferay 6.0.2 version

1. Have copied to ROOT/html/VAADIN/widgetset from the eclipse project after compiling.

2. my portlet.xml looks like follows
<portlet>
<portlet-name>Testingpush Application portlet</portlet-name>
<display-name>TestingPush</display-name>

<portlet-class>com.vaadin.terminal.gwt.server.ApplicationPortlet2</portlet-class>
<init-param>
<name>application</name>
<value>com.example.testingpush.TestingpushApplication</value>
</init-param>
<init-param>

<name>widgetset</name>
<value>com.vaadin.incubator.refresher.RefresherApplicationWidgetset</value>
</init-param>


After adding the #2, portlet is not displaying any UI components like labels. and no error message even with ?debug option

if i remove above bold section, it is display correctly ..but refresher not working.

Any clue to proceed on this? Any way to debug this

Appreciate your help

thanks
Joseph
Flag Flag
RE: Refresher
icepush deployment support support portal
8/5/10 9:57 AM as a reply to Henrik Paul.
Hi Henrik,

thanks for the link with icepush.. Tried with Liferay 6.0.2

ICE push has Only servlet deployment support..

// Push changes
ApplicationContext context = app.getContext();
if (context instanceof WebApplicationContext) {
PushContext pushContext = PushContext
.getInstance(((WebApplicationContext) context)
.getHttpSession().getServletContext());
pushContext.push(ICEPush.PUSH_GROUP);
} else {
throw new RuntimeException("Only servlet deployment is supported");
}

Recently, Seen that they have added support portal support too
http://jira.icefaces.org/browse/PUSH-65?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

Any idea how this can be intergrated with Vaadin addon

Appreciate all your advice

thanks
Joseph
Flag Flag
RE: Refresher
8/5/10 10:27 AM as a reply to Joseph george.
Joseph george:
thanks for the liferay pointers.. Had tried both these options with liferay 6.0.2 version

1. Have copied to ROOT/html/VAADIN/widgetset from the eclipse project after compiling.

2. my portlet.xml looks like follows
<portlet>
<portlet-name>Testingpush Application portlet</portlet-name>
<display-name>TestingPush</display-name>

<portlet-class>com.vaadin.terminal.gwt.server.ApplicationPortlet2</portlet-class>
<init-param>
<name>application</name>
<value>com.example.testingpush.TestingpushApplication</value>
</init-param>
<init-param>

<name>widgetset</name>
<value>com.vaadin.incubator.refresher.RefresherApplicationWidgetset</value>
</init-param>


After adding the #2, portlet is not displaying any UI components like labels. and no error message even with ?debug option

if i remove above bold section, it is display correctly ..but refresher not working.


You might want to use your own widgetset, which lets you add also other widgets to it when you need them.

I assume that the widgetset you use does inherit the default widgetset and the refresher widgetset, and the compilation went without errors, but do check that both the standard components and the refresher were included in the widgetset (select verbose widgetset compilation in Project properties -> Vaadin and recompile the widgetset).

Is your Liferay deployment using the same version of Vaadin with which you compiled the widgetset?

If the widgetset compilation succeeded, the most likely cause is a version mismatch between the Vaadin JAR used and the widgetset - in that case, either downgrade the Vaadin version you are using to that included in your Liferay installation, or upgrade the Liferay installation Vaadin JAR, themes and widgetsets.

As for the other question (about ICEPush use in portlets), Artur can probably answer it in the other thread where you asked it when he comes back from vacation.
Flag Flag
RE: Refresher
8/5/10 10:29 AM as a reply to Joseph george.
Joseph george:

<init-param>
<name>widgetset</name>
<value>com.vaadin.incubator.refresher.RefresherApplicationWidgetset</value>
</init-param>


That looks wrong. You should have a custom compiled widgetset for your application, and not use Refresher's widgetset. If you're using Eclipse, and your project is a Vaadin project, you should be able to compile your widgetset with the blue vaadin-icon in the toolbar. Otherwise, I don't know how a widgetset should be compiled for Liferay.

(...yeah, what Henri said)
Flag Flag