From e5799cab0a606f1e493d2c101d786054b1999bef Mon Sep 17 00:00:00 2001 From: Hannes Wellmann Date: Sun, 16 Feb 2025 15:02:12 +0100 Subject: [PATCH] Add info about E4 XPath re-implementation and deprecation Relates to - https://github.com/eclipse-platform/eclipse.platform.ui/issues/423 - https://github.com/eclipse-platform/eclipse.platform.ui/pull/2290 - https://github.com/eclipse-platform/eclipse.platform.ui/pull/2789 --- news/4.35/platform.html | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/news/4.35/platform.html b/news/4.35/platform.html index 198adafea..d0a7554ad 100644 --- a/news/4.35/platform.html +++ b/news/4.35/platform.html @@ -176,6 +176,25 @@

General Updates

+ + + E4 XPath supported reimplemented and revised + +

+ The XPath support of Eclipse E4 (i.e. the Plug-in org.eclipse.e4.emf.xpath) has been reimplemented to be purely based on javax.xml.xpath.XPath provided by the Java standard library. + This enabled the removal of Apache Commons JXPath as a dependency of the Eclipse SDK (and due to joint efforts even of the entire Eclipse Simultaneous Release). +

+

+ Furthermore it has been determined that the XPathContext API provided by the org.eclipse.e4.emf.xpath Plug-in is mostly unused among all Plug-ins of the Eclipse Simultaneous Release. + Therefore the entire org.eclipse.e4.emf.xpath Plug-in and all contained APIs have been marked as deprecated and for removal in a future release. + As a replacement, to query an E4 model using XPath from code, one new method has been added:
+ EModelService.findMatchingElements(MApplicationElement searchRoot, String xPath, Class<T> clazz) +

+ + +