Comment 1 Esben soeltoft 2013-07-09 05:36:37 EDT

When I try to edit an xml file in the xml editor or schema editor I am unable to use commands such as the delete key (backspace works fine), or keyboard shortcuts in general such as ctrl-c, ctrl-v or use the undo/redo/save actions actions.

When I open the same xml files in the normal eclipse text editor all the shortcuts and keys are working.

Comment 2 Salvador Zalapa 2013-07-09 09:03:03 EDT

What eclipse version are you using?, i am not able to see this wrong behavior using Eclipse Java EE IDE for Web Developers:
Version: Kepler Release
Build id: 20130614-0229

Comment 3 Esben soeltoft 2013-07-09 09:07:43 EDT

I have this same issue on two different installation of eclipse on different computers:

1 computer is running Fedora 18 with Eclipse Juno 4.2.2

2 computer is running Fedora 19 with Eclipse Kepler 4.3.0

Comment 4 Esben soeltoft 2013-07-09 09:10:31 EDT

Also I can add that

1 computer with Juno has WST XML core 3.4.0

2 computer with Kepler has WST XML core 3.5.0

Comment 5 Salvador Zalapa 2013-07-09 09:25:39 EDT

Can you see any error reported in the Error Log view ?

Comment 6 Esben soeltoft 2013-07-09 09:35:19 EDT

Created attachment 233273 [details]
juno eclipse errorlog

Comment 7 Esben soeltoft 2013-07-09 09:36:49 EDT

I saved the complete log for later if it is needed, then Delete the Eclipse log, and restarted eclipse, and then the attached error showed up.

Comment 8 Salvador Zalapa 2013-07-09 10:19:23 EDT

So, seem your are using Eclipse for Parallel Application Developers, instead of Java EE IDE for Web Developers. This might be related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=408606.

Comment 9 Esben soeltoft 2013-07-09 11:12:10 EDT

Created attachment 233279 [details]
eclipse kepler log3

Comment 10 Esben soeltoft 2013-07-09 11:12:41 EDT

Created attachment 233280 [details]
eclipse kepler log4

Comment 11 Esben soeltoft 2013-07-09 11:18:17 EDT

I must admit that my technical insight is insufficient to judge if it is exactly the same problem as the one you are referring.

However, to investigate the issue with the Parrallel Tools Platform, I uninstalled all PTP components on the kepler installation, and reset the errorlog, and removed the .eclipse directory in my home directory.

When I then started Eclipse i got the error in "eclipse kepler log3", and when I opened an xml file for editing the errors from "eclipse kepler log4" ticked in.

Having removed the PTP components, the error still persists in the xml and schema editor. Other editors such as text editor, javascript editor, php editor are working as they should.

Comment 12 Salvador Zalapa 2013-07-09 13:19:35 EDT

By the first log, seems that the PTP stuff was not removed at all, how did you did that? can you add the -clean param to the eclipse.ini to delete the cache data?. With the second logs seems that xalan.jar library is to being located or not started properly.

Comment 13 Esben soeltoft 2013-07-09 14:51:22 EDT

Created attachment 233289 [details]
eclipse kepler log5

Comment 14 Esben soeltoft 2013-07-09 14:51:54 EDT

Created attachment 233290 [details]
eclipse kepler log6

Comment 15 Esben soeltoft 2013-07-09 14:56:42 EDT

I removed the PTP components with yum. I simply asked it to remove all the ptp rpm packages.

I then tried to start eclipse from command line with your added command: eclipse -clean param. The result is in "eclipse kepler log5" It did not seem to remedy the problem.

I then tried to remove both the Workspace and .eclipse dir, and start the eclipse again with. eclipse -clean param. The result is in "eclipse kepler log6".

Still the problem persist.

Comment 16 Nitin Dahyabhai 2013-07-09 15:59:33 EDT

How was the rest of Kepler installed?

Comment 17 Esben soeltoft 2013-07-09 16:01:35 EDT

Kepler was installed with yum. Only yum has been used to install and/or remove Eclipse components.

Comment 18 Nitin Dahyabhai 2013-07-09 16:38:02 EDT

There's not much we can do when the whole thing was installed with yum--we're not involved in the creation of RPMs.  The Fedora packager might have some insight into what happened, but unless it was an EPP package or build zips from download.eclipse.org, there's not really much we can do to clear up the problem (we don't even know *where* it's putting anything).

You can try removing *all* of the Eclipse packages using yum and reinstalling .  It's possible that the Xalan jar is owned by more than one package and was removed incorrectly.  Alternately, you should be able to download a copy from download.eclipse.org, unpack that under your home directory, and just run that.

Comment 19 Esben soeltoft 2013-07-09 16:52:41 EDT

I will try then to speak with the Fedora packager then. 

Thank you for the help so far.

Comment 20 Krzysztof Daniel 2013-07-10 04:30:05 EDT

Assigning for investigation.

Comment 21 Esben soeltoft 2013-07-10 05:04:53 EDT

As suggested I tried to ask some fedora people about this issue, over at #fedora-java on freenode, which has resulted in some additional info, and a Red hat bugzilla report https://bugzilla.redhat.com/show_bug.cgi?id=982975

The problem seems to related to the xPath window of the xml perspective. closing the xPath window and switching out and back into the perspective removes the conflict which was blocking for the editing commands.

Comment 22 Krzysztof Daniel 2013-07-10 10:14:14 EDT

Most probably caused by invalid external dependency in Fedora. Closing as it has nothing to do with Eclipse Foundation.