Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a webapp that uses some adobe blazeds jars ie. flex-messaging-core.jar. I would like to step-in to methods contained within this jar (AMFConnection.java). I recompile this jar running an ant script from the source and place it in the WEB-INF\lib folder. What is the easiest way to debug this jar?
Conceptually debugging the source that resides in the jar and loaded by the war has nothing special about it. It should be easily done with IDE.
The only requirements are that your IDE will have the corresponding source files configured in the project.
Your project even doesn’t have to contain all the sources – its enough that it will have the relevant sources and you’ll be able to remotely debug your code.
In terms of application server/web server/any container whatsoever it boils down to running an application in the debug mode. Technically you supply some parameters to the JVM and it runs so that enabled connections from your favorite debugger – very flexible actually.
The only thing you should ensure (at least I would take a look on ant script for this 🙂 ) – that you don’t compile your sources with ‘-d’ option.
This option, when given to the java compiler, makes it compile the byte code that doesn’t contain debug information. This way you get the more optimized class but can’t debug it. For example by default the classes coming with JRE (java.lang.. java.util., and so on) are compiled this way.
Hope this helps