[Russ]

First of all the article was nicely done. It cover nearly everything I wanted to know about hooking up WAS 6.0 with MyEclipse workbench.

The only thing I can say is the difference I discovered between the final release of WAS and the beta used for this quickstart. There are two additional screens covering the deployment of the application. This is the Binding screen where the application must generate an initial default bindings and the Summary screen for an application’s installation.

Here is another minor thing. The Web context is a little off…… for testing the MyJsp.jsp. It should be “WSTestWeb” instead of “wstest”. This is assuming you used the default settings when one created the Web project entitled “WSTestWeb” like the screen shot shows.

How about replacing the Application Server QuickStart and us WebLogic 8.1?

Again, thank you again for a very nice article. It really ROCKS!

[Riyad Kalla]

First of all the article was nicely done. It cover nearly everything I wanted to know about hooking up WAS 6.0 with MyEclipse workbench.

Thank you, we are glad it helped you.

How about replacing the Application Server QuickStart and us WebLogic 8.1?

You mean instead of the JBoss/Tomcat combo? We probably wouldn’t replace it as most of our users use that combination but we could certainly augment it.

Thanks for the feedback!

[krogerted]

I have followed the steps in the instructions (and yes, I agree that it is excellent documentation) and everything seems to work fine except:
– changes to my web.xml file are not picked up by WebSphere
– new classes are not found by WebSphere

If I change an existing class, then it is picked up by WebSphere. The classes that I have tested this with are servlets. I am using WebSphere 6.1, so I had to make a couple of guesses when following the instructions.

Do you have any suggestions on how to fix this problem? Has the MyEclipse team looked into using JACL scripts to facilitate deploys to WebSphere?

Thanks for your help.
Ted

[Riyad Kalla]

– changes to my web.xml file are not picked up by WebSphere
– new classes are not found by WebSphere

This is actually an issue with WebSphere and how it “installs” applications. The temporary workaround is to create a new “Custom Location” deployment for your project, and specify the actual installedApplications directory to overlay your deployment ontop of the one WebSphere is reading from.

With that being said, for our 6.1 release we are going to focus on making the WebSphere experience much more friendly.

If I change an existing class, then it is picked up by WebSphere. The classes that I have tested this with are servlets. I am using WebSphere 6.1, so I had to make a couple of guesses when following the instructions.

The reason for that working and not the other one, is because MyEclipse hooks itself into the running WebSphere process and using code hot-sync, will actually inject your changed byte-code into the running app server for *existing* classes. But not for few ones.

[Author]

Posts