Problems with vaadin/spring/maven2



I’m developing my first ui with Vaadin and haven been struggling with couple of problems for quite a while. I hope someone could help me here.

  1. I use tomcat to run my application and maven to handle dependencies. I’ve added tomcat-maven plugin to my project and it seems to work fine. I can do mvn tomcat:run and it works but the problem is that if I change something in code and just restart the application by adding ?debug to URL and pressing restart those changes won’t take effect. Am I (again) missing something?

  2. This might not have much to do with Vaadin but maybe somebody have had the same problem with Vaadin spring integration.

If I run my project on my development environment (tomcat 2.0.29), the application starts fine, but when I package it and deploy to my production environment (tomcat 2.0.24) I get this weird error where my serviceBean can not be created and the root cause is:

Caused by: java.lang.IncompatibleClassChangeError: Implementing class
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(
        at org.apache.catalina.loader.WebappClassLoader.findClassInternal(
        at org.apache.catalina.loader.WebappClassLoader.findClass(
        at org.apache.catalina.loader.WebappClassLoader.loadClass(
        at org.apache.catalina.loader.WebappClassLoader.loadClass(
        at java.lang.ClassLoader.loadClassInternal(
        at org.hibernate.ejb.Ejb3Configuration.<clinit>(
        at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(
        at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(
        at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(
        ... 77 more

Can it really just be that small difference of tomcat versions or is there something wrong with the configuration?

Thanks for any answers!!