JRebel Agent log contains runtime information about JRebel Agent loading and instrumenting your classes (e.g. The two files commonly asked by support (and automatically sent if you use the IDE built-in support dialog) are the JRebel Agent log ( jrebel.log) and the JRebel IDE plugin log (e.g. No, files asked by support do not contain your source code, although might contain some class info (specified below). JRebel agent does use it to instrument the application server class loaders and other basic classes, but the API does not play part in the actual reloading process. Unfortunately it is limited to only changing method bodies (as is HotSwap) and also suffers from several additional quirks, which makes it not too useful in a real environment. The Instrumentation API was introduced in Java 5 and included a limited ability to redefine Java classes on-the-fly. However throwing away those instances is only possible if they are somehow managed by the framework, e.g. The problem is that unless you also throw away all of the instances of the classes loaded by said class loaders, the code will not reload. The solution of reloading Java classes by wrapping them in throwaway classloaders is a well-known one, but unfortunately also very limited. In fact JRebel does not add a single new class loader to your application.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |