[chaskins]

Hi,

I have setup myeclipse 5.1.0 on eclipse 3.2.0 and have deployed an existing project to a websphere 5.1 server. I setup following the setup instructions for websphere 6.0, as found here. The debugging part works fine, but when I make changes to a jsp or a java file the changes are not reflected in websphere until I do a manual redeployment.
When I check the timestamp on the files I changed under the installed apps dir of the websphere area and I notice that they have not been updated since my initial deployment.

Is hot replacement supported with myeclipse and websphere 5.1? If it is any ideas about what I maybe doing wrong?

Thanks

Chris

[Riyad Kalla]

Chris,
In that document check out Section 10, that is how you will get hot-sync with your files on WebSphere. What you essentially have to do is remove your packaged deployment, and overlay an exploded deployment ontop of it, because MyEclipse only supports hot syncing file chnages with exploded deployments.

When you change the deployments, you will probably want WebSphere shut down so you don’t run into any read-locks causing problems removing the old deployment.

[chaskins]

Hi,

Thanks for the reply.

I had done all that, but I cleared everything down and started again. It still doesn’t work.
When I make a change to a java file I get a dialog popup saying that the target vm doesn’t support hot code replace, and otions to continue, terminate or restart the server.

When I make a change to a jsp nothing happens, and I can not stop at a breakpoint in the jsp either.

Thanks for any help.

Regards,

Chris

[Riyad Kalla]

Chris,
The first problem is a limit of how flexible hot-code replacement in the VM is. You can change the contents of code blocks, but you cannot change the shape of the class (methods, member variables, etc.). The hot-sync will fail in this regard.

As far as reloading JSP pages that have changed, you might want to check the contents of the deployed files. Chances are MyEclipse is actually deploying them, but Websphere isn’t configured to reload changes to your webapp so it’s just ignoring the new JSP pages. You can probably fix this by logging into the administration console and configuring the settings for your app there in Websphere and tell it to reload the changes.

Lastly, I’m sorry I didn’t catch this before, but WebSphere 5.1 doesn’t support the full JSR-45 spec which is required for JSP debugging. That’s why the breakpoints are not getting hit (the source map comming back to MyEclipse isn’t sufficient to map the source lines to the currently executing code lines in the VM). Another user ask about it here:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-7011-view-next.html

[Author]

Posts