dashorst / dashboard Goto Github PK

Currently the number of projects surpass the number of graphbars that fit on one line. Make this more flexible, or at least fix the overflow to the next line

For unit testing, get rid of the singletons, use DI?

These events and deadlines can be shown on the page with different colors for different types of events or for different projects.

Currently, all data is discarded when new data is fetched. This makes it impossible to draw graphs containing the history of datasources.

The readme file prescribes
~/.dashboard/nl.topicus.onderwijs.dashboard.modules.Settings.json
the webapp won't start however.
When moving the config file to
~/.dashboard/nl.topicus.onderwijs.dashboard.config.Settings.json
the application starts.

When one has not placed the configuration in the correct location the application prints the error using System.err.println() and calls System.exit(). The problem is then untraceable as the error is nowhere to be found (nor in the logs nor console).

The display of request time is missing the units-declaration. Please append the unit declaration (ms) after the request time (or - alternatively - add it to the title of the column).

A nice widget would be a table that shows current departure times and delays of the trains departing at Deventer Central station (or any other station).

Trying to run the Start or jetty:run gives me this:

java.lang.IllegalStateException: init parameter 'wicket.configuration' is not set yet. Any code in your Application object that uses the wicketServlet/Filter instance should be put in the init() method instead of your constructor

full trace:

[INFO] Starting jetty 6.1.25 ...
[2010-11-24 20:19:29,164] [INFO] [main] ContextLoader | Root WebApplicationContext: initialization started
[2010-11-24 20:19:29,251] [INFO] [main] AbstractApplicationContext | Refreshing Root WebApplicationContext: startup date [Wed Nov 24 20:19:29 CET 2010]; root of context hierarchy
[2010-11-24 20:19:29,289] [INFO] [main] XmlBeanDefinitionReader | Loading XML bean definitions from class path resource [nl/topicus/onderwijs/dashboard/spring.xml]
[2010-11-24 20:19:29,769] [INFO] [main] DefaultListableBeanFactory | Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@12b27c38: defining beans [NSService,wetterComService,googleEventService,vocusStatusRetriever,parnassysStatusRetriever,vocusOuderportaalRetriever,mantisService,twitterService,random,svnService,online,hudsonService,updater,org.springframework.context.annotation.internalConfigurationAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalRequiredAnnotationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,wicketApplication,settings]; root of factory hierarchy
[2010-11-24 20:19:30,307] [INFO] [main] DefaultSingletonBeanRegistry | Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@12b27c38: defining beans [NSService,wetterComService,googleEventService,vocusStatusRetriever,parnassysStatusRetriever,vocusOuderportaalRetriever,mantisService,twitterService,random,svnService,online,hudsonService,updater,org.springframework.context.annotation.internalConfigurationAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalRequiredAnnotationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,wicketApplication,settings]; root of factory hierarchy
[2010-11-24 20:19:30,312] [ERROR] [main] ContextLoader | Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'updater' defined in file [/home/francisdb/workspace/dashboard.dashorst/target/classes/nl/topicus/onderwijs/dashboard/timers/Updater.class]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: init parameter 'wicket.configuration' is not set yet. Any code in your Application object that uses the wicketServlet/Filter instance should be put in the init() method instead of your constructor
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1420)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1272)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:489)
at org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132)
at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:441)
at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:383)
at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:210)
at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.lang.IllegalStateException: init parameter 'wicket.configuration' is not set yet. Any code in your Application object that uses the wicketServlet/Filter instance should be put in the init() method instead of your constructor
at org.apache.wicket.protocol.http.WebApplication.getInitParameter(WebApplication.java:184)
at org.apache.wicket.protocol.http.WebApplication.getConfigurationType(WebApplication.java:597)
at nl.topicus.onderwijs.dashboard.web.WicketApplication.isDevelopment(WicketApplication.java:136)
at nl.topicus.onderwijs.dashboard.timers.Updater.afterPropertiesSet(Updater.java:45)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1417)
... 51 more

www.buienradar.nl uses a semitransparant png to display the rainfall in a certain area. This can be parsed and shown in a widget that shows expected rainfall for the next hour in a certain area.

We need to display a clock!

The number of unit tests metric fails sometimes–returning 0 instead of the last successful build number.

Support for at least Dutch would be nice.

How to configure twitter / weather?
Would be nice if a config file template could be generated from code or that at least an indication of the missing configuration (what sections) is mentioned in the logs

With each update of the data, the wicket session grows by a few kb. With over 1 request per second, this quickly causes the session size to grow to many mb. This problem can be reproduced by setting the javascript heartbeat clock to 100ms.

Store all dashboard configuration in a file, not in the java code. This will make the application more flexible and runnable in other contexts than topicus.