[dmitry-a]

Here is what my environment is:
bea weblogic 8.1SP1 (or 3 — tried both, exactly the same behavior)
eclipse 3.0 release
myeclipse 2.8 beta
jdk1.4.2_05 (also tried 1.4.1, 1.4.2_02 — the same results)

When i change some java class while bea is running the application breaks (it does not give me classNotFound, rather a bunch of nullPointerExceptions, looks like it looses the app/session context some how) — i have to restart the server to get it back to working mode and pick resent changes as well.

It looks like the classpath gets screwed up some how. I’m wondering how it works in lomboz. Actually i would get the same behaviour with lomboz unless i turn off “use system classpath” option in lomboz configuration. I would imagine if it works with lomboz it should work with myeclipse — myeclipse is much better j2ee environment (i think). I also searched this forum for the answer, people seem to have a lot of problems with hot-redeploy overall, unfortunately i could not get definate answer if there is solution to this problem or not.

Please help.

[Riyad Kalla]

Dmitry,
Are there any exceptions in your log file? <workspace dir>\.metadata\.log?

Does running WebLogic from the console, then dropping in new class files manually work? If not, then this seems to be a WebLogic issue, not necessarily an ME issue that we can troubleshoot.

[dmitry-a]

there are tons of NullPointerExceptions in the log after the class is changed. This suggests to me that the app thinks that some things were not initialised (perhaps some objects placed in the session, etc…).

Few things i’m noticing and not sure if this is how it supposed to be.

When i create a new deployment configuration for web logic, my application ends up in C:\bea\user_projects\domains\mydomain\applications rather then in in C:\bea\user_projects\domains\mydomain\myserver\applications

As the result web logic does not see the appication untill i explicitly deploy it via bea web console (in addition to creating the deployment configuration in my eclipse), is this how it supposed to be?

Dmitry A>

[Riyad Kalla]

Dmitry,
Some app servers (WebLogic included) don’t allow an initial exploded deployment, so you have to deploy a packaged deployment (like you are doing now) then deploy it with the console, THEN in ME delete the packaged deployment and setup an exploded deployment… that should hook in the hot deployment feature. So basically you are working around WebLogic only wanting a packaged deployment.

Have you tried this?

[dmitry-a]

Actually I was not using the packaged deployment and that what was causing all my problems.

Now since i swtched to the packaged deployment everything works! Yahoo!

Thank you very much.

Dmitry A>

[Riyad Kalla]

Hey great, I’m glad it works now!

[Author]

Posts