This talk presents a number of conceptual and technical challenges that we discovered while building JRebel. At first, the JVM wasn't designed for live updates, so we will talk about the engine that mitigates the problem. Secondly, the diversity of Java ecosystem, created by the variety of application servers, the frameworks and tools, makes it challenging in creating a generic solution that would fit the majority of developers. We will see, how Java platform itself allows us to develop a solution by applying bytecode instrumentation mechanism.JRebel does live code reloading to ensure that the developer can keep instantly alternating between the developing environment and the web browser, to save wasted time and increase the productivity flow.
Author:
Simon Maple
Simon is a Developer Advocate at ZeroTurnaround and founder of the vJUG (virtualJUG), in addition to being an active member of the London Java Community (LJC) organising group and LJC JCP EC committee member. All of his community efforts culminated in him being awarded Java Champion status in 2014. Simon used to be a tester, developer and technical evangelist for IBM on the WebSphere Application Server for 12 years prior to joining ZeroTurnaround. He's married with a son and dog who he tries to spend as much quality time with as he can.
