[
https://jira.jboss.org/jira/browse/TEIID-1087?page=com.atlassian.jira.plu...
]
Steve Hawkins resolved TEIID-1087.
----------------------------------
Fix Version/s: 7.0
(was: 7.1)
Resolution: Done
added the xpathQuery function. It has the same signature as xpathValue, but returns all
values as a single XML value. Both functions are now namespace aware as the underlying
implementation was moved off of Saxon. This has two side effects. The first is that * is
no longer valid as a namespace search string (that was a Saxon feature to compensate for
the lack of namespace awareness), e.g. //*:foo - should instead be //prefix:foo or
//[local-name()="foo"]. The latter form was already incorporated by the web
services operation procedure editor for extracting values from the request document, so
this should have limited impact. The other side effect is that if the source document is
using namespaces, then the xpath should as well and a namespace string should provide the
uris for the xpath prefixes - xpathQuery(doc, '//x:foo',
'xmlns:x="http://something.com" xmlns=...'). The format of the
namespace string is the same used in an xml element to declare namespaces.
Add Function to Extract fragments from XML
------------------------------------------
Key: TEIID-1087
URL:
https://jira.jboss.org/jira/browse/TEIID-1087
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.0
We had a posting on the dev site (
http://devcentral.metamatrix.com/node/2089809383)
asking how they can retrieve an entire xml node from an input doc in a web service
transformation instead of just the node text. Our current xPath function xPathValue()
always return the text. We need something more like SQLXML extract()/extractvalue() so we
can return the xml OR the text.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira