[petem1030]

– System Setup ——————————-
Operating System and version: Windows XP SP2
Eclipse version: 3.2
Eclipse build id: M20060629-1905
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: None
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*:
MyEclipse version: 5
Eclipse JDK version: 1.4.2
Application Server JDK version: 1.4.2
Are there any exceptions in the Eclipse log file? No

If this is a DB related question please answer the following:

RDBMS vendor and version:
JDBC driver vendor and version, and access type (thin, type-2, etc):
Connection URL:
Eclipse error logs related to com.genuitec.eclipse.sqlexplorer packages:

– Message Body ——————————-

I was debugging a Servlet deployed in BEA WebLogic 8. When I would hit a break point and start stepping through the code, I noticed that the code did not match the changes I had made. It appeared that Eclipse was caching the Servlet. I tried removing the deployment, and building cleanly. To no avail. It still was showing the old code as I stepped through it.

[Scott Anderson]

This issue is likely that your changes might have been too extensive to be “hot swapped” into the WebLogic instance. You can find out if that’s the case by making sure the following preference is set to warn you when this happens:
Window > Preferences > Java > Debug > Show error when hot code replace fails
Ensure that this is selected and try deploying and making your changes again.

Also, hot code replacement works best when you run both Eclipse and WebLogic with the same level of JDK (ie. 1.4.2 for both or 1.5 for both but not 1.4.2 for one and 1.5 for the other).

[petem1030]

I was not doing hot swap. I shut down the server, removed the deployment, and then deployed the application. It still was showing the old code in debug mode. I am running the same JDK for both weblogic and eclipse.

[Author]

Posts