- This topic has 25 replies, 9 voices, and was last updated 13 years, 2 months ago by
.
-
Posts
-
ranaDatra,
Sorry for the delay. I’m able to replicate the problem. It’s not clear what is going on, and it doesn’t appear to be a problem in other versions of MyEclipse (e.g. the standard version) so we’re doing more research. Unfortunately, I don’t have a good workaround for you, at present. One possibility is to, in your operating system, associate .xml files with a text editor and then open the file within MyEclipse by selecting “System Editor” in the context menu.
We’ll report back with more information when we have it.
Sorry for the inconvenience.
Although I was able to replicate the problem once, I couldn’t do so again. It may be a problem with workspace corruption.
Please try starting MyEclipse with the -clean flag. This entry explains how: https://www.genuitec.com/forums/topic/troubleshoot-using-the-clean-command-line-argument/.
If that doesn’t work, try starting with a new workspace, then import the projects from the old workspace.
If neither of these methods work, would it be possible to put together a small project that exhibits this behaviour and attach it in a private message to me? In this way, we may have a better chance of replicating the problem and tracking it down.
hi tony,
I tried the -clean-flag and the new workspace. Doesn’t work either. We currently solved the problem by removing the Hibernate/JPA-Support- and all depending spring-features from myEclipse. Now there’s no problem with editing hbm-files (oh and eclipse is much faster, too^^)
Sorry for our impatience but we needed a working solution. I’ll try to create a project with that problem but same as you we don’t have that issue in every project so that could take a while and there are some deadlines we have to reach.
greetz
ceiphrenHi ceiphren,
Thanks for posting your workaround. That may give us a bit more information to work with.
If you do get the chance to put that small project together sometime, that would be great.
Somebody shoot me. My brand new Intel Core i5 2.5ghz 6GB memory and SSD machine hangs for THREE MINUTES when I even so much as hint at clicking on an hbm.xml. I mean, this is great in one respect, because I can get back in shape by jogging around the block between mouse clicks. Seriously, though, you guys need to fix this. hbm.xml file editing and navigating has been horrendous since I’ve been adopted MyEclipse 6 months ago. Yikes.
sfrancolla,
I’m sorry you’re having this issue and we’d love to fix it for you. Unfortunately, we can’t replicate the problem here reliably (I’ve only seen it once), which makes it difficult to fix. If you can create a workspace with a minimal project that replicates the issue and send it to us, it would be a great help in tracking this down.
Have you been able to use ceiphren’s workaround?
yes this is still true with 9.1 My eclipse for Spring. and It also slows down extremely when you navigate thru a hbm package.
rcolbert,
I’m sorry that you’re seeing this problem. It’s not a problem we can reproduce here. I’ve asked others this but if you could put together a small project that reliably exhibits this problem, in a clean workspace, we might be able to replicate it here.
I don’t think this is really a workaround but I did see the problem once in MyEclipse for Spring. In trying to see if it was a problem in other editions of MyEclipse, I opened the workspace in a standard MyEclipse installation. I didn’t see the problem there and never saw it again in MyEclipse for Spring, even with new projects and new workspaces. So, if you install the standard MyEclipse edition, and open your workspace there, it might just cure the problem. If so, please let us know.
Otherwise, the only workaround is the one posted in an earlier post by ranaDatra.
Meanwhile, we continue to investigate the issue.
I’ve got something interesting:
The problem occures everytime when I do something with the hbm.xml-file (selecting, opening, closing, even closing the package).
I’ve captured the network-trace and voila:
myEclipse tries to validate the hbm-file with the given doctype-url (which is a sourceforge-address) and losses round about 50% of the packages. If I reference to a file on my system the validation seems to run really fast.So I disabled xml-validation for the project: doesn’t work
Then I disabled xml-schema-validation: doesn’t work
Then I disabled dtd-validation: doesn’t work eitherThen I disabled every validator possible (angry programmers are not very logical) : same problem!
So here I gave up. I’m not able to supress the communication between myEclipse and the sourceforge-server. I looked into the received packages and found many filled with dtd-tags from the hibernate-mapping.dtd.
The problem occures in MyEclipse 8.5 and 9 (Spring Edition).
The only workaround I could figure out is to reference the DOCTYPE-tag to a local file.
Again the problems are gone when I remove the hibernate/jpa-support. Looks like that there’s a daemon that hooks itself in every operation I do with an *hbm.xml-file.
The strange thing is that the network-acitivity is nearly the same but now it doesn’t freeze myEclipse.
Oh and the problem appears in every project I create, no matter what type is it.
ranaDatra,
We found one of the sources of delays and would like to see they are the cause of the delays you are experiencing.
The problem we isolated was in MyEclipse for Spring. I have a fix for 9.1 which I will send you privately.
If any other users are experiencing this problem in 9.1 (not 8.x) and would like to try this fix, please let me know.
