[binyan]

I have not tried the previous work around yet, I will in a few minutes as I’m tired trying to debug WTF eclipse/ME is doing. I will eetually have to punt on this (assuming the workaround still works) and get back to my day job.

[Riyad Kalla]

Have you ever tried duplicating this problem with Eclipse 2.1.3/MyEclipse 2.7.x? This is the only time we’ve ever run down this problem before (on 2.x or 3.x) and for some reason it keepings happening to you. I’m wondering if there is something going on with your environment (Libraries, etc.) or the version of Eclipse you are using.

Do you have a home machine to try this on?

I will eetually have to punt on this (assuming the workaround still works) and get back to my day job.

Absolutely, we appreciate you long-standing patience with this obviously hair-ripping experience. Without your feedback and help we would be at a loss for words right now as we are unable to reproduce this problem internally. Sometimes more elusive bugs like this require the users help and we appreciate it when they do.

[binyan]

Eclipse bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=28307 and the enclosed linked bugs are beginning to make me think this isn’t an ME issue. I have spent most of today trying to narrow down exactly what causes this. It really doesn’t have to do anything we trying to create an ejb class or a servlet. That’s just the way I encountered it and since I only encountered it that way I thought that was it. Actually all I have to do is create an ejb project and then try and open the “Open Type” dialog, ctrl-shift-t, and select any class/interface that is in a jar in the J2EE 1.3 library contqainer, then presto I ge the dialog. I will note that if I try and create a class or interface then I will ge the popup, but the action will succeed correctly when I hit “Finish”. However if I try and open the “Open Type” dialog then I get the popup and the dialog goes away. I will open an eclipse bug on this.

[Riyad Kalla]

binyan,
Thank you for the detailed rundown of this problem, I will alert the other devs and support team about it so we can recognize it in the future. Also if you could post back here with the link to the bug when its filed, that would be great.

[binyan]

I have entered eclipse bug 58607. It has other detailed info that might be relevant for ME.

[Riyad Kalla]

Thank you.

[binyan]

Please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=58607 for an update on this issue, but it seems as if ME does do incorrect handling of its CLASSPATH variables (atleast for me anyways). On my systems, the ME classpath variables MYECLIPSE_LIB_HOME and MYECLISPE_STRUTS_HOME are defined as absolute paths that start with a preceeding ‘/’ chanracter.

MYECLIPSE_LIB_HOME = /C:/dev/MyEclipse/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_3.7.2/data/libraryset
MYECLIPSE_STRUTS_HOME = /C:/dev/MyEclipse/eclipse/plugins/com.genuitec.eclipse.cross.easystruts.eclipse_3.7.2/data

Now, can anyone verify that the slashes appear on their classpath variables? I can remove the slashes and go to the j2ee 1.3 library set preference and hit apply and then all will be well untill the next restart of eclipse, at which point the slashes return. The struts home is not a problem because AFAICT that variable is never added to a project, instead it is the location of where to copy files from into a project locally.

[Riyad Kalla]

binyan,
I just checked my install and do not have a preceeding slash… to boot, the backslash character is used not the front slash character. SO my paths look like normal Windows paths. This is very odd!

You are on Windows XP correct? Any strange locale?

What happens to your classpath vars if you shutdown Eclipse, move the <eclipse install>\links file for MyEclipse to your desktop (effectively uninstalling MyEclipse) and then restart Eclipse… are the paths still wrong? This may be an Eclipse issue…

[Riyad Kalla]

binyan,
I just received this reply from one of our devs:

I believe this problem is related to the platform or file system of
installation configuration. I’m speculating that when the ME runtime looks
up the ME plugin installation location it is getting back a URL of the form
file:///C: …. When this is converted to a file I suspect that the protocol
may be not fully stripped on Binyan’s platform.

URL basePlatformContextURL = thePlugin.getDescriptor().getInstallURL();
URL platformContextURL =
subDirPath != null ?
new URL(basePlatformContextURL, subDirPath.toString()) :
basePlatformContextURL;
URL osContextURL = Platform.resolve(platformContextURL);

osPath = new Path(osContextURL.getFile());

So my previous questions stand (about OS and Locale) but also what JDK are you running? Is there anything unique or strange about the OS/JDK? Maybe you build the JDK from source? 🙂

[binyan]

@support-rkalla wrote:

binyan,
I just checked my install and do not have a preceeding slash… to boot, the backslash character is used not the front slash character. SO my paths look like normal Windows paths. This is very odd!

You are on Windows XP correct? Any strange locale?

What happens to your classpath vars if you shutdown Eclipse, move the <eclipse install>\links file for MyEclipse to your desktop (effectively uninstalling MyEclipse) and then restart Eclipse… are the paths still wrong? This may be an Eclipse issue…

Believe me, it is indeed odd. I guess I should feel privledged that I have undercovered some obscure bug. Anyhoo, I am on Windows XP, with normal US locale, using sdk java 1.4.2_04 on my work machine and 1.4.2_03 on my personal laptop.

I started looking at what happens without ME this morning and I have the following variable defined in a clean eclipse install (i.e. fresh unzip in a new directory with no ME):

ECLIPSE_HOME = c:\dev\eclipse
JRE_LIB = C:\j2sdk1.4.2_04\jre\lib\rt.jar
JRE_SRC = C:\j2sdk1.4.2_04\src.zip
JRE_SRCROOT = (empty)
JUNIT_HOME = /c:\dev\eclipse\plugins\org.junit_3.8.1\

As you can see JUNIT_HOME has a preceeding slash, but if I create a Java project and add the junit.jar to the project using the JUNIT_HOME variable I have no problem opening the Test.class for example or creating TestCase subclasses.

The fact that a fresh eclipse install has this pushes me back toward eclipse be in the wrong, which in a weird way is good because I have the source for that and I can (hopefully) debug wtf is going on. Why I see this on 2 different systems, has made me wonder whether I have pissed off the gods and I’m not being made an example of. 🙂

P.S.

Forgot to mention that the jdk is the standard Sun sdk.

[Riyad Kalla]

has made me wonder whether I have pissed off the gods and I’m not being made an example of. 🙂

Hah, it sure sounds like it. Keep us posted if you find out what might be going on, we’ll stay tuned on our end and appreciate all the work you are doing to unravel this (our dev was impressed you debugged down into the JDT).

[binyan]

LOL, well if you thought that was something take a look at the latest edition. I had to go deep to get to where the preceeding slash is added, now why that is the case and why it causes no problems for others is a big unknown for me.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=58607

[Author]

Posts