I haven’t had time yet to split the project into it’s own separate project. In the mean time, use the pom.xml I attached to a previous post (contains an old Vaadin version):
https://vaadin.com/forum/-/message_boards/view_message/2489264#_19_message_2615033
First
Let me say Vaadin is THE tool kit in town for rich web apps.
So Thank you guys.
And the code is very clean.
Here is my pom,
you will also need the run jetty run plugin for eclipse, it makes debugging within eclipse trivial.
after which i was able to run it from eclipse as “run jetty”
http://localhost:8080/quicktickets-dashboard
12838.xml (5.15 KB)
Hi Guys,
I can’t get rid of the problem with widgetset.
When I am deploying the application I am getting this information:
Of course in the end of deploying the server is started.
Next when I try to load the application, by putting: [quote]
http://localhost:8080/quicktickets-dashboard
[/quote] in the browser, after a while I get this error:
I searched the web and nothing, which I have found, worked. Do you have any idea ?
Hi Gents,
I have the same issue, please advise.
Thanks.
hi
@Michal Rogulski
@Sergey Lesun
assumed that you use eclipse and the vaadin plugin is installed, navigate to this file
dashboard-demo-master\src\main\resources\com\vaadin\demo\dashboard\DashboardWidgetSet.gwt.xml
and compile the widgetset, after compilation is finished re-run your server, or package your war and deploy
it to your server.
it should run
greets
Hi,
yep you’re right I am using Eclipse with the Vaadin plugin. Unfortunately I’ve made everything you said, and nothing worked. Still I have the same problem. Or maybe I have done something wrong. What do you mean, by saying: [quote]
and compile the widgetset
[/quote]. How should I do this ?
Thanks in advice
Edited 06.03.2013
Hi, I’ve been searching the web for “widgetset compilation” informations, and I found, that to “compile the widgetset” we need to click correct button in eclipse toolbar. I’ve done it, and after the :widgetset compilation", everything works fine. Thank you guys for help.
Hi Michal.
i think that Ercan mentioned that:
point 16.2.2 compile the widget set
You can do it in Eclipse if you have installed the Eclipse Vaadin plugin. If you’re using Maven to build the project, just do “mvn install” and it should compile the widgetset too. If it doesn’t work, try to invoke “mvn clean” first.
My god. You have made a completely new CSS Theme for the Dashboard! Its a nice theme, will be great if it becomes part of Vaadin.
I’ve got the same problem as “doublem dbm” where Marven reports of missing modules. Could someone please post a walkthrough of how to apply this theme? It is kind of hard for a first time user of Vaadin 
Thanks
Hi, Jouni,
Great demo!
And I have found a litter issue and fixed it, pl. seeing the following:
My env is Windows XP JP(Japanese), so, while building the source, building will failed caused by encoding related issues.
So, after I added the following into pom.xml’s properties setting, the building is OK.
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
BTW:
Currently, vaadin-charts-1.0.0,jar can be only downloaded from https://vaadin.com/directory, and I suggest that we should put or update maven repo to add the these jars.
Otherwise, maybe users will download these jars and install into local maven repo manually.
Thanks
–Tang Yong(http://osgizone.typepad.com/tangyong/)
Hi!
The pom.xml should be fixed now in the GitHub repo, so it should compile out-of-the-box.
Hi, Jouni,
After I deployed the demo into Glassfish 3.1.2.2 and my env was behind a proxy server, once I access “http://localhost:8080/quicktickets-dashboard-1.0.0/”,
The following exception happened in my browser,
type Exception report
message
descriptionThe server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -2
root cause
java.lang.ArrayIndexOutOfBoundsException: -2
note The full stack traces of the exception and its root causes are available in the GlassFish Server Open Source Edition 3.1.2.2 logs.
Then, I found the following in glassfish server.log,
=================================================================
Vaadin is running in DEBUG MODE.
Add productionMode=true to web.xml to disable debug features.
To show debug window, add ?debug to your application URL.
=================================================================|#]
[#|2013-03-20T23:29:46.562+0900|SEVERE|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=106;_ThreadName=Thread-2;|java.net.UnknownHostException: api.rottentomatoes.com
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
at java.net.Socket.connect(Socket.java:579)
at java.net.Socket.connect(Socket.java:528)
at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:378)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:473)
at sun.net.www.http.HttpClient.(HttpClient.java:203)
at sun.net.www.http.HttpClient.New(HttpClient.java:290)
at sun.net.www.http.HttpClient.New(HttpClient.java:306)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:995)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:931)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:849)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1299)
at java.net.URL.openStream(URL.java:1037)
at com.vaadin.demo.dashboard.data.DataProvider.readJsonFromUrl(DataProvider.java:200)
at com.vaadin.demo.dashboard.data.DataProvider.loadMoviesData(DataProvider.java:155)
at com.vaadin.demo.dashboard.data.DataProvider.(DataProvider.java:51)
at com.vaadin.demo.dashboard.DashboardUI.(DashboardUI.java:62)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at java.lang.Class.newInstance0(Class.java:372)
at java.lang.Class.newInstance(Class.java:325)
at com.vaadin.server.UIProvider.createInstance(UIProvider.java:33)
at com.vaadin.server.AbstractCommunicationManager.getBrowserDetailsUI(AbstractCommunicationManager.java:2457)
at com.vaadin.server.AbstractCommunicationManager.handleBrowserDetailsRequest(AbstractCommunicationManager.java:2362)
at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:325)
at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:201)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:722)
|#]
…
[#|2013-03-20T23:29:46.937+0900|WARNING|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=106;_ThreadName=Thread-2;|StandardWrapperValve[QuickTicketsDashboard]
: PWC1406: Servlet.service() for servlet QuickTicketsDashboard threw exception
java.lang.ArrayIndexOutOfBoundsException: -2
at java.util.ArrayList.elementData(ArrayList.java:371)
at java.util.ArrayList.get(ArrayList.java:384)
at com.vaadin.demo.dashboard.data.DataProvider.createTransaction(DataProvider.java:404)
at com.vaadin.demo.dashboard.data.DataProvider.generateTransactionsData(DataProvider.java:343)
at com.vaadin.demo.dashboard.data.DataProvider.(DataProvider.java:53)
at com.vaadin.demo.dashboard.DashboardUI.(DashboardUI.java:62)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at java.lang.Class.newInstance0(Class.java:372)
at java.lang.Class.newInstance(Class.java:325)
at com.vaadin.server.UIProvider.createInstance(UIProvider.java:33)
at com.vaadin.server.AbstractCommunicationManager.getBrowserDetailsUI(AbstractCommunicationManager.java:2457)
at com.vaadin.server.AbstractCommunicationManager.handleBrowserDetailsRequest(AbstractCommunicationManager.java:2362)
at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:325)
at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:201)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:722)
|#]
So, whether demo should consider the case (connecting internet by a proxy server)?
Thanks
–Tang Yong
I am sorry t, please ignore the above exception and It’s my env’s problem.
Now, I have accessed the built demo successfully.
Thanks
–Tang
Hi.
I checkout the dashboard from github, using maven SCM…
The project isn’t compiling. I’m getting this errors:
Plugin execution not covered by lifecycle configuration: com.vaadin:vaadin-maven-plugin:7.0.2:resources (execution: default, phase: process-resources)
Plugin execution not covered by lifecycle configuration: com.vaadin:vaadin-maven-plugin:7.0.2:update-widgetset (execution: default, phase: process-classes)
What I’m need to do to solve they?
Hi Roberto
These errors are IDE-related. The IDE/Maven plugin you’re using (I’m guessing Eclipse/m2e) doesn’t understand the execution phases defined in the plugin configuration.
The current dashboard pom.xml isn’t bloated with any IDE-specific configuration but you can add it yourself by quick-fixing the errors with “Permanently mark goal resources in pom.xml as ignored in Eclipse build”.
The pom configuration is intact as such and the project compiles nicely from the command line for example (mvn install).
Solved!
I just add tag between the and tags, as described at this link
How to solve “Plugin execution not covered by lifecycle configuration” for Spring Data Maven Builds
, and everything comes to be fine again!
I am having the same issue. Where can I find these packages?
Thank you
Hi!
I think those dependencies should be handled by Maven, you shouldn’t need to add anything extra to the project you get from GitHub.
Hi Guys, I wonder if anybody could help me. I compiled and deployed the QuickTickets code from incubator trunk. Deployed it onto Tomcat as ROOT. I saw in the tomcat manager that it was started. But when I visit it through brouwser it gives 404 error. Could you please tell me what could be wrong?