- This topic has 11 replies, 3 voices, and was last updated 10 years, 3 months ago by
.
-
Posts
-
MyEclipse Enterprise Workbench 2014: Issue with deleting XML
I have issues deleting XML files that I created from the IDE. However, I can delete the files that are pre-existing.Is anyone else facing this issue?
Thanks,
BijuBiju,
We couldn’t replicate the issue at our end.
Can you please answer some queries to help us investigate further :
1) Can you please clarify whether you see any error popup or message after selecting delete ? Please attach the .log file located at <Workspace dir>/.metadata/.log file to help us investigate further.
2) Can you please switch to a new workspace and check whether you can replicate the issue in the new workspace ?
3) Can you please mention in which project(java/web/ejb/etc) you created the xml file ? Also please mention how did you create the XML file ?
4) If possible, can you please attach the xml file which exhibits this issue, to help us replicate the issue at our end ?
5) Can you please attach the MyEclipse installation details from MyEclipse > Installation summary > Installation details ?Pradeep:
All questions are answered as below:
1) Can you please clarify whether you see any error popup or message after selecting delete ? Please attach the .log file located at <Workspace dir>/.metadata/.log file to help us investigate further.
A: Yes, a pop-up shows saying “An exception has been caught while processing the refactoring ‘Delete’. Reason: Problems encountered while deleting resources.
Details:
Problems encountered while deleting resources.
Could not delete ‘C:\WorkSpaceOL9\Onelink9AgencyWebV2.0\trunk\src\main\resources\NewFile.xml’.
Problems encountered while deleting files.
Could not delete: C:\WorkSpaceOL9\Onelink9AgencyWebV2.0\trunk\src\main\resources\NewFile.xml.
Log file is attached.
2) Can you please switch to a new workspace and check whether you can replicate the issue in the new workspace ?
A: No I cannot replicate this on a new workspace.
3) Can you please mention in which project(java/web/ejb/etc) you created the xml file ? Also please mention how did you create the XML file ?
A: Maven-based Web Project.
On src/main/resources folder click New->XML (Basic Templates)
4) If possible, can you please attach the xml file which exhibits this issue, to help us replicate the issue at our end ?
A: the content of the XML file is:<?xml version="1.0" encoding="UTF-8"?> <root> <test/> </root>5) Can you please attach the MyEclipse installation details from MyEclipse > Installation summary > Installation details ?
A: Here are the details:*** Date: Friday, January 3, 2014 9:47:23 AM CST *** System properties: OS=Windows7 OS version=6.1.0 OS arch=amd64 Profile arch=x86_64 Window system=win32 Java version=1.7.0_45 Workspace=file:/C:/WorkSpaceOL9/ VM Args=-Xmx768m -XX:MaxPermSize=320m -XX:ReservedCodeCacheSize=64m -Dosgi.nls.warnings=ignore -jar C:\MYECLI~2\plugins/OR8508~1.JAR *** Subscription information Product Id: E3MP (MyEclipse Professional Subscription) License version: 3.0 Full Maintenance Included Subscription expiration date (YYYYMMDD): 20140923 Number of users: 50 *** Eclipse details: MyEclipse Enterprise Workbench Version: 2014 Build id: 12.0.0-20131202 Blueprint: N/A com.genuitec.eclipse.mobile.feature - 12.0.0.201311260528 com.genuitec.myeclipse.database - 12.0.0.me201311281640 com.genuitec.myeclipse.desktop - 12.0.0.me201311281640 com.genuitec.myeclipse.enterprise.workbench - 12.0.0.me201311281640 com.genuitec.myeclipse.icefaces.feature - 12.0.0.me201311281640 com.genuitec.myeclipse.imageeditor - 12.0.0.me201311281640 com.genuitec.myeclipse.jboss - 12.0.0.me201311281640 com.genuitec.myeclipse.jsf - 12.0.0.me201311281640 com.genuitec.myeclipse.maven - 12.0.0.me201311281640 com.genuitec.myeclipse.persistence - 12.0.0.me201311281640 com.genuitec.myeclipse.tomcat - 12.0.0.me201311281640 com.genuitec.myeclipse.uml2 - 12.0.0.me201311281640 com.genuitec.myeclipse.visualvm - 12.0.0.me201311281640 com.genuitec.myeclipse.visualvm.server - 12.0.0.me201311281640 com.genuitec.myeclipse.ws - 12.0.0.me201311281640 org.eclipse.datatools.connectivity.feature - 1.11.1.me201311281640 org.eclipse.datatools.enablement.feature - 1.11.1.me201311281640 org.eclipse.datatools.modelbase.feature - 1.11.1.v201306041610-7707GCcNBHLDaKTEcRi org.eclipse.datatools.sqldevtools.feature - 1.11.1.me201311281640 org.eclipse.emf - 2.9.1.v20130902-0605 org.eclipse.gef - 3.9.1.201308190730 org.eclipse.graphiti.feature - 0.10.1.v20130918-0838 org.eclipse.jpt.jpa.feature - 3.3.1.me201311281640 org.eclipse.jpt.jpadiagrameditor.feature - 1.2.0.me201311281640 org.eclipse.jst.common.fproj.enablement.jdt - 3.4.0.me201311281640 org.eclipse.jst.enterprise_ui.feature - 3.5.0.me201311281640 org.eclipse.jst.server_adapters.ext.feature - 3.3.103.me201311281640 org.eclipse.jst.server_adapters.feature - 3.2.201.me201311281640 org.eclipse.jst.server_ui.feature - 3.4.1.me201311281640 org.eclipse.jst.ws.axis2tools.feature - 1.1.200.me201311281640 org.eclipse.m2e.feature - 1.4.0.me201311281640 org.eclipse.sapphire.platform - 0.6.6.201310081535 org.eclipse.wst.common.fproj - 3.4.0.me201311281640 org.eclipse.wst.server_adapters.feature - 3.2.300.me201311281640 org.eclipse.xsd - 2.9.1.v20130902-0605 org.springframework.ide.eclipse.feature - 3.3.0.me201311281640 fr.obeo.acceleo.bridge.feature - 2.6.0.me201311281640 org.aspectj - 1.7.3.20130613144500-a org.eclipse.ajdt - 2.2.3.e43x-RELEASE-20130627-0800 org.eclipse.contribution.weaving - 2.2.3.e43x-RELEASE-20130627-0800 org.eclipse.contribution.weaving.source - 2.2.3.e43x-RELEASE-20130627-0800 org.eclipse.contribution.xref - 2.2.3.e43x-RELEASE-20130627-0800 org.eclipse.contribution.xref.source - 2.2.3.e43x-RELEASE-20130627-0800 org.eclipse.cvs - 1.4.0.v20130911-1000 org.eclipse.draw2d - 3.9.1.201308190730 org.eclipse.e4.rcp - 1.2.1.v20130910-2014 org.eclipse.egit - 3.1.0.201310021548-r org.eclipse.epp.mpc - 1.2.1.I20130917-2019 org.eclipse.equinox.p2.core.feature - 1.2.1.v20130827-1605 org.eclipse.equinox.p2.discovery.feature - 1.0.100.v20130502-0334 org.eclipse.equinox.p2.extras.feature - 1.2.0.v20130827-1605 org.eclipse.equinox.p2.rcp.feature - 1.2.0.v20130828-0031 org.eclipse.equinox.p2.user.ui - 2.2.0.v20130828-0031 org.eclipse.equinox.weaving.sdk - 1.0.200.I20130319-1000 org.eclipse.help - 2.0.1.v20130911-1000 org.eclipse.jdt - 3.9.1.v20130911-1000 org.eclipse.jgit - 3.1.0.201310021548-r org.eclipse.jsf.feature - 3.7.0.me201311281640 org.eclipse.mylyn.bugzilla_feature - 3.9.1.v20130917-0100 org.eclipse.mylyn.commons - 3.9.1.v20130917-0100 org.eclipse.mylyn.commons.identity - 1.1.1.v20130917-0100 org.eclipse.mylyn.commons.notifications - 1.1.1.v20130917-0100 org.eclipse.mylyn.commons.repositories - 1.1.1.v20130917-0100 org.eclipse.mylyn.context_feature - 3.9.1.v20130917-0100 org.eclipse.mylyn.cvs - 1.1.1.v20130917-0100 org.eclipse.mylyn.discovery - 3.9.1.v20130917-0100 org.eclipse.mylyn.git - 1.1.1.v20130917-0100 org.eclipse.mylyn.ide_feature - 3.9.1.v20130917-0100 org.eclipse.mylyn.java_feature - 3.9.1.v20130917-0100 org.eclipse.mylyn.monitor - 3.9.1.v20130917-0100 org.eclipse.mylyn.tasks.ide - 3.9.1.v20130917-0100 org.eclipse.mylyn.team_feature - 3.9.1.v20130917-0100 org.eclipse.mylyn.versions - 1.1.1.v20130917-0100 org.eclipse.mylyn_feature - 3.9.1.v20130917-0100 org.eclipse.ocl - 3.1.0.v20110606-1427 org.eclipse.pde - 3.9.1.v20130911-1000 org.eclipse.platform - 4.3.1.v20130911-1000 org.eclipse.rcp - 4.3.1.v20130911-1000 org.sonatype.m2e.mavenarchiver.feature - 0.15.0.201207090125-signed-20130612210623 Eclipse startup command=-data C:\WorkSpaceOL9 -os win32 -ws win32 -arch x86_64 -showsplash -launcher C:\MyEclipse2014\myeclipse.exe -name Myeclipse --launcher.library C:\MyEclipse2014\plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_64_3.2.0.v201103301700\eclipse_3215.dll -startup C:\MyEclipse2014\plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar -exitdata 1c6c_60 -install C:\MyEclipse2014 -vm C:\MyEclipse2014\binary/com.sun.java.jdk7.win32.x86_64_1.7.0.u45/bin/javaw.exebijurk,
Thanks for the details provided.
> Can you please clarify whether you can replicate the issue in other projects too (in the workspace which exhibits this issue) ?
> You mentioned in your earlier response that you couldn’t replicate the issue in the new workspace. So, can you please import your existing project(project that exhibits the issue) into your new workspace and check whether you can replicate the issue, as there might be some workspace problem.
Unfortunately with the number of projects in the workspace and the number of customized variables, it is not easy to move to a new workspace just because a migration was done. It is getting to where I am afraid of doing any upgrades coz’ it almost always screws up the workspace and your only advice is to create new workspace. Pretty irresponsible.
Biju,
I’m sorry you’re seeing these problems continuing.
There may have been some misunderstanding about the use of a new workspace. As you had stated that you don’t see the problem with a new workspace, I guess you have already tried importing an existing project into that new workspace, though this may not have ben clear. The questions relating to a new workspace were to try and determine whether the problem is perhaps with some workspace corruption, or something else.
I understand that moving to a new workspace is inconvenient, with a large number of projects or complex settings, so we’ll try to get to the bottom of the problem. However, our main interest is to get you working as soon as possible, however that is achieved.
Just to be clear on the issue, this is what I understand. You have used a previous release of MyEclipse and have now moved to MyEclipse 2014, opening an existing workspace with the new release (using project migration in 2014, where necessary). Existing XML files in any of the workspace projects can be deleted but any XML file that you create in any of those projects cannot consequently be deleted, with attempts to do so logging the errors you reported. Is that your situation? If not, please state the issue in detail as that can help us home in on a solution.
At first glance, what you’re doing is creating a file in an eclipse project, which creates a file on the file system. The inability to delete a file, using eclipse functionality, would usually indicate that another process is holding on to the file. It’s hard to see how a newly created file could be open in another process but I’m wondering if some process is scanning for newly created files and obtaining a handle to such files which stops them being deleted. Or perhaps some third party eclipse plug-in is becoming involved in the create or delete process, which is causing this issue.
To try to refine the problem further, please try some or all of the following (the results of some may reveal information that will resolve the issue, making subsequent tests redundant):
- Wait a few minutes before trying to delete a newly created XML file
- Create a new XML file, restart MyEclipse and try to delete that file
- Create a new XML file in MyEclipse then try to delete it from a Windows command line, with and without MyEclipse running
- Create a new XML file in another project and try to delete it
[*}Create a new XML file in a different location of the project and try to delete it - Create another type of file, with MyEclipse, and try to delete that one.
- If you have an eclipse installation, try to create and delete a new XML file in an existing project.
Hopefully, the results of these will help us narrow down the problem. Obviously, we’d try these ourselves but as we can’t replicate your problem, it would suggest that the issue lies in your system or MyEclipse set up, in some way.
Please let us know how you get on and sorry again for the inconvenience.
You stated it correctly. That is my issue.
Here are some of the tests:
1. Wait a few minutes before trying to delete a newly created XML file
A. I created an empty XML file using the wizard and did not open it immediately. Then waited for a few minutes and deleted the same successfully. If I create the empty XML file and open it immediately, close it without editing and then I cannot delete the file anymore, even after close and reopen the ME.2.Create a new XML file in MyEclipse then try to delete it from a Windows command line, with and without MyEclipse running
Cannot delete using windows explorer when ME is open.
Able to delete when the ME is closed.3. If you have an eclipse installation, try to create and delete a new XML file in an existing project.
Do not have eclipse installation.I will try out other scenarios based on my availability of time and report here.
bjurk,
Thanks for the information and for going through some scenarios.
This one is interesting:
@bijurk wrote:
A. I created an empty XML file using the wizard and did not open it immediately. Then waited for a few minutes and deleted the same successfully. If I create the empty XML file and open it immediately, close it without editing and then I cannot delete the file anymore, even after close and reopen the ME.
The new XML file wizard actually opens the new file when complete. Are you using the MyEclipse new XML file wizard to create the file? It seems so but I thought I’d check because it appears to be working differently from the way it should, in not opening the new file at the end of the wizard.
When you opened the new file after using the wizard, which editor did you use, the standard MyEclipse XML editor?
For existing XML files (existing before the migration), did you open those with the same editor but are still able to delete them?
You’ve previously reported that you can’t replicate the problem in a new workspace. Have you tried replicating the issue in a new project created in your existing workspace? If you can, then it would seem as though there are some workspace settings that are causing this extremely odd behavior.
If the problems continue, we may need to ask for a zip of the .plugins folder of the .metadata folder in your workspace to see if we can replicate the issue here with that. That folder is likely very large, though several sub-folders can be safely deleted to drastically cut down a zip file. Those folders would be org.eclipse.m2e.core\nexus, org.eclipse.jdt.core, org.springframework… folders, any com.google… folders and any org.eclipse.birt… folders. Hidden files should be included. You can attach the zip file here or send it to tony at genuitec.com.
Sorry about the inconvenience but this is very strange behavior and is difficult to track down.
Q: Are you using the MyEclipse new XML file wizard to create the file?
A: Yes.Q: When you opened the new file after using the wizard, which editor did you use, the standard MyEclipse XML editor?
A: I double-clicked, which should use the default editor (I believe). I have not customized the default behavior.Q: For existing XML files (existing before the migration), did you open those with the same editor but are still able to delete them?
A: Yes, always double-clicking the file.Q: Have you tried replicating the issue in a new project created in your existing workspace?
A: When I tried on a new project on a new workspace, no matter what I try, I can delete the file without any issues.Q:If you can, then it would seem as though there are some workspace settings that are causing this extremely odd behavior.
A: Is there a way I can provide you my workspace setting?Q: If the problems continue, we may need to ask for a zip of the .plugins folder of the .metadata folder in your workspace to see if we can replicate the issue here with that.
A: I have attached the zip file for your scrutiny.Biju
bijurk,
Thanks for the answers and the workspace setting zip file. I’ve tried replicating the problem with those settings but can’t get the delete of a new XML file to fail.
My guess is that, somehow, a process is holding a handle to the new file. The only other common reason for failure to delete a file is a permissions problem but, as you can create files and delete XML files from existing projects, that seems unlikely. Microsoft provide Process Explorer, a utility that can show file handles (amongst other things). It can be downloaded from this page. If you have this utility, you can search for the handle for the file you can’t delete.
One thing I’ve noticed from an earlier post of yours is that you mentioned an error message about a file you tried to delete. The path shown in that error message is “C:\WorkSpaceOL9\Onelink9AgencyWebV2.0\trunk\src\main\resources\NewFile.xml”. It appears as though the project is linked to a version control system (possibly SVN) and has been checked out above the “trunk” folder. However, the settings in the zip file seem to indicate that the “trunk” part of the project folder structure isn’t there. Can you clear up that difference?
If the projects with which you’re experiencing this problem are version controlled, please try deleting the projects and then check them out again. See if they still cause a problem after that.
Sorry for the continued problem; this is proving difficult to analyze. It may turn out that shifting to a new workspace and checking out your projects from there might be the way to eliminate the problem.
Tony:
Yes this project uses SVN and the earlier workspace was checked out at the trunk level. On your recommendation, I created a new project workspace and checked out the project at a lower level. So that definitely has nothing to do with this issue.
For now I have a work-around of deleting the file after closing the ME2014 and deleting it from the Windows Explorer. Let’s wait and see if anyone else reports this in the future.
Thanks,
Biju
