Home > JavaEE > ‘Learning Vaadin’ contest winners

‘Learning Vaadin’ contest winners

November 28th, 2011 Leave a comment Go to comments

Dear readers,

Thanks for your participation in the ‘Learning Vaadin’ contest. It’s my pleasure to announce the winners:

  • Adolfo Benedetti who commented on the integration side of ‘Learning Vaadin’
  • Sebastian who also commented about integration
  • A. Jansenn who noted the Vaadin team is very positive about ‘Learning Vaadin’ and that it’s a good complement to the available documentation

The winners will be contacted by a Packt representative about the details.

The choice was hard and I know there will be some deception for not having won a copy. Nevertheless, you can always purchase the book at Packt or Amazon.

email
Categories: JavaEE Tags:
  1. Armand Janssen
    December 1st, 2011 at 16:03 | #1
    Reply | Quote

    Thanks guys!

    I really appreciate it!
    I have already read bits and bytes in the book and it is looking very good!!!

    Keep up the good work!

  2. Sebastian
    December 13th, 2011 at 15:21 | #2
    Reply | Quote

    Thank you very much. I already had a quick look in some chapters I’m really curious about and so far it looked really good.

  3. Nicolas Frankel
    December 13th, 2011 at 17:34 | #3
    Reply | Quote

    Thanks guys! If you feel like it, please fill out a comment at Amazon (or rate it): http://www.amazon.com/Learning-Vaadin-Nicolas-Frankel/dp/1849515220

  4. cseg
    February 14th, 2012 at 20:26 | #4
    Reply | Quote

    So, I’ve just started reading Learning Vaadin. I got through the eclipse example (using the Vaadin plugin) and thought I’d try to do the same thing with SpringSource Tool Suite (STS). Well, it’s not working so easily.

    I’m on Windows 7. I had to install with the zip file because when I installed with the windows installer, the tc Server instance is in the distribution tree which is read only.

    Even after unzipping the zip file (with Cygwin unzip) I had to make all the *.exe, *.ddl and *.bat files executable.

    Now I can run “STS.exe”. It already has a “tc” server configured, but I follow your instructions to install the Vaadin plugin and create my first vaadin project (well, except I call the context root app).

    Well, before I even try to run the app, I see four errors like this one:

    Classpath entry VAADIN_DOWNLOAD/gwt-dev/2.3.0/gwt-dev.jar will not be exported or published. Runtime ClassNotFoundExceptions may result.

    Hmm, I see that there is a Quick Fix for them, so I apply it to all four and they go away.

    (There is also an error about a serializable class without a versionid, which I supppress.)

    Now there are no errors, so I should be able to run the app in the tc Server. I select the pre-existing server, it asks me if I want to install Insight, and I say yes.

    If I make the changes to web.xml that you suggest (mappings for /app/* and /VAADIN/*), I get a 404: The requested resource (/app/) is not available.

    However, if I revert to /* (and leave /VAADIN/* in place), then it works at http://localhost:8080/app/. That doesn’t make any sense. But it works.

    I also see this line in the console, which I thought was causing my problem at first:

    INFO: validateJarFile(…\springsource\vfabric-tc-server-developer-2.6.1.RELEASE\spring-insight-instance\wtpwebapps\MyFirstVaadinProject\WEB-INF\lib\gwt-dev.jar) – jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class

    There is a similar error for gwt-user.jar. I guess they have the javax.servlet classes in them. But the app still works if you use /*.

    Maybe I should have said No for installing insight. Or maybe the tc Server is more different than Tomcat than one would think.

    Anyway, great book so far. Now I’m going to try Netbeans (I’m an IntelliJ guy, but it’s a good time to check out these other IDEs.)

  5. Nicolas Frankel
    February 15th, 2012 at 11:31 | #5
    Reply | Quote

    Hello,

    Well, before I even try to run the app, I see four errors like this one:

    Classpath entry VAADIN_DOWNLOAD/gwt-dev/2.3.0/gwt-dev.jar will not be exported or published. Runtime ClassNotFoundExceptions may result.

    These are warnings, not errors. Eclipse mistakes those as runtime dependencies whereas they are compile-time GWT dependencies. You can safely ignore them.

    Now there are no errors, so I should be able to run the app in the tc Server. I select the pre-existing server, it asks me if I want to install Insight, and I say yes.

    The book shows example with Tomcat: tc Server is a boosted Tomcat, with no advantages whatsoever in the light of learning Vaadin.

    If I make the changes to web.xml that you suggest (mappings for /app/* and /VAADIN/*), I get a 404: The requested resource (/app/) is not available.

    However, if I revert to /* (and leave /VAADIN/* in place), then it works at http://localhost:8080/app/. That doesn’t make any sense. But it works.

    There’s a confusion between the context root and the servlet mapping: in STS, right-click on the Vaadin project and check the Web Settings menu. This should be the context root. What I write about is the servlet mapping. Morevoer, each time you update the web.xml, you have to explicitly publish the updated configuration and restart the server. Please keep the /app/* and /VAADIN/* mappings and this should work after having published and restarted.

    If you want to follow the examples, I suggest you stick to Tomcat and not use tc Server (which I admit I have no experience of).

  1. No trackbacks yet.