- This topic has 1 reply, 1 voice, and was last updated 18 years, 9 months ago by
.
-
Posts
-
I am getting an error when trying to set up debugging of java classes (not jsps). The error is:
Unable to install breakpoint in <class-name> due to missing line number attributes. Modify compiler options to generate line number attributes.After searching the forums, there are many people with similar problems if they are using Ant to build their project, but I am not. I’m just using Eclipse to build the project. The compiler has line numbers checked, and I have unchecked and checked it again to force a rebuild. It will hit the breakpoint at the correct time, but then it throws the error.
Here is what I have done:
1. Create a web project, then create an Enterprise project with the web project as a web module (per instructions in a different forum post)
2. Set a breakpoint in a source file in the web project
3. Use the deployment manager to deploy the EAR to OC4J
4. Start the OC4J server and navigate to a page in the project, which successfully works
5. Fill out the form and submit it, which causes the project to hit the source file with the breakpoint–that’s where the error above is thrownSystem information:
I’m trying to deploy to OC4J 10.1.2
I am using JDK 1.4.1 to run OC4J and Eclipse
I am running Eclipse v3.0.2 and MyEclipse v3.84–It was a fresh install of both–I did have to do the manual install of MyEclipse, but it seemed to work fine. (we’re testing moving away from JDeveloper)
Upgrading to version 4.1 is not an option because that requires JDK 1.4.2, and our production JDK is currently 1.4.1.
I am running XP SP2
I have not installed any other external plug-insPlease let me know if you need further information.
After digging through the forums for some other things, I found that it was necessary to create both my web project and my enterprise app project as J2EE 1.3-compliant, rather than J2EE 1.4 compliant (I didn’t even notice the setting until I saw it on the forums), based on the version of OC4J that I am running. Once I had done this, debugging began to work.
