[Mike Miller]

I justed installed the new version 3.7.2 on top of my existing Eclipse 3.0 M8 build. Following the instructions at the end of the install, I started MyEclipse but was never prompted to accept new features, possibly because Eclipse was not actively running at the time? I stopped Eclipse for the installation. As a result, I couldn’t ‘Alllow Eclipse to restart…”.

At this point, I looked at the properties of the MyEclipse icon and noticed it was pointing to my existing eclipse but was not using my -data workspace parms. After waiting a bit, I killed the eclipse.exe and started eclipse with my shortcut and MyEclipse appears to be have been installed. The MyEclipse perspective is there, docs are there. I was able to run the getting started tutorial as well.

Found the install log:
Installation: Successful with warnings.

1797 SUCCESSES
1 WARNINGS
0 NONFATAL ERRORS
0 FATAL ERRORS
and the warning was

Create Shortcut: C:\Documents and Settings\mmiller\Start Menu\MyEclipse.lnk Status: WARNING
Additional Notes: WARNING – Shortcut has no target: ignoring

Did I do something wrong during the install? Why are the features/plugin files not installed under my c:\eclipse\features and c:\eclipse\plugins directories? I still see them under c:\MyEclipse?

[Riyad Kalla]

Nope you did everything right, we install MyEclipse into your Eclipse workbench by means of the \links mechanism (C:\eclipse\links). This keeps our plugins clearly separate from your Eclipse plugins so no ‘tainting’ occurs. It also makes updating/installation/uninstallation easier as well. If you look under MyEclipse\plugins and \features, you’ll see that would be QUITE a few plugins to drop into the Eclipse dir to keep track of between updates.

[Mike Miller]

Thanks for the quick response. I saw them under there and worried when they weren’t copied. Good to know about the links.

Product looks great. This is the first one that actually delivered on the ‘native’ jsp debugging. Granted I only did the tutorial but none of the other Jsp editors I’ve tried (Strecl, Lomboz and even the new NitroX from M7) could even do that. I need do some more testing with our existing web applications.

Does the jsp debugging rely on the the project being a Web Project created by MyEclipse or should I be able to debug an existing web app with Jsp pages using my existing sysdeo tomcat launcher and my existing java project?

[Riyad Kalla]

Does the jsp debugging rely on the the project being a Web Project created by MyEclipse or should I be able to debug an existing web app with Jsp pages using my existing sysdeo tomcat launcher and my existing java project?

It may work, although I don’t know that it would hurt to convert it to a web project, give it a try and see. I can’t garuntee that something won’t break along the way though 😉

That is a good question, give it a try and see. Just make sure you are using our JSP Editor to set the breakpoints and such.

[Mike Miller]

Tried my existing project and it didn’t work. If by “convert it to a web project” you meant, right-click on project, then MyEclipse->Add Web Capabilities, that didn’t seem to help either, as a matter of fact, that process seemed to hang. I had to kill Eclipse and restart. Once restarted, I could see a couple new project properties, I adjusted those values and still no luck.

I also tried un-installing Lomboz so there was no potential conflicts. I read some other postings and saw a comment indicating that the JSP debugger works based on some new JSP (cant remember the number). Question: Should my web application context xml document contain an entry for the workDir, or will this potentially confuse MyEclipse? I currently have the workDir defined because that was how Lomboz documented the JSP debugging – you debugged using the generated source not the native jsp page.

[Riyad Kalla]

mikemil,
To get debugging working with MyEclipse you need:
1) To run Eclipse with a 1.4+ JDK
2) To run your App Server with a 1.4+ JDK
3) To run your App Server in debug mode (See the server connector Launch options in MyEclipse > App Server preferences

You don’t need to setup anything fancy with the webapp or context, so changing your context to be a normal context setup may help. Also make sure when you open your JSPs you are using our Editor (right click, Open With, MyEclipse JSP Editor).

If this doesn’t work, please let me know the actions you are taking, what is happening, and what you expected to happen and we will get it working for you.

[Mike Miller]

So do I have to use the app server launcher from ME or can I still use the Sysdeo Tomcat launcher?

[Riyad Kalla]

Yes I believe you do. You don’t have to use your deployment tool, but the app launcher you need to. That allows the remote debugger to hook up to Tomcat.

[Mike Miller]

Ok, I got one of my projects working by creating a Web Module Project, then importing all of the files into the provided directory structure. I deployed and was able to debug one of the jsp pages.

Next, I tried to redeploy the app. This encountered a problem with one of the files and the text of the error msg indicated that there was a “undeployment failure” and that I could manually undeploy the project from tomcat. So manually deleted that project folder from under tomcat/webapps. Now the deployment manager dialog does is not working. Now, neither the Remove nor the Redeploy buttons work. There seems to a quick flash or ‘painting’ but nothing happens. As a result, I can redeploy after the manual deletion of the my web application directory.

[Riyad Kalla]

mikemil,
You need to restart Eclipse, and the bad deployments will autoamtically be removed. If that doesn’t help, please check your log file (and paste here for us to look at) any exceptions:
<eclipse install>\workspace\.metadata\.log

[Mike Miller]

That got it. Thanks!

[Riyad Kalla]

np, glad it worked.

[Author]

Posts