Comments on: Eleven reasons to use the Play! Framework for Java Web Development http://www.rojotek.com/blog/2010/04/10/eleven-reasons-to-use-the-play-framework-for-java-web-development/ Software Development in Brisbane Fri, 03 Feb 2012 20:00:10 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: Atlanta Web Development http://www.rojotek.com/blog/2010/04/10/eleven-reasons-to-use-the-play-framework-for-java-web-development/comment-page-1/#comment-29994 Atlanta Web Development Thu, 29 Apr 2010 08:14:09 +0000 http://www.rojotek.com/blog/?p=929#comment-29994 good work done keep it up. good work done keep it up.

]]> By: Executing Play! from outside of Play! code - Rob@Rojotek http://www.rojotek.com/blog/2010/04/10/eleven-reasons-to-use-the-play-framework-for-java-web-development/comment-page-1/#comment-29895 Executing Play! from outside of Play! code - Rob@Rojotek Mon, 26 Apr 2010 09:30:29 +0000 http://www.rojotek.com/blog/?p=929#comment-29895 [...] Rob@Rojotek Software Development in Brisbane « Eleven reasons to use the Play! Framework for Java Web Development [...] [...] Rob@Rojotek Software Development in Brisbane « Eleven reasons to use the Play! Framework for Java Web Development [...]

]]> By: Nick http://www.rojotek.com/blog/2010/04/10/eleven-reasons-to-use-the-play-framework-for-java-web-development/comment-page-1/#comment-29732 Nick Sun, 18 Apr 2010 22:31:30 +0000 http://www.rojotek.com/blog/?p=929#comment-29732 Im saying its .... unorthadox. :) statics galore. exceptions to return data. Im saying its …. unorthadox. :)

statics galore.
exceptions to return data.

]]> By: Mario http://www.rojotek.com/blog/2010/04/10/eleven-reasons-to-use-the-play-framework-for-java-web-development/comment-page-1/#comment-29598 Mario Mon, 12 Apr 2010 12:09:25 +0000 http://www.rojotek.com/blog/?p=929#comment-29598 I think things like this are simply entertaining: // Really I don't like this stuff if(request.path.equals("/favicon.ico")) { response.status = 404; return true; } (from CorePlugin-1.0.2 line 45-49: http://bazaar.launchpad.net/~play-developers/play/1.0/annotate/head:/framework/src/play/CorePlugin.java#L45) and to make sure /favicon.ico is dead: // Patch favicon.ico if (!request.path.equals("/favicon.ico")) { super.init(); } (from server.HttpHandler-1.0.2 line 455-458: http://bazaar.launchpad.net/~play-developers/play/1.0/annotate/head:/framework/src/play/server/HttpHandler.java#L455) Is it implemented good or bad? Try to change/extend it! I think it is mostly ok for its age. Have fun! I think things like this are simply entertaining:

// Really I don’t like this stuff
if(request.path.equals(“/favicon.ico”)) {
response.status = 404;
return true;
}
(from CorePlugin-1.0.2 line 45-49: http://bazaar.launchpad.net/~play-developers/play/1.0/annotate/head:/framework/src/play/CorePlugin.java#L45)

and to make sure /favicon.ico is dead:

// Patch favicon.ico
if (!request.path.equals(“/favicon.ico”)) {
super.init();
}
(from server.HttpHandler-1.0.2 line 455-458: http://bazaar.launchpad.net/~play-developers/play/1.0/annotate/head:/framework/src/play/server/HttpHandler.java#L455)

Is it implemented good or bad? Try to change/extend it! I think it is mostly ok for its age.

Have fun!

]]> By: Rob http://www.rojotek.com/blog/2010/04/10/eleven-reasons-to-use-the-play-framework-for-java-web-development/comment-page-1/#comment-29582 Rob Sun, 11 Apr 2010 21:54:28 +0000 http://www.rojotek.com/blog/?p=929#comment-29582 Methinks Nick is pointing out that it is entertaining :). The focus seems to be on making Play! clean to use, and using whatever heavy lifting is possible to get there. I would be grumpy if someone on my team wrote the code in Play!, but can live with it in the framework. Happily they are responsive to change, so if there is a bug it gets fixed. Methinks Nick is pointing out that it is entertaining :) . The focus seems to be on making Play! clean to use, and using whatever heavy lifting is possible to get there. I would be grumpy if someone on my team wrote the code in Play!, but can live with it in the framework. Happily they are responsive to change, so if there is a bug it gets fixed.

]]> By: Jack http://www.rojotek.com/blog/2010/04/10/eleven-reasons-to-use-the-play-framework-for-java-web-development/comment-page-1/#comment-29575 Jack Sun, 11 Apr 2010 17:42:11 +0000 http://www.rojotek.com/blog/?p=929#comment-29575 Nick, Are you saying that the way it is implemented is good or bad? Nick,

Are you saying that the way it is implemented is good or bad?

]]> By: Nick http://www.rojotek.com/blog/2010/04/10/eleven-reasons-to-use-the-play-framework-for-java-web-development/comment-page-1/#comment-29558 Nick Sat, 10 Apr 2010 21:15:57 +0000 http://www.rojotek.com/blog/?p=929#comment-29558 If you want some entertainment, have a closer look under the hood at how its implemented :) If you want some entertainment, have a closer look under the hood at how its implemented :)

]]> By: Tweets that mention Eleven reasons to use the Play! Framework for Java Web Development - Rob@Rojotek -- Topsy.com http://www.rojotek.com/blog/2010/04/10/eleven-reasons-to-use-the-play-framework-for-java-web-development/comment-page-1/#comment-29547 Tweets that mention Eleven reasons to use the Play! Framework for Java Web Development - Rob@Rojotek -- Topsy.com Sat, 10 Apr 2010 03:39:18 +0000 http://www.rojotek.com/blog/?p=929#comment-29547 [...] This post was mentioned on Twitter by rojotek, Atlanta Web Design. Atlanta Web Design said: Eleven reasons to use the Play! Framework for Java Web Development: ...the dynamic languages world (Rails and Djan... http://bit.ly/c0l9WN [...] [...] This post was mentioned on Twitter by rojotek, Atlanta Web Design. Atlanta Web Design said: Eleven reasons to use the Play! Framework for Java Web Development: …the dynamic languages world (Rails and Djan… http://bit.ly/c0l9WN [...]

]]>