Support Vaadin7 (beta3) about dellroad-stuff HOT 10 CLOSED

Thanks, started working on this.

Just as an update: Basic stuff on 
[https://github.com/aanno/dellroad-stuff-aanno] is now working, including 
@VaadinConfigurable. Biggest hurdles for general consumption are now (a) I'm 
extending VaadinServlet (and I think this is a very bad idea) and (b) I'm not 
fully understanding the new concepts (and lifecycles) of UI (and their ids), 
VaadinServiceSession, and VaadinServlet at present.

Well, I probably should mention that my changes are on the 'tp' branch while 
the 'master' branch just tracks the original upstream svn repository.

Thanks. I am trying to implement this (from scratch) using the approach 
suggested by the Vaadin folks. See http://dev.vaadin.com/ticket/9733 for a 
related discussion.

Once I get it committed (hopefully soon), I'd very much appreciate your review.

BTW, extending VaadinServlet is indeed required.

Just as an update: After reading your link, and reasoning on myself 
[https://vaadin.com/forum/-/message_boards/view_message/1875525], I've 
concluded that the 'normal' spring context scope for vaadin7 should be bound to 
VaadinServiceSession. That's what the code does now. I've also added a Spring 
UI-bound scope that can be used within (and outside!) this context. On top of 
that I'm experimenting with an UI-scoped EventBus (as a building block for some 
Spring-based MVP support inspired by 
[https://vaadin.com/directory#addon/mvp-lite]).

The is another (competing vaadin7 Spring integration) 
[https://vaadin.com/forum/-/message_boards/view_message/1811100]. I will have a 
look on this soon to decide if there are ideas there that are missing here.

However, I'm really not interested at forking your stuff. Best thing that could 
happen to my that your implementation is working again soon. And I would be 
glad if you incorporate the more useful ideas (well, not the hacked code, 
probably). 

I should have something ready to commit in the next day or two. You are correct 
that VaadinServiceSession is the new place to hang the "Vaadin application" and 
Spring context.

r528 seems to work more or less. The dellroad-stuff example on github (branch 
'vaadin7') has been updated to work with it.

Check it out and let me know what you think.

Dear Archie,

thank you for the regular updates to the vaadin 7 stuff. I basically use your 
code out-of-the-box. However there are some minor glitches (like the broken 
'mvn deploy' compatibility (especially then it comes to SNAPSHOTs), basic 
eclipse support, make AbstractUpdatingDataSource compatible with java7, ...) 
that makes me still 'rebase'ing my tp2 branch on top of your code.

There is only one issue that perhaps need more profound consideration: It's the 
scope of an vaadin application. You decided to bound the vaadin application 
lifecycle to the lifetime of the UI. This is a valid choice, as it makes 
possible to log-in to the same web application with *two* different users in 
two different tabs. As the UI is not shared, all works as expected.

However, this is not the only possible choice. If you want *one* web 
application that supports several browser native tabs, this is possible with 
vaadin as well - but will be difficult with your spring integration. In this 
case the lifecyle of the vaadin application should be bound to the HttpSession 
(as a new UI is just another tab in your browser).

The bad news is that I need the later. (I need to support mobile (phone+tablet) 
clients, and because of this I would favourite native browser tabs above the 
tab widget of vaadin.)

A possible solution to with is to bound the spring context to the HttpSession 
and in addition provide a Spring scope that is UI-bound. With way, both 
scenarios would be supported...

Not sure I understand the scope question. The latest vaadin7 package associates 
the Vaadin application context to the VaadinSession, not any particular UI 
instance. See the latest Javadoc API:

http://dellroad-stuff.googlecode.com/svn/trunk/publish/reports/javadoc/org/dellr
oad/stuff/vaadin7/SpringVaadinServlet.html

Or am I misunderstanding something?

I've folded in some of your changes into SVN. Thanks!