Why doesn't Java have instant turnaround ? | Why Java EE applications take from 15s up to 10 minutes to build & redeploy ??

[postlink] https://j2ee-tutorials-videos.blogspot.com/2012/08/why-doesnt-java-have-instant-turnaround.html [/postlink] http://www.youtube.com/watch?v=Dl3dxiq5GoAendofvid [starttext]In the dynamic languages it's a given. In .NET the problem is much smaller.

But Java EE applications take from 15s up to 10 minutes to build & redeploy, after every change, no matter how small. IDE automate the process, but still require the wait. Why is that and how can it be solved?

In the recent years JRebel rose to prominence as the answer to this issue. Challengers like Oracle FastSwap are also on the market. And instant turnaround is one of the core attractions of the Play! framework, Grails and Tapestry 5. In this talk we will review the technical and conceptual challenges involved in solving this issue and the options available today, including the tools mentioned. [endtext]

Why doesn't Java have instant turnaround ? | Why Java EE applications take from 15s up to 10 minutes to build & redeploy ??

Development of JSF 2.0 applications using JRebel in which changes are made and seen without a single redeployment

[postlink] https://j2ee-tutorials-videos.blogspot.com/2011/12/development-of-jsf-20-applications.html [/postlink] endofvid [starttext]The first 10 minutes of this video has a conversation with "JSF Ninja" Kito Mann. Then the rest of the presentation shows development of JSF 2.0 applications using JRebel in which changes are made and seen without a single redeployment

[endtext]

Development of JSF 2.0 applications using JRebel in which changes are made and seen without a single redeployment