bsblabs / embed-for-vaadin Goto Github PK

Add basic support for Vaadin 7

A maven archetype would ease a bit more the integration and be useful for demo/test purpose. This could become an easy way to report known issues.

the tomcat embed API for some reason does not manage the HTTP session properly. If one starts two vaadin applications they timeout each other.

To reproduce:

• Start embed for vaadin and invoke some action on the screen
• Start a second copy and invoke some action (the same or another one, it does not matter)
• Go back to the first vaadin application, invoke an action

Expected: it simply works
Actual: a "Session expired" message is displayed. When it gets resolved, switching back to the second application leads to a session expired as well

Tracing that, the HTTP session is null in AbstractApplicationServlet#getExistingApplication

It would be very handy to be able to specify parameters to the opened url. For example, adding a "#anchor" to the following url to open directly a specific section : http://localhost:2173/#anchor.

For example you could add a new property in the configuration file like "url_parameters" which is concatenated to the base url, and it should be possible to add it as a program argument also

The beta2 has some significant changes in the API compared to the alpha. The changes from Root to UI is the most visible one but they are others change on the way that will affect some of the features that embed for vaadin provides.

When the root context is read from a java.util.Properties it does not get cleaned (i.e. adding a forward slash if one is missing)

Right now, the development header for a component is mandatory unless one extend the API. It should be an option in the builder because it has some impact on the styling.

Embed for Vaadin hasn't moved for quite some time.

Checking it still works properly against the latest 7.x release is also required.

In beta2, we used to be able to override the VaadinServletService to provide the list of UIProviders to use. In the case of embedding a component that was already built, we just return a singleton list with our special ui provider that returns that very specific component.

This seems to have changed in beta3.

The doc and Javadoc states that the development header when embedding a component is optional while it is not.

Add the ability to change the production mode in case of apps being deployed on heroku or other systems.

Update to the latest Vaadin 7 release.

Just upgrade to the latest and greatest Tomcat release.

When specifying a port, first logs seems to point that the port is automatically generated when it is not and the specified port is used.

Starting the application like this :

EmbedVaadin.forApplication(MyApplication.class)
.withHttpPort(8080)
.start();

Logs show this :

23:12:58.254 [main] DEBUG c.b.c.vaadin.embed.EmbedVaadinConfig - Using EmbedVaadinConfig{port=0, context=, webapp dir=/var/folders/lx/4zbpjm8j5g78pm2s0qbs_xr00000gn/T/1334178778246-0}
23:12:58.474 [main] INFO c.b.c.v.e.AbstractEmbedVaadinTomcat - Deploying application to [http://localhost:[auto]/]
Apr 11, 2012 11:12:59 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Apr 11, 2012 11:12:59 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Tomcat
Apr 11, 2012 11:12:59 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.26
Apr 11, 2012 11:13:00 PM org.apache.catalina.util.SessionIdGenerator createSecureRandom
INFO: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [115] milliseconds.
Apr 11, 2012 11:13:00 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
23:13:00.322 [main] INFO c.b.c.v.e.AbstractEmbedVaadinTomcat - Application has been deployed to [http://localhost:8080/]

The first two lines shows that the port is 0 and then [auto].
The last log line shows the correct port and the application is started on the right port, it's just the logs that are confusing.

In Vaadin 6.8 setSplitPosition now takes a float instead of a int. This breaks the API and any existing embed for vaadin release will not work unless they get recompiled.

See http://dev.vaadin.com/ticket/9336

Need to find a way to support both cases, preferably.

The update to Vaadin 7 beta 2 (#11) led to a regression. Using the shutdown button of the development header still stops the server but does not close the browser tab anymore.

This leads to an exception after some time since Vaadin tries to contact the server for some reason.

Created #9805 in the Vaadin trac