SpringOne Platform 2016 Keynote - Spring Boot Weather Application Demo

Keynote recorded at SpringOne Platform 2016.
Stephane Nicoll and Josh Long tag team a live code, tour de force on Spring Boot 1.4, the weather, cyan cats, and everything.

[@YadabRajOjha]

Its great!, thank you Stephane Nicoll and Josh Long for wonderful presentation.

[@dmpg0231]

@8:28 Stephane introduce the 404.html under the error folder, and then the page is opened in the editor with a full content, so I thought that Spring Boot fulfill the error pages but not... Spring boot just create a blank 404.html page without any content inside. So I wondering how is that Sptephane get the 404.html page´s content after he created that file???? (I asked Spteph on Tweeter but he didn't get what I was actually asking about :0)

[@TheDekeyras]

They probably overwrote the default html template for the demo.

[@snicoll]

Sorry for the super late reply. I just used a trick from IntelliJ IDEA called file template. It has nothing to do with spring boot, really. Rather than me coding the HTML page in front of the audience, I had it prepared with a shortcut. So I basically created a new file from a template and use devtools to refresh the app and that's how the smiley showed up. You could try yourself by creating an empty page and just put some title or text and you'll see boot will use it automatically. Hope that helps.

[@vikashkaushik6205]

which tool you have mentioned for browser to pull new data from server?

[@snicoll]

I assume you're talking about LiveReload, check the free plugin for your browser here: livereload.com/extensions/

[@zakariaamine88]

any chance getting the code of the demo app?

[@snicoll]

Here you go: github.com/springoneplatform2016/weather-app

[@zakariaamine88]

Cool thanks

[@xenoterracide]

@AutoconfigureMvcMock (or whatever) is awesome, but I haven't found @WebMvcTest to be practically useful, I use too much Spring Data. Sadly because I'm not using JPA the only one of these I've found useful is the @JsonTest one, otherwise I end up using the full @SpringBootApplicationTest (or whatever my memory for these is useless without an IDE)

[@snicoll]

That must be `SpringBootTest`. If you have a repository layer you could mock it though.

[@xenoterracide]

Sure, and mock out every save method to add an id, and every find method to provide previously saved results, and ignore bugs created because you were messing with mocks instead of thinking about transactions. And what about Spring Security? A lot of our services rely heavily on it or transactions. Problem is that even the simplest app's I've built are more complex than this is helping with. Now that I'm migrating back to JPA the JpaTest might be useful.

[@scoff7032]

Nyan cat :D