Add this URL to your Eclipse Installation to reach this solution's update site.
Enables evaluation of XPath expressions against the active text editor containing XML.
Unsuccessful Installs in the last 7 Days: 1
By adding the following code below to your website you will be able to add an install button for Eclipse XPath evaluation plugin.HTML Code:
Submitted by Fred Ted on Sun, 2015-12-06 13:05
using Eclipse Version: 4.4.2
(note: spaces in URL because URL was rejected as spam)
Bad HTTP Request: https : // raw.github.com/stoupa91/eclipse-xpath-evaluation-plugin/master/eclipse-xpath-evaluation-plugin-update-site/#sthash.U3Qmiawq.dpuf/features/eu.musoft.eclipse.xpath.evaluation.plugin_188.8.131.52511010953.jar
I checked this URL in a browser and it is in fact bad - returns 400 Bad Request
Submitted by Martin Uhlir on Mon, 2015-12-07 21:52
Hi, can you please go in your Eclipse to the Help->Install New Software and click on Available Software Sites and check which URL you have there for the installation of this plugin? In case you have more URLs for this plugin, please remove all of them. Then either install the plugin through the Eclipse marketplace again or add new site by yourself which will point to this URLhttps://raw.githubusercontent.com/stoupa91/eclipse-xpath-evaluation-plugin/master/eclipse-xpath-evaluation-plugin-update-site/
I don't know why the other URL (reported by you) doesn't work anymore, but I've just tried this new URL and I was able to install the plugin successfully. Let me know if you will be able to resolve the issue with this.
Submitted by Martin Uhlir on Sun, 2015-10-25 02:46
For those who have been using previous versions of this plugin, please uninstall it and install it again either through Eclipse Marketplace or use this new update site:
The reason for this is, that the plugin (and its update site) has been moved from Google to Github and it wouldn't get updated to this latest or future releases.
Submitted by Martin Uhlir on Sun, 2015-10-25 02:59
I forgot to mention that starting from this version the support for Java 5 HAS BEEN DROPPED! If you need to run the Eclipse with Java 5, please don't upgrade to this nor future versions, as it might cause problems in the functionality of the plugin.
Submitted by Helko Glathe on Tue, 2015-10-20 05:04
I get always an exception when running the namespace loader.
Here are the details:
An internal error occurred during: "Namespace loader".
XPathFactory#newInstance() failed to create an XPathFactory for the default object model: hattp://java.sun.com/jaxp/xpath/dom with the XPathFactoryConfigurationException: javax.xml.xpath.XPathFactoryConfigurationException: java.util.ServiceConfigurationError: javax.xml.xpath.XPathFactory: bundleresource://853.fwk1407675409/META-INF/services/javax.xml.xpath.XPathFactory:2: Illegal configuration-file syntax
Any hints for solving the problem?
Submitted by Martin Uhlir on Sun, 2015-10-25 02:50
Hi, I have already fixed the issue with the Namespace loader. Please update the plugin to the latest version 1.4.1. Please, see the release note above, as it's necessary to uninstall the plugin first and then install it newly again.
Submitted by Martin Uhlir on Sat, 2015-10-24 03:24
Hi, I believe you are using Java 8, right? It seems the issues is related to this bug https://saxonica.plan.io/issues/1944 in the Saxon library.
As a temporary workaround you can put following line into your eclipse.ini anywhere after the "-vmargs":-Djavax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom=net.sf.saxon.xpath.XPathFactoryImpl
I've just tested that on my system and it works well with the modified eclipse.ini file. I will try to fix the issue soon though, so the workaround won't be needed. I hope, it helps!
Submitted by Eric Cornely on Thu, 2015-10-01 08:48
When a file has a default namespace (xmlns="something") without prefix nothing is selectable.
Even when adding manualy the namespace value association with an empty string.
I have to define a prefix and use that prefix all arround...
Submitted by Martin Uhlir on Sun, 2015-10-25 02:52
Hi, thanks for reporting the issue. It has been fixed. Please, update to the latest version 1.4.1. Please, see the release note above to correctly update to the latest version.
Submitted by Sergey Zolotaryov on Fri, 2014-02-21 07:21
- does not gather namespace info from the file itself, would be very easy to implement; it's quite tedious to fill it in by hand, esp. taking into account that this info is forgotten when you close the xml file
- would be nice to have options to ignore namespaces, etc.
Submitted by Martin Uhlir on Fri, 2014-06-13 13:45
Thanks for suggestion. I've just released new version 1.3.0 which contains a new button to load all the namespaces from the current file, so no need to enter those data manually anymore.
Submitted by Tw Bert on Thu, 2013-08-15 17:23
A list of the returned XPath objects would in some cases be preferable, the raw xml is a lot of clutter if you are looking for all results of a complex query. A simple 'Number of results' in a Text widget would already be a big improvement.
In total: very nice plugin, also without the above request. Great that the namespaces work like they should (a feature that many online XPath evaluators miss or don't implement right).
Drag&Drop from the browser into Indigo also worked fine for me, chiq.
Kind regards, tw
Submitted by Martin Uhlir on Thu, 2013-08-22 05:28
Thanks for suggesting new enhancements. I've just implemented your request for showing "Number of results" of the executed query, so feel free to update to the newest version:-)
Can you, please, let me know more specifically what you mean by "list of returned XPath objects"?
Submitted by Werner Keil on Fri, 2011-11-18 04:44
Looks good, I also installed it via Drag&Drop from the browser successfully into Indigo. Why haven't you converted the Google Code Project into EclipseLabs btw., or started there in the first place?
Submitted by Martin Uhlir on Mon, 2011-11-21 01:24
Thanks. Yeah, I think I should have done that. Well, I'll check the possibilities of moving the project under EclipseLabs.
Back to the top