[Roman Bórik]

In an early versions of the MyEclipse IDE (may be Eclipse) was possible in Debug mode to evaluate expression (Display – Ctrl+Shift+D) that has contains name of the class that is known in current debug context. But from certain time (I realy do not know from which version) this not working.

E.g. following expression raises error message: MyConstants cannot be resolved to a variable.

request.getParameter(MyConstants.MY_CONSTANT)

If expression contains full qualified name of the class, evaluation works fine:

request.getParameter(eu.mypackage.MyConstants.MY_CONSTANT)

Why this feature is now not able to recognize classes that are in current debug context?
As I was mentioned, in earlier versions of the IDE this feature to work properly.

Can you fix it to work fully and properly?

Actually we use MyEclipse Enterprise Workbench, Version: 2013 SR2, Build id: 11.0.2-20130823

Thanx.

[support-swapna]

RomBor,

Sorry that you are seeing this issue. I could not replicate the issue at my end.
The evaluation works fine for me for the case you mentioned.

If possible please prepare a sample project which exhibits the issue and send it over to help us take a look.

[Roman Bórik]

Thank you for your reply.

It is confusing… If I create simple Java project (2 classes in different packages) evaluating working fine. But in our (very complex) project, evaluating not working properly.

On the following image you can see what happens:

On the second image you can see that class Configuration is correctly imported, thus it should be visible in the current debug context:

It happens no matter if are static variables or static methods referenced from expression together or separately. It hold generally practically for all imported classes.

When I add fully qualified name of the class, evaluation is always successful:

It is possible to switch-on some internal Eclipse logging where I can found e.g. Exception or any info about “evaluating error”? May be this help us to solve this issue.

Thanks

[support-swapna]

RomBor,

Thank you for the screenshots.I could replicate the issue at my end with a slightly bigger project.I have filed it for investigation with the dev team.

I am afraid I cannot suggest any workaround for now.Sorry for the inconvenience caused.

[Roman Bórik]

Thank you for your investigation.

I find out that if I in our project run only some main() method, evaluating works properly.
But if application is started normally through Tomcat server, I get this issue.
Thus I think that problem may be with “connection” between Eclipse and Tomcat.
We tested it with Apache Tomcat 6.0.18 and 7.0.37. Java version is 1.7.0_45

Best regards, Roman

[Author]

Posts