We just upgraded from 6.8.2 to 6.8.3 and noticed that we’re also having trouble with our main login process which also goes to a URI fragment but it’s not firing.
On login under 6.8.3, I do end up with the URL in the browser showing as expected:
http://localhost/open-eSignFormsVaadin/vaadin/#WelcomeTipsView/Welcome
But that fragment is not fired and so no view is displayed. If I click on the view from our menu that is the default view, the same URL is shown, but the original welcome page is shown as expected. This is is because it then fires the fragment changed event.
When I roll back to 6.8.2, it works fine again, so this is definitely something introduced in 6.8.3.
When I look at my application logs, 6.8.2 shows these additional lines after login that are now missing in 6.8.3, which seems to be one extra request that does triggers my fragment code:
[font=Courier New]
2012-09-10 17:46:50,025 DEBUG (com.esignforms.open.vaadin.EsfVaadinApplication) onRequestStart() requestUrl: /open-eSignFormsVaadin/vaadin/UIDL?windowName=main; hostIp: 127.0.0.1; useragent: Mozilla/5.0 (Windows NT 6.1;
WOW64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1; loggedInUser: Support David support@david.com
2012-09-10 17:46:50,026 DEBUG (com.esignforms.open.vaadin.main.MainWindow) fragmentChanged() - fragment: WelcomeTipsView/Welcome; viewName: WelcomeTipsView; viewParam: Welcome
2012-09-10 17:46:50,026 DEBUG (com.esignforms.open.vaadin.main.MainWindow) showView() - viewName: WelcomeTipsView; viewParam: Welcome
2012-09-10 17:46:50,034 DEBUG (com.esignforms.open.vaadin.EsfVaadinApplication) onRequestEnd()
[/font]
When I review the closed items for 6.8.3 I don’t see anything that jumps out at me as what would cause this.
UPDATED TO NOTE TICKET 8916:
Perhaps it’s
http://dev.vaadin.com/ticket/8916
that has done this. Ticket 8916 isn’t shown in the
list of closed issues for the 6.8.3
, but I think it must be the reason since it talks about this feature directly.