![]() ![]() That, in turn, makes it unnecessary to restart a running application during development, an often time-consuming and frustrating task. After making modifications to a Java class definition, JRebel notices such changes and reloads the modified class inside a running JVM. Then if you launch the server in JRebel Debug (icon looks like a bug with a little JR in the corner) changes to static assets are picked up as you make them and changes to classes are picked up as you compile them (shift-command-f9 for an incremental compile of the selected tab).JRebel (formerly known as JavaRebel) has been an increasingly popular item in the Java-and other JVM language-developer's tool chest. If you use JRebel, you can add a rebel.xml to src/main/resources that looks similar to: Do a single SBT package and then launch the server in debug mode within Intellij and your breakpoints should work. In the deployment tab make sure that it references /path_to_your_project/webapp. Instead of setting it up for remote debugging and connecting to SBT, set it up as a local Jetty server. ![]() I use a different method when debugging with Intellij that works well for me. Would posting complete source code help solving the problem? Could that be the source of problems?Īnother thing to mention, I downloaded sample Lift projects from the official site, and there debugging works! It seems that something is totally broken in my own project. I'm not sure if the warning about "NO JSP Support for /" is important. Started Total time: 7 s, completed 19:57:12 NO JSP Support for /, did not find .JspServlet C:\Users\Roman\Downloads\LiftHelloWorld\src\main\scala\Chat.scala:26: non-variable type argument String in type pattern Vector is unchecked since it is eliminated by erasure Compiling 4 Scala sources to C:\Users\Roman\Downloads\LiftHelloWorld\target\scala-2.10\classes. This is the output of sbt console when I do container:start: No breakpoints are hit, even though I attach my remote debugging session before calling container:start. I'm on Windows 8.1, and here's code for my sbt.bat: I create default "remote" configuration for debugging in IDEA. Maybe I'm debugging just the SBT session? What could that mean? Another interesting symptom is that I can already successfully start remote debugging when I launch just SBT, but don't call the "container:start" command there. I put breakpoints to every method in the Chat.scala, ChatIn.scala and ChatServer.scala, but none of them appears as active (there's no check-mark inside the red circle). The problem is, my breakpoints are not hit. I can run the Jetty container from SBT, and I even can connect my remote debug configuration to the SBT session, because I see Connected to the target VM, address: 'localhost:5005', transport: 'socket' message in the IDEA's debugging output. What I've achieved so far: I have my Lift app running in the browser, and following instructions from !topic/liftweb/ixWOc9H9aJ0 I created a "remote" debugging configuration in IDEA. I encounter one issue which I can't resolve myself, could you kindly guide me in the right direction? I thought debugging it would help me find the problem quickly, however setting the debugging up itself is quite time-consuming, and I'm not there yet. Somewhere, that's why it doesn't work as expected (chat message doesn'tĪppear in the list on submit, but text disappear from the text box). I typed it by hand, so I've probably made a mistake The code of the app is taken from "Simply Lift" book's first chapter, I'm just staring with Lift, and trying to debug a very simple application, which doesn't work for some unknown reason. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |