“Unlike most Java frameworks, you can change a single code file and reload the page in your browser, the framework will automatically compile the code. It takes a few seconds but it’s still quick enough to enjoy this feature. I feel that this could make things messy, but mostly enjoyed it because it makes learning so much easier”
Hum … isn’t this what JSPs have been doing since the time of the dinosaurs? You “touch” the file and it recompiles it the next time somebody loads it …
Correct me if I’m wrong, but from what I have in mind, my experience with JSP is hiding in the past, this only applies to the view itself. What if you change a helper class to send an email? Does JSP reload that too?
I haven’t investigated this, but I haven’t seen a lot of JSP projects lately. That’s why I wrote “most frameworks..”. But please let me know if you have made different experiences!
Remo is right, You can get the latest work on page refresh (without compiling) if you change the JSP’s ONLY, and not with the Java classes. Here with Play… if you change a SYSOUT (for say) you don’t have to compile the class… just do the page refresh and it will show you the latest SYSOUT. I must say its an extremely rapid application development framework.
jrebel has been out for ages, so the recompilation shouldn’t be an issue for those who opt to work with that. having said that it’s good that it’s supported out-of-the-box and not with the help of a 3rd party tool.
Thanks, will try to have a look at JRebel, never worked with it before!
It’s not just compilation of classes, which jrebel does nicely (little bit pricey for my taste). JVM also “supports” this if you are lucky to get it work. Or you switch to NetBeans which kinda does it on some stacks.
It’s configuration and properties files, persistence and application wide settings and other low level things Play! also reloads on the fly.
Also for everybody working EE stuff, startup time of Play! stack is so much faster than Glasfish, JBoss and Tomcat.
So no more depoy or hotdeploy, no more waiting for container to start up, no more looking at stacktraces.
7 Comments
“Unlike most Java frameworks, you can change a single code file and reload the page in your browser, the framework will automatically compile the code. It takes a few seconds but it’s still quick enough to enjoy this feature. I feel that this could make things messy, but mostly enjoyed it because it makes learning so much easier”
Hum … isn’t this what JSPs have been doing since the time of the dinosaurs? You “touch” the file and it recompiles it the next time somebody loads it …
Correct me if I’m wrong, but from what I have in mind, my experience with JSP is hiding in the past, this only applies to the view itself. What if you change a helper class to send an email? Does JSP reload that too?
I haven’t investigated this, but I haven’t seen a lot of JSP projects lately. That’s why I wrote “most frameworks..”. But please let me know if you have made different experiences!
Remo is right, You can get the latest work on page refresh (without compiling) if you change the JSP’s ONLY, and not with the Java classes. Here with Play… if you change a SYSOUT (for say) you don’t have to compile the class… just do the page refresh and it will show you the latest SYSOUT. I must say its an extremely rapid application development framework.
jrebel has been out for ages, so the recompilation shouldn’t be an issue for those who opt to work with that. having said that it’s good that it’s supported out-of-the-box and not with the help of a 3rd party tool.
Thanks, will try to have a look at JRebel, never worked with it before!
Today we published a Play 2 web application deployment tutorial that may be useful – http://blog.jelastic.com/2013/07/02/play-2-web-application-deployment-tutorial/
It’s not just compilation of classes, which jrebel does nicely (little bit pricey for my taste). JVM also “supports” this if you are lucky to get it work. Or you switch to NetBeans which kinda does it on some stacks.
It’s configuration and properties files, persistence and application wide settings and other low level things Play! also reloads on the fly.
Also for everybody working EE stuff, startup time of Play! stack is so much faster than Glasfish, JBoss and Tomcat.
So no more depoy or hotdeploy, no more waiting for container to start up, no more looking at stacktraces.